zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: completion but extra options allowed
Date: Mon, 14 Feb 2000 12:56:23 +0100 (MET)	[thread overview]
Message-ID: <200002141156.MAA10295@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Fri, 11 Feb 2000 17:55:55 +0000


[ moved to zsh-workers ]

Bart Schaefer wrote:

> ...
>
> Yes, I noticed just after posting that this isn't actually handled by
> _mutt and _mailboxes.  In attempting to do something with this, I found
> some rather strange things going on in the guts of the completion.
> 
> _mutt calls _arguments in the expected way.
> 
> _arguments calls "_description arguments expl mailbox" which sets expl
> to (-J -default-).
> 
> _arguments then calls "_mailboxes -J -default-" which (after setting up
> the cache) calls "_wanted files expl 'mailbox specification'" which again
> sets expl to (-J -default-).
> 
> _mailboxes then calls "compadd -J -default- -J -default- - ..." which
> seems a bit odd.  The first -J -default- is from "$@" and the second is
> of course "$expl[@]".  Is that really doing the right thing?

1) Depending of the setting of the group-name style you may have gotten
different names.
2) Yes, that's ok. The _description in _mailboxes sets up a default
description that may be overridden by a calling function.
3) Depending on the implementors preferences, he may or may not change 
the '-f+:mailbox:_mailboxes' to '-f+:mailbox: _mailboxes', which will
make _arguments *not* give a description to _mailboxes (i.e., then you 
only get the second one).


In another message:

> ...
> 
> One thing that makes this difficult is that _path_files does not accept
> the -i option of compadd, only the -P option.

All completion I can think of are written so that they work nicely
when PREFIX/IPREFIX (and SUFFIX/ISUFFIX) are set up appropriately.

> However, even calling
> 
> compadd -i + -f -W ~/Mail
> 
> directly does not accomplish what I expected it to.  Is this a bug, or am
> I missing something?  What IS the compadd equivalent of
> 
> compctl -x 's[+] c[-1,-f],s[-f+]' -W ~/Mail -f ...

-i just *adds* some string to IPREFIX. It is really only useful when
used with -U, i.e. by functions that have to do all the matching
themselves (because then IPREFIX isn't used by the completion code and 
-i can be used to tell it about an ignored prefix).

So, the right way to do the same as that compctl would be:

  if compset -P '+|-f+' || [[ $words[CURRENT-1] = -f ]]; then
    _files -W ~/Mail
  else
    ...
  fi

where the compset sets up PREFIX/IPREFIX for us.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-14 11:56 Sven Wischnowsky [this message]
     [not found] ` <20000210153411.A27005@fruitcom.com>
     [not found]   ` <1000210175857.ZM6927@candle.brasslantern.com>
     [not found]     ` <20000210195143.A26109@br-online.de>
2000-02-11 18:45       ` Bart Schaefer
     [not found]       ` <1000211175555.ZM32309@candle.brasslantern.com>
     [not found]         ` <20000214150010.B17427@br-online.de>
2000-02-14 15:11           ` Completion for mutt Ollivier Robert
2000-02-14 17:21             ` Bart Schaefer

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=200002141156.MAA10295@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).