From: Ian Tegebo <ian.tegebo@gmail.com>
To: zsh-users@sunsite.dk
Subject: Re: Suggestion: Allow whence to report path(s) for autoloaded functions
Date: Sat, 25 Apr 2009 18:38:34 -0700 [thread overview]
Message-ID: <c21da7250904251838g65127233o1069284355a025b9@mail.gmail.com> (raw)
In-Reply-To: <090425125518.ZM13002@torch.brasslantern.com>
On Sat, Apr 25, 2009 at 12:55 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> I had something of an afterthought on this one ...
>
> On Apr 21, 2:14pm, Ian Tegebo wrote:
> }
> } It seems like 'whence -v _MYFUNC' is the intuitive place to look for
> } this behavior. I'd imagine it working like:
> }
> } $ whence -v _MYFUNC
> } _MYFUNC is a shell function defined in /blah/path/_MYFUNC
>
> This information could be misleading. Functions are not always loaded
> from $fpath; they can be defined in init files, edited and/or hand-
> entered on the command line, etc. To make whence useful, the shfunc
> structure would have to record where the function came from, or whence
> must only report the above if the function has NOT YET been loaded.
>
> There's also the question of what to do about files that are found in
> the $fpath directories but are not marked for autoloading.
>
> } Consequently, removing the '&& break' provides the expected result for
> } 'whence -a':
> }
> } $ whence -av _MYFUNC
> } _MYFUNC is a shell function defined in /blah/path_one/_MYFUNC
> } _MYFUNC is a shell function defined in /blah/path_two/_MYFUNC
>
> That's also misleading. If _MYFUNC were an executable located in two
> directories, it would be possible to explicitly choose which to run
> by typing the full path name as reported by whence. For a function,
> there's no [straightforward] way to bypass the fpath search order.
>
> (The non-straightforward way is to run
> FPATH=/blah/path_two:"$FPATH" _MYFUNC
> but that can produce unexpected results if _MYFUNC calls autoloaded
> functions that should come from /blah/path_one instead.)
>
Thanks for that.
Obviously, I didn't fully appreciate how specific my use case was (nor
did I know about the idiom Peter suggested). Now I realize I only
wanted a quick way to resolve a named file within a PATH-like
structure, and not the more general case about functions that my
suggestion implied.
--
Ian Tegebo
prev parent reply other threads:[~2009-04-26 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 21:14 Ian Tegebo
2009-04-22 8:29 ` Peter Stephenson
2009-04-25 19:55 ` Bart Schaefer
2009-04-26 1:38 ` Ian Tegebo [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=c21da7250904251838g65127233o1069284355a025b9@mail.gmail.com \
--to=ian.tegebo@gmail.com \
--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).