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 744837 - Output ^? should be ignored rather than backspace
Output ^? should be ignored rather than backspace
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
0.39.x
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-02-20 00:28 UTC by Egmont Koblinger
Modified: 2015-02-27 11:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix (416 bytes, patch)
2015-02-20 00:52 UTC, Egmont Koblinger 		none Details | Review
Fix v2 (1.31 KB, patch)
2015-02-26 17:03 UTC, Egmont Koblinger 		committed Details | Review

Description Egmont Koblinger 2015-02-20 00:28:20 UTC 
echo -e "ijk\x7Flm"

xterm output: ijklm
vte output:   ijlm

Apparently ^? (127) should totally be ignored when received as an application's output.  (It does not even snap back the cursor to the last column if it's beyond.)  In current vte it seems to do the same as backspace.

I guess this is independent from stty erase, that one is for the keyboard input only -- am I right?
Comment 1 Egmont Koblinger 2015-02-20 00:52:58 UTC 
Created attachment 297347 [details] [review]
Fix

This one fixes the bug.

Apparently any keyword there (except for the empty string) which is not found in vteseq-n.gperf is silently ignored.  An explicit nop function might be nicer though :)
Comment 2 Egmont Koblinger 2015-02-26 17:03:13 UTC 
Created attachment 298004 [details] [review]
Fix v2

Fix with an explicit nop method; I have a slight preference towards this approach.
Comment 3 Egmont Koblinger 2015-02-27 11:39:39 UTC 
Fixed