From: "Mattias Engdegård" <mattiase@acm.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>, 44273@debbugs.gnu.org
Subject: bug#44273: "total used in directory 19 available 5.2 GiB"
Date: Wed, 28 Oct 2020 12:18:56 +0100 [thread overview]
Message-ID: <83DA3F8B-E525-43F6-8A72-A5AF6C0EEA38@acm.org> (raw)
In-Reply-To: <877dravck1.fsf@gnus.org>
forcemerge 44273 36379
stop
28 okt. 2020 kl. 12.02 skrev Lars Ingebrigtsen <larsi@gnus.org>:
> I didn't see any howling in that bug report, though? I just skimmed it
> quickly.
I think there was some discussion (if you can call it that) outside that report, but I may be misremembering.
> As an aside: The general design of dired is frustrating. Dumping
> whatever the system "ls" gives us into a buffer and then trying to make
> do isn't a good approach.
>
> The argument that Tramp needs to parse "ls" output is valid, and that
> "ls" is faster than `ls-lisp' is, too, but it's still backwards: Dired
> should take a well-defined data structure and then render it according
> to however the user wants.
Definitely, and if it is faster to fork another process and parse its output with slow regexps in Emacs to do the job of what ordinarily just takes a few syscalls, then we aren't doing our job properly. It's not hard to read directories efficiently.
In any case I'm merging the bugs, optimistically keeping them open.
next prev parent reply other threads:[~2020-10-28 11:18 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 5:12 bug#44273: "total used in directory 19 available 5.2 GiB" 積丹尼 Dan Jacobson
2020-10-28 10:37 ` Mattias Engdegård
2020-10-28 10:43 ` Lars Ingebrigtsen
2020-10-28 10:53 ` Mattias Engdegård
2020-10-28 11:02 ` Lars Ingebrigtsen
2020-10-28 11:18 ` Mattias Engdegård [this message]
2020-10-28 11:23 ` Lars Ingebrigtsen
2020-10-28 11:47 ` Andreas Schwab
2020-10-28 12:10 ` Lars Ingebrigtsen
2020-10-28 12:18 ` Mattias Engdegård
2020-10-28 12:26 ` Andreas Schwab
2020-10-28 12:29 ` Lars Ingebrigtsen
2020-10-28 15:38 ` Eli Zaretskii
2020-10-28 15:34 ` Eli Zaretskii
2020-10-29 8:36 ` Michael Albinus
2020-10-28 14:39 ` Drew Adams
2020-10-28 14:49 ` Mattias Engdegård
2020-10-28 15:28 ` Eli Zaretskii
2020-10-30 11:36 ` Lars Ingebrigtsen
2020-10-30 11:41 ` Eli Zaretskii
2020-10-31 9:44 ` Eli Zaretskii
2020-10-28 15:19 ` Eli Zaretskii
2020-10-28 15:55 ` Stefan Kangas
2020-10-28 15:59 ` Eli Zaretskii
2020-10-29 0:03 ` Stefan Kangas
2020-10-29 3:34 ` Eli Zaretskii
2020-10-29 8:48 ` Andreas Schwab
2020-10-30 3:05 ` Richard Stallman
2020-10-30 7:18 ` Juri Linkov
2020-10-30 8:17 ` Eli Zaretskii
2020-10-30 11:33 ` Lars Ingebrigtsen
2020-10-30 11:39 ` Eli Zaretskii
2020-10-30 11:41 ` Lars Ingebrigtsen
2020-10-30 11:49 ` Eli Zaretskii
2020-11-01 11:33 ` Lars Ingebrigtsen
2020-10-31 19:14 ` Juri Linkov
2020-11-01 11:38 ` Lars Ingebrigtsen
2020-11-01 11:55 ` Mattias Engdegård
2020-11-01 15:21 ` Eli Zaretskii
2020-11-01 15:41 ` Mattias Engdegård
2020-11-01 15:51 ` Eli Zaretskii
2020-11-01 16:37 ` Mattias Engdegård
2020-11-01 19:25 ` Jean Louis
2021-10-11 12:35 ` Stefan Kangas
2020-11-01 19:16 ` Jean Louis
2020-11-01 18:57 ` Jean Louis
2020-11-01 19:33 ` Eli Zaretskii
2020-11-01 19:38 ` 積丹尼 Dan Jacobson
2020-11-01 19:43 ` Eli Zaretskii
2020-11-01 19:51 ` 積丹尼 Dan Jacobson
2020-10-31 4:47 ` Richard Stallman
2020-10-30 19:03 ` Drew Adams
2020-11-03 3:17 ` Drew Adams
2020-11-03 18:39 ` Juri Linkov
2020-11-03 19:51 ` Drew Adams
2020-11-04 19:41 ` Juri Linkov
2020-11-04 20:53 ` Drew Adams
2020-10-30 11:34 ` Lars Ingebrigtsen
2020-10-29 4:54 ` Richard Stallman
2020-10-30 12:22 ` Lars Ingebrigtsen
2020-10-30 12:25 ` Eli Zaretskii
2020-10-30 13:39 ` Michael Albinus
2020-10-30 13:46 ` Eli Zaretskii
2020-10-30 14:54 ` Michael Albinus
2020-10-31 0:12 ` 積丹尼 Dan Jacobson
2020-10-31 4:45 ` Richard Stallman
2020-10-31 4:47 ` Richard Stallman
2020-10-31 4:47 ` 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=83DA3F8B-E525-43F6-8A72-A5AF6C0EEA38@acm.org \
--to=mattiase@acm.org \
--cc=44273@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.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).