unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Bob Floyd" <bobfloyd@comcast.net>
To: "'Juri Linkov'" <juri@linkov.net>
Cc: 48421@debbugs.gnu.org
Subject: bug#48421: 28.0.50; Edit region for query-replace gets lost
Date: Fri, 14 May 2021 16:54:25 -0700	[thread overview]
Message-ID: <002401d7491c$7cccafa0$76660ee0$@net> (raw)
In-Reply-To: <87y2ch6w20.fsf@mail.linkov.net>

Yes, I know you fixed it in bug#45617 as it was I who reported it, and thank
you!

However, it has resurfaced in the development version I'm using - perhaps
the fix was not put into the repository?

The query-replace incorrectly selects all of the `_nmPrmset`s and not just
those in the edit region.

-----Original Message-----
From: Juri Linkov [mailto:juri@linkov.net] 
Sent: Friday, May 14, 2021 11:14 AM
To: Bob Floyd
Cc: 48421@debbugs.gnu.org
Subject: Re: bug#48421: 28.0.50; Edit region for query-replace gets lost

> Note the edit region of 1,2,3 is lost.

Actually, the region is not lost.  We fixed this in bug#45617 recently,
so now query-replace operates on the correct region boundaries.

But during replacement the region is deactivated deliberately.
If you could confirm that query-replace preforms replacements
only in the selected region (although the region is deactivated
during replacement), then everything is correct.






  reply	other threads:[~2021-05-14 23:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 16:53 bug#48421: 28.0.50; Edit region for query-replace gets lost Bob Floyd
2021-05-14 18:13 ` Juri Linkov
2021-05-14 23:54   ` Bob Floyd [this message]
2021-05-15  9:45     ` Gregory Heytings
2021-05-17 15:56       ` Bob Floyd
2022-07-13  1:47         ` Lars Ingebrigtsen
2022-07-13 16:00           ` Bob Floyd
2022-07-14 17:05             ` Lars Ingebrigtsen

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='002401d7491c$7cccafa0$76660ee0$@net' \
    --to=bobfloyd@comcast.net \
    --cc=48421@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).