> The history will only save mutt commands and not anything you do in your
> shell
I don't think that's what he's saying. Some programs (like PostgreSQL's psql
tool) remember their history across invocations. The request (and i think
it's a great one) is for mutt to do the same.
--
Mike Schira
Will --
...and then Will Yardley said...
%
% is there any way to have the line editor keep some sort of history /
% cache? (the editor you use when typing addresses, executing shell
% commands or what not)?
Hmmm... Yeah, if we're talking about the same thing; just hit the colon
and then hit y
is there any way to have the line editor keep some sort of history /
cache? (the editor you use when typing addresses, executing shell
commands or what not)?
i know most people probably never leave mutt or just open subshells, but
i do occasionally exit mutt, and it would be really cool if you c
* R. Leponce ([EMAIL PROTECTED]) [010808 09:49]:
> Hello all,
>
> just a simple question: I always have my $EDITOR variable set to vim, so I
> wanted to try the builtin editor of Mutt. I unset this variable (and
> also $VISUAL), and evenis vi is not mentionned in my .muttr
Hello all,
just a simple question: I always have my $EDITOR variable set to vim, so I
wanted to try the builtin editor of Mutt. I unset this variable (and
also $VISUAL), and evenis vi is not mentionned in my .muttrc, vi stays the
default editor.
Is there a "real" builtin editor for M
Lars Hecking writes:
> Leon Breedt writes:
> > Lars Hecking spake thus:
> >
> > > 80. I don't think the builtin editor can be configured to wrap lines
> > > automatically. If you're not using the builtin editor, check the manual
> > > for
