Your message dated Mon, 8 Jun 2026 09:34:28 +0530
with message-id <aiY_TBMn_NVTWPbI@riviera>
and subject line Re: ksh: arrow keys no longer work in an interactive shell
has caused the Debian Bug report #908227,
regarding ksh: the status of the options should not depend on $VISUAL
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
908227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908227
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ksh
Version: 93u+20120801-3.1
Severity: important
Arrow keys no longer work in an interactive shell. Here's what I get
with Up, Down, Right, Left:
cventin:~> ksh93
$ ^[[A^[[B^[[C^[[D
Same issue with xterm, rxvt and GNOME Terminal. Thus this is not a
terminal issue.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ksh depends on:
ii binfmt-support 2.1.8-2
ii libc6 2.27-6
ksh recommends no packages.
ksh suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.0~rc.1-1
On Sun, Jun 07, 2026 at 09:51:47PM +0200, Vincent Lefevre wrote:
> I have an old machine with old debs under /var/cache/apt/archives,
> so that I could test old ksh93u+m versions. I confirm that this
> bug still occurs in ksh93u+m 1.0.0~beta.2-1 (2021-12-06), but
> no longer occurs in ksh93u+m 1.0.0~rc.1-1 (2022-07-30), and it
> no longer occurs in the current version either.
That aligns with the release history, the fix first went into rc.1.
Thanks for testing,
Anuradha
--- End Message ---
