From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: autoload with explicit path
Date: Thu, 19 Jan 2017 09:39:13 +0000 [thread overview]
Message-ID: <20170119093913.27aa4211@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <alpine.LRH.2.00.1701181422530.4560@toltec.zanshin.com>
On Wed, 18 Jan 2017 14:26:12 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> I think the implied question was "Given that this works if I don't use
> an explicit path, why isn't there a way for it to work when I do want
> to give an explicit path? (Now that explicit paths work at all.)"
>
> Where "this works" means having a function name with a slash in it.
>
> I think it's a rather rare case that we may not want to bother with, but
> we've bothered with all sorts of other rarities.
I think the official answer is "well, you'll just have to lump it".
If there's a clear use case that someone needs we can no doubt find a
way. I hadn't even registered that this worked (with $fpath) until I
started looking.
pws
next prev parent reply other threads:[~2017-01-19 9:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 22:18 PATH: " Peter Stephenson
2016-12-12 16:05 ` Bart Schaefer
2016-12-12 16:31 ` Peter Stephenson
2016-12-12 18:09 ` Bart Schaefer
2017-01-10 19:31 ` Peter Stephenson
2017-01-11 11:42 ` Peter Stephenson
2017-01-11 20:51 ` Peter Stephenson
2017-01-12 20:42 ` Peter Stephenson
2017-01-13 18:04 ` Peter Stephenson
2017-01-16 10:37 ` Peter Stephenson
2017-01-16 15:04 ` Daniel Shahaf
2017-01-16 15:48 ` Peter Stephenson
2017-01-16 15:22 ` Bart Schaefer
2017-01-16 15:59 ` Peter Stephenson
[not found] ` <CAHYJk3SB1NDj6y5TRHHsAVsyjHfZQhTzMRzTR2c-SVEc9oAwzA@mail.gmail.com>
2017-01-24 11:10 ` Peter Stephenson
2017-01-11 21:13 ` Peter Stephenson
2017-01-17 18:36 ` PATCH: " Peter Stephenson
2017-01-17 22:17 ` Daniel Shahaf
2017-01-18 0:06 ` Bart Schaefer
2017-01-18 9:21 ` Peter Stephenson
2017-01-18 9:17 ` Peter Stephenson
2017-01-18 22:26 ` Bart Schaefer
2017-01-19 9:39 ` Peter Stephenson [this message]
2017-01-18 9:53 ` Peter Stephenson
[not found] <CGME20170112125605eucas1p1b2539afbacec2d28d44c6fd73b0d50af@eucas1p1.samsung.com>
2017-01-12 12:56 ` Peter Stephenson
2017-01-12 15:40 ` Daniel Shahaf
2017-01-12 15:59 ` Peter Stephenson
2017-01-12 16:09 ` Daniel Shahaf
2017-01-12 16:16 ` Peter Stephenson
2017-01-12 16:23 ` Daniel Shahaf
2017-01-12 16:34 ` Peter Stephenson
2017-01-12 16:05 ` Vin Shelton
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=20170119093913.27aa4211@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).