From: Michael Heerdegen <michael_heerdegen@web.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 64897@debbugs.gnu.org, Warren Lynn <wrn.lynn@gmail.com>
Subject: bug#64897: 29.0.91; Bug (and patch) in find-dired-with-command
Date: Sun, 06 Aug 2023 01:35:08 +0200 [thread overview]
Message-ID: <87r0ohf4gj.fsf@web.de> (raw)
In-Reply-To: <87sf99l56g.fsf@gmx.de> (Michael Albinus's message of "Thu, 27 Jul 2023 17:55:51 +0200")
Hello Michael and Warren,
Your change - this part in particular:
| @@ -244,8 +244,8 @@ find-dired-with-command
| (erase-buffer)
| (setq default-directory dir)
| ;; Start the find process.
| - (shell-command (concat command "&") (current-buffer))
| - (let ((proc (get-buffer-process (current-buffer))))
| + (let ((proc (start-file-process-shell-command
| + (buffer-name) (current-buffer) command)))
| ;; Initialize the process marker; it is used by the filter.
| (move-marker (process-mark proc) (point) (current-buffer))
| (set-process-filter proc #'find-dired-filter)
causes the following for me:
I am using this setting:
#+begin_src emacs-lisp
(setq find-ls-option
(setq find-ls-option-default-exec
'("-exec ls -adhl {} +" . "-adhl")))
#+end_src
and the *Find* buffer now contains lots of lines like
'./Zacher/Mauricio Kagel - Fantasia for Organ.mp4'
or
"./Gideon Klein/Gideon Klein's 'Praeludium,' Played by Arturo Fernandez.mp4"
i.e. lines with file names quoted inside '...' or "...". These lines
are not functional - dired can't handle them. I can reproduce this
problem with emacs -Q. The above setting worked ok before.
Is this expected and my fault or a regression?
TIA,
Michael.
next prev parent reply other threads:[~2023-08-05 23:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:24 bug#64897: 29.0.91; Bug (and patch) in find-dired-with-command Warren Lynn
2023-07-27 15:55 ` Michael Albinus
[not found] ` <CAMyoMRXkC+UkeHSpA7gZdUXkHySFqjDOni6hjoUVWCWg47KVow@mail.gmail.com>
[not found] ` <87sf985m0m.fsf@gmx.de>
[not found] ` <CAMyoMRUL6nEyLa2B8rnrq_9C3jVfBRpzo_N6L433M1RHN0CB6A@mail.gmail.com>
2023-07-31 15:53 ` Michael Albinus
2023-08-05 23:35 ` Michael Heerdegen [this message]
2023-08-06 11:02 ` Michael Albinus
2023-08-07 1:17 ` Michael Heerdegen
2023-08-07 2:17 ` Michael Heerdegen
2023-08-12 3:50 ` Michael Heerdegen
2023-08-12 12:38 ` Michael Albinus
2023-08-13 4:02 ` Michael Heerdegen
2023-08-13 7:42 ` Michael Albinus
2023-08-13 8:20 ` Eli Zaretskii
2023-08-13 9:33 ` Michael Albinus
2023-08-13 9:46 ` Eli Zaretskii
2023-08-13 10:01 ` Michael Albinus
2023-08-14 1:25 ` Michael Heerdegen
2023-08-14 11:52 ` Eli Zaretskii
2023-08-15 3:15 ` Michael Heerdegen
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=87r0ohf4gj.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=64897@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=wrn.lynn@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).