GNU bug report logs - #6316
24.0.50; unexpected region highlighting with disabled transient-mark-mode

Previous Next

Full log

Message #38 received at 6316 <at> debbugs.gnu.org (full text, mbox):

From: Stephen Berman <stephen.berman <at> gmx.net>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, 6316 <at> debbugs.gnu.org
Subject: Re: bug#6316: 24.0.50; unexpected region highlighting
Date: Wed, 02 Jul 2014 15:50:37 +0200

On Wed, 2 Jul 2014 06:29:19 -0700 (PDT) Drew Adams <drew.adams <at> oracle.com> wrote:

>> 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.)
>
> `highlight-nonselected-windows' = t controls whether the region remains
> highlighted in nonselected windows.

As I noted, when you call `C-h f' or `C-h v', it doesn't make the *Help*
buffer current, i.e., the window containing the now unhighlighted region
is still selected.

> But after a command the region is deactivated, so depending on your
      ^^^^^^^^^^^^^^^
      "After certain non-motion commands, including any command that
changes the text in the buffer," according to (emacs)Mark.

> recipe you will not notice the effect of the variable.  IOW, in your
> recipe, your command `C-h v' deactivated the region in the original
> buffer.

Evidently it did; but should it, and if so, why?

Steve Berman

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.