I originally thought setting a default editor mode would be a good idea,
but after Glenn's comments, I discussed this with our standards expert.
He agrees that we should *not* set a default command-line editing
mode if EDITOR and VISUAL are not set and set -o vi|emacs|gmacs are not set.
So, no, we should not be setting a default command-line editor in ksh93.
It would be violating POSIX standards.
April
> X-Unix-From: gsf at research.att.com Mon May 15 09:12:15 2006
> X-Original-To: ksh93-integration-discuss at opensolaris.org
> Delivered-To: ksh93-integration-discuss at opensolaris.org
> Date: Mon, 15 May 2006 12:12:09 -0400 (EDT)
> From: Glenn Fowler <gsf at research.att.com>
> Mime-Version: 1.0
> Content-Transfer-Encoding: 7bit
> To: ksh93-integration-discuss at opensolaris.org
> Subject: Re: [ksh93-integration-discuss] Re: TAB-TAB completion patch #003
(which makes "gmacs" the default editor mode) / was: Re: [ast-users] RFE: Make
TAB completion in ksh93 work like ESC-'='...
> Cc: ast-users at research.att.com
> X-BeenThere: ksh93-integration-discuss at opensolaris.org
> X-Mailman-Version: 2.1.4
> List-Id: Korn Shell 93 integration/migration project discussion
<ksh93-integration-discuss.opensolaris.org>
> List-Unsubscribe:
<http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss>,
<mailto:ksh93-integration-discuss-request at
opensolaris.org?subject=unsubscribe>
> List-Archive:
<http://mail.opensolaris.org/pipermail/ksh93-integration-discuss>
> List-Post: <mailto:ksh93-integration-discuss at opensolaris.org>
> List-Help:
<mailto:ksh93-integration-discuss-request at opensolaris.org?subject=help>
> List-Subscribe:
<http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss>,
<mailto:ksh93-integration-discuss-request at opensolaris.org?subject=subscribe>
>
>
> On Mon, 15 May 2006 17:21:49 +0200 I. Szczesniak wrote:
> > On 5/15/06, Glenn Fowler <gsf at research.att.com> wrote:
> > > i.e., I believe the default editor must be NONE
> > > with ksh93 the user can always do the appropriate .profile / ENV file
> > > magic for editor preference
>
> > Why does bash then claim full POSIX conformance and default to emacs
editing?
>
> bash overclaimed
> the posix text for the "set" special builtin utility
> for the "User Portability Utilities option"
> states that the default values for set -o options are off
> an sh that starts with any of these on by default is not conforming
>
> also note that only "set -o vi" mode is defined in the standard (see the
rationale)
> implementations are allowed to provide other command line editing modes
> but those modes would be subject the the same "default value off" text
>
> _______________________________________________
> ksh93-integration-discuss mailing list
> ksh93-integration-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss
