On 20Sep2015 21:36, Ian Zimmerman <i...@buug.org> wrote:
Mutt asks me this after any pipe-message command. I can see how it is
necessary for commands that produce output; otherwise I wouldn't get a
chance to see the output. But what about commands that produce nothing
on stdout? Some non-interactive commands may save their output in a
file, so their stdout is empty. And then there are commands with an
interactive UI loop of their own, like lynx. For both of these types
the extra prompt to close the output is useless and annoying. Can I get
rid of it?
I have:
set wait_key=no
In principle you can write macros to turn this on (or off) around specific
actions.
The price for the above, absent special macros, is that I need to pipe commands
through less if I care to review their output.
Cheers,
Cameron Simpson <c...@zip.com.au>
