From: "David R. Favor" <dfavor@austin.ibm.com>
To: Zsh List <zsh-users@math.gatech.edu>
Subject: [Fwd: Parameter Expansion questions]
Date: Mon, 17 Aug 1998 10:17:59 -0500 [thread overview]
Message-ID: <35D849A7.4EB5F516@austin.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Type: message/rfc822, Size: 1577 bytes --]
From: "David R. Favor" <dfavor@austin.ibm.com>
To: Zefram <zefram@tao.co.uk>
Subject: Re: Parameter Expansion questions
Date: Mon, 17 Aug 1998 10:16:58 -0500
Message-ID: <35D8496A.B936DCDF@austin.ibm.com>
> > splitpath=${buf:gs/:/ /}
>
> That's doing a substitution, rather than field splitting. Since the
> effect you're asking for is actually a substitution, rather than field
> splitting (since you're just joining up the fields again anyway), this
> is logically the correct thing to do.
>
> OTOH, I suspect that you *really* want to be using an array parameter.
> $path is an array version of $PATH, so you don't even need to do the
> splitting manually in that case.
Here's a larger fragment of the function I'm using, that is a wrapper
around vi to check several directories for a file to edit. What is the
recommended way to accomplish this in zsh, hopefully while retaining
ksh compatibility also? I would like to get rid of the $shell_type
nonsense and the ${=editpath} syntax in the loop.
Thanks.
_______
# paths to search
editpath=${EDITPATH:-"$PATH:$CDPATH"}
IFS=:
if [ $shell_type = 'zsh' ] ; then <<< $shell_type
editpath=${editpath:gs/:/ /}
else
editpath=$editpath
fi
IFS="$BACKUP_IFS"
for name in $* ; do
for dir in ${=editpath} ; do <<< ${=editpath}
# find/edit the file
done
done
next reply other threads:[~1998-08-17 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-17 15:17 David R. Favor [this message]
1998-08-17 15:44 ` Bruce Stephens
1998-08-17 15:52 ` vi wrapper -> vim + "set path" Sven Guckes
1998-08-17 16:08 ` [Fwd: Parameter Expansion questions] Peter Stephenson
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=35D849A7.4EB5F516@austin.ibm.com \
--to=dfavor@austin.ibm.com \
--cc=zsh-users@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).