clifm alternatives and similar packages
Based on the "System" category.
Alternatively, view clifm alternatives based on common mentions on social networks and blogs.
9.5 5.8 clifm VS hapistranoDeploy tool for Haskell applications, like Capistrano for Rails
9.5 0.0 clifm VS ghc-hotswapExample code for how we swap compiled code within a running Haskell process.
9.5 3.3 clifm VS nix-deployDeploy software or an entire NixOS system configuration to another NixOS system
9.1 5.0 clifm VS typed-processAlternative API for processes, featuring more type safety
8.8 0.0 clifm VS system-fileioContains the system-filepath and system-fileio packages
8.4 0.0 clifm VS openssh-github-keysControl SSH access to your servers via GitHub teams
8.3 3.8 clifm VS directory-contentsRecursively build a tree of directory contents, avoiding symlink cycles
Do you think we are missing an alternative of clifm or a related project?
Command Line Interface File Manager
Clifm is a small file manager written in Haskell with a terminal-based interface. It allows you to explore directories in multiple Panes/Tabs and perform basic operations.
Note: Directory navigation will do no harm, but double-check before starting operations on your file system. I take no responsibility for what you do with this software.
Note: You may need to install
ncurseson your system before using clifm
For ArchLinux the binary from the latest github release should work. For other Linux distro the binary may work as well, or you can build from source.
$ cabal install clifm
or install from the cloned repository:
$ git clone https://github.com/pasqu4le/clifm.git $ cd clifm $ cabal install
If your terminal supports a mouse you can use it to change Tab/Pane, click a button on the bottom, change your selection or open it (double-click), but using the keyboard you can perform every possible action. This is the list of all the keybindings:
- L: open Se*l*ection menu
- A: open T*a*b menu
- P: open Pane menu
- BackSpace: go back to main menu
- Esc/Q: Quit
- Enter: Open directory/run executable file/open readable file in editor
- Ctrl+(X/C): Cut/Copy the selected Item
- Up/Down Arrow: move the selection in the current Tab
- PageUp/PageDown: move the selection in the current Tab by one page at a time
- Home/End: move the selection in the current Tab to beginning or end of list
- Ctrl+R: Rename the selected Item
- Ctrl+D: Delete the selected Item
- Ctrl+O: Open the selected directory in a New Tab
- S: Show info about the selected Item
- Tab/BackTab: Move to the next/previous tab
- Ctrl+(Left/Right Arrow): Swap current tab's position with the previous/next one
- Ctrl+V: Paste in the current Tab's directory
- Ctrl+S: Search for a file/folder in the current Tab's directory
- K: Kill (close) the current Tab
- M: Make a new directory
- T: Touch (create an empty) file
- G: Go to another directory
- E: Open Empty Tab
- R: Refresh the current Tab
- O: Order by file name/file size/access time/modification time
- I: Invert order
- Left/Right Arrow: Focus on the previous/next Pane
- Ctrl+E: Open Empty Pane
- Ctrl+K: Kill (close) the current Pane
The actions above will not work only if a prompt is up, or you try to do something not possible.
Command line arguments
You can have a list of command line arguments by running
If you specify nothing
clifm will open the current directory, but you can select another directory using
-d, for example:
clifm -d "/home".
If the directory path is not valid
clifm will open on an empty tab.
clifm will look for an editor in your environment variables:
$EDITOR (in this order).
If both cannot be found it will try to use
You can select an editor with the option
-e, for example:
clifm -e nano
You can load a theme from a file using
-t, for example:
clifm -t "theme/phosphor.ini". If the file does not exists or cannot be loaded
clifm will use the default theme.
You can use one of the existing themes in the
- paper.ini (inverted blackAndWhite)
- phosphor.ini (like old monochrome monitors)
- ocean.ini (very blue)
You can also write and use your own themes: copy the
themes/template.ini file, fill in the attributes you want to change and delete those you like as default.
Complete explanation from Brick.Themes:
The file format is as follows:
Customization files are INI-style files with two sections, both optional: "default" and "other".
The "default" section specifies three optional fields:
- "default.fg" - a color specification
- "default.bg" - a color specification
- "default.style" - a style specification
A color specification can be any of the strings black, red, green, yellow, blue, magenta, cyan, white, brightBlack, brightRed, brightGreen, brightYellow, brightBlue, brightMagenta, brightCyan, brightWhite, or default.
A style specification can be either one of the following values (without quotes) or a comma-delimited list of one or more of the following values (e.g. "[bold,underline]") indicating that all of the specified styles be used. Valid styles are standout, underline, reverseVideo, blink, dim, and bold.
The other section specifies for each attribute name in the theme the same fg, bg, and style settings as for the default attribute. Furthermore, if an attribute name has multiple components, the fields in the INI file should use periods as delimiters. For example, if a theme has an attribute name ("foo" <> "bar"), then the file may specify three fields:
- foo.bar.fg - a color specification
- foo.bar.bg - a color specification
- foo.bar.style - a style specification
Any color or style specifications omitted from the file mean that those attribute or style settings will use the theme's default value instead.
Attribute names with multiple components (e.g. attr1 <> attr2) can be referenced in customization files by separating the names with a dot. For example, the attribute name "list" <> "selected" can be referenced by using the string "list.selected".
Threads for directory size computation
Directory size is calculated by visiting a directory tree to sum it's files sizes (using conduit) and it may take a while. For this reason these will be calculated in different threads.
You can limit how many of these threads to have at the same time by using
-n, for example:
clifm -n 8.
You are likely to have the best results with as many threads as your processor's cores. The default limit is set to 4.
Right now nothing is planned.
Suggestions and requests are always welcome, if you have any or you find a bug please open a new issue.
Special thanks to @batarian71 for the logo.