From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: whence question
Date: Sat, 14 Jan 2017 11:13:26 -0800 [thread overview]
Message-ID: <e7c99994-29cf-88cf-e243-37846accf013@eastlink.ca> (raw)
In-Reply-To: <alpine.LRH.2.00.1701140902270.4560@toltec.zanshin.com>
On 14/01/17 09:11 AM, Bart Schaefer wrote:
> The options you're changing only matter when globbing FAILS. If the
> local file matching grub-r* exists, then globbing SUCCEEDS, and your
> option changes mean nothing in context.
Tx.
>
> Just being devil's advocate here of course but in this case does not the
> 'm' switch in effect 'state' an exception? That is, is it not an
> explicit request to change the rules vis a vis globing?
> No, it isn't, because globbing is done by the shell long before it tries
> to execute the "whence" (or any other) command, so at the time globbing
> is done "-m" is just another syntactic word with no special meaning.
Yeah, I understand the order of processing (at least that detail), so my
idea of special treatment for 'm' would indeed be an exception and could
be ruled out for that reason alone. I understand that it's no small
thing to suggest it even if it were possible and maybe it simply isn't
possible anyway. Still, you hafta admit my first example has to be seen
as a defect because 'whence -ma' has no reason to care about local
files; globing in that situation is a different animal since whence has
different targets. IOW 'whence -ma' only does what it is expected to do
when normal globing fails. But perhaps this is so long established
that the safe thing to do is to use Daniel's alias. I'll make no
further noise about it since I have a solution anyway and it's something
I'm used to using.
Besides, it works fine when the glob is quoted and the docs say to quote
when using 'm' and that's normal hygiene anyway ... so what am I
bitching about ;-) I'm being overly theoretical and wasting people's time.
next prev parent reply other threads:[~2017-01-14 19:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 4:13 Ray Andrews
2017-01-14 5:11 ` Bart Schaefer
2017-01-14 6:09 ` Ray Andrews
[not found] ` <7b890e89-d01b-ab5c-32bf-b75bfa8d945c__41234.9168131643$1484374276$gmane$org@eastlink.ca>
2017-01-14 6:48 ` Daniel Shahaf
2017-01-14 16:36 ` Ray Andrews
2017-01-14 17:11 ` Bart Schaefer
2017-01-14 19:13 ` Ray Andrews [this message]
2017-01-14 17:46 ` Jens Elkner
2017-01-14 17:59 ` Bart Schaefer
2017-01-14 18:23 ` Jens Elkner
2017-01-14 19:08 ` Nikolay Aleksandrovich Pavlov (ZyX)
2017-01-14 20:13 ` Daniel Shahaf
2017-01-14 21:04 ` Bart Schaefer
[not found] ` <4cca17742cded21984e6092622265ab9@cmgw03.eastlink.ca>
2017-01-14 21:44 ` Ray Andrews
[not found] <652bcc3f-7365-2e52-d39c-8576278606bc__74.9235078275845$1484367323$gmane$org@eastlink.ca>
2017-01-14 4:40 ` Daniel Shahaf
2017-01-14 4:57 ` Ray Andrews
2017-01-14 18:32 ` Ray Andrews
2017-01-14 18:55 ` Bart Schaefer
2017-01-14 19:51 ` Ray Andrews
2017-01-14 20:56 ` Daniel Shahaf
2017-01-14 21:26 ` Ray Andrews
2017-01-14 21:53 ` Daniel Shahaf
2017-01-15 19:53 ` Ray Andrews
2017-01-14 21:43 ` Bart Schaefer
2017-01-14 21:55 ` Bart Schaefer
2017-01-15 20:06 ` Ray Andrews
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=e7c99994-29cf-88cf-e243-37846accf013@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).