From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Suggestion: Allow whence to report path(s) for autoloaded functions
Date: Sat, 25 Apr 2009 12:55:18 -0700 [thread overview]
Message-ID: <090425125518.ZM13002@torch.brasslantern.com> (raw)
In-Reply-To: <c21da7250904211414y609f2a62q426555c8feac39e@mail.gmail.com>
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.)
next prev parent reply other threads:[~2009-04-25 19:56 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 [this message]
2009-04-26 1:38 ` Ian Tegebo
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=090425125518.ZM13002@torch.brasslantern.com \
--to=schaefer@brasslantern.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).