Your message dated Sun, 21 Jun 2026 00:11:25 +0530 with message-id <[email protected]> and subject line Re: Bug#1037971: ksh93u+m: read statement in subshell fails for 0 or 1 character followed by tab has caused the Debian Bug report #1037971, regarding ksh93u+m: read statement in subshell fails for 0 or 1 character followed by tab 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.) -- 1037971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037971 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ksh93u+m Version: 1.0.4-3 Severity: normal Dear Maintainer, The following: ( read a; print "$a" ) beeps and ignores a tab if entered before two other characters have been typed. With () removed, it works in an interactive shell but fails in an invoked script. Bill -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages ksh93u+m depends on: ii libc6 2.36-9 ksh93u+m recommends no packages. Versions of packages ksh93u+m suggests: pn binfmt-support <none> -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.0.7-1 On Wed, Jun 14, 2023 at 02:34:12PM -0700, Bill Brelsford wrote: > ( read a; print "$a" ) > > beeps and ignores a tab if entered before two other characters have > been typed. With () removed, it works in an interactive shell but > fails in an invoked script. Hi Bill, Thanks for the report. This was a line editor issue that was fixed upstream between 1.0.4 and 1.0.7. I was able to reproduce it on 1.0.4-3 but not on 1.0.7-1 or any subsequent versions, so closing against 1.0.7-1. Anuradha
--- End Message ---
