From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Yuri Khan Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: dired-du Date: Sat, 27 May 2017 17:59:57 +0700 Message-ID: References: <8737brwz2a.fsf@calancha-pc> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1495882869 28582 195.159.176.226 (27 May 2017 11:01:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 27 May 2017 11:01:09 +0000 (UTC) Cc: Emacs developers To: Tino Calancha Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 27 13:01:06 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dEZSy-0007D4-PG for ged-emacs-devel@m.gmane.org; Sat, 27 May 2017 13:01:04 +0200 Original-Received: from localhost ([::1]:40234 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dEZSz-0004q1-Lf for ged-emacs-devel@m.gmane.org; Sat, 27 May 2017 07:01:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50898) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dEZSG-0004pr-O2 for emacs-devel@gnu.org; Sat, 27 May 2017 07:00:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dEZSG-0008TC-2r for emacs-devel@gnu.org; Sat, 27 May 2017 07:00:20 -0400 Original-Received: from mail-wr0-x22c.google.com ([2a00:1450:400c:c0c::22c]:32845) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dEZSF-0008T4-TQ for emacs-devel@gnu.org; Sat, 27 May 2017 07:00:20 -0400 Original-Received: by mail-wr0-x22c.google.com with SMTP id w50so13242042wrc.0 for ; Sat, 27 May 2017 04:00:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=UEF1cYjeu06MpRmmq0HavEVpVR2kE+QoAM4PP+pfND0=; b=fexLHXtfhMJt6bpeb4qkhtTK9g5iISsKrKpopNP3sdpaFRDKmYoqNXFvvR1Am37i8B B0+77BszouHu18Ob4oZ4ZWuciXqMyRI0FviBSvBKcJmSfBZk7VVWfwFo7CkV00yVHITe HgVv38LTmS0DYfU3NgwxUW3sc3CUzA02FTRyGheXXHUIuEAzFdT5WGIObX9t2giuAhzu ++TGT8sVwRb8tKdOrO4TVKz8+CbSQ1KynPw9wH4CvWnTOHsu9Sf1oKLpHqDM24o5cOOR cd3cSp1tj6eSJkWgZjRmTW6igQ3V7eofxjAorsvmUk6o25K9ciE3RlqMMaBLfmi/M/JE ZDwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=UEF1cYjeu06MpRmmq0HavEVpVR2kE+QoAM4PP+pfND0=; b=S+vDr2YOm5Vi2LmCULD48cAFh7ciqLywb3/NE2J6F1emNEM23kxd++68PLPH/Htlwa wlGtKNEqIAuOf4y3z4NYrwg92lxhDe9NdHqLbs3o/gddwqE8p88GhZ1jSEbCRV/+s1V0 PQWxMM5SQvCN/RDOjoZCxrzfSk0ys2LsijTLSD64ZOBDZ9BH52lDeGwcDd4i3X2ENuqj AgHwnRTGwe/wkVWfDhUNyMUo0/3cdDzQpSMBM+jRvSg8LGW9vAGjDkpxPh6ymNBk72IV mZlLrn6XYYsDiUkGwnYafWmZtwKm3RklsjY96+BLb6vlrzb6YHy/9ka2PlcERdO10NkM zDZA== X-Gm-Message-State: AODbwcB6wNexAYc4MHnRuhf8OeaaNplYlsKaV8z2OsLSTJyBKsbTA3nv YlyhLGg1+AyI6EmX+I5FT6hDSI+Suw== X-Received: by 10.223.179.199 with SMTP id x7mr4960834wrd.72.1495882818388; Sat, 27 May 2017 04:00:18 -0700 (PDT) Original-Received: by 10.223.163.196 with HTTP; Sat, 27 May 2017 03:59:57 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: nlEshi0j4e_zpjA5I4Zl9EngbJw X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:400c:c0c::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:215261 Archived-At: On Sat, May 27, 2017 at 5:06 PM, Tino Calancha wr= ote: >> 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 fallba= ck, > but it is not the recomended way. Actually I show one warning encouragin= g > the user to install `du'. That=E2=80=99s why I=E2=80=99m 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=E2=80=99t it make sense to share the cache across all Dired buffe= rs >> 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=E2=80=A6 will it work over Tramp/ssh?