unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: isearch replace on org-mode buffer overlays caused error
Date: Wed, 18 Dec 2024 13:08:02 +0100	[thread overview]
Message-ID: <87a5ct42jh.fsf@web.de> (raw)
In-Reply-To: CAL1eYuJ3=CeWxo4Uf01+_Jj9A=L4vfYp5V02m8yuqK9D=CdXOw@mail.gmail.com

stardiviner <numbchild@gmail.com> writes:

> Yes, it's weird, I'm pretty sure I'm in an normal org-mode
> (major-mode) buffer. Don't know why magit-mode involved.

I think I have been wrong: that the advice is shows up in the backtrace
is normal once you have Magit loaded.  It will just fall back to the
original function.  This is probably not our culprit.

Ok - but you are using something called `pcre-query-replace-regexp', not
the original `isearch' `query-replace'.  My first question would be: can
you reproduce this issue using the vanilla `query-replace'?  If not, it
may be a problem in `pcre-query-replace-regexp', some side effect that
interferes with isearch' open-and-close-invisible-areas mechanism.


Michael.




  reply	other threads:[~2024-12-18 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16  7:42 isearch replace on org-mode buffer overlays caused error Christopher M. Miles
2024-12-16 10:23 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-18  6:20   ` stardiviner
2024-12-18 12:08     ` Michael Heerdegen via Users list for the GNU Emacs text editor [this message]
2024-12-18  6:21   ` stardiviner

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=87a5ct42jh.fsf@web.de \
    --to=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.
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).