From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: Wordcode files and compinit
Date: Fri, 24 Mar 2000 13:05:36 +0100 (MET) [thread overview]
Message-ID: <200003241205.NAA25922@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Fri, 24 Mar 2000 14:31:23 +0300
Andrej Borsenkow wrote:
> > Hm. The wordcode files already store the complete pathnames used when
> > calling zcompile. That could be changed to prepend $PWD to names not
> > starting with a slash. Then we could change the patch for
> > `autoload -w'
> > to make `autoload -w foo.zwc a b c' mark only a, b and c for
> > autoloading. And then we could make `autoload -mw foo.zwc
> > "*/Completion/Debian/*"'
> > mark only those functions for autoloading.
>
> This won't help in case of completion.
It isn't possible any more anyway (because of `zcompile -c ...').
> We need the information from
> comments and comments are lost when compiling zsh code. With current way
> completion is initialized, functions must be present in source form. I
> am not happy about it.
I'm very happy with it. No way for anyone to give completion functions
(or any functions) without also giving the source code.
> Keeping two form of the same function always
> increases the possibility of two getting out of sync.
Have you had a look at the zrecompile function I sent? It should make
this simple. Also, the wordcode files could be organised in a way that
makes the source files be preferred when they are younger (just create
a wordcode file for each completion directory named like the directory
with a trailing `.zwc'). That would be less efficient than using one
big wordcode file, though (zrecompile can help with both approaches).
And anyway, the distributed functions will, from a user's or
administrator's point of view, be relatively stable.
Please also remember that in the part of my message which you didn't
quote I said that I hadn't thought about using wordcode files for a
package concept and that the above was just a quick thought...
I don't plan to think much more about the package stuff now, there are
other things higher on my lsit, so only another quick thought: we
could enhance the wordcode file format to allow user's to store extra
information for each function...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-03-24 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-24 12:05 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-14 10:40 Sven Wischnowsky
2000-03-24 11:31 ` Andrej Borsenkow
2000-03-14 10:30 Andrej Borsenkow
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=200003241205.NAA25922@beta.informatik.hu-berlin.de \
--to=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).