Updated Home (markdown)

Mischievous Meerkat 2020-02-03 08:33:31 +05:30
parent 866a919b67
commit 2537c304d3

@ -154,20 +154,19 @@ so you can easily handle files together (**even at the `nnn` command prompt!**):
## List files
`nnn` can start in a mode where it displays a list of files you give it as input. You can give it either relative or absolute path, but they must be separated by `\0` (NULL byte). The input doesn't need to be terminated by NULL. `nnn` will only accept up to 65,536 paths and will read no more than 256 MiB of input.
`nnn` can receive a list of files as input. The paths should be NUL-separated (`\0`) but doesn't need to be NUL-terminated. Paths and can be relative to the current directory or absolute. `nnn` can handle up to 65,536 paths and will read up to 256 MiB of input.
You start `nnn` in this mode by writing to its standard input.
You can give it the output of another command, for example listing files in current directory larger than 1M:
Start `nnn` in this mode by writing to its standard input. So the output of another command can be piped to it. For example, to list files in current directory larger than 1M:
find -maxdepth 1 -size +1M -print0 | nnn
or you can give it a preexisting list from a file:
or you can redirect a list from a file:
nnn < files.txt
A temporary directory will be created containing symlinks to the given paths. Any action performed on these symlinks will be performed _only_ on their targets, after which they might become invalid.
Even though the term "files" was used, anything can be given as long as it's a valid path. Invalid paths will be ignored.
Though the term "files" is used, any input is valid as long as it's a valid path. Invalid paths will be ignored.
## Prompts