Chrome Version: 66.0.3359.139 (Official Build) (64-bit)
OS: linux
What steps will reproduce the problem?
(1) Log in to google via secure shell
(2) In bash type Ctrl-Q Alt-C [or Ctrl-V Alt-C]
(3)
What is the expected result?
^[c
What happens instead?
c
More specifically, Alt-C in emacs is broken.
There are a couple of ways to send Alt-C.
One is with 0x80 | 'c'.
The other is with Escape c.
Experiments show secure shell sends Escape <letter>.
[I'm assuming it's secure shell that is processing keycodes here.]
This is working for every letter except 'c'.
Another way to repro:
bash$ echo "<Ctrl-Q><Alt-C>" | od -tx1
It prints 63 0a when it should print 1b 63 0a.
This worked relatively recently just fine (I use Alt-C in emacs a lot).
It's entirely possible something else is screwing up.
The above examples work just fine in a native shell on my laptop.
It's just not working in secureshell.
---
Please use labels and text to provide additional information.
If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
Comment 1 by vapier@chromium.org
, Jun 17 2018Summary: hterm: Alt-c isn't working (was: Alt-c is broken in secure shell)