unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: RE: dired-details: show/hide file details in Dired
Date: Wed, 4 Jul 2007 13:00:17 -0700	[thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACIEDBCAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1I68NC-0002mt-Ie@fencepost.gnu.org>

> Thank you for sending the code.  I got the other code, too,
>     fit-frame.el
>     autofit-frame.el
>     dired-details.el
>
> which looks to be needed to test the library.

No, not really. As I said, the frame-fitting part is optional. The `require'
is soft (no error if not found), and if you do not have the *-frame.el
libraries, the Dired hide/show code still works just fine. I use non-nil
pop-up-frames, so frame fitting is important to me, but it is not necessary
for the other features provided by dired-details+.el. You can no doubt
imagine that without frame fitting not much would be gained by removing
Dired details: the frame would occupy just as much screen real estate as for
the detailed listing.

dired-details.el is required because dired-details+.el is just a tweak for
it.

> You forgot to create the variable dired-details-state; I put
>     (setq dired-details-state nil)
> at the beginning of dired-details+.el and have not had any trouble
> since.

No, I didn't forget to create that variable. dired-details+.el is just a
tweak on top of dired-details, which defines `dired-details-state' with
`defvar'. If I had written dired-details, then I would have just modified it
directly, instead of creating a separate tweak library.

> It seems to work on a short test; however, I do like the long listing
> that dired provides, I especially find it important to see permission,
> owners, size, and date, as well name.  And I hardly ever use frames.
>
> So for me, all this would be useless.  But others operate differently.

I understand. Use of this feature would be optional. As with all options,
not every Emacs user will find it useful. As always, it depends on your own
usage patterns. It can even depend on your operating system. I am often on
M$ Windows these days, so I often don't need to bother with the file
permissions, for instance.

I don't claim that everyone will find this useful. I do, and I'm glad that
Rob wrote it. I keep my Dired buffers with the file-name-only display 90% of
the time. YMMV. And, besides being optional, you have a toggle to change the
display. I too "like the long listing that dired provides". I just like to
be able to also have a short listing.

Thanks for giving it a try and reporting what you found.

  reply	other threads:[~2007-07-04 20:00 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 12:55 [doug@bagley.org: Re: mouse-1-click-follows-link in dired surprising] Richard Stallman
2006-07-04 13:18 ` Chong Yidong
2006-07-04 17:40 ` [doug@bagley.org: Re: mouse-1-click-follows-link in diredsurprising] Drew Adams
2006-07-05  2:24   ` Miles Bader
2006-07-05  3:42     ` Dired coloring and other conveniences Drew Adams
2007-07-02  5:42       ` dired-details: show/hide file details in Dired Drew Adams
2007-07-02 13:04         ` Mathias Dahl
2007-07-02 13:46           ` Drew Adams
2007-07-02 20:50             ` Mathias Dahl
2007-07-02 21:04               ` Drew Adams
2007-07-02 14:02           ` add directory selection to the "compile" command lucatrv
2007-07-02 15:55             ` Denis Bueno
2007-07-04 18:38               ` lucatrv
2007-07-02 14:04         ` dired-details: show/hide file details in Dired Rob Giardina
2007-07-02 22:39           ` Richard Stallman
2007-07-02 22:53             ` Drew Adams
2007-07-02 23:01               ` Rob Giardina
2007-07-03  1:17               ` Stefan Monnier
2007-07-03  5:44                 ` Drew Adams
2007-07-05 13:41                   ` Stefan Monnier
2007-07-04  3:43               ` Richard Stallman
2007-07-04  3:53                 ` Rob Giardina
2007-07-05  1:30                   ` Richard Stallman
2007-07-04  5:51                 ` Drew Adams
2007-07-04 10:53                   ` Robert J. Chassell
2007-07-04 14:57                     ` Drew Adams
2007-07-04 17:10                     ` Robert J. Chassell
2007-07-04 20:00                       ` Drew Adams [this message]
2007-07-04 21:57                         ` Robert J. Chassell
2007-07-05  1:31                       ` Richard Stallman
2007-07-05  6:58                         ` Drew Adams
2007-07-05 11:38                           ` Robert J. Chassell
2007-07-05 20:34                             ` Richard Stallman
2007-07-05 20:49                               ` Drew Adams
2007-07-05 21:35                                 ` Robert J. Chassell
2007-07-08 22:24                                 ` Richard Stallman
2007-07-05 20:34                           ` Richard Stallman
2007-07-05  1:30                   ` Richard Stallman
2007-07-05  2:40                     ` Rob Giardina
2007-07-05 20:34                       ` Richard Stallman
2007-07-05  1:30                   ` Richard Stallman
2007-07-05  3:22                     ` Rob Giardina
2007-07-05 20:34                       ` Richard Stallman
2006-07-06 13:32     ` [doug@bagley.org: Re: mouse-1-click-follows-link in diredsurprising] Richard Stallman
2006-07-06 21:41       ` Miles Bader
2006-07-08 20:57         ` Richard Stallman
2006-07-08 21:24           ` Luc Teirlinck
2006-07-09 19:02             ` Richard Stallman
2006-07-08 21:35           ` Luc Teirlinck
2006-07-08 22:15           ` Luc Teirlinck
2006-07-09 19:02             ` Richard Stallman

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=BNELLINCGFJLDJIKDGACIEDBCAAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    /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).