From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Completing parameter names that have yet to be set.
Date: Fri, 11 Aug 2000 09:54:01 +0200 (MET DST) [thread overview]
Message-ID: <200008110754.JAA09690@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Felix Rosencrantz's message of Thu, 10 Aug 2000 23:30:09 -0700 (PDT)
Felix Rosencrantz wrote:
> Since there is some talk about parameter completion... I've had a
> custom version of _parameter for some time that I've been meaning to
> document and submit. The customization was that it could complete
> parameters that were not yet set. Using a style, the user specifies a
> list of parameters that they want zsh to know about to complete.
>
> For example, with the zsh distribution there is the TESTNUM environment
> variable, which can be used to specify a subset of the zsh tests when
> running "make check" . However, most of the time this environment
> variable is unset. I can't always remember the special variable. So
> it's nice that zsh completion can.
That's why I gave the `fake' style such a generic name. Although that
probably wasn't so clever, because the value-formats may have to
differ for different types of completions to fake.
> I think it would be useful if the style specification allowed for descriptions
> of these parameters. The descriptions could be used for parameters that
> are already set. Though I'm not sure how to do this (with _values?).
`fake' doesn't allow this yet (and the way it is used makes it hard
(and probably a bit ugly, code-wise) to implement it there). But of
course one can always do it with tag-labels and ignored-patterns.
> ...
>
> It seems like the ability to tell zsh of words that can't be found by
> querying the system (e.g. these parameter names, files that don't exist
> yet, etc. ) would be useful. I was thinking that it would be useful
> to add some generic code that would (maybe a completer). Maybe using
> the new cache system. The code would allow the user to specify a set of
> words to be tossed in with the words that standard completion functions
> complete. I'm not sure what would be a good solution. This is more
> meant to provoke some response/thought by the completion gurus.
Given that the faked completions depend on the contexts, the type of
completions and the user's preferences, I don't know how a function
could help here. Maybe we'll just have to use `fake' (or several
`fake-this-or-that' styles that replace `fake'), get some experience
with it and then find out if and how we can improve it. And if it's
needed.
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-08-11 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-11 7:54 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-06 7:41 Sven Wischnowsky
2000-09-06 7:00 Felix Rosencrantz
2000-08-14 8:03 Sven Wischnowsky
2000-08-14 8:01 Sven Wischnowsky
2000-08-14 5:51 Felix Rosencrantz
2000-08-14 7:15 ` Bart Schaefer
2000-08-11 6:30 Felix Rosencrantz
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=200008110754.JAA09690@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).