Nettle SSH nono from nano

When using Nettle/vt220 v0.2043b on RISC OS 5.29 to SSH into Raspberry Pi OS there is a problem with the Nano editor.
eg sudo nano /etc/samba/smb.conf
The editor works as far as adding new lines, but it won’t exit via enter or carrier return, so it is not possible to save any changes.

Nano works ok if used directly via a command window from VNC.

Has anybody else experienced this behaviour?
(and is Aldershot a suitable place to ask?)

That’s weird, isn’t it? Any Return in nano just jumps to EOF for me (is it acting like Ctrl-J?) and I can’t exit either when ssh in via Nettle using vt220/xterm/linux. Nor does numpad Enter work. If I ssh in, do od -t x1 -, press Return a few times then Ctrl-D I see a stream of 0a as might be expected. Trusty old vi does work though.

I can ssh into the pi (an up-to-date Raspbian 11) from Putty on Windows (same user) and use nano fine.

I also ran into that problem when I recently switched over to using SSH instead of VNC for interacting with a RPi OS machine.

The “solution” I went with was to use packman to install the openssh package, then configure Nettle to run SSH as an ANSI task (and make sure RISC OS has the TERM environment variable set to a sensible value). That makes enter/return in nano work, but then I’m stuck with a different problem, which is that using the arrow keys in the Linux shell just print the terminal escape codes instead of working properly. Meanwhile, arrow keys in nano work fine. (Also Delete performs the same operation as Backspace, but that’s less annoying)

Linux, the TERM environment variable on RISC OS, and Nettle are all configured to the same thing (xterm-color). Maybe if I play around I’ll be able to find a different terminal setting which works properly, but for the moment I’m just living with it.

I found the solution to a nano display problem the other day – it messes up scrolling inside tmux. The solution is to set the TERM variable to ‘screen’, ie ‘export TERM=screen’ before you start nano.

This is not the same problem, but perhaps you could try tweaking TERM and seeing if it makes a difference?

Thanks for the suggestions. I tried tweaking TERM but it had no effect.
However, I have swapped keyboards for one with separate keys for “Return” and “Enter” and hey ho the “Enter” works!