zsh-workers
 help / color / mirror / code / Atom feed
From: "Richard Hartmann" <richih.mailinglist@gmail.com>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: "Zsh hackers list" <zsh-workers@sunsite.dk>
Subject: Re: Feature suggestion for autoload
Date: Thu, 17 Jul 2008 01:44:33 +0200	[thread overview]
Message-ID: <2d460de70807161644u483c2c33l53734590710102d6@mail.gmail.com> (raw)
In-Reply-To: <080715183948.ZM10577@torch.brasslantern.com>

On Wed, Jul 16, 2008 at 03:39, Bart Schaefer <schaefer@brasslantern.com> wrote:


>    fpath+=(thedirectory)
>    autoload thedirectory/*(:t)

Peter's snippet is

  autoload -- ~/.zfunc/[^_]*(:t)

It was the part with not loading files that have a leading underscore that
eluded me.


>    fpath+=(thedirectory)
>    cd thedirectory
>    autoload *
>    cd -

True, but that's not as elegant as the above. As it was not time critical,
I prefered not to 'hack' something up.


> "autoload" is just an alias for "typeset -fu" ... I'm excited neither
> about making it a separate implementation nor about teaching typedef
> how to read directories.

Good reason, agreed.


> "Finds" where?

What I meant was 'autoload every file you find in fpath'. That suggestion
is moot now, though.


> Yes, you can certainly do that.  There's no practical limit on the
> number of function names you can pass to a single autoload command.

Brain fart, of course you can. Sorry.


Thanks,
Richard


  reply	other threads:[~2008-07-16 23:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 17:10 Richard Hartmann
2008-07-16  1:39 ` Bart Schaefer
2008-07-16 23:44   ` Richard Hartmann [this message]
2008-07-17  0:55     ` Phil Pennock
2008-07-17  9:05     ` Peter Stephenson
2008-07-17 13:24       ` Richard Hartmann
2008-07-17 13:43         ` Bart Schaefer
2008-07-17 14:33           ` Richard Hartmann

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=2d460de70807161644u483c2c33l53734590710102d6@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@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).