Mostly, I will not use | less
for each and every command from the shell.
Pipe to less is used only when I actually run the command without is and find out that it does not fit on the page. That costs me two runs of the same shell command.
Is there a way so that every time a command result is more than a display page, it automatically gets piped to less?
In general, automatically piping to
less
requires the shell to be prescient about the output that will be produced by the commands it runs - and it is hard enough for humans to predict that without trying to make programs do so.You could write a shell that does it for you - that captures the output (but what about stderr?) and paginates if necessary, but it would most certainly not be a standard shell.
Pipe it to
less -F
aka--quit-if-one-screen
:The most significant problem with trying to do that is how to get it to turn off when running programs that need a tty.
What I would recommend is that, for programs and utilities you frequently use, create shell functions that wrap them and pipe to
less -F
. In some cases, you can name the function the same as the program and it will take precedence, but can be overridden.Here is an example wrapper function which would need testing and perhaps some additional code to handle edge cases, etc.
If you use the same name as I have in the example, it could break things that expect different behavior. To override the function to run the underlying program directly precede it with
command
:will run
foo
without using the function of the same name.I wrote this wrapper function and put it in my .profile. You can use this before a command and it will automatically pipe it to less if it is longer than 1 page.
So 'lcmd ls' would ls the current directory and pipe that output to less.
You could always pipe to less -E (this will cause less to automatically quit at the end of the file). For commands with short output it would do what you want. I don't think you can automatically pipe to less when there is a lot of output.