unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Juri Linkov <juri@jurta.org>
Cc: Tom Tromey <tromey@redhat.com>, 4341@debbugs.gnu.org
Subject: bug#4341: 23.1; M-x locate runs synchronously
Date: Tue, 03 Nov 2020 18:04:31 +0100	[thread overview]
Message-ID: <87d00u2wyo.fsf@web.de> (raw)
In-Reply-To: <87y6onr35h.fsf@mail.jurta.org> (Juri Linkov's message of "Thu, 10 Sep 2009 04:17:14 +0300")

Juri Linkov <juri@jurta.org> writes:

> > I think it would be preferable to run locate in asynchronously.
>
> This would be possible when `locate' were more similar to `find-dired'.
> I don't mean its output should be formatted as files in dired.
> For that we could create a new command like `locate-dired'.
> But maybe internals of `find-dired' should be generalized to
> accept arbitrary commands.  This would allow implementing
> `locate-dired', `rgrep-dired', `lgrep-dired', i.e. any command
> that searches files with their output formatted for dired
> like `find-name-dired', `find-grep-dired' and `find-dired'.

That sounds nice.

It's not trivial: find calls ls by itself.  From processes Emacs can
receive anything, and it would have to decide by itself on the fly if
it's an ok file line and call "ls" to format the file line.  "locate"
for example can report files that have been deleted in the meantime.

Michael.





  reply	other threads:[~2020-11-03 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 19:15 bug#4341: 23.1; M-x locate runs synchronously Tom Tromey
2009-09-10  1:17 ` Juri Linkov
2020-11-03 17:04   ` Michael Heerdegen [this message]
2020-11-03 19:45     ` Juri Linkov
2020-11-04 11:14       ` Michael Heerdegen
2020-11-08 19:47         ` Juri Linkov
2020-11-08 20:23           ` Stefan Kangas
2020-11-15 20:20             ` Juri Linkov

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=87d00u2wyo.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=4341@debbugs.gnu.org \
    --cc=juri@jurta.org \
    --cc=tromey@redhat.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).