From: Eli Zaretskii <eliz@gnu.org>
To: Harald Judt <h.judt@gmx.at>
Cc: philipk@posteo.net, visuweshm@gmail.com, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: dired-duplicates
Date: Thu, 02 Nov 2023 07:55:13 +0200 [thread overview]
Message-ID: <83lebg8zsu.fsf@gnu.org> (raw)
In-Reply-To: <2b30b6e0-d30e-41e1-83a5-05b0c3fa8aa6@gmx.at> (message from Harald Judt on Wed, 1 Nov 2023 21:09:48 +0100)
> Date: Wed, 1 Nov 2023 21:09:48 +0100
> Cc: visuweshm@gmail.com, emacs-devel@gnu.org
> From: Harald Judt <h.judt@gmx.at>
>
> Thanks for the numbers. What troubles me a bit more than the speed is which
> effects inserting such a large file into a buffer has memory-wise?
It is IMO okay to fail when sha256sum is not available and a file is
larger than the available VM, so Emacs runs out of memory, if this is
the situation that worries you. But these cases should be relatively
rare, and so there's no reason to fail to have this feature in the
much more frequent case that the files are not as large as the
available VM.
If the file can be read by Emacs, even if it's large, then killing the
buffer after computing the hash should not have any adverse effects on
memory usage of that Emacs session.
next prev parent reply other threads:[~2023-11-02 5:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 10:34 [ELPA] New package: dired-duplicates Harald Judt
2023-10-31 12:21 ` Philip Kaludercic
2023-10-31 21:05 ` Harald Judt
2023-11-01 2:14 ` Michael Heerdegen
2023-11-01 15:16 ` [External] : " Drew Adams
2023-11-01 15:45 ` Eli Zaretskii
2023-11-01 16:28 ` Drew Adams
2023-11-01 16:47 ` Eli Zaretskii
2023-11-01 16:33 ` Philip Kaludercic
2023-11-01 11:32 ` Philip Kaludercic
2023-11-01 20:04 ` Harald Judt
2023-11-01 21:29 ` Philip Kaludercic
2023-11-02 8:44 ` Harald Judt
2023-11-03 8:19 ` Philip Kaludercic
2023-11-03 20:19 ` Harald Judt
2023-11-04 15:27 ` Philip Kaludercic
2023-11-06 9:33 ` Harald Judt
2023-11-10 8:37 ` Philip Kaludercic
2023-11-10 10:02 ` Harald Judt
2023-11-23 6:12 ` Philip Kaludercic
2023-10-31 21:24 ` Harald Judt
2023-11-01 17:40 ` Stefan Kangas
2023-11-01 3:30 ` Eli Zaretskii
2023-11-01 13:53 ` Visuwesh
2023-11-01 14:12 ` Eli Zaretskii
2023-11-01 17:57 ` Philip Kaludercic
2023-11-01 19:24 ` Eli Zaretskii
2023-11-01 20:09 ` Harald Judt
2023-11-02 5:55 ` Eli Zaretskii [this message]
2023-11-08 20:29 ` Harald Judt
2023-11-09 5:52 ` Eli Zaretskii
2023-11-09 8:00 ` Harald Judt
2023-11-09 8:38 ` tomas
2023-11-09 8:48 ` Eli Zaretskii
2023-11-09 8:43 ` Eli Zaretskii
2023-11-09 8:53 ` tomas
2023-11-09 9:18 ` Harald Judt
2023-11-09 14:52 ` Harald Judt
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=83lebg8zsu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=h.judt@gmx.at \
--cc=philipk@posteo.net \
--cc=visuweshm@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 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).