After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 659521 - VT ESC sequence ESC E not recognized
VT ESC sequence ESC E not recognized
Status: RESOLVED DUPLICATE of bug 693013
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-19 21:31 UTC by mike.jost
Modified: 2014-04-12 15:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
echoserv.c by Paul Griffiths modified to dump esc sequences on client connect (4.79 KB, text/plain)
2011-09-19 21:31 UTC, mike.jost
Details

Description mike.jost 2011-09-19 21:31:16 UTC
Created attachment 197003 [details]
echoserv.c by Paul Griffiths modified to dump esc sequences on client connect

the ESC E squence is handled as CR only.

IND – Index
ESC D   

This sequence causes the active position to move downward one line without changing the column position. If the active position is at the bottom margin, a scroll up is performed. Format Effector


NEL – Next Line
ESC E   

This sequence causes the active position to move to the first position on the next line downward. If the active position is at the bottom margin, a scroll up is performed. Format Effector


test app (attached) produces this output with redhat gnome terminal 2.16.0 and appearantly other versions as well.

4 ESC E sequences
4 ESC E sequences. completed
4 ESC D sequences




4 ESC D sequences. completed


xterm and other terminals produce this output
4 ESC E sequences




4 ESC E sequences. completed
4 ESC D sequences




4 ESC D sequences. completed

steps
compile and run test app using any available port number.

telnet to selected port observe output.
Comment 1 Egmont Koblinger 2014-01-05 20:26:10 UTC
I believe this was fixed in bug 693013.
Comment 2 Christian Persch 2014-04-12 15:37:09 UTC

*** This bug has been marked as a duplicate of bug 693013 ***