From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: "whence -v" and function file names
Date: Sun, 17 May 2015 18:44:40 -0700 [thread overview]
Message-ID: <150517184440.ZM32461@torch.brasslantern.com> (raw)
In-Reply-To: <5558FF85.1060400@thequod.de>
On May 17, 10:52pm, Daniel Hahler wrote:
} Subject: Re: "whence -v" and function file names
}
} % whence -v _git
} _git is an autoload shell function
} % git <tab>
} % whence -v _git
} _git is a shell function
}
} It would be nice if it could provide the path, at least with the second call.
Yes, that would be nice, but the code that loads the function definition
does not record the path and I didn't see any simple way to cause it to
do so. I wasn't in this to rewrite autoloading, so you get what's there
at the time "whence" is invoked.
next prev parent reply other threads:[~2015-05-18 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 19:51 Bart Schaefer
2015-05-17 20:52 ` Daniel Hahler
2015-05-18 1:44 ` Bart Schaefer [this message]
2015-05-18 2:31 ` Mikael Magnusson
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=150517184440.ZM32461@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).