From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Barrett <dbarrett@blazemonger.com>
Cc: npostavs@users.sourceforge.net, 24554@debbugs.gnu.org
Subject: bug#24554: 24.5; kill-ring-save fails to give visual feedback on first run, but does on the second
Date: Tue, 27 Sep 2016 17:45:45 +0300 [thread overview]
Message-ID: <8337klcsfa.fsf@gnu.org> (raw)
In-Reply-To: <22506.26733.265243.529443@blazemonger.com> (message from Daniel Barrett on Tue, 27 Sep 2016 08:39:09 -0400)
> Date: Tue, 27 Sep 2016 08:39:09 -0400
> From: Daniel Barrett <dbarrett@blazemonger.com>
> Cc: Daniel Barrett <dbarrett@blazemonger.com>, 24554@debbugs.gnu.org
>
> On September 27, 2016, npostavs@users.sourceforge.net wrote:
> >Are you saying that region highlighting doesn't work in Emacs 24.5 in
> >graphical mode?
>
> Correct.
In that case, I cannot reproduce it here. Region highlighting does
work for me in both text and GUI mode.
> (And in addition, kill-ring-save doesn't blink the point and mark
> on the first try, but it does on the second, third, etc.)
It doesn't blink on the first try because the region is highlighted,
as far as Emacs is concerned. So the fact you don't see the highlight
is the only problem in this case, and that problem is specific to your
system, somehow.
If you invoke "emacs -Q" n GUI mode and then type
M-x list-faces-display RET
does the 'region' face has a distinct background color?
next prev parent reply other threads:[~2016-09-27 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 12:00 bug#24554: 24.5; kill-ring-save fails to give visual feedback on first run, but does on the second Daniel Barrett
2016-09-27 12:33 ` npostavs
2016-09-27 12:39 ` Daniel Barrett
2016-09-27 14:45 ` Eli Zaretskii [this message]
2016-09-27 16:05 ` Daniel Barrett
2016-09-27 16:27 ` Eli Zaretskii
2016-09-27 22:33 ` Daniel Barrett
2016-09-28 14:46 ` Eli Zaretskii
2016-09-28 22:41 ` Daniel Barrett
2016-09-29 2:47 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8337klcsfa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24554@debbugs.gnu.org \
--cc=dbarrett@blazemonger.com \
--cc=npostavs@users.sourceforge.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.