Follow-up Comment #5, bug #57340 (project gforth):
[comment #3 comment #3:]
> On another machine (Ubuntu submodule of Windows 10) it is:
> lrwxrwxrwx 1 root root 15 Jun 1 2019 /etc/alternatives/x-terminal-emulator
-> /usr/bin/lxterm
But you likely aren't using that in the WSL, because there's no graphical
session in WSL, only a terminal session. You are using the terminal from
Windows. You can use it directly if you start an Xserver on Windows, and then
start lxterm on the WSL instance.
I have Windows 1909, and there, using the mintty based terminal Microsoft has
now (replacing the old cmd.exe-style terminal) works as it should.
> To further test, I also used termux on android to access the linux mint PC.
It also shows the same ekey effect. I can't tell you the
etc/alternatives/x-terminal-emulator, because termux doesn't have that.
So you are using termux to access the PC, which means there's another remote
connection (ssh? what? please say) in between your termux and the PC, which
you don't mention.
> Next I did a fresh install of gforth on an Ubuntu VPS installed on vultr.com
(using sudo apt-get install gforth). Tried ekey with shift-backspace there --
same effect from both PCs as well as Android termux.
You definitely don't sit in front of this cloud computer. You have some
remote connection. This is likely the interesting part.
> I also accessed the VPS from a browser based terminal. However, that
terminal did not seem to allow shift-backspace. shift-backspace registered in
gforth as just backspace.
Yes, that's the normal way. There is no shift-backspace on the normal
terminal. It's not about “allow”, it's very likely that the remote
connection software you are using intercepts shift-backspace, and when you
press it, the terminal goes into line mode (without Gforth knowing about
this).
> Finally, I tried XTerm on Windows 10, connecting to the ubuntu LSM. There,
keystrokes also don't show after ekey, but shift-backspace is captured as 27
(ESC).
Still, the interesting part is how you connect.
For us, Linux is on our PC right before us, not in a VM, not in the cloud.
The terminal is running on our computer.
> Oh, I also tried xterm on the Mint 18 (Ubuntu xenial equiv), but same
effect.
So here you run an xterm locally and start gforth locally, or is there some
other program in between that might filter out shift-backspace?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57340>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
