GNU bug report logs - #64897
29.0.91; Bug (and patch) in find-dired-with-command

Previous Next

Package: emacs;

Reported by: Warren Lynn <wrn.lynn <at> gmail.com>

Date: Thu, 27 Jul 2023 14:25:02 UTC

Severity: normal

Found in version 29.0.91

Fixed in version 29.2

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


Message #22 received at 64897 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 64897 <at> debbugs.gnu.org, Warren Lynn <wrn.lynn <at> gmail.com>
Subject: Re: bug#64897: 29.0.91; Bug (and patch) in find-dired-with-command
Date: Mon, 07 Aug 2023 03:17:00 +0200
Michael Albinus <michael.albinus <at> gmx.de> writes:

> find . \( -name \*\ \* \) -exec ls -adhl \{\} +
>
> which returns indeed quoted file names as you have shown. What if you
> set instead
>
> (setq find-ls-option
>       (setq find-ls-option-default-exec
>             '("-exec ls -abdhl {} +" . "-abdhl")))

Then the quotes are completely gone.

Obviously I don't want to need use -b however, since the escaped space
chars in the file names add a lot of noise.

I don't understand what is going on.  I tried to compare the situations
before and after the patch.  In both cases the `call-process' parameters
are more or less the same.  The process sentinels already seem to
receive different strings (one time without, the other time including
the quotes) - so seems it's not about sentinels.

Michael.




This bug report was last modified 2 years and 9 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.