Is that any reason why bash shouldn't always restore the the terminal
settings after any program it launches exits? (where by "restore" I mean
restore the settings as they were before launching the program, not
necessarily the default ones).
--
You received this bug notification because you are
Errata: by "is that" I meant "is there", of course
** Package changed: gnome-terminal (Ubuntu) => bash (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1566437
Title:
That's right.
By convention, the expected behavior is that vim restores the terminal's
settings. If it exits uncleanly, it might leave the terminal in a
nondefault state, to which usually typing "reset", or closing the
terminal and opening a new one might be an easy workaround.
I've always
> A terminals just obeys the instructions it receives in a single stream,
> it doesn't even have the notion of "shell", "application" (started from that
> shell),
> "exit" (of that shell)
Mmm, I probably do misunderstand something, but then I'm under the
impression this might just be a bug in
... "exit" (of that *application*) ...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1566437
Title:
Scrolling randomly stops working
To manage notifications about this
> The terminal shouldn't rely on applications exiting cleanly.
You misunderstand the very basics of terminals.
A terminals just obeys the instructions it receives in a single stream,
it doesn't even have the notion of "shell", "application" (started from
that shell), "exit" (of that shell),
> If it gets stuck in this mode at your shell prompt,
yes it did
> it means that your application did not exit cleanly and left the
terminal in this mode.
The very fact that that can happen is a bug. After exiting whatever
application triggered "alternate screen", normal scrolling should be
The behavior you describe happens when the terminal switches to the so-
called "alternate screen" upon encountering a certain escape sequence
that is printed by your application. Usually fullscreen applications
(such as the "mc" file manager, "less" pager, text editors etc.) use
this mode.
If it
