zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: About the new long/short options changes
Date: Fri, 20 Jul 2001 09:26:26 +0000	[thread overview]
Message-ID: <1010720092626.ZM6384@candle.brasslantern.com> (raw)
In-Reply-To: <200107200738.JAA09207@beta.informatik.hu-berlin.de>

On Jul 20,  9:38am, Sven Wischnowsky wrote:
} Subject: Re: About the new long/short options changes
}
} Bart Schaefer wrote:
} 
} > I mostly like the way it looks in listings, though I wish

Not so incidentally, Sven:  That praise sounds rather faint, so I want to
say that I really do think the stuff you come up with is quite amazing,
and I apologize for not saying so more often.

} > 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
} 
} ?

That would be fine, too; but as the current selection code highlights
both the option name and the description, I thought it might be easier
to split the display into only two kinds of columns:  Options for which
the descriptions have been suppressed because they're identical to some
other option, and the options that have that identical description.  On
some hunch that it might be easier to line up the rows that way.
 
} 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.

Yes, that is what I was thinking, though rather than dummy matches I
was thinking about chopping up the display into groups with different
columnations, as already happens when matches are explicitly added in
different groups.

} What are we coming to... ;-)

I'm not sure ...

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-07-20  9:28 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
2001-07-20  9:26   ` Bart Schaefer [this message]
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=1010720092626.ZM6384@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.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).