Version 70 (modified by slavazanko, 13 years ago) (diff)


Welcome to the Midnight Commander Development Center

Latest released version: 4.7.1 What's new.

Latest released stable version: What's new in stable release.

Our workflow of releases?


GNU Midnight Commander is a visual file manager, licensed under GNU General Public License and therefore qualifies as Free Software. It's a feature rich full-screen text mode application that allows you to copy, move and delete files and whole directory trees, search for files and run commands in the subshell. Internal viewer and editor are included.

Midnight Commander is based on versatile text interfaces, such as Ncurses or S-Lang, which allows it to work on a regular console, inside an X Window terminal, over SSH connections and all kinds of remote shells.

This site hosts the new home of the Midnight Commander. Due to the recent restructuring of the development team, the main project repository was moved from Savannah to this new Git repository.

Development team (active developers only); contributors.


Source code

A list of the latest releases is available here. If you are interested in helping with the development please also have a look at our Git repository. In order to check out the repository tree use the following commands:

We also have an autosyncing Git mirror at It uses gitweb as the web-interface to Git and can therefore provide some information normally unavailable via Trac Git browser plug-in:

Binary builds

The binaries are normally provided by the distributions, who choose to ship mc along with their packages. We have, however, set up a machine which builds nightly RPM packages from the snapshot of the master Git branch at around 4:30 (GMT+3) for a number of platforms and architectures (EL4, EL5, FC10, FC11, FC12, both x86 and x86_64). Please check out the NightlyBuilds for details.

For stable releases, please check the Binaries page for builds for Ubuntu and various Redhat distributions.


At the moment, unfortunately, Midnight Commander lacks a comprehensive set of documentation covering its common features and various best practices. A project is under way to create such a documentation. Currently we are gathering various bits of information which would be later converted to a more suitable format (DocBook, ...?) in the wiki. Any help would be gladly appreciated.

Please check out the drafts of the documentation project.

Developers mailing lists

mc-devel (at) gnome (dot) org

Mailing list for the development-related discussions:

mc-commits (at) googlegroups (dot) com

Mailing list reserved for the applied commits into master/mc-4.6 branches only (suitable for use as RSS):

mc-bugs (at) googlegroups (dot) com

Mailing list reserved for the ticket and comment notifications only (suitable for use as RSS):

Mailing list for the users

mc (at) gnome (dot) org

Other resources

mc-dev (at)

This is our English-speaking jabber room.


You are interested in mc and would like to improve it? Cool! Feel free to report bugs (please, use search before), attach your patches to the tickets and review the patches, that are already in there. If you are going to do this on a regular basis, we'll ask you if you'd like to join us. However, please search before reporting your issues to reduce the amount of work, needed to close duplicate reports. Please also have a look at our WorkingGuideLines before you actually start messing with the ticket system.

If you are not familiar with git, you might find our GitGuideLines enlightening. It's a short overview of the practical side of our workflow with Git.

For translators

We have account on Transifex project. If you want help us with translations - just sign in (or log in) on the Transifex and do it :).

Learn more about work with Transifex.