From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: completion caching layer
Date: Wed, 2 Aug 2000 16:13:29 +0200 (MET DST) [thread overview]
Message-ID: <200008021413.QAA11687@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Adam Spiers's message of Wed, 2 Aug 2000 14:35:07 +0100
Adam Spiers wrote:
> Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
> > It's a bit unfortunate that _cache_invalid can be called twice (in
> > your examples), once directly and once from _retrieve_cache. I think.
>
> Yes, I didn't like that either, but couldn't think of a better
> design. The problem is that there are actually two caching layers -
> the parameters, and the cache files on disk, but the _cache_invalid
> check needs to be invoked if either is about to be used. Suggestions
> for how to avoid this welcome.
Couldn't we stuff everything in _retrieve_cache? So that one only
needs to call:
if ! _retrieve_cache RPMs _rpms; then
_rpms=(...)
_store_cache RPMs _rpms
fi
> ...
>
> > About the lookup: I /think/ it would be more convenient if the type of
> > information cached would appear in the context, so that you could say
> > `zstyle ":completion:*:rpms" cache-policy ...'. Haven't really played
> > with it yet, though.
>
> I agree entirely. That way also I could make _perl_modules set a
> default style (if one is not already set) when the function is loaded,
> rather than each time it's invoked. But where would it appear in the
> context? My knowledge of this stuff is slightly weak, I'm afraid.
After the last colon:
zstyle -t ":completion:${curcontext}:" ...
^here
I.e., instead of the tag (if you would use tags). One problem is your
naming scheme (upper-case) which is different from what we've used so
far.
And then the tags should be documented, or similar tags which are
already used elsewhere could be used for caching.
> > And another thing: with `zstyle -e' one could use a boolean style
> > `cache-invalid' or whatever and let the user do the rest. It's hard to
> > give arguments to that, though. Other than by documenting
> > $_cache_path, that is.
>
> I think I understand that, but how would it be better than the current
> system?
Maybe hopefully consistency(?) I'm not too sure about this either,
since there are still other styles which allow to give names of
functions to be called (tag-order, for example).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-08-02 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 14:13 Sven Wischnowsky [this message]
2000-08-02 15:01 ` Adam Spiers
2000-08-03 12:21 ` Adam Spiers
-- strict thread matches above, loose matches on Subject: below --
2000-08-04 6:59 Sven Wischnowsky
2000-08-03 7:11 Sven Wischnowsky
2000-08-02 9:36 Sven Wischnowsky
2000-08-02 13:35 ` Adam Spiers
2000-07-27 8:00 Sven Wischnowsky
2000-08-01 16:31 ` Adam Spiers
2000-08-01 17:03 ` Bart Schaefer
2000-08-01 17:09 ` Bart Schaefer
2000-08-01 23:37 ` Adam Spiers
2000-08-02 3:53 ` Bart Schaefer
2000-07-19 14:48 Sven Wischnowsky
2000-07-26 19:53 ` Adam Spiers
2000-07-17 14:38 Adam Spiers
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=200008021413.QAA11687@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).