all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: dired-du
Date: Sat, 27 May 2017 17:59:57 +0700	[thread overview]
Message-ID: <CAP_d_8X-2Yj3a6D7yFWEEw5=qhTaRi0BEdyu4P8DaAr4gS8=Gw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705271833110.14415@calancha-pc>

On Sat, May 27, 2017 at 5:06 PM, Tino Calancha <tino.calancha@gmail.com> wrote:

>> Would it be useful to extract the Lisp replacement of du as a separate
>> library, or does that raise too many questions about cache management?
>
> That part is expected to be very slow.  I just added recently as a fallback,
> but it is not the recomended way.  Actually I show one warning encouraging
> the user to install `du'.

That’s why I’m suggesting extracting it: so that the casual user
reading the code does not spend time in the fallback; or,
alternatively, focuses on it specifically.

>> Wouldn’t it make sense to share the cache across all Dired buffers
>> and persist it independently of buffer lifetimes?
>
> I don't know.  I decided the implementation according with my use case:
> i just wanted to see the actual size of my dirs in human readable units. For
> this naive purpose the buffer locallity of `dired-du-dir-info' is fine.
> Once other people start using the lib we might find convenient to change
> those particular aspects of the implementation.

Okay.

I wonder… will it work over Tramp/ssh?



  reply	other threads:[~2017-05-27 10:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 13:02 [ELPA] New package: dired-du Tino Calancha
2017-05-26 13:45 ` Clément Pit-Claudel
2017-05-26 14:57   ` Tino Calancha
2017-05-26 17:04 ` Yuri Khan
2017-05-26 17:53   ` Eli Zaretskii
2017-05-26 18:12     ` Yuri Khan
2017-05-26 19:03       ` Eli Zaretskii
2017-05-27 10:06   ` Tino Calancha
2017-05-27 10:59     ` Yuri Khan [this message]
2017-05-29  1:37       ` Tino Calancha
2017-05-29 14:41   ` Filipp Gunbin

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='CAP_d_8X-2Yj3a6D7yFWEEw5=qhTaRi0BEdyu4P8DaAr4gS8=Gw@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=tino.calancha@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.