unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: RE: patch for Dired second header line info
Date: Mon, 3 Mar 2008 11:01:19 -0800	[thread overview]
Message-ID: <001801c87d60$f777b8d0$c2b22382@us.oracle.com> (raw)
In-Reply-To: <E1JWFNX-0001QV-Rq@fencepost.gnu.org>

>       files 420/694 space used 19646 available 56456000
> I think
>       files shown 420 in dir 694 their size 19646 available 56456000
> 
> is cleaner, for the usual case where the buffer shows one
> directory (or a subset of it).

Feel free to adjust it as you like. 

BTW, what you propose works not only for the usual case, but also for any
included subdirs. Each subdir listing has its own such info line.

> Does the "files shown" get updated by all the Dired commands
> that alter which files are shown?  If not, I think it is misleading.

No, unfortunately. I use `dired-after-readin-hook' to trigger the update,
because I don't know of a better way. But that hook is sometimes run without
all the files being shown (for some reason).

For example, if you use `+' to create a directory, the hook is run with only
the new directory shown. However, in that case, the directory header is also
now showing, so it is at least not updated incorrectly to 1 - it remains
(incorrectly) what it was before the `+'.

Anyone know of a better hook to use for this or a better way to trigger the
update?

Wrt it being misleading: If no better implementation is found, to have it
update automatically in all cases (e.g. chmod, deletion, file copy,...),
then the doc should say that it is updated only when the directory is read
in. It should be enough to say that you can use `g' at any time to update
the files figures.





  reply	other threads:[~2008-03-03 19:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01  1:03 patch for Dired second header line info Drew Adams
2008-03-01 13:31 ` Richard Stallman
2008-03-01 16:31   ` Drew Adams
2008-03-01 23:09     ` Richard Stallman
2008-03-02  2:55 ` Juri Linkov
2008-03-02  8:05   ` Drew Adams
2008-03-02 14:36     ` Juri Linkov
2008-03-02 16:27       ` Drew Adams
2008-03-02 17:49         ` Drew Adams
2008-03-02 17:57           ` Juri Linkov
2008-03-02 18:56             ` Drew Adams
2008-03-02 19:06               ` Drew Adams
2008-03-03  0:47                 ` Drew Adams
2008-03-03 18:27             ` Richard Stallman
2008-03-03 21:45               ` Stefan Monnier
2008-03-03 22:29                 ` Drew Adams
2008-03-04 17:38                   ` Richard Stallman
2008-03-04 19:44                     ` Drew Adams
2008-03-04 22:28                       ` Drew Adams
2008-03-05 21:33                       ` Richard Stallman
2008-03-03 18:27           ` Richard Stallman
2008-03-03 19:01             ` Drew Adams [this message]
2008-03-02 17:56         ` Juri Linkov

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='001801c87d60$f777b8d0$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@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).