From: Peter Whaite <peta@cortexmachina.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Picky criticism of ls completion list formatting
Date: Thu, 28 Jun 2001 15:49:27 -0400 [thread overview]
Message-ID: <200106281949.PAA16170@aragorn.cortexmachina.com> (raw)
In-Reply-To: Message from Peter Stephenson <pws@csr.com> of "Thu, 28 Jun 2001 17:57:42 BST." <Tc0a88d01546c9e1632@mailsweeper01.cambridgesiliconradio.com>
Peter Stephenson said:
> "Bart Schaefer" wrote:
> > On Jun 28, 12:21pm, Peter Whaite wrote:
> > } Subject: Picky criticism of ls completion list formatting
> > }
> > } Listing completions for 'ls' uses more lines because it formats using
> > } one less column.
> >
> > Try `setopt list_packed'. If that doesn't make a difference, then there
> > may be something wrong with the "packing" code that we need to look at.
>
> list_packed still uses three spaces between columns, it just varies the
> column widths. It might be time to make the column spacing configurable.
> Presumably that's not too hard.
Yes list_packed made a satisfactory difference.
OK I see. The (GNU) ls algorithm uses variable column widths separated with 2
spaces, whereas zsh by default uses the same column width for all the columns
separated by 3 spaces. List_packed makes the widths variable but still keeps
the spacing of 3.
Configurable spacing sounds good sometime. I assume 3 was for readability,
but 2 or 1 is better to conserve space. TeXish stretch and shrink?
---
peta
next prev parent reply other threads:[~2001-06-28 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 16:21 Peter Whaite
2001-06-28 16:50 ` Bart Schaefer
2001-06-28 16:57 ` Peter Stephenson
2001-06-28 19:49 ` Peter Whaite [this message]
2001-06-29 2:35 ` Bart Schaefer
2001-06-29 7:13 ` Sven Wischnowsky
2001-06-29 8:33 ` Bart Schaefer
2001-06-29 8:37 ` Sven Wischnowsky
2001-06-29 8:27 ` Alexandre Duret-Lutz
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=200106281949.PAA16170@aragorn.cortexmachina.com \
--to=peta@cortexmachina.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).