From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: 'whence' question
Date: Sun, 09 Nov 2014 10:51:39 -0800 [thread overview]
Message-ID: <141109105139.ZM27532@torch.brasslantern.com> (raw)
In-Reply-To: <20141108204123.1fcc698e@pws-pc.ntlworld.com>
On Nov 8, 8:41pm, Peter Stephenson wrote:
}
} It's not worth factoring out the common code; it would need a whole
} heap of options passing in, passing back a value ignored in one case,
} passing in both a string and a pattern where only one is used each
} time... Unless someone else can see a neater way. Anyway, I will
} commit this and someone else can apply their elegant optimisations.
Cf. 33656.
} The results would look better with a bit more sorting, but that's a
} separate issue.
With 33653:
torch% noglob whence -m zsh*
/usr/local/bin/zsh
/usr/local/bin/zsh-5.0.2-dev-0
/usr/local/bin/zsh-5.0.3
/usr/local/bin/zsh-5.0.4
/usr/local/bin/zsh-5.0.5
/usr/local/bin/zsh-5.0.7
/usr/local/bin/zsh.old
/etc/zshenv
/etc/zshrc
torch% noglob whence -am zsh*
/usr/local/bin/zsh-5.0.7
/usr/local/bin/zsh-5.0.3
/usr/local/bin/zsh
/usr/local/bin/zsh-5.0.4
/usr/local/bin/zsh.old
/usr/local/bin/zsh-5.0.5
/usr/local/bin/zsh-5.0.2-dev-0
/bin/zsh
torch%
We've lost /etc/zshenv and /etc/zshrc in the -a case. This isn't wrong,
because they're filtered out by iscom(). However:
torch% whence -mv zshenv
zshenv is /etc/zshenv
torch% whence -av zshenv
zshenv not found
torch% whence -amv zshenv
torch%
With 33656 the output of -amv is the same as -av in this latter case
(both print "zshenv not found"). Yes, an "else" could be added to the
"if (iscom(...))" in 33653 to get the "not found", but 33656 also
produces the -m sort order for -am when there is more than one match.
--
Barton E. Schaefer
next prev parent reply other threads:[~2014-11-09 18:51 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 [this message]
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
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=141109105139.ZM27532@torch.brasslantern.com \
--to=schaefer@brasslantern.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).