emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#25992: closed (perform-replace leaves mark-active


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#25992: closed (perform-replace leaves mark-active when not transient-mark-mode)
Date: Tue, 07 Mar 2017 19:27:02 +0000

Your message dated Tue, 07 Mar 2017 21:25:55 +0200
with message-id <address@hidden>
and subject line Re: bug#25992: perform-replace leaves mark-active when not     
transient-mark-mode
has caused the debbugs.gnu.org bug report #25992,
regarding perform-replace leaves mark-active when not transient-mark-mode
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
25992: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25992
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: perform-replace leaves mark-active when not transient-mark-mode Date: Sun, 05 Mar 2017 18:02:23 -0800
When transient-mark-mode is turned off, perform-replace leaves mark-active set 
to `t`.

Step 1:  Launch emacs -q

Step 2:  Turn off transient-mark-mode.  (transient-mark-mode -1)

Step 3:  Evaluate mark-active and verify it is `nil`.

Step 4:  Run a simple perform-replace such as:  (replace-regexp ";" "@" nil 1 2)

Step 5:  Evaluate mark-active and see that it is now set `t`.

The desired behavior is to leave `mark-active` set to `nil` if it was 
previously set to `nil`.

I fixed this in my own setup with a very simple test at the outset of 
perform-replace to see whether mark-active was set to `t` at the outset and 
then turn it off at the end of the function if it was not previously active.

Thanks,

Keith



--- End Message ---
--- Begin Message --- Subject: Re: bug#25992: perform-replace leaves mark-active when not transient-mark-mode Date: Tue, 07 Mar 2017 21:25:55 +0200
> Date:  Tue, 07 Mar 2017 09:32:58 -0800
> From:  Keith David Bershatsky <address@hidden>
> Cc:  address@hidden
> 
> Yes, thank you, please close out bug#25992.

Done.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]