zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Option description and _oldlist
Date: Mon, 13 Sep 1999 14:25:03 +0200 (MET DST)	[thread overview]
Message-ID: <199909131225.OAA21121@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Thu, 9 Sep 1999 19:38:51 +0400


Andrej Borsenkow wrote:

> bor@itsrm2:/tools/src/ntp-4.0.97f%> zsh -f
> itsrm2% autoload compinit; compinit
> itsrm2% compconf group_matches=yes message_format='%d' description_format='%d' d
> escribe_options=yes
> itsrm2% xterm -f<TAB><TAB>
> option
> -fb           -fi           -font
> -fg           -fn           -foreground
> 
> As I understand, the description is expected on the status line? When I move
> from option to option in menu completion?

(Maybe this is clear already, I just wanted to mention the thing
below...)

No, they are displayed with the matches.

...interesting idea, however.

> And one more strange thing (assuming the zsh from above):
> 
> itsrm2% zmodload complist
> itsrm2% SELECTMIN=0
> itsrm2% compconf completer=_oldlist:_complete
> itsrm2% patch --s<TAB> ... till you get
> 
> itsrm2% patch --suffix=
> option
> --set-time   --set-utc    --strip      --suffix
> 
> ENTER -> --suffix is not highlighted
> TAB ->
> 
> itsrm2% patch --set-time
> option
> 
> TAB ->
> 
> itsrm2% patch --set-utc
> option
> --set-time   --set-utc    --strip      --suffix

(...this one.)

This is one of the things I dislike about the behavior of `_arguments -s':
to be able to display the prefix character and still complete single
letter options, we have to use display lists whenever `-s' is
used. It's just that in cases like this one you simply don't see that
it's a display list -- looking like a normal list of matches.
Since I really don't want to list options without the prefix character 
(I could live with a config key turning that on/off, of course), we
would need something else here. Which brings me back to thinking about 
a (set of) option(s) for `compadd' that allows us to give display
strings per match. With such display strings we could use menu-selection
(but we can't use menu-selection with the display lists we have now,
because the completion code can't find out if there is a one-to-one
correspondence between the elements of the display list and the
matches, so it doesn't know which one to highlight).
Implementing display strings is probably not too hard. Maybe we could
even have different types: strings that should be listed in columns,
strings that should be listed one per line. Probably strings in which
the `%'-escapes are interpreted (and other types of strings where they 
aren't).

It would be nice to use them throughout the completion functions, then 
(in the functions using `ps' this would probably be a bit hairy, but I 
think still implemntable).


In another message:

> 3.1.6-pws-3 with patches up to 7750
> 
> bor@itsrm2:/tools/src/zsh-3.1.6-pws-3%> zsh -f
> itsrm2% autoload compinit
> itsrm2% compinit -D  
> itsrm2% bindkey -e
> itsrm2% ./configure --pre=/toTAB
> itsrm2% ./configure --prefix=/toTAB
> B-e-e-p
> 
> itsrm2% ls -d /to*
> /tools

I hope this is now solved, too. At least it works for me.


And in yet-another-message:

> In my case `patch --in=/' does not work either.
> 
> bor@itsrm2:~%> zsh -f
> itsrm2% autoload compinit; compinit -D
> itsrm2% patch --in=/<TAB>
> itsrm2% patch --input=/<TAB>
> B-e-e-p
> 
> This is 3.1.6-pws-3 with patches up to 7750
> 
> Note that both --dir or --output work; even `-i TAB' works as expected.

Can't help here either. My `patch' doesn't support `--input' and for
all other options it works.

Bye
 Sven


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


             reply	other threads:[~1999-09-13 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-13 12:25 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-09-09 13:54 Silly questions about _arguments & Co (and probably bugs) Tanaka Akira
1999-09-09 15:38 ` Option description and _oldlist Andrej Borsenkow

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=199909131225.OAA21121@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).