zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: David Korn <dgk@research.att.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Proposal to standardize the shell
Date: Tue, 10 Jul 2001 12:40:04 +0100	[thread overview]
Message-ID: <3B4AE994.14216030@u.genie.co.uk> (raw)
In-Reply-To: <20010709223550.73E8514283@pwstephenson.fsnet.co.uk>

David Korn wrote:

> I would like to see if it is possible to come up with an enhanced
> shell standard that could be met by at least ksh, bash, and zsh.
> 
> If the zsh workers are also interested in this effort let me know.

The effort does sound interesting to me. Your suggested starting points
seem sensible and I'd be keen for there to be input from us so that
current zsh features and incompatibilities can be accounted for in the
process.

> Also, if you know who else should be included, please let me know.

Maybe the pdksh developers but I'm not sure how alive that project is.

Peter Stephenson wrote:

> Quite what degree of compatibility is possible between the more advanced
> features I really don't know, but it's worth thinking about.  We've been
> treating ksh93 as a sort of de facto standard for some of the advanced
> features, though there's still quite a lot of that missing and (according
> to my reading of Oliver Kiddle's post to zsh-workers just now) some of it
> appears to be incompatible.

Certainly, there may be problems with some of the more advanced
features but I think there is a fair amount of scope for extensions to
POSIX which wouldn't cause many problems. If I'm not mistaken, there
were quite a few extensions to POSIX that were in ksh88 and these are
fairly well followed by bash and zsh. I think there are also a number of
newer features where we don't have incompatibilities. Process
substitution would be one example.

Can anyone please point me in the direction of the canonical web
location for the POSIX shell definition because my search wasn't very
successful?

> In interactive features, there might be something we do with simple things
> like key binding syntax, for example.  I doubt if it'll go much deeper than

I didn't mention ksh93 key binding in my recent post but it is very
different. In short, there is a KEYBD trap which you override to change
keypresses. I expect the zsh/bash bindkey builtin was inspired by tcsh.

There might be other areas of interactive features which can be
standardised on though. Parts of the history mechanism, fc options
maybe.

Oliver

_____________________________________________________________________
This message has been checked for all known viruses by the 
MessageLabs Virus Scanning Service. For further information visit
http://www.messagelabs.com/stats.asp


  reply	other threads:[~2001-07-10 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 19:42 David Korn
2001-07-09 22:35 ` Peter Stephenson
2001-07-10 11:40   ` Oliver Kiddle [this message]
2001-07-10 17:34 ` Bart Schaefer
2001-07-15 12:00 ` Zefram
2001-07-18  6:12 Felix Rosencrantz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B4AE994.14216030@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --cc=dgk@research.att.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).