unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stephen Berman <stephen.berman@gmx.net>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 6316@debbugs.gnu.org
Subject: bug#6316: 24.0.50; unexpected region highlighting
Date: Wed, 2 Jul 2014 06:29:19 -0700 (PDT)	[thread overview]
Message-ID: <8270a362-a76c-46bd-bf13-fc5ff59cc911@default> (raw)
In-Reply-To: <8738ek2jqd.fsf@rosalinde.fritz.box>

> 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.

But after a command the region is deactivated, so depending on your
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.

To see the effect of the variable: C-SPC M-f C-x C-o C-SPC M-f.





  reply	other threads:[~2014-07-02 13:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31  7:30 bug#6316: 24.0.50; unexpected region highlighting with disabled transient-mark-mode Stephen Berman
2010-05-31 12:29 ` Stephen Berman
2012-05-29 20:42   ` bug#6316: 24.0.50; unexpected region highlighting Stephen Berman
2014-05-27 13:57     ` Stephen Berman
2014-05-27 15:00       ` Stefan Monnier
2014-05-27 20:51         ` Stephen Berman
2014-06-23 16:31           ` Stefan Monnier
2014-06-24 15:59             ` Stephen Berman
2014-07-01 18:14               ` Stefan Monnier
2014-07-02  9:27                 ` Stephen Berman
2014-07-02 13:29                   ` Drew Adams [this message]
2014-07-02 13:50                     ` Stephen Berman
2019-09-26 10:17 ` Stefan Kangas

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=8270a362-a76c-46bd-bf13-fc5ff59cc911@default \
    --to=drew.adams@oracle.com \
    --cc=6316@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stephen.berman@gmx.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).