Midnight Commander

Midnight Commander is an orthodox (two-pane) file manager, supporting standard file operations, virtual filesystems, panelizing of external commands, and user menus. It also includes an internal viewer, editor, and visual diff tool.

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

Installation

Install the mc package, or mc-git^AUR for the development version.

Skins

Midnight Commander comes with multiple skins by default. You can set the skin in Options > Appearance.

Additional third-party skins can be installed separately:

mc-solarized-git — Solarized color scheme for Midnight Commander

https://github.com/nkulikov/mc-solarized-skin || mc-solarized-git^AUR

mc-skin-modarin-debian — Thin versions of the modarin theme

https://launchpad.net/debian/+source/mc/3:4.8.13-3 || mc-skin-modarin-debian^AUR

Usage

The below section provides a short overview on usage of Midnight commander.

Interface

In prominent view are two vertical panes. Either can list directory contents, show a plain text preview, file details, or a directory tree (see ). File operations are accessible through the function keys or the mouse. More options are visible in a dynamic user menu () and option menu (). Keys above (F13 up to F20) are accessible through . Menu and dialog options have one letter highlighted - pressing this letter (or inside a text entry) directly activates the respective option.

Below, a command line is visible, connected to a subshell. This shell is generally of the same type mc was launched from, and may be switched to at will (), see . On this command line, cd is interpreted by Midnight Commander, and not passed to the shell for execution. As such, special completion (such as from Zsh) is unavailable. Files in the pane interact with the command line; for example, copies the name of a (selected) file to the command line.

Keybindings are generally similar to GNU Emacs. A more strict emacs keymap can be enabled (see ). New users may however use Lynx-like (arrow) keybindings (enabled in Options > Panel options) and mouse clicks for navigation.

Mouse support for Linux virtual consoles can be enabled with General purpose mouse.

Modules

These can be called via the mc interface (with Use internal enabled in Options > Configuration), or separately as symbolic links to the mc binary.

mcedit - Text and binary file editor, with regex replace, syntax highlighting, macros and shell piping, see
mcview - Text and hex viewer with goto marks and regex search
mcdiff - Compares and edits two files in-place ( d)

Per instance, multiple modules can be run concurrently and you can switch between them using (see mc(1) § Screen selector). External editors may be used instead, and parameters configured accordingly.

Configuration

Most of the Midnight Commander settings can be changed from the menus. However, a small number of settings such as clipboard commands, codeset detection and parameters for external editors can only be changed from . See and following for a complete description of options.

Additionally, the following environment variables are respected: , , , , MC_DATADIR, , KEYBOARD_KEY_TIMEOUT_US, , , .

extfs

extfs allows to easily create new virtual filesystems for mc. See for details.

Tips and tricks

Start from the menu

Midnight commander can be run from a menu with the correct Desktop entry. For example:

[Desktop Entry]
Type=Application
Version=1.0
Name=Midnight Commander
Comment=Visual file manager
Exec=mc
Icon=folder
MimeType=inode/directory
Terminal=true
Categories=Utility;

Trash support

Midnight Commander does not support a trash can by default.

Using libtrash

Install the package, and create an mc alias in the initialization file of your shell (e.g., or ~/.zshrc):

alias mc='LD_PRELOAD=/usr/lib/libtrash.so mc'

To apply the changes, reopen your shell session or the shell initialization file.

Default settings are defined in ; the default trash directory is . You can overwrite these settings per-user in , for example:

TRASH_CAN = .Trash
INTERCEPT_RENAME = NO
IGNORE_EXTENSIONS= o;exe;com
UNCOVER_DIRS=/dev

Now files deleted by Midnight Commander (launched with mc) will be moved to the directory.

Warning:

Applications launched from mc inherit LD_PRELOAD, which may cause problems with some applications.
With GLOBAL_PROTECTION = YES set (default), files deleted outside the home directory are moved to the trash, even if they are on a different partition. Depending on the file, this may cause a significant delay.

Troubleshooting

Exit to the current directory

On exit, the shell returns to the directory Midnight Commander was started from, instead of the last active directory. A wrapper script is included, which can be used by adding this line to your or ~/.zshrc:

alias mc=". /usr/lib/mc/mc-wrapper.sh"

This will alias to the wrapper script.

For the fish shell use this wrapper: http://mc-wrapper.fish. Place it to or execute the content inside shell and than run

funcsave mc

Another simple workaround is to use the subshell (). This may however interfere with other terminal applications.

Garbled screen

Press to redraw the display. This only redraws, but does not refresh (Ctrl+r) the file list.

Opening files

mc reads the environment variable to open files, which defaults to xdg-open when unset.

if mc is blocked until the resulting process ends, or the process exits together with mc, use :

and set accordingly:

$ export MC_XDG_OPEN=~/bin/nohup-open

Find file shows no results

If the Find file dialog (accessible with , or , or the MC menu) shows no results, check the current directory for symbolic links. Find file does not follow symbolic links, so use bind mounts (see mount(8)) instead, or the External panelize command.

Broken shortcuts

With certain terminal definitions such as or , shortcuts such as may not work or act as different combinations. To remedy this, assign the terminal sequences manually with the dialog.

Settings will be stored in the file, for example for :

Note: The following example assumes F13–F20 are bound to Shift+F3–Shift+F10.

No bold text in urxvt

If started under urxvt with the default setting, text that is usually bold in many other terminals will not appear so. The root of the issue is because xterm couples bright text color with the bold attribute (thus, bright colors will always appear as bold in xterm).

urxvt does not have this limitation, which Slang (the library mc uses for text display by default) honors. Because Slang can decouple the bold attribute from bright colors on urxvt, mc would need to explicitly specify the bold attribute as appropriate (which it does not).

The solution is to configure mc to explicitly use bold colors as desired, e.g. by editing the default skin as follows:

$ mkdir ~/.local/share/mc/skins 
$ cp /usr/share/mc/skins/default.ini ~/.local/share/mc/skins/
$ sed -i -E 's/^(.* = (gray|brightred|brightgreen|yellow|brightblue|brightmagenta|brightcyan|white);.*)$/\0;bold/' ~/.local/share/mc/skins/default.ini

The above will create a copy of the default skin, but with all bright colors having an explicit bold attribute added.

Another common workaround is to set , however this causes other issues due to mismatching termcap/terminfo, such as certain keys not working.

gollark: What? That makes no sense.

gollark: The algorithms don't *entirely* match the Haskell version, but they're very close, and it produces mostly the same output apart from this weirdness.

gollark: It's not really a Rust problem as much as a my-code-implemented-in-Rust problem, but basically the fractal generator program randomly introduces blotches of various sizes of really different colors to the rest, which the Haskell thing it is based on does not do, and I have no idea why.

gollark: Well, you wrote DDGBot, no?

gollark: <@!330678593904443393> You use Rust a bit, please help.