From: Phil Pennock <phil@athenaeum.demon.co.uk>
To: Zsh Development Workers <zsh-workers@math.gatech.edu>
Subject: Notes on bash(1)
Date: Wed, 9 Dec 1998 03:25:32 +0000 [thread overview]
Message-ID: <19981209032532.54741@athenaeum.demon.co.uk> (raw)
I recently needed to check something in bash(1) and noticed some
interesting points in the manual. I'm throwing them this way for
discussion/whatever. Bash is 2.01.1(1)-release.
* bash has arrays. 'declare', 'local' & 'readonly' each accept '-a' to
declare an array. Is it reasonable to add '-a' to 'typeset'? This
would automatically duplicate the bash-ism.
Further, would it be an idea to then deprecate 'set -A' which
overloads parameter setting onto 'set'?
* ${parameter/pattern/string} and ${parameter//pattern/string}
pattern is expanded as per pathname expansion. Longest match of
pattern against parameter is replaced with string. Once for / and for
all instances with //. #pattern anchors to beginning, %pattern
anchors to end. string may be null. Applied to an array, this works
on each element.
zsh has a some of this with the colon-modifier 's'.
The anchors in particular are nice. They would make it easy to fully
replicate basename(1) without forking. We can't currently (AFAIK)
accurately duplicate $(basename file .ext) (think - filename: .ext.ex)
% base=${var:t:s/%.ext//}
* ${parameter:offset} and ${parameter:offset:length} provide substring
and array extraction. Both length and offset are arithmetic
expressions. length>=0. offset may be negative to measure from end.
zsh notably has ${parameter[start,stop]} already. How desirable is
this alternate syntax, given that zsh allows history modifiers in the
same place? It doesn't look like there would be a conflict, provided
zsh requires $[...] for variables there. Testing, bash allows:
$ foo=abcde; t=2; echo ${foo:t}
--
--> Phil Pennock ; GAT d- s+:+ a22 C++(++++) UL++++/I+++/S+++/H+ P++@ L+++
E-@ W(+) N>++ o !K w--- O>+ M V !PS PE Y+ PGP+ t-- 5++ X+ R !tv b++>+++ DI+ D+
G+ e+ h* r y?
next reply other threads:[~1998-12-09 3:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-09 3:25 Phil Pennock [this message]
1998-12-09 9:01 ` Peter Stephenson
1998-12-09 17:04 ` PATCH: 3.1.5: bash ${.../old/new} Peter Stephenson
1998-12-10 15:52 ` Strange substring search behaviour Peter Stephenson
1998-12-09 19:43 ` PATCH: Docs out of sync Phil Pennock
1998-12-12 7:45 ` 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=19981209032532.54741@athenaeum.demon.co.uk \
--to=phil@athenaeum.demon.co.uk \
--cc=zsh-workers@math.gatech.edu \
/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).