all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Ludwig, Mark'" <ludwig.mark@siemens.com>,
	"'Steven Degutis'" <sbdegutis@gmail.com>,
	<help-gnu-emacs@gnu.org>
Subject: RE: `auto-dim-other-windows` -- scrutiny invited
Date: Wed, 3 Apr 2013 09:37:14 -0700	[thread overview]
Message-ID: <DE18E951366C480B9452A487838EEF51@us.oracle.com> (raw)
In-Reply-To: <BC5672F8AD4C054BAF167C9801500D1ABCB0FB65@USSLMMBX003.net.plm.eds.com>

> I have to confess to never noticing the change in mode line
> shading (until this thread)!

The default mode-line face difference is not great - not pronounced enough, IMO.

FWIW, I use quite different backgrounds for these two faces:

 mode-line:          PaleGoldenrod
 mode-line-inactive: LightGray

I also have the cursor change automatically to a box (from a bar) when Emacs is
idle (2 sec, by default).  The (trivial) code for this is in oneonone.el.
http://www.emacswiki.org/emacs-en/download/oneonone.el

For even more visibility you can have Emacs show crosshairs (vertical and 
horizontal lines across the window) through the cursor when Emacs is idle.
For this, see library crosshairs.el.  (Here the default is 5 sec.)
http://www.emacswiki.org/emacs-en/download/crosshairs.el

These things can help make the selected window more obvious.  Of course one
person's helpful indication is another person's distraction or annoyance. ;-)

Personally, I do not use the automatic crosshairs-when-idle highlighting.

(I do toggle crosshairs mode on/off by hitting `C-+'.  The crosshairs follow the
cursor.  But this is for a different purpose than just noticing the selected
window.)





      parent reply	other threads:[~2013-04-03 16:37 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 21:06 `auto-dim-other-windows` -- scrutiny invited Steven Degutis
2013-04-02 22:19 ` Óscar Fuentes
2013-04-02 22:48   ` Steven Degutis
2013-04-02 23:14     ` Óscar Fuentes
2013-04-02 23:19       ` Steven Degutis
     [not found]       ` <mailman.23338.1364944796.855.help-gnu-emacs@gnu.org>
2013-04-03 13:03         ` Michael Heerdegen
2013-04-03 13:27           ` Steven Degutis
     [not found] ` <mailman.23335.1364941179.855.help-gnu-emacs@gnu.org>
2013-04-03 13:11   ` Michael Heerdegen
2013-04-03 13:19     ` Steven Degutis
2013-04-03 14:44 ` Steven Degutis
2013-04-03 14:47   ` Mark Skilbeck
2013-04-03 14:52     ` Steven Degutis
2013-04-03 14:55       ` Mark Skilbeck
2013-04-03 15:09         ` Steven Degutis
2013-04-03 15:17           ` Óscar Fuentes
2013-04-03 15:15   ` Óscar Fuentes
2013-04-03 15:32     ` Steven Degutis
2013-04-03 16:03       ` Steven Degutis
2013-04-03 17:03         ` Óscar Fuentes
2013-04-03 17:13           ` Steven Degutis
2013-04-03 17:17             ` Óscar Fuentes
2013-04-03 17:42               ` Steven Degutis
2013-04-03 18:10                 ` Óscar Fuentes
2013-04-03 18:54                   ` Steven Degutis
2013-04-03 19:19                     ` Steven Degutis
2013-04-03 20:13         ` Stefan Monnier
2013-04-03 20:22           ` Steven Degutis
2013-04-03 22:23             ` Stefan Monnier
2013-04-04 21:55               ` Drew Adams
2013-04-04 22:01                 ` Steven Degutis
2013-04-05 12:49                   ` Stefan Monnier
2013-04-06 19:23                     ` Drew Adams
     [not found]       ` <mailman.23406.1365005023.855.help-gnu-emacs@gnu.org>
2013-04-03 17:20         ` Michael Heerdegen
2013-04-03 17:44           ` Steven Degutis
2013-04-03 20:55           ` Steven Degutis
2013-04-04 16:02           ` Steven Degutis
2013-04-04  7:27         ` Joost Kremers
2013-04-04 20:52           ` Ludwig, Mark
2013-04-04 20:53             ` Steven Degutis
2013-04-04 21:31               ` Steven Degutis
2013-04-03 15:57   ` Ludwig, Mark
2013-04-03 16:06     ` Steven Degutis
2013-04-03 16:37     ` Drew Adams [this message]

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=DE18E951366C480B9452A487838EEF51@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=ludwig.mark@siemens.com \
    --cc=sbdegutis@gmail.com \
    /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.