It will not break scripts or commands that depend on
less since shell aliases would not be expanded for scripts or other commands.
Shell aliases are only there for convenience in your interactive shell session. They are not carried over into shell scripts and commands that you start from that shell session because aliases are not part of the environment that is inherited by child processes.
The only issue would be if you yourself forgot that you had this alias and then proceeded to use it with extra options in an interactive shell session. These options would then be given to
You may also consider using
view rather than
Regarding "enormous files", these are files that are of sizes larger than your RAM, or at least of the same size a sizeable chunk of the available RAM. Traditionally, editors would load the whole file into memory as you opened them, and some still do this. Opening large files would therefore
- be slow
- potentially run the editor into a resource restriction (out of memory)
I believe that the Vim editor is working around this using its "swap files" (the ones that you may have seen with the
.swp filename suffix). See
:help swap-file in Vim.
less pager will, by default, keep all read data in memory when reading from a pipe. If more data is read than there is available RAM for, you will have issues. Fortunately, there is a
--auto-buffers) option that forces
less to only keep the last portion of the read data in memory. However, this obviously makes it impossible to jump back to previously viewed lines of input.
more pager is sometimes
less in disguise (just a hard link to the
less binary). On systems where
more is actual
more, the pager does not allow scrolling backwards when viewing data read from pipes.
more needs to read a file completely to be able to view the contents of it. Both would seek through the file to the appropriate location.