Vincent Lefevre <[EMAIL PROTECTED]> wrote:
>
> Because I like this behavior with other programs (e.g. less), and
> even with Mutt when I quit Mutt (but not when I pipe a message or
> reply to a message).
You are fickle. :)
At any rate, Mutt does not really have the level of control that you
seem to want. Mutt is talking to the curses library, and curses sends
the escape sequences to swap screens. Mutt only knows to call initscr()
when it wants curses to manage the screen, and endwin() when it wants to
stop. When calling another program that will take over the screen (i.e.
your editor), Mutt must call endwin() to stop using the screen, then
initscr() again when it regains control.
As far as I know, there's no endwin_but_dont_swap_to_the_default_screen(),
or initscr_but_pretend_were_already_on_the_background_screen() functions.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer | PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
