From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: wordcode files
Date: Thu, 2 Mar 2000 16:43:23 +0000 [thread overview]
Message-ID: <1000302164323.ZM15688@candle.brasslantern.com> (raw)
In-Reply-To: <200003021003.LAA12189@beta.informatik.hu-berlin.de>
On Mar 2, 11:03am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: wordcode files
}
} I wrote:
}
} > Bart Schaefer wrote:
} >
} > > This all sounds fine, although I lean towards requiring that the .zwc
} > > extension appear in the $fpath listing. What happens, for example, if
} > > I have both a ~/zshfun/ and ~/zshfun.zwc and I list ~/zshfun in $fpath?
} >
} > You get the functions in ~/zshfun because you named that. But we can
} > change that to be more consistent (I mean: requiring the extension).
}
} This'll do?
I'm not exactly sure. It looks like that patch forces zcompile to tack
the .zwc extension on to the end of the name (and to only look for
wordcode in files that have the .zwc extension). Is that right?
That's fine, but ...
How does that help with the situation where I have a directory named
"foo" and a file named "foo.zwc" both within the same parent directory?
What *I* meant was, fpath=(foo) would look only for directories named
"foo", so I'd have to use fpath=(foo.zwc) if I really wanted the file;
but if there was a file foo/func.zwc then "autoload func" would still
find it. That's independent of whether a non-.zwc file might contain
wordcode.
However, I don't have a strong opinion. Anyone else?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-03-02 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-02 10:03 Sven Wischnowsky
2000-03-02 16:28 ` Bart Schaefer
2000-03-02 16:43 ` Bart Schaefer [this message]
2000-03-02 17:52 ` Zefram
-- strict thread matches above, loose matches on Subject: below --
2000-03-09 9:37 Sven Wischnowsky
2000-03-02 9:09 Sven Wischnowsky
2000-03-03 4:09 ` Bart Schaefer
2000-03-01 16:00 Sven Wischnowsky
2000-03-01 10:06 Sven Wischnowsky
2000-03-01 15:24 ` Tanaka Akira
2000-03-01 16:58 ` Bart Schaefer
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=1000302164323.ZM15688@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).