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: Wed, 04 Nov 2020 12:14:08 +0100 [thread overview]
Message-ID: <87pn4tv0fz.fsf@web.de> (raw)
In-Reply-To: <87a6vyz0k9.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 03 Nov 2020 21:45:42 +0200")
Juri Linkov <juri@jurta.org> writes:
> Is it possible to avoid using "ls"? If ls formatting is not needed,
> then the output buffer will look like a Dired buffer with enabled
> 'dired-hide-details-mode' that shows only file names.
I guess it is possible, I have no clue. It's what we do now.
A downside is that developers would have to keep this in mind when
working on dired, otherwise things may work only partially or break.
For example, if you (in current Emacs master) mark files in a *locate*
output buffer, they get marked and you can act on them, but marked files
are not highlighted.
OTOH, if we leave the corner case of non-existing files aside for now -
when we do call ls (what would be the downsides?), we would get a fully
functional dired support out of the box.
Privately, I have adviced `locate' to insert the list of found files
into a new dired buffer (by calling `dired' with the explicit list of
files), and so far I find it better. That is actually already all I can
contribute so far.
Regards,
Michael.
next prev parent reply other threads:[~2020-11-04 11:14 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
2020-11-03 19:45 ` Juri Linkov
2020-11-04 11:14 ` Michael Heerdegen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn4tv0fz.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.