From: Wataru Kagawa <wkagawa@jota.gsc.riken.go.jp>
To: zsh-users@sunsite.dk
Subject: a question about argument corrections
Date: Sun, 7 Aug 2005 15:21:16 +0900 [thread overview]
Message-ID: <BDDEED7A-9B31-41A0-9AA1-DC329FCFD5BE@jota.gsc.riken.go.jp> (raw)
Hi all,
I find the 'correctall' option to be useful in most cases, except for
the case described below.
zsh% ls
foo1 foo2 foo3
zsh% cp foo3 foo4
zsh: correct 'foo4' to 'foo3'? [nyae] n
The same thing happens for the mv command.
zsh% mv foo3 foo4
zsh: correct 'foo4' to 'foo3'? [nyae] n
I wouldn't want to be asked for the correction as long as foo4
doesn't exist. Is there a way to customize this so that only the
first file is checked when the command is cp or mv?
Suggestions are greatly appreciated.
Wataru Kagawa
next reply other threads:[~2005-08-07 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 6:21 Wataru Kagawa [this message]
2005-08-07 6:31 ` UVV
2005-08-07 6:52 ` Wataru Kagawa
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=BDDEED7A-9B31-41A0-9AA1-DC329FCFD5BE@jota.gsc.riken.go.jp \
--to=wkagawa@jota.gsc.riken.go.jp \
--cc=zsh-users@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).