.\" Code generated by gen/man.sh DO NOT EDIT. .TH LF 1 .SH NAME lf \- terminal file manager .SH SYNOPSIS .SY lf .OP \-cpuprofile path .OP \-doc .OP \-last-dir-path path .OP \-memprofile path .OP \-remote command .OP \-selection-path path .OP \-server .OP \-version .RI [ directory ] .YS .SH DESCRIPTION lf is a terminal file manager. .PP Source code can be found in the repository at https://github.com/gokcehan/lf. .PP This documentation can either be read from terminal using 'lf -doc' or online at https://godoc.org/github.com/gokcehan/lf. You can also use 'doc' command (default '') inside lf to view the documentation in a pager. .PP You can run 'lf -help' to see descriptions of command line options. .SH REFERENCE The following commands are provided by lf with default keybindings: .PP .EX up (default 'k' and '') half-up (default '') page-up (default '' and '') down (default 'j' and '') half-down (default '') page-down (default '' and '') updir (default 'h' and '') open (default 'l' and '') quit (default 'q') top (default 'gg' and '') bottom (default 'G' and '') toggle (default '') invert (default 'v') unselect (default 'u') copy (default 'y') cut (default 'd') paste (default 'p') clear (default 'c') redraw (default '') reload (default '') read (default ':') shell (default '$') shell-pipe (default '%') shell-wait (default '!') shell-async (default '&') find (default 'f') find-back (default 'F') find-next (default ';') find-prev (default ',') search (default '/') search-back (default '?') search-next (default 'n') search-prev (default 'N') mark-save (default 'm') mark-load (default "'") mark-remove (default `"`) .EE .PP The following commands are provided by lf without default keybindings: .PP .EX draw draw the ui load load modified files and directories sync synchronize copied/cut files with server echo print arguments to the message line echomsg same as echo but logging echoerr same as echomsg but red color cd change working directory to the argument select change current file selection to the argument glob-select select files that match the given glob glob-unselect unselect files that match the given glob source read the configuration file in the argument push simulate key pushes given in the argument delete remove the current file or selected file(s) .EE .PP The following command line commands are provided by lf with default keybindings: .PP .EX cmd-escape (default '') cmd-complete (default '') cmd-enter (default '' and '') cmd-history-next (default '') cmd-history-prev (default '') cmd-delete (default '' and '') cmd-delete-back (default '' and '') cmd-left (default '' and '') cmd-right (default '' and '') cmd-home (default '' and '') cmd-end (default '' and '') cmd-delete-home (default '') cmd-delete-end (default '') cmd-delete-unix-word (default '') cmd-yank (default '') cmd-transpose (default '') cmd-interrupt (default '') cmd-word (default '') cmd-word-back (default '') cmd-capitalize-word (default '') cmd-delete-word (default '') cmd-uppercase-word (default '') cmd-lowercase-word (default '') cmd-transpose-word (default '') .EE .PP The following options can be used to customize the behavior of lf: .PP .EX anchorfind boolean (default on) color256 boolean (default off) dircounts boolean (default off) dirfirst boolean (default on) drawbox boolean (default off) globsearch boolean (default off) icons boolean (default off) hidden boolean (default off) ignorecase boolean (default on) ignoredia boolean (default off) incsearch boolean (default off) preview boolean (default on) reverse boolean (default off) smartcase boolean (default on) smartdia boolean (default off) wrapscan boolean (default on) wrapscroll boolean (default off) number boolean (default off) relativenumber boolean (default off) findlen integer (default 1) (zero to prompt until single match) period integer (default 0) (zero to disable periodic loading) scrolloff integer (default 0) tabstop integer (default 8) errorfmt string (default "\e033[7;31;47m%s\e033[0m") filesep string (default "\en") ifs string (default ”) (not exported if empty) previewer string (default ”) (not filtered if empty) promptfmt string (default "\e033[32;1m%u@%h\e033[0m:\e033[34;1m%w/\e033[0m\e033[1m%f\e033[0m") shell string (default 'sh') sortby string (default 'natural') timefmt string (default 'Mon Jan _2 15:04:05 2006') ratios string (default '1:2:3') info string (default ”) shellopts string (default ”) .EE .PP The following variables are exported for shell commands: .PP .EX $f current file $fs selected file(s) separated with 'filesep' $fx current file or selected file(s) if any $id id number of the client .EE .PP The following variables are set to the corresponding values: .PP .EX $LF_LEVEL current nesting level .EE .PP The following default values are set to the environmental variables on unix when they are not set or empty: .PP .EX $OPENER open # macos $OPENER xdg-open # others $EDITOR vi $PAGER less $SHELL sh .EE .PP The following default values are set to the environmental variables on windows when they are not set or empty: .PP .EX %OPENER% start %EDITOR% notepad %PAGER% more %SHELL% cmd .EE .PP The following additional keybindings are provided by default: .PP .EX map zh set hidden! map zr set reverse! map zn set info map zs set info size map zt set info time map za set info size:time map sn :set sortby natural; set info map ss :set sortby size; set info size map st :set sortby time; set info time map gh cd ~ .EE .PP The following keybindings to applications are provided by default: .PP .EX map e $$EDITOR $f map i $$PAGER $f map w $$SHELL .EE .SH CONFIGURATION Configuration files should be located at: .PP .EX os system-wide user-specific unix /etc/lf/lfrc ~/.config/lf/lfrc windows C:\eProgramData\elf\elfrc C:\eUsers\e\eAppData\eLocal\elf\elfrc .EE .PP Marks file should be located at: .PP .EX unix ~/.local/share/lf/marks windows C:\eUsers\e\eAppData\eLocal\elf\emarks .EE .PP History file should be located at: .PP .EX unix ~/.local/share/lf/history windows C:\eUsers\e\eAppData\eLocal\elf\ehistory .EE .PP You can configure the default values of following variables to change these locations: .PP .EX $XDG_CONFIG_HOME ~/.config $XDG_DATA_HOME ~/.local/share %ProgramData% C:\eProgramData %LOCALAPPDATA% C:\eUsers\e\eAppData\eLocal .EE .PP A sample configuration file can be found at https://github.com/gokcehan/lf/blob/master/etc/lfrc.example. .SH PREFIXES The following command prefixes are used by lf: .PP .EX : read (default) builtin/custom command $ shell shell command % shell-pipe shell command running with the ui ! shell-wait shell command waiting for key press & shell-async shell command running asynchronously .EE .PP The same evaluator is used for the command line and the configuration file for read and shell commands. The difference is that prefixes are not necessary in the command line. Instead, different modes are provided to read corresponding commands. These modes are mapped to the prefix keys above by default. .SH SYNTAX Characters from '#' to newline are comments and ignored: .PP .EX # comments start with '#' .EE .PP There are three special commands ('set', 'map', and 'cmd') and their variants for configuration. .PP Command 'set' is used to set an option which can be boolean, integer, or string: .PP .EX set hidden # boolean on set nohidden # boolean off set hidden! # boolean toggle set scrolloff 10 # integer value set sortby time # string value w/o quotes set sortby 'time' # string value with single quotes (whitespaces) set sortby "time" # string value with double quotes (backslash escapes) .EE .PP Command 'map' is used to bind a key to a command which can be builtin command, custom command, or shell command: .PP .EX map gh cd ~ # builtin command map D trash # custom command map i $less $f # shell command map U !du -sh # waiting shell command .EE .PP Command 'cmap' is used to bind a key to a command line command which can only be one of the builtin commands: .PP .EX cmap cmd-escape .EE .PP You can delete an existing binding by leaving the expression empty: .PP .EX map gh # deletes 'gh' mapping cmap # deletes '' mapping .EE .PP Command 'cmd' is used to define a custom command: .PP .EX cmd usage $du -h -d1 | less .EE .PP You can delete an existing command by leaving the expression empty: .PP .EX cmd trash # deletes 'trash' command .EE .PP If there is no prefix then ':' is assumed: .PP .EX map zt set info time .EE .PP An explicit ':' can be provided to group statements until a newline which is especially useful for 'map' and 'cmd' commands: .PP .EX map st :set sortby time; set info time .EE .PP If you need multiline you can wrap statements in '{{' and '}}' after the proper prefix. .PP .EX map st :{{ set sortby time set info time }} .EE .SH KEY MAPPINGS Regular keys are assigned to a command with the usual syntax: .PP .EX map a down .EE .PP Keys combined with the shift key simply use the uppercase letter: .PP .EX map A down .EE .PP Special keys are written in between '<' and '>' characters and always use lowercase letters: .PP .EX map down .EE .PP Angle brackets can be assigned with their special names: .PP .EX map down map down .EE .PP Function keys are prefixed with 'f' character: .PP .EX map down .EE .PP Keys combined with the control key are prefixed with 'c' character: .PP .EX map down .EE .PP Keys combined with the alt key are assigned in two different ways depending on the behavior of your terminal. Older terminals (e.g. xterm) may set the 8th bit of a character when the alt key is pressed. On these terminals, you can use the corresponding byte for the mapping: .PP .EX map á down .EE .PP Newer terminals (e.g. gnome-terminal) may prefix the key with an escape key when the alt key is pressed. lf uses the escape delaying mechanism to recognize alt keys in these terminals (delay is 100ms). On these terminals, keys combined with the alt key are prefixed with 'a' character: .PP .EX map down .EE .PP Please note that, some key combinations are not possible due to the way terminals work (e.g. control and h combination sends a backspace key instead). The easiest way to find the name of a key combination is to press the key while lf is running and read the name of the key from the unknown mapping error. .SH PUSH MAPPINGS The usual way to map a key sequence is to assign it to a named or unnamed command. While this provides a clean way to remap builtin keys as well as other commands, it can be limiting at times. For this reason 'push' command is provided by lf. This command is used to simulate key pushes given as its arguments. You can 'map' a key to a 'push' command with an argument to create various keybindings. .PP This is mainly useful for two purposes. First, it can be used to map a command with a command count: .PP .EX map push 10j .EE .PP Second, it can be used to avoid typing the name when a command takes arguments: .PP .EX map r push :rename .EE .PP One thing to be careful is that since 'push' command works with keys instead of commands it is possible to accidentally create recursive bindings: .PP .EX map j push 2j .EE .PP These types of bindings create a deadlock when executed. .SH SHELL COMMANDS Regular shell commands are the most basic command type that is useful for many purposes. For example, we can write a shell command to move selected file(s) to trash. A first attempt to write such a command may look like this: .PP .EX cmd trash ${{ mkdir -p ~/.trash if [ -z "$fs" ]; then mv "$f" ~/.trash else IFS="`printf '\en\et'`"; mv $fs ~/.trash fi }} .EE .PP We check '$fs' to see if there are any selected files. Otherwise we just delete the current file. Since this is such a common pattern, a separate '$fx' variable is provided. We can use this variable to get rid of the conditional: .PP .EX cmd trash ${{ mkdir -p ~/.trash IFS="`printf '\en\et'`"; mv $fx ~/.trash }} .EE .PP The trash directory is checked each time the command is executed. We can move it outside of the command so it would only run once at startup: .PP .EX ${{ mkdir -p ~/.trash }} .EE .PP .EX cmd trash ${{ IFS="`printf '\en\et'`"; mv $fx ~/.trash }} .EE .PP Since these are one liners, we can drop '{{' and '}}': .PP .EX $mkdir -p ~/.trash .EE .PP .EX cmd trash $IFS="`printf '\en\et'`"; mv $fx ~/.trash .EE .PP Finally note that we set 'IFS' variable manually in these commands. Instead we could use the 'ifs' option to set it for all shell commands (i.e. 'set ifs "\en"'). This can be especially useful for interactive use (e.g. '$rm $f' or '$rm $fs' would simply work). This option is not set by default as it can behave unexpectedly for new users. However, use of this option is highly recommended and it is assumed in the rest of the documentation. .SH PIPING SHELL COMMANDS Regular shell commands have some limitations in some cases. When an output or error message is given and the command exits afterwards, the ui is immediately resumed and there is no way to see the message without dropping to shell again. Also, even when there is no output or error, the ui still needs to be paused while the command is running. This can cause flickering on the screen for short commands and similar distractions for longer commands. .PP Instead of pausing the ui, piping shell commands connects stdin, stdout, and stderr of the command to the statline in the bottom of the ui. This can be useful for programs following the unix philosophy to give no output in the success case, and brief error messages or prompts in other cases. .PP For example, following rename command prompts for overwrite in the statline if there is an existing file with the given name: .PP .EX cmd rename %mv -i $f $1 .EE .PP You can also output error messages in the command and it will show up in the statline. For example, an alternative rename command may look like this: .PP .EX cmd rename %[ -e $1 ] && printf "file exists" || mv $f $1 .EE .PP One thing to be careful is that although input is still line buffered, output and error are byte buffered and verbose commands will be very slow to display. .SH WAITING SHELL COMMANDS Waiting shell commands are similar to regular shell commands except that they wait for a key press when the command is finished. These can be useful to see the output of a program before the ui is resumed. Waiting shell commands are more appropriate than piping shell commands when the command is verbose and the output is best displayed as multiline. .SH ASYNCHRONOUS SHELL COMMANDS Asynchronous shell commands are used to start a command in the background and then resume operation without waiting for the command to finish. Stdin, stdout, and stderr of the command is neither connected to the terminal nor to the ui. .SH REMOTE COMMANDS One of the more advanced features in lf is remote commands. All clients connect to a server on startup. It is possible to send commands to all or any of the connected clients over the common server. This is used internally to notify file selection changes to other clients. .PP To use this feature, you need to use a client which supports communicating with a UNIX-domain socket. OpenBSD implementation of netcat (nc) is one such example. You can use it to send a command to the socket file: .PP .EX echo 'send echo hello world' | nc -U /tmp/lf.${USER}.sock .EE .PP Since such a client may not be available everywhere, lf comes bundled with a command line flag to be used as such. When using lf, you do not need to specify the address of the socket file. This is the recommended way of using remote commands since it is shorter and immune to socket file address changes: .PP .EX lf -remote 'send echo hello world' .EE .PP In this command 'send' is used to send the rest of the string as a command to all connected clients. You can optionally give it an id number to send a command to a single client: .PP .EX lf -remote 'send 1000 echo hello world' .EE .PP All clients have a unique id number but you may not be aware of the id number when you are writing a command. For this purpose, an '$id' variable is exported to the environment for shell commands. You can use it to send a remote command from a client to the server which in return sends a command back to itself. So now you can display a message in the current client by calling the following in a shell command: .PP .EX lf -remote "send $id echo hello world" .EE .PP Since lf does not have control flow syntax, remote commands are used for such needs. For example, you can configure the number of columns in the ui with respect to the terminal width as follows: .PP .EX cmd recol %{{ w=$(tput cols) if [ $w -le 80 ]; then lf -remote "send $id set ratios 1:2" elif [ $w -le 160 ]; then lf -remote "send $id set ratios 1:2:3" else lf -remote "send $id set ratios 1:2:3:5" fi }} .EE .PP Besides 'send' command, there are also two commands to get or set the current file selection. Two possible modes 'copy' and 'move' specify whether selected files are to be copied or moved. File names are separated by newline character. Setting the file selection is done with 'save' command: .PP .EX lf -remote "$(printf 'save\encopy\enfoo.txt\enbar.txt\enbaz.txt\en')" .EE .PP Getting the file selection is similarly done with 'load' command: .PP .EX load=$(lf -remote 'load') mode=$(echo "$load" | sed -n '1p') list=$(echo "$load" | sed '1d') if [ $mode = 'copy' ]; then # do something with $list elif [ $mode = 'move' ]; then # do something else with $list fi .EE .PP There is a 'quit' command to close client connections and quit the server: .PP .EX lf -remote 'quit' .EE .PP Lastly, there is a 'conn' command to connect the server as a client. This should not be needed for users. .SH FILE OPERATIONS lf uses its own builtin copy and move operations by default. These are implemented as asynchronous operations and progress is shown in the bottom ruler. These commands do not overwrite existing files or directories with the same name. Instead, a suffix that is compatible with '--backup=numbered' option in GNU cp is added to the new files or directories. Only file modes are preserved and all other attributes are ignored including ownership, timestamps, context, links, and xattr. Special files such as character and block devices, named pipes, and sockets are skipped and links are followed. Moving is performed using the rename operation of the underlying OS. This can fail to move files between different partitions when it needs to copy files. For these cases, users are expected to explicitly copy files and then delete the old ones manually. Operation errors are shown in the message line as well as the log file and they do not preemptively finish the corresponding file operation. .PP File operations can be performed on the current selected file or alternatively on multiple files by selecting them first. When you 'copy' a file, lf doesn't actually copy the file on the disk, but only records its name to memory. The actual file copying takes place when you 'paste'. Similarly 'paste' after a 'cut' operation moves the file. .PP You can customize copy and move operations by defining a 'paste' command. This is a special command that is called when it is defined instead of the builtin implementation. You can use the following example as a starting point: .PP .EX cmd paste %{{ load=$(lf -remote 'load') mode=$(echo "$load" | sed -n '1p') list=$(echo "$load" | sed '1d') if [ $mode = 'copy' ]; then cp -R $list . elif [ $mode = 'move' ]; then mv $list . fi lf -remote 'send load' lf -remote 'send clear' }} .EE .PP Some useful things to be considered are to use the backup ('--backup') and/or preserve attributes ('-a') options with 'cp' and 'mv' commands if they support it (i.e. GNU implementation), change the command type to asynchronous, or use 'rsync' command with progress bar option for copying and feed the progress to the client periodically with remote 'echo' calls. .PP By default, lf does not assign 'delete' command to a key to protect new users. You can customize file deletion by defining a 'delete' command. You can also assign a key to this command if you like. An example command to move selected files to a trash folder and remove files completely after a prompt are provided in the example configuration file. .SH SEARCHING FILES There are two mechanisms implemented in lf to search a file in the current directory. Searching is the traditional method to move the selection to a file matching a given pattern. Finding is an alternative way to search for a pattern possibly using fewer keystrokes. .PP Searching mechanism is implemented with commands 'search' (default '/'), 'search-back' (default '?'), 'search-next' (default 'n'), and 'search-prev' (default 'N'). You can enable 'globsearch' option to match with a glob pattern. Globbing supports '*' to match any sequence, '?' to match any character, and '[...]' or '[^...] to match character sets or ranges. You can enable 'incsearch' option to jump to the current match at each keystroke while typing. In this mode, you can either use 'cmd-enter' to accept the search or use 'cmd-escape' to cancel the search. Alternatively, you can also map some other commands with 'cmap' to accept the search and execute the command immediately afterwards. Possible candidates are 'up', 'down' and their variants, 'updir', and 'open' commands. For example, you can use arrow keys to finish the search with the following mappings: .PP .EX cmap up cmap down cmap updir cmap open .EE .PP Finding mechanism is implemented with commands 'find' (default 'f'), 'find-back' (default 'F'), 'find-next' (default ';'), 'find-prev' (default ','). You can disable 'anchorfind' option to match a pattern at an arbitrary position in the filename instead of the beginning. You can set the number of keys to match using 'findlen' option. If you set this value to zero, then the the keys are read until there is only a single match. Default values of these two options are set to jump to the first file with the given initial. .PP Some options effect both searching and finding. You can disable 'wrapscan' option to prevent searches to wrap around at the end of the file list. You can disable 'ignorecase' option to match cases in the pattern and the filename. This option is already automatically overridden if the pattern contains upper case characters. You can disable 'smartcase' option to disable this behavior. Two similar options 'ignoredia' and 'smartdia' are provided to control matching diacritics in latin letters. .SH OPENING FILES You can define a an 'open' command (default 'l' and '') to configure file opening. This command is only called when the current file is not a directory, otherwise the directory is entered instead. You can define it just as you would define any other command: .PP .EX cmd open $vi $fx .EE .PP It is possible to use different command types: .PP .EX cmd open &xdg-open $f .EE .PP You may want to use either file extensions or mime types from 'file' command: .PP .EX cmd open ${{ case $(file --mime-type $f -b) in text/*) vi $fx;; *) for f in $fx; do xdg-open $f > /dev/null 2> /dev/null & done;; esac }} .EE .PP Following command is provided by default: .PP .EX cmd open &$OPENER $f .EE .PP You may also use any other existing file openers as you like. Possible options are 'libfile-mimeinfo-perl' (executable name is 'mimeopen'), 'rifle' (ranger's default file opener), or 'mimeo' to name a few. .SH PREVIEWING FILES lf previews files on the preview pane by printing the file until the end or the preview pane is filled. This output can be enhanced by providing a custom preview script for filtering. This can be used to highlight source codes, list contents of archive files or view pdf or image files as text to name few. For coloring lf recognizes ansi escape codes. .PP In order to use this feature you need to set the value of 'previewer' option to the path of an executable file. lf passes the current file name as the first argument and the height of the preview pane as the second argument when running this file. Output of the execution is printed in the preview pane. You may want to use the same script in your pager mapping as well if any: .PP .EX set previewer ~/.config/lf/pv.sh map i $~/.config/lf/pv.sh $f | less -R .EE .PP Since this script is called for each file selection change it needs to be as efficient as possible and this responsibility is left to the user. You may use file extensions to determine the type of file more efficiently compared to obtaining mime types from 'file' command. Extensions can then be used to match cleanly within a conditional: .PP .EX #!/bin/sh .EE .PP .EX case "$1" in *.tar*) tar tf "$1";; *.zip) unzip -l "$1";; *.rar) unrar l "$1";; *.7z) 7z l "$1";; *.pdf) pdftotext "$1" -;; *) highlight -O ansi "$1" || cat "$1";; esac .EE .PP Another important consideration for efficiency is the use of programs with short startup times for preview. For this reason, 'highlight' is recommended over 'pygmentize' for syntax highlighting. Besides, it is also important that the application is processing the file on the fly rather than first reading it to the memory and then do the processing afterwards. This is especially relevant for big files. lf automatically closes the previewer script output pipe with a SIGPIPE when enough lines are read. When everything else fails, you can make use of the height argument to only feed the first portion of the file to a program for preview. .SH COLORSCHEMES lf tries to automatically adapt its colors to the environment. On startup, first '$LS_COLORS' environment variable is checked. This variable is used by GNU ls to configure its colors based on file types and extensions. The value of this variable is often set by GNU dircolors in a shell configuration file. dircolors program itself can be configured with a configuration file. dircolors supports 256 colors along with common attributes such as bold and underline. .PP If '$LS_COLORS' variable is not set, '$LSCOLORS' variable is checked instead. This variable is used by ls programs on unix systems such as Mac and BSDs. This variable has a simple syntax and supports 8 colors and bold attribute. .PP If both of these environment variables are not set, then lf fallbacks to its default colorscheme. Default lf colors are taken from GNU dircolors defaults. These defaults use 8 basic colors and bold attribute. .PP You should also note that lf uses 8 color mode by default which uses sgr 3-bit color escapes (e.g. '\e033[34m'). If you want to use 256 colors, you need to enable 'color256' option which then makes lf use sgr 8-bit color escapes (e.g. '\e033[38;5;4m'). This option is intended to eliminate differences between default colors used by ls and lf since terminals may render 3-bit and 8-bit escapes differently even for the same color. .PP Keeping this mechanism in mind, you can configure lf colors in two different ways. First, you can configure 8 basic colors used by your terminal and lf should pick up those colors automatically. Depending on your terminal, you should be able to select your colors from a 24-bit palette. This is the recommended approach as colors used by other programs will also match each other. .PP Second, you can set the values of environmental variables mentioned above for fine grained customization. This is useful to change colors used for different file types and extensions. '$LS_COLORS' is more powerful than '$LSCOLORS' and it can be used even when GNU programs are not installed on the system. You can combine this second method with the first method for best results. .PP Lastly, you may also want to configure the colors of the prompt line to match the rest of the colors. Colors of the prompt line can be configured using the 'promptfmt' option which can include hardcoded colors as ansi escapes. See the default value of this option to have an idea about how to color this line.