From: Sven Guckes <guckes@math.fu-berlin.de>
To: Zsh List <zsh-users@math.gatech.edu>
Cc: "David R . Favor" <dfavor@austin.ibm.com>
Subject: Re: vi wrapper -> vim + "set path"
Date: Mon, 17 Aug 1998 17:52:47 +0200 [thread overview]
Message-ID: <19980817175247.A23355@math.fu-berlin.de> (raw)
In-Reply-To: <35D849A7.4EB5F516@austin.ibm.com>; from David R. Favor on Mon, Aug 17, 1998 at 10:17:59AM -0500
Quoting David R. Favor (dfavor@austin.ibm.com):
> .. wrapper around vi to check several directories for a file to edit.
> What is the recommended way to accomplish this in zsh?
vim -c "se cp path=.,,dir1,dir2,...,dirN"
Sven ;-)
next prev parent reply other threads:[~1998-08-17 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-17 15:17 [Fwd: Parameter Expansion questions] David R. Favor
1998-08-17 15:44 ` Bruce Stephens
1998-08-17 15:52 ` Sven Guckes [this message]
1998-08-17 16:08 ` 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=19980817175247.A23355@math.fu-berlin.de \
--to=guckes@math.fu-berlin.de \
--cc=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).