zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Enhanced shell
Date: Sun, 29 Jul 2001 23:07:03 +0100	[thread overview]
Message-ID: <20010729220708.8256314291@pwstephenson.fsnet.co.uk> (raw)
In-Reply-To: "Zefram"'s message of "Sun, 29 Jul 2001 10:53:39 BST." <E15QnGV-0000hL-00@bowl.fysh.org>

Zefram wrote:
> Peter Stephenson wrote:
> >emulate builtin
> 
> We should only standardise "emulate posix_v2" as a way of specifying
> "this is written for the enhanced shell standard".  Then future
> revisions of the standard get to add new permitted arguments to emulate.
> Without an emulate command in a script, the shell has to behave in a
> manner compatible with the original POSIX.

Hmm.  Zsh obviously doesn't, you have to trick it some other way.
 
> >? =cmd?
> 
> With cleaned-up semantics, yes.  It shouldn't be doing alias expansion.

Yes, I'm not sure how long that's been there, and I don't think it's all
that useful --- using the parameters module for this as for other
similar things strikes me as a better bet.  I find it hard to believe
anyone is relying on it, either, given that you can't tell if you're
going to end up with an external command, which are found in preference,
opposite to the normal order of lookup.  So I'm very tempted to remove
it or stick it in a deprecated option, off by default.

> >? glob qualifiers (perhaps in some standardised NO_BARE_GLOB_QUAL form)
> 
> The NO_BARE_GLOB_QUAL form should probably simply be an explicit way of
> introducing the qualifier syntax we already have.  That was the idea
> behind the option -- BARE_GLOB_QUAL makes glob qualifier syntax clash
> with glob grouping syntax.

I suppose you mean any enhanced-shell version should be a separate
option.  I can certainly see a point in that.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@csr.com
Web: http://www.pwstephenson.fsnet.co.uk


  reply	other threads:[~2001-07-29 21:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-22 22:47 Peter Stephenson
2001-07-23 11:13 ` Oliver Kiddle
2001-07-23 11:38   ` Peter Stephenson
2001-07-23 18:03     ` Bart Schaefer
2001-07-24 13:42       ` Oliver Kiddle
2001-07-23 12:00   ` Nadav Har'El
2001-07-23 16:38     ` Enable/disable (was Re: Enhanced shell) Bart Schaefer
2001-07-23 22:00       ` Nadav Har'El
2001-07-24  1:12         ` Bart Schaefer
2001-07-24  2:45           ` Here-strings and $functions Bart Schaefer
2001-07-24  6:18             ` Bart Schaefer
2001-07-24  8:12               ` Sven Wischnowsky
2001-07-24 12:16                 ` Bart Schaefer
2001-07-24  9:23         ` Enable/disable (was Re: Enhanced shell) Peter Stephenson
2001-07-24 12:10           ` PATCH: Doc errors (Re: Enable/disable (was Re: Enhanced shell)) Bart Schaefer
2001-07-29  9:53 ` Enhanced shell Zefram
2001-07-29 22:07   ` Peter Stephenson [this message]
2001-07-30  1:34     ` Bart Schaefer
2001-07-30  2:19   ` Bart Schaefer

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=20010729220708.8256314291@pwstephenson.fsnet.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --cc=zsh-workers@sunsite.auc.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).