From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: PATCH: zmv with alternative commands
Date: Wed, 3 Jul 2013 20:00:58 +0100 [thread overview]
Message-ID: <20130703200058.705eb872@pws-pc.ntlworld.com> (raw)
In-Reply-To: <130703110933.ZM8733@torch.brasslantern.com>
On Wed, 03 Jul 2013 11:09:33 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> If -p splits, do we even need -o any more, or is there a reason
> that splitting with -o was separated from providing the command with -p?
No, we don't really need -o any more. It's more natural if you
don't need to change the command name, but want to add an option. -p is
more natural if you are suppling consecutive words like a command and a
subcommand. There's definitely no point in using both.
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
prev parent reply other threads:[~2013-07-03 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 11:17 Peter Stephenson
2013-07-03 15:57 ` Bart Schaefer
2013-07-03 16:06 ` Peter Stephenson
2013-07-03 18:09 ` Bart Schaefer
2013-07-03 19:00 ` Peter Stephenson [this message]
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=20130703200058.705eb872@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/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).