zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Enhanced shell standard. summary
Date: Mon, 30 Jul 2001 10:51:38 +0100	[thread overview]
Message-ID: <Tc0a88d01550fe509ce@mailsweeper01.cambridgesiliconradio.com> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Mon, 30 Jul 2001 01:53:38 -0000." <1010730015338.ZM29147@candle.brasslantern.com>

Bart Schaefer wrote:
> } I don't want this preliminary round to drag on much longer since until
> } the people from the other shell have commented it's a bit of a moot
> } discussion.     ^^^^^^^^^^^^^^^
>                       Plural?
> 
> I don't want it to drag on either, but because I think we need to send
> off our list to DK et al. as soon as possible.  Either the ball is not
> rolling, or it's rolling where we can't see it.

That was pretty much what I was saying.  Here's the list I sent.  I've
simply removed stuff we can't really agree on ourselves.  It turned out
$LOGNAME is already mentioned in the single UNIX spec, so I deleted the
line about USER/USERNAME/LOGNAME.

basic
-----
builtins: disown, builtin, suspend, pushd, whence, typeset, declare
[[ ... ]]
COLUMNS/LINES
process substitution, at least <<(...)
${name/pattern/repl}
{a,b}
** math power operator
parameters:
  HOST or HOSTNAME
  SHLVL, RANDOM, SECONDS
  HOSTTYPE, OSTYPE, MACHTYPE
cd takes care of symlinks, optionally resolves linkso
-l option to shell for login
some form of enhanced pattern matching, e.g. like ksh88.
Use of $-expansion in prompts to be standard

additions
---------
emulate <name-indicating-enhanced-shell-standard>
autoload -U, NO_ALIASES option
<<<'word'
functionality of precmd, chpwd, periodic, but with cleaner interface
${+foo} to check whether set
coproc keyword (as |& is quite useful as a csh-like abbreviation)
{0..10} => 0 1 2 3 4 5 6 7 8 9 10
glob qualifiers e.g. *(.) => all regular files
** recursive search
version of enhanced shell spec available maybe via namespace
  (${.sh.ess_version})
functionality associated with disable/enable for builtins --- but name clash
repeat loop (repeat 10; do print hello; done)
standardisation of basic key bindings [need list of these]
-L options to may builtins to list in form for input to shell
  [or make this defined behaviour for builtins --- will need option in zsh
  for compatibility]
`=cmdname' expands to full path to command cmdname.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  reply	other threads:[~2001-07-30  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-29 22:11 Peter Stephenson
2001-07-30  1:53 ` Bart Schaefer
2001-07-30  9:51   ` Peter Stephenson [this message]
2001-07-30 15:39     ` Clint Adams
2001-07-30 16:17       ` Peter Stephenson
2001-07-30  5:14 ` Borsenkow Andrej

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=Tc0a88d01550fe509ce@mailsweeper01.cambridgesiliconradio.com \
    --to=pws@csr.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).