Re: bin/58690: ksh: "command" doesn't make special builtins not special

["LU via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR bin/58690; it has been noted by GNATS.

From: LU <X13_SPIDER%proton.me@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/58690: ksh: "command" doesn't make special builtins not special
Date: Mon, 23 Sep 2024 17:35:56 +0000

 KSH is only there for Co-process functionality
 
 
 
 weep not for me
 run for your life
 
 Lu
 
 Sent with Proton Mail secure email.
 
 On Monday, September 23rd, 2024 at 1:20 PM, Valery Ushakov via gnats <gnats=
 -admin%NetBSD.org@localhost> wrote:
 
 > The following reply was made to PR bin/58690; it has been noted by GNATS.
 >=20
 > From: Valery Ushakov uwe%stderr.spb.ru@localhost
 >=20
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: bin/58690: ksh: "command" doesn't make special builtins not
 > special
 > Date: Mon, 23 Sep 2024 20:19:08 +0300
 >=20
 > On Mon, Sep 23, 2024 at 17:10:02 +0000, Robert Elz via gnats wrote:
 >=20
 > > If you desire a ksh style interface
 >=20
 >=20
 > I don't, but I was touching the profile/shrc files and they have to
 > work with the ksh we ship. ksh doesn't have "tabcomplete" option, so
 >=20
 > set -o tabcomplete
 >=20
 > will cause it to exit. The usual feint of
 >=20
 > command set -o tabcomplete 2> /dev/null
 >=20
 >=20
 > doesn't work b/c of this bug, so we have instead
 >=20
 > ( set -o tabcomplete 2>/dev/null ) && set -o tabcomplete
 >=20
 >=20
 > in /etc/shrc, a mouthful...
 >=20
 >=20
 > -uwe