From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: 'whence' question
Date: Tue, 11 Nov 2014 11:14:19 -0800 [thread overview]
Message-ID: <CAH+w=7asXdD6fRAXb89P30mg4kyxiXd+SRpvqpWMUZw1a-8SSg@mail.gmail.com> (raw)
In-Reply-To: <54623EBF.8040308@eastlink.ca>
On Tue, Nov 11, 2014 at 8:52 AM, Ray Andrews <rayandrews@eastlink.ca> wrote:
> Got that patch. It works as advertised
If you haven't already, you might want to get minimally familiar with
"git" so you can pull from the development repository rather than
applying individual patches.
> but I noticed this:
>
> $ whence -vam zsh* << UNQUOTED
What's happening here is that zsh* is being expanded as a file glob in
the local directory, and then "whence" is being called with the
resulting file names as arguments and looking up each of them in turn.
Try
$ echo whence -vam zsh*
and see what you get. I think this will explain all your confusion.
> For now the moral of the story is to always quote, but why would
> one ever *not* quote?
For "whence" one probably would always quote patterns. For most other
commands that operate on file names, one probably wants them unquoted,
so that is the default behavior. Command line input semantics
including globbing are entirely separate in *nix from the semantics
internal to the command itself -- very unlike DOS where it is up to
the command to invoke globbing on its arguments.
> I mean is there some valid use of it unquoted, or is that
> just always wrong? If always wrong, they can we 'autoquote' some how?
You could use
alias whence='noglob whence '
(the trailing space is important, see the description of the "alias" command).
next prev parent reply other threads:[~2014-11-11 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <545A6D66.3080500@eastlink.ca>
[not found] ` <1458.1415209763@thecus.kiddle.eu>
[not found] ` <20141105180035.22f6e9b1@pwslap01u.europe.root.pri>
[not found] ` <141105204330.ZM2973@torch.brasslantern.com>
2014-11-06 21:10 ` Peter Stephenson
2014-11-06 21:58 ` Bart Schaefer
2014-11-08 20:41 ` Peter Stephenson
2014-11-09 18:51 ` Bart Schaefer
2014-11-10 5:15 ` 'whence' question and others Ray Andrews
2014-11-10 8:20 ` Bart Schaefer
2014-11-10 8:23 ` Bart Schaefer
2014-11-10 16:57 ` Ray Andrews
2014-11-10 19:53 ` Vin Shelton
2014-11-11 16:52 ` 'whence' question Ray Andrews
2014-11-11 19:14 ` Bart Schaefer [this message]
2014-11-11 19:38 ` Bart Schaefer
2014-11-11 20:22 ` Ray Andrews
2014-11-11 18:16 ` Ray Andrews
2014-11-11 19:33 ` Bart Schaefer
2014-11-11 20:40 ` Ray Andrews
2014-11-08 21:55 ` Bart Schaefer
2014-11-10 10:04 ` 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='CAH+w=7asXdD6fRAXb89P30mg4kyxiXd+SRpvqpWMUZw1a-8SSg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--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).