From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: 9871@debbugs.gnu.org
Subject: bug#9871: `query-replace' and friends break text properties
Date: Mon, 19 Aug 2019 13:37:08 -0700 [thread overview]
Message-ID: <87k1b828p7.fsf@mouse.gnus.org> (raw)
In-Reply-To: <8736hx35q2.fsf_-_@gmail.com> ("Štěpán Němec"'s message of "Mon, 19 Aug 2019 10:43:49 +0200")
Štěpán Němec <stepnem@gmail.com> writes:
> Yes it would. I also think that the straightforward case where all the
> text has the same value for a property will be much more frequent than
> your contrived example (note my property wasn't even visible at all; in
> case of font-locking for example I'd expect the result to get
> refontified as usual anyway).
I just used a face because that's visible; the same applies to any text
property.
Thinking about it a bit more, I don't really feel that
delete-then-insert semantics will be very nice as a feature, either.
(with-temp-buffer
(insert (propertize "hello" 'face 'bold))
(goto-char (point-min))
(replace-regexp "hello" "hey")
(buffer-string))
If you replace a phrase that has one face with a different phrase, if
text properties are preserved, surely you'd expect that "hey" to also be
bold. But it won't be, since the "hello" was deleted first and then
"hey" was inserted.
So I don't really think there's any way to DWIM here that is "what I
mean", and if you want to copy over text properties in one form of
another, you have to write some code to express what you want to have
happen.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-08-19 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 22:20 bug#9871: `query-replace' and friends break text properties Štěpán Němec
2019-08-19 0:03 ` Lars Ingebrigtsen
2019-08-19 0:57 ` Drew Adams
2019-08-19 8:43 ` Štěpán Němec
2019-08-19 20:37 ` Lars Ingebrigtsen [this message]
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=87k1b828p7.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=9871@debbugs.gnu.org \
--cc=stepnem@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 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.