zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: PATH: autoload with explicit path
Date: Mon, 16 Jan 2017 10:37:08 +0000	[thread overview]
Message-ID: <20170116103708.46d2ee66@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20170113180423.12225591@pwslap01u.europe.root.pri>

On Fri, 13 Jan 2017 18:04:23 +0000
Peter Stephenson <p.stephenson@samsung.com> wrote:
> On Wed, 11 Jan 2017 20:51:22 +0000
> Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> > With a bit of work this can be expanded to paths for already loaded
> > functions, and possibly elsewhere though I think the pickings are
> > a lot smaller.
> 
> This does the former of that --- it was less work than I expected.
>...
> The only significant extra requirement is use of the heap to get the
> filename in "whence -v" --- that's a bit of laziness, we could just print
> out the components using the same logic as getshfuncfile().  Might fix
> that later.

I fixed this up when I pushed it.  One very minor change is that to
avoid the intermediate string quotedzputs() now runs separately on the
directory and the filename, e.g.

% whence -v my\ stupid\ function\ name
my stupid function name is a shell function from /export/home/pws/src/zsh-git/code/'my stupid function name'

You might even consider that a feature.

pws


  reply	other threads:[~2017-01-16 10:37 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11 22:18 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 [this message]
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
2017-01-18  9:53         ` Peter Stephenson
     [not found] <CGME20170127151334epcas2p4c32b57f69fcae22b40b309793eb8ceb6@epcas2p4.samsung.com>
2017-01-27 15:12 ` PATH: " Sebastian Gniazdowski
2017-01-27 16:24   ` Peter Stephenson
2017-01-27 18:40     ` Sebastian Gniazdowski
2017-01-27 18:44       ` Peter Stephenson
2017-01-27 19:00         ` Sebastian Gniazdowski
2017-01-28 18:05         ` Bart Schaefer
2017-01-28 19:12           ` Peter Stephenson
2017-01-28 19:45             ` Bart Schaefer
2017-01-28 19:56               ` Peter Stephenson
2017-01-28 20:37                 ` Sebastian Gniazdowski
2017-01-29 12:27             ` Sebastian Gniazdowski
2017-01-29 16:11               ` Bart Schaefer
2017-01-29 17:32                 ` Sebastian Gniazdowski
2017-01-29 18:37                   ` Bart Schaefer
2017-01-29 21:53                     ` Vin Shelton
2017-01-30 10:06                       ` Peter Stephenson
2017-01-29 17:58                 ` Peter Stephenson
2017-01-30 11:37                   ` Sebastian Gniazdowski
2017-01-30 11:55                     ` Peter Stephenson

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=20170116103708.46d2ee66@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).