On Wed, Jun 12, 2013 at 02:10:04PM +0300, Riku Saikkonen wrote: > (Following up to my own bug report.) > > Hmm. I just found the same problem reported as bug #456943 (reassigned > to grep), where the first few messages indicate that this is not > actually an xterm bug but intended behavior for VT100-compatible > terminals. Though it does not appear to be easy to find out what grep > should do either... > > Also, a friend of mine found a real-life DEC VT220 terminal and tried to > see what happens there; and the VT220 terminal acts exactly like xterm > does. See the attached picture of the screen. (The latter example in the > image turns on auto-wrap in case it wasn't on before, but here it was > (the default setting is user-configurable in the menus of the terminal > itself).) thanks. I had some confirmation of this when I added a test-screen to vttest a while back to demonstrate the differences. > So it appears that xterm (and rxvt) is indeed correct and > gnome-terminal, konsole, screen, tmux and rxvt-unicode do not emulate > the VT220 exactly, and grep does the wrong thing by default in this > case. > > Now I'm not sure what should be done with this bug report. Maybe > reassign it to grep and merge it with #456943? Should I report separate > bugs against gnome-terminal, konsole, screen, tmux and rxvt-unicode > because they don't behave like a real VT220 does? tmux is maintained - might help - I'm not sure about the others. pterm (putty) also differs. -- Thomas E. Dickey <dickey@invisible-island.net> http://invisible-island.net ftp://invisible-island.net
Attachment:
signature.asc
Description: Digital signature