zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: autoload with explicit path
Date: Wed, 18 Jan 2017 14:26:12 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.00.1701181422530.4560@toltec.zanshin.com> (raw)
In-Reply-To: <20170118091717.68edeb96@pwslap01u.europe.root.pri>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 860 bytes --]

On Wed, 18 Jan 2017, Peter Stephenson wrote:

> On Tue, 17 Jan 2017 22:17:54 +0000
> Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > Suppose $^fpath/foo/bar(N) has two matches, how do I explicitly autoload
> > the second one?  I.e., how do I disambiguate «autoload foo/bar» (with no
> > leading slash) to load a particular copy of foo/bar?
>
> You don't; the mechanism only applies to the last path component so it
> will pick the latest version of "bar".

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.

  reply	other threads:[~2017-01-18 22:26 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 [this message]
2017-01-19  9:39               ` Peter Stephenson
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=alpine.LRH.2.00.1701181422530.4560@toltec.zanshin.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).