[debbugs-tracker] bug#6316: closed (24.0.50; unexpected region highlighting with disabled transient-mark-mode)

[GNU bug Tracking System]

Your message dated Thu, 26 Sep 2019 12:17:48 +0200
with message-id <address@hidden>
and subject line Re: bug#6316: 24.0.50; unexpected region highlighting
has caused the debbugs.gnu.org bug report #6316,
regarding 24.0.50; unexpected region highlighting with disabled 
transient-mark-mode
to be marked as done.

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


-- 
6316: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6316
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 24.0.50;	unexpected region highlighting with disabled transient-mark-mode
>
>
>
>
> Date: 
>
> Mon, 31 May 2010 09:30:34 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
>
>
>
>
> 1. emacs -Q
> 2. Type `M-x transient-mark-mode' to disable transient-mark-mode.
> 3. Select some text with the mouse.  To give a specific example for the
> sake of replication, type `C-h v transient-mark-mode RET', then in the
> *Help* buffer double click on the left parenthesis of "(only . OLDVAL)"
> to select the whole sexp, which thus gets highlighted.
> 4. Type `M-w', then put point at the start of the paragraph (in *Help*)
> beginning "Non-nil also enables highlighting".  Note that the region is
> not highlighted.
> 5. Paste "(only . OLDVAL)" into *scratch*, then double click on "OLDVAL",
> selecting and highlighting it.
> 6. Type `C-x o' to switch back to the *Help* buffer.
> => The region in *Help* between point and the left parenthesis of 
> "(only . OLDVAL)" is now highlighted.
>
> This annoying misbehavior has existed for some time, but I can't say
> when it first appeared.
>
>
> In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.18.6)
>  of 2010-05-29 on escher
> Windowing system distributor `The X.Org Foundation', version 11.0.10605000
> configured using `configure  '--without-toolkit-scroll-bars''
>
> Important settings:
>   value of $LC_ALL: nil
>   value of $LC_COLLATE: nil
>   value of $LC_CTYPE: nil
>   value of $LC_MESSAGES: nil
>   value of $LC_MONETARY: nil
>   value of $LC_NUMERIC: nil
>   value of $LC_TIME: nil
>   value of $LANG: en_US.UTF-8
>   value of $XMODIFIERS: @im=local
>   locale-coding-system: utf-8-unix
>   default enable-multibyte-characters: t
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: bug#6316: 24.0.50; unexpected region highlighting Date: Thu, 26 Sep 2019 12:17:48 +0200

Stephen Berman <address@hidden> writes:

> On Tue, 01 Jul 2014 14:14:52 -0400 Stefan Monnier <address@hidden> wrote:
>
>>> However, with your new patch, temporarily enabling transient-mark-mode,
>>> when it is disabled, seems to break transient-mark-mode; here's a recipe:
>>
>> Yes, the buffer "remembers" that it was nil.
>> I installed an additional patch which tries to avoid this problem,
>
> I confirm that it fixes that problem.  In addition, it fixes (presumably
> in combination with your previous patch) another case of unexpected
> region highlighting that differs somewhat from the recipe of my OP:
>
> 0. emacs -Q
> 1. M-x transient-mark-mode (disabling it).
> 2. C-SPC to set the mark in *scratch*, then move point, creating a
>    nonempty region, which, as expected, is not highlighted.
> 3. Open another buffer, e.g. with `C-h v transient-mark-mode RET' and
>    select and highlight a region in it, e.g. with `C-SPC C-SPC M-f'.
> 4. Switch back to *scratch*.
> => The region in *scratch* is now highlighted.
[...]
>> tho it probably comes with other undesirable cases.
>
> I haven't found any new ones yet, and given the above problem, I would
> be in favor of backporting your last two patches to emacs-24 (sorry I
> didn't notice the above problem earlier).

Good.  That confirms that the original issue has been solved.

> There is another apparently longer-standing behavior (at least it
> happens with -Q in 24.3, as well as emacs-24 and trunk), which I noticed
> while testing you latest patch: if you mark and highlight a region in a
> buffer and then call e.g. `C-h f' or `C-h v', when the *Help* buffer
> opens this unhighlights the region in the other buffer, although the
> latter remains the current buffer.  Is this supposed to happen, and if
> so, why?  (If it's not supposed to happen, I'll open a new bug.)

I can't reproduce this on current master.  I'm going to assume that it's
been fixed some time in the last five years.

It therefore looks like everything is done here, and I'm closing this
bug.  If that's incorrect, please reopen the bug.

Best regards,
Stefan Kangas

--- End Message ---