> I found a hacky workaround - add this to your $PS1:
The workaround of resetting relevant settings from the prompt has
already been mentioned – although without showing a concrete example.
> Given how randomly it happens, I believe there is a real bug in
Terminator
I'm about 99.999% sure that t
Getting this with 1.91 on Arch, it likes to happen during package
updates for some reason.
I found a hacky workaround - add this to your $PS1:
\[\e[?1049l\e[?2004l\e[?1006l\e[?1002l\e[?1001r\e[?1l\]
It'll fix it as soon as you get to a prompt.
Given how randomly it happens, I believe there is a
oops this is a wrong place to report it as a terminator bug, but the
workaround should work anyway ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566437
Title:
Scrolling randomly stops working
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bash (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566437
Title:
Scrol
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566437
Title:
Scrolling randomly stops
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 a
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 wonder
> 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 t
... "exit" (of that *application*) ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566437
Title:
Scrolling randomly stops working
To manage notifications about this bug go to:
https://bugs.launc
> 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), "clea
> 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
rees
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 g
12 matches
Mail list logo
