zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Borzenkov Andrey <Andrey.Borzenkov@siemens.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: Passsing descriptions down in completion functions
Date: Thu, 09 Jan 2003 17:11:34 +0100	[thread overview]
Message-ID: <32584.1042128694@finches.logica.co.uk> (raw)
In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5CF@MOWD019A>

On 9 Jan, you wrote:
> 
> Sure, I understand that. We already discussed it and I still think that
> instead of modifying every completion function _all_labels should just check
> for existing options and not add them (are there more than just -X? As I

-J and perhaps also -V, -E, -1 and -2. It'd be hard to know which to
check for.

> understand the only options that can be modified by _all_labels are those
> used for explanations. It does not look all that simple after reviewing
> _all_labels but it should be doable).

There are cases where you do want to override any passed descriptions
such as where a function completes something in parts (e.g. in _urls)
but you might want to pass on other options. I'm not too sure about
your suggested change to _all_labels because the result would be less
flexible. If you wanted a solution like that, it might be better to
always add explanations to the end of the options unless some option
was passed to _all_labels. I think the current system is simpler but
will concede that modifying all the functions will be a bore. I'll
volunteer for the job if we agree on doing that though.

> The general question - should completion functions ever accept (be used
> with) other options than compadd? If not the above is perfectly valid and
> probably more simple that modifying every single function. If yes, here is
> the list of functions that use _wanted without '-'.

Quite a few functions accept non compadd options though zparseopts can
easily strip them before they get passed to compadd. Provided they
don't conflict, I don't see a problem with this.

Oliver

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.


  reply	other threads:[~2003-01-09 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 13:17 Borzenkov Andrey
     [not found] ` <32149.1042120127@finches.logica.co.uk>
2003-01-09 14:04   ` Oliver Kiddle
2003-01-09 15:09   ` Borzenkov Andrey
2003-01-09 16:11     ` Oliver Kiddle [this message]
2003-01-09 16:26 Borzenkov Andrey
2003-01-09 17:09 ` Oliver Kiddle
2003-01-10  8:10   ` Borzenkov Andrey
2003-01-14 15:43     ` 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=32584.1042128694@finches.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=Andrey.Borzenkov@siemens.com \
    --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).