zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-users@sunsite.dk
Subject: Re: Completion function for bitkeeper?
Date: Fri, 14 Nov 2003 14:09:19 +0100	[thread overview]
Message-ID: <22727.1068815359@gmcs3.local> (raw)
In-Reply-To: <644.1068806872@csr.com>

Peter wrote:
 
> I don't think we *need* both, and the brace is clearer --- more to the
> point, use of the space is almost completely opaque, plus it's hard to
> search for in the documentation.  So switching the code makes sense.
> However, we might need a pointer in case people wonder about it, and
> since the documentation consists of one sentence it's not clear how much
> difference it makes to change it there (except to say it's deprecated).

Do we need to actually say it's deprecated? Can't we just remove that
part of the documentation and add a bit under the brace form about
expl. We can mention in the next release note and in a comment inside
_arguments that the feature is deprecated.

> What about a single unquoted space to indicate no matches?  Why do we
> need the space at all?  Surely if there's nothing there it indicates no
> possible matches?  It's all a bit Zen-like.

Yes, that's also pointless. Virtually nobody bothers to use it anyway.
Leaving the action empty is what most people have done (though varying
on whether to include the trailing colon). So we can get rid of that
from the documentation too.

I'll come up with a patch this weekend. Including finding all
the places we've used the initial space in existing functions.

Oliver


  reply	other threads:[~2003-11-14 13:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 16:00 Steve Borho
2003-05-23 16:01 ` Danek Duvall
2003-11-06 15:32   ` Danek Duvall
2003-11-07 19:17     ` Oliver Kiddle
2003-11-10 18:20       ` Danek Duvall
2003-11-11  8:22         ` Oliver Kiddle
2003-11-11 10:42           ` Peter Stephenson
2003-11-11 15:21             ` Oliver Kiddle
2003-11-11 15:24               ` Peter Stephenson
2003-11-11 16:13                 ` Oliver Kiddle
2003-11-11 16:23                   ` Peter Stephenson
2003-11-11 16:44                     ` Oliver Kiddle
2003-11-11 16:23           ` Danek Duvall
2003-11-11 19:06             ` Oliver Kiddle
2003-11-11 21:28               ` Danek Duvall
2003-11-14  8:04                 ` Oliver Kiddle
2003-11-14 10:47                   ` Peter Stephenson
2003-11-14 13:09                     ` Oliver Kiddle [this message]
2003-11-14 16:12                       ` Bart Schaefer
2003-11-14 16:23                         ` Peter Stephenson
2003-11-14 17:14                           ` Bart Schaefer
2003-11-14 17:01                         ` Oliver Kiddle
2003-11-14 15:46                   ` Danek Duvall
2003-11-14 21:24                     ` Danek Duvall
2003-11-17 15:47                     ` Oliver Kiddle
2003-11-17 17:51                       ` Danek Duvall
2003-11-19 10:23                         ` Oliver Kiddle

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=22727.1068815359@gmcs3.local \
    --to=okiddle@yahoo.co.uk \
    --cc=zsh-users@sunsite.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).