From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: grindeg@yandex.ru, 36085@debbugs.gnu.org
Subject: bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text
Date: Sun, 09 Jun 2019 15:49:01 +0300 [thread overview]
Message-ID: <83lfyac4aq.fsf@gnu.org> (raw)
In-Reply-To: <377032D3-8461-4E82-9CB5-319DE2E9C1F6@acm.org> (message from Mattias Engdegård on Sun, 9 Jun 2019 14:39:32 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 9 Jun 2019 14:39:32 +0200
> Cc: grindeg@yandex.ru, 36085@debbugs.gnu.org
>
> > One other consideration is that for large directory trees the current
> > implementation of find-dired updates the buffer in parallel with
> > 'find' still running, whereas the alternatives will not return until
> > the whole listing has been generated, which might take a long time.
>
> This concern is definitely valid. I don't know to what extent parallelism is possible in the current thread implementation.
Just a note: the current "parallel" implementation is not really
parallel either: 'find' indeed runs in parallel, but the process
filter functions in Emacs only run when Emacs is idle, so if the user
types very quickly after invoking find-dired, they will not see the
results until they make a break in typing. And our threads work in
the same manner, at least in principle, so we should be good running
the Lisp implementation in a non-main thread. Of course, until
someone actually tries that, we won't know whether there are any
obstacles: the devil, as always, is in the details.
> Again, improvements in this respect would have benefits beyond find-dired.
Sure.
next prev parent reply other threads:[~2019-06-09 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 3:43 bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text Nikita
2019-06-04 11:44 ` bug#36085: Screenshots for th bug Никита Никита
2019-06-08 12:20 ` bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text Eli Zaretskii
2019-06-09 12:34 ` Tomas Nordin
2019-06-09 12:51 ` Eli Zaretskii
2019-06-08 15:14 ` Mattias Engdegård
2019-06-08 15:34 ` Eli Zaretskii
2019-06-09 5:22 ` Eli Zaretskii
2019-06-09 9:08 ` Mattias Engdegård
2019-06-09 10:57 ` Eli Zaretskii
2019-06-09 12:39 ` Mattias Engdegård
2019-06-09 12:49 ` Eli Zaretskii [this message]
2022-03-13 6:05 ` Visuwesh
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=83lfyac4aq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36085@debbugs.gnu.org \
--cc=grindeg@yandex.ru \
--cc=mattiase@acm.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).