How to Install and Uninstall vifm.x86_64 Package on CentOS 8 / RHEL 8

Last updated: November 26,2024

1. Install "vifm.x86_64" package

Here is a brief guide to show you how to install vifm.x86_64 on CentOS 8 / RHEL 8


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                vifm.x86_64
            
                    
    
    Copied

2. Uninstall "vifm.x86_64" package

Learn how to uninstall vifm.x86_64 on CentOS 8 / RHEL 8:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                vifm.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the vifm.x86_64 package on CentOS 8 / RHEL 8

Last metadata expiration check: 1 day, 8:58:08 ago on Sun May 9 13:03:46 2021.
Available Packages
Name : vifm
Version : 0.10.1
Release : 3.el8
Architecture : x86_64
Size : 700 k
Source : vifm-0.10.1-3.el8.src.rpm
Repository : epel
Summary : File manager with curses interface, which provides Vi[m]-like environment
URL : http://vifm.info/
License : GPLv2+
Description : Vifm is a curses based vi[m] like file manager extended with some useful ideas
: from mutt. If you use vi[m], vifm gives you complete keyboard control over your
: files without having to learn a new set of commands. It goes not just about
: vi[m] like keybindings, but also about modes, options, registers, commands and
: other things you might already like in vi[m].
:
: Just like vi[m], vifm tries to adhere to the Unix philosophy. So instead of
: working solutions which are set in stone user is provided with a set of means
: for customization of vifm to one's likings. Though builtin functionality should
: be enough for most of use cases.