zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: context names
Date: Fri, 11 Feb 2000 19:16:46 +0000	[thread overview]
Message-ID: <E12JLVf-0003L0-00.2000-02-11-19-13-47@mail6.svr.pol.co.uk> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Thu, 03 Feb 2000 14:59:31 +0100." <200002031359.OAA13490@beta.informatik.hu-berlin.de>

Sorry, this is over a week old now.  I queued it up for sending and didn't
reconnect, and I've been away again for most of this week.  I think it's
still pertinent.

Sven Wischnowsky wrote:
> 
> This makes context names (in the completion system) consistent (I
> hope). The format is always:
> 
>   :completion:<func>:<completer>:<command>:<argument>:<tag>

First point.

Fine, except that now we have to contend with builtin defaults like...

zstyle ':completion:*::::' completer _complete
zstyle ':completion:*::::default' list-colors 'no=0' ...
 
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?

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.


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.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>


  reply	other threads:[~2000-02-11 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-03 13:59 Sven Wischnowsky
2000-02-11 19:16 ` Peter Stephenson [this message]
2000-02-14 10:34 Sven Wischnowsky
2000-02-15  9:02 Sven Wischnowsky
2000-02-15  9:18 Sven Wischnowsky

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=E12JLVf-0003L0-00.2000-02-11-19-13-47@mail6.svr.pol.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --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).