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

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

[debbugs-tracker] bug#13169: closed ([PATCH] kill-region fails to deacti


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#13169: closed ([PATCH] kill-region fails to deactivate mark after cutting empty region)
Date: Fri, 21 Dec 2012 03:51:02 +0000

Your message dated Fri, 21 Dec 2012 11:49:54 +0800
with message-id <address@hidden>
and subject line Re: bug#13169: [PATCH] kill-region fails to deactivate mark 
after cutting empty region
has caused the debbugs.gnu.org bug report #13169,
regarding [PATCH] kill-region fails to deactivate mark after cutting empty 
region
to be marked as done.

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


-- 
13169: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13169
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH] kill-region fails to deactivate mark after cutting empty region Date: Thu, 13 Dec 2012 00:19:16 -0800 (PST)
On 24.2, emacs -Q
C-SPC M-w C-p
kill-ring-save copied an empty region, and deactivated the mark. This is 
correct. But now do
C-SPC C-w C-p
kill-region cut an empty region, which is correct, but the mark is still 
active, which is incorrect. When the buffer and text aren't read-only, 
kill-region relies on the command loop to deactivate the mark after the buffer 
is modified, but when cutting an empty region, the buffer isn't modified, so 
the mark is never deactivated.
The attached killregionbug.patch fixes it.

Attachment: killregionbug.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#13169: [PATCH] kill-region fails to deactivate mark after cutting empty region Date: Fri, 21 Dec 2012 11:49:54 +0800 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.91 (gnu/linux)
Kelly Dean <address@hidden> writes:

> C-SPC C-w C-p
> kill-region cut an empty region, which is correct, but the mark is
> still active, which is incorrect. When the buffer and text aren't
> read-only, kill-region relies on the command loop to deactivate the
> mark after the buffer is modified, but when cutting an empty region,
> the buffer isn't modified, so the mark is never deactivated.
> The attached killregionbug.patch fixes it.

Committed to trunk, thanks.


--- End Message ---

reply via email to

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