zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: vux/vuxctl completion
Date: Fri, 12 Mar 2004 11:00:03 +0100	[thread overview]
Message-ID: <29555.1079085603@trentino.logica.co.uk> (raw)
In-Reply-To: <20040311213540.GA907@scowler.net>

Clint Adams wrote:
> For vux 0.4.8.

> Index: Completion/Unix/Command/_vux
> +#compdef vux vuxctl
> +
> +case "$service" in
> +	(vux)

Sorry to winge about this but could we please have consistency on
indentation across completion functions. Convention is for two spaces.

> +
> +_arguments -s -C \
> +	'-x:action:(p g m w r f)' \

Those actions could really do with descriptions:
  '...:((p\:description g\:...))'
works.

> +	compadd start clean double half up down next previous forward \
> +		replay pause resume stop reload save history help

This should really have an _wanted before it. We should never be adding
matches without some sort of description.

> Index: Completion/Unix/Command/_mtr
> 
> +       '(--report)-r[report]' \
> +       '(-r)--report' \
> +       '(--report--cycles)-c[report cycles]:count:' \
> +       '(-c)--report-cycles:count:' \

Since in 4.1, matches are grouped where they have the same description,
it is much nicer to give the description to both the long and short
option. The convention is to do this with brace expansion:

  '(-r --report)'{-r,--report}'[report]' \
  '(-c --report-cycles)'{-c,--report-cycles}'[report cycles]:count' \

Except the descriptions could be rather more, um, descriptive.

Oliver


  reply	other threads:[~2004-03-12 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 21:35 Clint Adams
2004-03-12 10:00 ` Oliver Kiddle [this message]
2004-03-12 15:24   ` Clint Adams
2004-03-12 15:42   ` Clint Adams

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=29555.1079085603@trentino.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=zsh-workers@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).