From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: About the new long/short options changes
Date: Fri, 20 Jul 2001 09:38:04 +0200 (MET DST) [thread overview]
Message-ID: <200107200738.JAA09207@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <1010720050115.ZM6144@candle.brasslantern.com>
Bart Schaefer wrote:
> I mostly like the way it looks in listings, though I wish it would line up
> the single-letter options in a column (or else always list the short form
> first when there is one, though that might look odd when some of the long
> forms have no short form).
My only problem with that is that there may be cases where we have more
than two matches with the same description, something like:
--foo --Foo --fOO -- turn on fooing
--long-option -- turn on longing
If that gets out of hand... But then I don't know how often this will
happen at all.
> However, I strongly *dis*like the way it works in menu-selection. So much
> so that I'd rather just turn it off entirely if it can't be made to work
> better. In particular I don't want selection to consume twice as many
> lines (half of which are largely blank) as listing consumes. I find it
> better to have listing consume more lines in the first place than to have
> the display change so radically when switching from listing to selection.
I think you have seen from the discussion that I'm not happy about it,
too. One thing we could do is allow users to de-select the long/short
form as has been suggested (there is a slight problem with
auto-descriptions, btw).
The other is to try to implement what you and we prefer anyway:
> ...
>
> What I'd like to see, I think, is something like the following (where `['
> and `]' delimit the menu-selection highlight). For purposes of drawing
> a more interesting picure, suppose that the -X option doesn't exist.
>
> Completing option
> [--binary ] -b -- Unix line endings LF
> ...
>
> TAB to the next selection (list now truncated for brevity):
>
> Completing option
> --binary [-b -- Unix line endings LF ]
> ...
Really that or:
--binary [-b] -- Unix line endings LF
?
> After three more TABs:
>
> Completing option
> --binary -b -- Unix line endings LF
> --change-cygdrive-prefix -c -- cygdrive prefix
> [--cygwin-executable -- all files under mountpoint are cygwin e]
> ...
Same here.
I have some ideas how we could achive this, part of the stuff we need is
already there. Think of some combination of list-packed, list-rows-first
and `dummy' matches that get slots in the listing but show nothing and
can't be selected. We'll have to find a way to make this easy to select
and handle. I'll think about this at the weekend.
What are we coming to... ;-)
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-07-20 7:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 5:01 Bart Schaefer
2001-07-20 7:38 ` Sven Wischnowsky [this message]
2001-07-20 9:26 ` Bart Schaefer
2001-07-20 9:43 ` Andrej Borsenkow
2001-07-25 8:49 ` Sven Wischnowsky
2001-07-25 9:15 ` Borsenkow Andrej
2001-07-25 9:20 ` Sven Wischnowsky
2001-07-25 9:24 ` Borsenkow Andrej
2001-07-25 10:13 ` Peter Stephenson
2001-07-25 10:43 ` Sven Wischnowsky
2001-07-25 11:36 ` Borsenkow Andrej
2001-07-25 12:16 ` Sven Wischnowsky
2001-07-25 12:35 ` Sven Wischnowsky
2001-07-25 17:49 ` Bart Schaefer
2001-07-27 12:53 ` Sven Wischnowsky
2001-07-30 8:22 ` Sven Wischnowsky
2001-07-30 8:38 ` Sven Wischnowsky
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=200107200738.JAA09207@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).