From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Whaite <peta@cortexmachina.com>,
zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Picky criticism of ls completion list formatting
Date: Fri, 29 Jun 2001 02:35:38 +0000 [thread overview]
Message-ID: <1010629023538.ZM8673@candle.brasslantern.com> (raw)
In-Reply-To: <200106281949.PAA16170@aragorn.cortexmachina.com>
On Jun 28, 3:49pm, Peter Whaite wrote:
}
} Peter Stephenson said:
} >
} > 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.
}
} 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.
This is not the behavior I see.
With
listpacked off
listtypes on
I get equally-sized columns with three spaces between.
With
listpacked on
listtypes on
I *still* get equally-sized columns with three spaces between.
With
listpacked on
listtypes off
I get differently-sized columns with *two* spaces between.
Finally, with
listpacked off
listtypes off
I get equally-sized columns with *two* spaces between.
--
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
next prev parent reply other threads:[~2001-06-29 2:37 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
2001-06-29 2:35 ` Bart Schaefer [this message]
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=1010629023538.ZM8673@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).