Difference between revisions of "Main Page"
(→Features: Add new ones)
(→Overview: Update short description)
|Line 1:||Line 1:|
== Overview ==
== Overview ==
'''Vifm''' is [https://en.wikipedia.org/wiki/] [https://en.wikipedia.org/wiki/]like , some useful ideas from [https://en.wikipedia.org/wiki/Mutt_(email_client) mutt].
If you, vifm gives you complete keyboard control over your files without having to learn a new set of commands.
=== Features ===
=== Features ===
Revision as of 15:41, 22 January 2018
Vifm is a file manager with curses interface, which provides Vim-like environment for managing objects within file systems, extended with some useful ideas from mutt. If you're used to Vi[m], vifm gives you complete keyboard control over your files without having to learn a new set of commands.
To make it easier to understand use cases and to connect features to their configuration and controls some details are provided in spoilers.
- cross-platform (GNU/Linux, *BSD, Solaris, Windows, Mac OS)
- user mappings (almost like in vi) ...
Input model is very Vi[m]-alike. Each mode has set of commands for managing mappings (see :map, :noremap and :unmap) associated with it. One-argument or no-argument form of mapping commands can be used to list existing keys.
Ambiguity leads to timeouts (see 'timeoutlen' option) as with builtin commands.
Mappings can include angle bracket notation to designate various special keys (e.g. Ctrl+X).
Note that mapped sequence can span across mode boundaries.
- ranges for command-line commands ...
Ranges provide a way to specify range of files to be processed.
Employing ranges can change that to renaming all files with
:%substitute/pat/subst or grepping only file under the cursor with
Since ranges are not always handy to type manually, normal mode contains ! command, which generates range, for example, hitting !G yields :.,$.
- user defined commands (support ranges)
- registers ...
Registers serve as additional buffers, which allow sorting files into several groups for later processing.
Some registers are managed implicitly and provide additional convenience, others need to be named explicitly on calling commands (e.g. "xdd deletes file(s) to
x register). Some registers are available by two names: lower case and upper case one; using first form reassigns register content, while the second one appends to it.
:registers command yields menu that displays files in the registers.
Content of registers can be saved across sessions.
- directory tree comparison
- operation undoing/redoing ...
Foreground file operations can be reversed and replayed again if their nature allows it. For example, deletion (not moving to trash) or file overwrite can't be reversed, on the other hand any rename operations can be reversed unless previous file names conflict with names of newly created files. Irreversible operations require explicit confirmation of some form.
Undo is u, redo is Ctrl-R.
Undo list is not saved across sessions.
- FUSE file systems support
- multiple files renaming (also known as "bulk renaming" or "batch renaming")
- color schemes, which can also be applied to specific sub-trees ...
- colorization of files according to their type and/or name
- vi-like marks and named bookmarks (tags)
- operation backgrounding
- customizable file viewers
- handy less-like preview mode with support of colors
- (interactive) filtering out and searching with match highligh for files using regular expressions
- one or two pane view (vertical or horizontal) ...
Single pane view is enabled by Ctrl-W+o or :only command.
Vertical split is activated by Ctrl-W+v or :vsplit command.
Horizontal split can be activated by Ctrl-W+s or :split command.
Any of the above commands can be placed into configuration file to setup initial view layout after startup.
- shell-like command-line editing
- table/ls/tree-like views
- customizable file name prefixes and suffixes
- built-in integration with GNU Screen and tmux
- external editing of command line
- multi-block selection
- remembering position in previously visited directories
- remote command execution
- command-line abbreviations
- ability to script configuration for specific directories
- trash ...
Apart from being storage for files which are about to be erased this is also a place for files that were "cut" (which corresponds to "delete" operation in Vi[m]), but not pasted yet.
Trash is enabled by default ('trash' option) and it is better to leave it in this state. 'trashdir' can used to customize location of trash directories, which are media-specific by default and are named
List of files in trashes is available on :lstrash command. :trashes lists trash directories themselves, optionally along with their sizes. Inside trash directory :restore command restores file to the place where it used to be, it's also possible to just move files by other means, which will automatically demangle their names.
:empty command is there to clean trashes in background.
Registers are connected with trashes, which allows managing several groups of files at the same time.
- UTF-8 aware
- Contributing. Advices for those who would like to contribute bug report or feature request.
- Contributing to This Wiki. A place to map out and plan the topics found in the wiki.
- Development. Some information about development process.
- FAQ. Answers to frequently asked questions.
- Glossary. Explanation of abbreviations or ambiguous words.
- HOWTOs. Tutorials on various subjects.
- Manual. Main tutorial.
- Obtaining Vifm. Details about obtaining Vifm in different environments.
- Tips and Tricks. Description of some possibly unexpected/non-obvious uses of features.
- Utility scripts. Scripts that help utilize external applications.
- Vifm on the Web. List of pages related to Vifm.