Open-source project
vifm/vifm avatar
vifm/vifm

Vifm: the README documents version 0.15 while the newest tag is v0.14.4

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.

3,288 stars150 forksCGPL-2.0

At a glance

What is it?
A curses file manager that borrows Vim's keybindings, modes, options, registers and commands, and adds ideas from mutt, distributed under GPL 2 or later. The installation table gives fourteen native package commands and no Windows row, and the two AppImage snippets offered as a convenience do not select the same file.
Who is it for?
Vifm is a serious tool for people who already live in Vim and want the same muscle memory over files, and it rewards reading its cheatsheet before configuring anything. Three checks are worth doing first.
Can I use it commercially?
Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 5 days ago.
What is it written in?
Mainly C, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • vifm/vifm3,288 ★ · +15
Star history
Repository2026-09-242026-11-15
vifm/vifm3.3k3.3k

15 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The README says version 0.15 and the newest release is v0.14.4

One line near the top of the file settles the version question and then contradicts the release history. It reads, in italics, that this is version 0.15 and that the file was last updated on 17 June 2026.

The tags tell a different story. The newest release is v0.14.4, dated 2026-05-31. Before that came v0.14.3 from 2025-06-04 and v0.14.2 from 2025-05-07, so one patch line sat for a year and the next moved in a month.

So the README is describing the development line rather than a shipped release, which is normal practice and easy to misread. The last push on the default branch is dated 2026-10-01, well after the date the file claims for itself, so even the update stamp is behind the code it describes.

Fourteen install commands, two rows with a second option, and no Windows

The installation table is the most immediately useful thing in the file. It gives one native command per platform: apk add vifm for Alpine, pacman -S vifm for Arch and derivatives, apt install vifm for Debian and derivatives including Ubuntu, emerge vifm for Gentoo, guix package -i vifm for Guix, zypper install vifm for OpenSUSE, sbopkg -i vifm for Slackware, and pkg_add vifm for both NetBSD and OpenBSD.

Two rows carry a second command. Fedora gets dnf install vifm or yum install vifm, and macOS gets brew install vifm or port install vifm. FreeBSD gets pkg install vifm and Linuxbrew gets brew install vifm, which means the same package manager name appears against two different systems.

The Nix row uses nix-env -i vifm rather than a profile command. And there is no Windows row at all, in a file that otherwise covers fourteen systems, while Windows searches are common for this program.

The two AppImage snippets do not pick the same file

For a distribution that does not package Vifm, or that ships an outdated version, an AppImage is offered so nobody has to compile from sources. Two variants are given, and they differ in how they choose the download.

The first builds the asset name itself, taking the tag from the GitHub API and appending an architecture suffix:

bash
curl -Lso ~/.local/bin/vifm \
    "https://github.com/vifm/vifm/releases/latest/download/vifm-v$(
        curl -Ls "https://api.github.com/repos/vifm/vifm/releases/latest" |
        sed -nE '/"tag_name":/s/.*"v*([^"]+)".*/\1/p'
    )-x86_64.AppImage" && chmod +x ~/.local/bin/vifm

The second asks the API for assets and takes anything whose name ends in .AppImage, with no architecture filter:

bash
wget -qO ~/.local/bin/vifm "$(
        wget -qO - "https://api.github.com/repos/vifm/vifm/releases/latest" |
        jq -r '.assets[] | select(.name|endswith(".AppImage")) | .browser_download_url'
    )" && chmod +x ~/.local/bin/vifm

Both save to the same path and mark it executable. Both also require a FUSE-capable kernel on a system younger than 10 years.

The AppImage route cannot reach vifm-pause before v0.15

One limitation is stated plainly, and it is the kind that only shows up later. Helpers such as vifm-pause, which is what the :!! command uses, are not accessible in an AppImage before v0.15.

That is a specific capability gap rather than a vague caveat. If your workflow leans on shell escapes from inside the file manager, the convenience install will not behave like a packaged one until the version the README is describing ships.

The snippets are credited to a contributor, with a reference to issue 975 on the project's tracker, which is where the reason for the change would be explained.

The gap is also why the two install routes are not interchangeable for everyone. A distribution package pulls in whatever the packager built for your version, helpers included, while the AppImage is a single self-contained binary assembled from the release assets. Anything that lives outside the main binary, such as a helper invoked by a command, is exactly what differs between the two.

Three separate tools handle image preview, and none of them is in this tree

Image preview is not built in. Three external repositories are listed instead, and the choice between them is decided by what your terminal can do.

The first is vifmimg, which displays images through Überzug. The second is a sixel preview tool for terminals that support Sixel, with a link to a page answering whether a given terminal does. The third is thu.sh, which works with either Sixel or Kitty. Each lives in its own repository under separate maintainers.

That is three dependencies to evaluate for one feature, and none of them is versioned against a Vifm release in anything visible here.

Around them sit smaller extras of the same shape: a Vim plugin, a maintained colorscheme repository with a separate preview page, and two devicon or favicon setups. The sample configuration and a suggested fragment of a bashrc are also hosted elsewhere, in a dotfiles repository.

The configuration file is reached with :edit $MYVIFMRC

The suggested way in is to skim the cheatsheet for the main mode, which the file names as Normal mode, read the basic usage sections on the wiki, and then look at a sample configuration. The command given for that last step is :edit $MYVIFMRC, so the path to your own settings is held in an environment variable rather than typed out.

The design commitment is stated next to it. Vifm tries to follow the Unix philosophy, and rather than handing over finished solutions set in stone it gives you a set of means to customize, with the claim that the built-in functionality is enough for most uses.

Two posts are recommended for getting used to the Vim-like nature, Seven habits of effective text editing by Bram Moolenaar and Your problem with Vim is that you don't grok vi by Jim Dennis.

Autotools in the tree, build badges pointing at AppVeyor and vifm.info

The build is GNU Autotools and the generated script is committed: configure.ac, aclocal.m4, Makefile.am and Makefile.in, build-aux/, and a configure file sitting in the tree next to them.

Documentation is kept in the repository in the older style, as separate top-level files rather than one document. There is AUTHORS, BUGS, FAQ, HACKING.md, INSTALL, NEWS, THANKS and TODO, plus two licence files, COPYING and COPYING.3party for third-party code. A CHANGELOG sits next to a second one named ChangeLog.LuaAPI, which is the only place a scripting interface is named anywhere in the tree.

The badges at the top of the README point at AppVeyor and at a ci.vifm.info host, and no .github directory appears among the top-level entries, so the continuous integration for this project is not running from the repository it builds.

The licence is stated in one line as the GNU General Public License, version 2 or later, which is a slightly wider grant than a plain version 2 designation, and the third-party file next to COPYING is where bundled code with its own terms would be accounted for. Both README and README.md sit in the root, so the file rendered on the repository page and the one tracked in the tree are not necessarily the same document.

Editorial conclusion

Vifm is a serious tool for people who already live in Vim and want the same muscle memory over files, and it rewards reading its cheatsheet before configuring anything. Three checks are worth doing first. Work out which version you are actually getting, because the README describes 0.15 while the newest tag is v0.14.4 and the two AppImage snippets are not interchangeable, one of them filtering for x86_64 and the other taking any AppImage asset it finds. Note that the AppImage route drops helpers such as vifm-pause before 0.15. And decide where your configuration lives, since the sample vifmrc and the suggested bashrc fragment both live in an external dotfiles repository rather than in this one.

Frequently asked questions

What is vifm used for?

It is a curses based Vim-like file manager extended with some useful ideas from mutt. The file says that if you use Vim, Vifm gives you complete keyboard control over your files without learning a new set of commands, and that this covers keybindings, modes, options, registers and commands.

How do I install vifm on Debian or Ubuntu?

The installation table gives apt install vifm for Debian and derivatives such as Ubuntu. Other rows cover apk add vifm for Alpine, pacman -S vifm for Arch, dnf install vifm or yum install vifm for Fedora, pkg install vifm for FreeBSD and emerge vifm for Gentoo.

Does vifm run on Windows?

The installation table in the README has no Windows row. It covers Alpine, Arch, Debian, Fedora, FreeBSD, Gentoo, Guix, Linuxbrew, NetBSD, Nix, OpenBSD, OpenSUSE, Slackware and macOS, and offers an AppImage for Linux distributions that do not package Vifm or ship an outdated version.

How do I install vifm from an AppImage?

Two snippets are given: one combining curl with sed and one combining wget with jq, each querying the GitHub API for the latest release, saving the file as ~/.local/bin/vifm and marking it executable. It requires a FUSE-capable kernel on a system younger than 10 years.

What are the different Vim modes?

The repository does not enumerate Vim's modes. It says Vifm mirrors Vim in modes, options, registers and commands, points at a cheatsheet for its own Normal mode, and recommends two articles on text editing, one by Bram Moolenaar and one by Jim Dennis.

Official sources

  1. License: GPL-2.0
  2. Project website
  3. README
  4. Releases
  5. vifm/vifm on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/vifm-vifm.svg)](https://hysenlabs.com/projects/vifm-vifm)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/vifm-vifm.svg)](https://hysenlabs.com/projects/vifm-vifm)

Was this useful?