On Thu, Oct 21, 1999 at 12:53:46 -0500, David DeSimone wrote:
> 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.
But perhaps there should be an option so that Mutt doesn't call
endwin when it starts a process (pipe, editor). For instance,
less has a similar option (-X):
-X Disables sending the termcap initialization and deini-
tialization strings to the terminal. This is sometimes
desirable if the deinitialization string does something
unnecessary, like clearing the screen.
--
Vincent Lefèvre <[EMAIL PROTECTED]> - PhD student in Computer Science
Web: <http://www.vinc17.org/> or <http://www.ens-lyon.fr/~vlefevre/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International
des Jeux Mathématiques et Logiques, TETRHEX, etc.
