On Tue, Nov 08, 2016 at 04:02:53PM +0000, Ian Campbell <[email protected]>
wrote:
> I said that I think this might be down to the sequence
> "<ESC>[1B<ESC>[1A^M" and might maybe have something to do with the
> behaviour of the CUU and CUD cursor movement ANSI codes at the edge of
> the screen, but frankly I'm out of my depth...
Hi, thanks for bringing this to our attention.
I haven't analyzed this in depth, but the urxvt behaviour is incorrect w.r.t
vt100, so very likely a bug. The only reason why it might not be is that rxvt
behaves the same, and rxvt compatibility is obviously important for urxvt.
In general, however, wikipedia is a bad source for authoritative
information, and using it to blindly output sequences that happen to work
on one terminal might not make them work on others - you should generally
use terminfo or curses instead of hardcoding random sequences, so this
might just as well be a bug in docker in addition to a urxvt bug - it
shouldn't output the wrong sequence to a terminal, and even if urxvt might
change behaviour, the sequence is still not working on all terminals, and
likely never will.
So I would suggest going for a sequence that works more portably - other
programs seem to be able to do it, so docker should be, too.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
