unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@CS.UCLA.EDU>
Subject: Re: dired-move-to-filename-regexp
Date: Thu, 23 Sep 2004 11:27:39 -0700	[thread overview]
Message-ID: <87llf0den8.fsf@penguin.cs.ucla.edu> (raw)
In-Reply-To: <E1CAWip-0006Kj-Mu@fencepost.gnu.org> (Richard Stallman's message of "Thu, 23 Sep 2004 12:45:31 -0400")

Richard Stallman <rms@gnu.org> writes:

> I think a better solution is if we can turn off the new "feature"
> of adapting the column widths to the data.

One way would be to extend --format to allow fairly arbitrary formats
that can specify column widths.  For example, Emacs could do this:

  ls --format='%11m %2l %8o %8g %7s %12d %f'

to have "ls" list the mode, link, owner, group, size, date, and file
name in the traditional widths for "ls -l".  This would resemble the
way "ls --time-style" already handles date formats.

Another possibility is to have a new option to disable the new
feature, e.g. "ls --traditional-column-widths".  This would be a bit
easier to implement, but would be less general and might have problems
of its own (e.g., users and implementations don't agree on what the
traditional widths are).

I understand that some non-GNU ls implementations also adapt column
widths to data, so the Emacs problem would remain with these
implementations, regardless of how we change GNU ls.

  parent reply	other threads:[~2004-09-23 18:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-19  7:44 dired-move-to-filename-regexp Lars Hansen
2004-09-19  8:20 ` dired-move-to-filename-regexp Paul Eggert
2004-09-20  0:05   ` dired-move-to-filename-regexp Richard Stallman
2004-09-20  4:49     ` dired-move-to-filename-regexp Paul Eggert
2004-09-20  5:00       ` dired-move-to-filename-regexp Miles Bader
2004-09-21 18:30         ` dired-move-to-filename-regexp Richard Stallman
2004-09-22  6:09           ` dired-move-to-filename-regexp Paul Eggert
2004-09-23 16:45             ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 17:57               ` dired-move-to-filename-regexp Stefan Monnier
2004-09-24 23:40                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-25  5:20                   ` dired-move-to-filename-regexp Stefan
2004-09-25 15:36                     ` dired-move-to-filename-regexp Richard Stallman
2004-09-25 19:08                       ` dired-move-to-filename-regexp Stefan
2004-09-26 18:19                         ` dired-move-to-filename-regexp Richard Stallman
2004-09-29  3:17                           ` dired-move-to-filename-regexp Stefan
2004-09-23 18:27               ` Paul Eggert [this message]
2004-09-24 23:40                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 23:27               ` dired-move-to-filename-regexp Miles Bader
2004-09-24 23:41                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-27  3:34                   ` dired-move-to-filename-regexp Miles Bader
2004-09-24  5:51               ` dired-move-to-filename-regexp Jim Meyering
2004-09-25  7:08                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-21 18:30       ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 18:59     ` dired-move-to-filename-regexp Lars Hansen
2004-09-24 23:40       ` dired-move-to-filename-regexp Richard Stallman
2004-09-20  6:11   ` dired-move-to-filename-regexp Lars Hansen
2004-09-20 23:28     ` dired-move-to-filename-regexp Paul Eggert

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87llf0den8.fsf@penguin.cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).