#3786: "|" pipe command should use $PATH
-----------------------------+----------------------
Reporter: jidanni | Owner: mutt-dev
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: user interface | Version: 1.5.24
Resolution: | Keywords:
-----------------------------+----------------------
Comment (by dgc):
Readline is not particularly relevant; mutt doesn't use it. I believe that
readline doesn't interact especially well with a full-screen curses
application, so it's not an option. We would lose the ability to bind
arbitrary mutt events to keystrokes in the editor, too.
Readline does perform filename completion out of the box, but in a very
basic way that, for a host application like mutt, would perhaps best be
called "stupid." It's the default completion for readline, but you don't
always want filenames popping up just anywhere in the editor bar.
So it's up to mutt to decide where/when and how to complete things. We
have completions for certain cases -- variable names, config directives,
mailboxes, a few others. Completing filenames seems like a nice option,
but the critical question is: when is a filename completion appropriate?
The answer turns out to be "rarely." There are not very many instances in
the editor (broadly) where what you really want is a filename completion.
There are cases where we indeed do have filename completion: for example,
while saving a message or attachment. So it's not that there is no
filename completion, but that it's not active when the OP wants it.
So please outline your use case, and maybe it can be enabled there too.
But we won't simply make tabs complete filenames any time you press it,
because when you're typing in the editor bar you're almost never trying to
type a filename.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3786#comment:7>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
