From: Juri Linkov <juri@linkov.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 57293@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
Mike Kupfer <mkupfer@alum.berkeley.edu>
Subject: bug#57293: 29.0.50; query-replace with Wdired skips symlink target
Date: Sat, 27 Aug 2022 22:44:56 +0300 [thread overview]
Message-ID: <861qt1o4hz.fsf@mail.linkov.net> (raw)
In-Reply-To: <8735dmil6d.fsf@web.de> (Michael Heerdegen's message of "Wed, 24 Aug 2022 01:39:54 +0200")
>> *** Search and replace in Dired/Wdired supports more regexps.
>> For example, the regexp ".*" will match only characters that are part
>> of the file name. Also "^.*$" can be used to match at the beginning
>> -of the file name and at the end of the file name.
>> +of the file name and at the end of the file name. In Wdired this can
>> +be used when the new user option 'wdired-search-replace-filenames' is
>> +non-nil (which is the default).
>
> Can we say that the behavior in dired is optional, too, and maybe just
> list the options (and commands) at the end?
I tried to improve this, please check.
>> -(defun isearch-search-fun-in-text-property (search-fun property)
>> - "Return the function to search inside text that has the specified PROPERTY.
>> +(defun isearch-search-fun-in-text-property (search-fun properties)
>> + "Return the function to search inside text that has the specified PROPERTIES.
>> The function will limit the search for matches only inside text which has
>> -this property in the current buffer.
>> +these list of PROPERTIES in the current buffer.
>
> "which has at least one of the text PROPERTIES" may be better (I also
> added "text" so that the docstring at least once tells that this is only
> about text props).
Fixed this as well.
next prev parent reply other threads:[~2022-08-27 19:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 3:11 bug#57293: 29.0.50; query-replace with Wdired skips symlink target Mike Kupfer
2022-08-21 0:47 ` Michael Heerdegen
2022-08-21 1:07 ` Stefan Kangas
2022-08-21 1:46 ` Michael Heerdegen
2022-08-21 1:54 ` Mike Kupfer
2022-08-21 16:37 ` Juri Linkov
2022-08-22 6:16 ` Michael Heerdegen
2022-08-22 6:52 ` Juri Linkov
2022-08-22 22:20 ` Michael Heerdegen
2022-08-23 19:27 ` Juri Linkov
2022-08-23 23:39 ` Michael Heerdegen
2022-08-24 1:15 ` Mike Kupfer
2022-08-27 4:03 ` Mike Kupfer
2022-08-27 19:45 ` Juri Linkov
2022-08-27 19:44 ` Juri Linkov [this message]
2022-08-28 2:34 ` 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=861qt1o4hz.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=57293@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=mkupfer@alum.berkeley.edu \
--cc=stefankangas@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).