From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: context names
Date: Mon, 14 Feb 2000 11:34:23 +0100 (MET) [thread overview]
Message-ID: <200002141034.LAA09767@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Fri, 11 Feb 2000 19:16:46 +0000
Peter Stephenson wrote:
> ...
>
> and I still want to be able to override them with ':completion:*', which
> won't work because it's `less specific'. Is there an advantage for
> specifying all those colons here?
No.
> In any case, I'm gradually coming round to the view that the defaults for
> styles should be hard-wired into the functions (i.e. should be set as
> values internally if style retrieval failed). The big drawback is you
> can't see them with `zstyle'. However, they are almost always the
> simplest, most basic behaviour, so I don't think that's a big problem (they
> should of course be documented anyway). It's pretty normal for settings of
> any kind to have builtin defaults which you don't see. The benefits are
> presumably obvious: everything the user enters takes precedence, nothing
> bogus (that will never be used) shows up with zstyle, nothing needs
> deleting.
Right. I won't have enough time to do this now, I'll try it later...
> Second point.
>
> ^Xh always gives a context with no added trailing colon for the tag,
> e.g. `:completion::complete:echo:'. I presume we're retaining the feature
> of the old system that since tags weren't always useful, the relevant colon
> wasn't added. If we're now adopting the convention that all (other) colons
> always appear, then it might be more consistent to have the colon before
> the notional tag there too, so there would be six colons altogether, any
> time the completion context is used, with or without an actual tag at the
> end.
Oops. This was an oversight.
Bye
Sven
diff -ru ../z.old/Completion/Commands/_complete_help Completion/Commands/_complete_help
--- ../z.old/Completion/Commands/_complete_help Mon Feb 14 11:29:02 2000
+++ Completion/Commands/_complete_help Mon Feb 14 11:32:09 2000
@@ -12,7 +12,7 @@
for i in "${(@k)help_funcs}"; do
text="${text}
-tags in context :completion:${i}"
+tags in context :completion:${i}:"
for j in "${(@s.:.)help_funcs[$i][2,-1]}"; do
text="${text}${help_tags[${i}${j}]} (${j})"
done
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-02-14 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 10:34 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-15 9:18 Sven Wischnowsky
2000-02-15 9:02 Sven Wischnowsky
2000-02-03 13:59 Sven Wischnowsky
2000-02-11 19:16 ` Peter Stephenson
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=200002141034.LAA09767@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).