Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#702827: #702827 screen: Cursor not repositioned properly after launching altscreen application and resizing the terminal
4 views
Skip to first unread message
Thomas Dickey
Mar 12, 2013, 10:10:02 AM3/12/13
to
The problem as described is due to the way the cursor-save and alternate-screen
features work - in the terminal itself. xterm has a workaround for this (if you're
using xterm I can investigate if/how to improve that). Other terminals lack
workarounds - no help there.
--
Thomas E. Dickey <dic...@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net
features work - in the terminal itself. xterm has a workaround for this (if you're
using xterm I can investigate if/how to improve that). Other terminals lack
workarounds - no help there.
--
Thomas E. Dickey <dic...@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net
Eric Pruitt
Mar 12, 2013, 10:30:02 AM3/12/13
to
Hey Thomas,
On Tue, Mar 12, 2013 at 10:01:31AM -0400, Thomas Dickey wrote:
> The problem as described is due to the way the cursor-save and
> alternate-screen features work - in the terminal itself. xterm has a
> workaround for this (if you're using xterm I can investigate if/how to
> improve that).
I only began experiencing this problem when I upgraded from Screen
version 4.00.03jw4, so this seems unlikely to me. Was there a
significant change in altscreen handling? In any case, I am using
indeed using xterm if you would still be willing to investigate for me.
I have now reverted to 4.00.03jw4 due to frequent segfaults that also
appear to be related to altscreen. The issues are reminiscent of what's
described in bug
[#666052](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666052), but
I experienced no segfaults until I upgraded to Wheezy and, in the
process, upgraded GNU screen.
Thank you,
Eric
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
On Tue, Mar 12, 2013 at 10:01:31AM -0400, Thomas Dickey wrote:
> The problem as described is due to the way the cursor-save and
> alternate-screen features work - in the terminal itself. xterm has a
> workaround for this (if you're using xterm I can investigate if/how to
> improve that).
version 4.00.03jw4, so this seems unlikely to me. Was there a
significant change in altscreen handling? In any case, I am using
indeed using xterm if you would still be willing to investigate for me.
I have now reverted to 4.00.03jw4 due to frequent segfaults that also
appear to be related to altscreen. The issues are reminiscent of what's
described in bug
[#666052](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666052), but
I experienced no segfaults until I upgraded to Wheezy and, in the
process, upgraded GNU screen.
Thank you,
Eric
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Thomas Dickey
Mar 12, 2013, 8:40:01 PM3/12/13
to
On Tue, Mar 12, 2013 at 09:19:23AM -0500, Eric Pruitt wrote:
> Hey Thomas,
>
> On Tue, Mar 12, 2013 at 10:01:31AM -0400, Thomas Dickey wrote:
> > The problem as described is due to the way the cursor-save and
> > alternate-screen features work - in the terminal itself. xterm has a
> > workaround for this (if you're using xterm I can investigate if/how to
> > improve that).
>
> I only began experiencing this problem when I upgraded from Screen
> version 4.00.03jw4, so this seems unlikely to me. Was there a
> significant change in altscreen handling? In any case, I am using
> indeed using xterm if you would still be willing to investigate for me.
hmm - I'll add a to-do item to see what the story is
> Hey Thomas,
>
> On Tue, Mar 12, 2013 at 10:01:31AM -0400, Thomas Dickey wrote:
> > The problem as described is due to the way the cursor-save and
> > alternate-screen features work - in the terminal itself. xterm has a
> > workaround for this (if you're using xterm I can investigate if/how to
> > improve that).
>
> I only began experiencing this problem when I upgraded from Screen
> version 4.00.03jw4, so this seems unlikely to me. Was there a
> significant change in altscreen handling? In any case, I am using
> indeed using xterm if you would still be willing to investigate for me.
(I maintain xterm, not screen of course...)
0 new messages