unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13225@debbugs.gnu.org
Subject: bug#13225: 24.3.50; Non-selected window has not mode-line-inactive face
Date: Thu, 20 Dec 2012 10:59:00 +0100	[thread overview]
Message-ID: <50D2E164.8090300@gmx.at> (raw)
In-Reply-To: <83zk1anhzd.fsf@gnu.org>

 > I can fix this with the kludge shown below, but do we care about yet
 > another global variable, in addition to selected_window?  If we don't
 > want this, then the only other way I see is to drag this window all
 > the way down to display_mode_lines through the calling sequences.
 > (That's assuming that only the mode-line display wants to know about
 > the _real_ selected_window.)

There might still be glitches with the region as Angelo mentioned in the
previous thread.  But I am surprised that currently the cursor is drawn
correctly, that is, a hollow box is drawn on the non-selected frame's
window.  How is that managed without a kludge similar to the one you
describe here?

In any case, I think that some crashes Drew reported could be due to the
inconsistency Stefan tries to resolve here.  So it might be better to go
on with the changes and look first whether these crashes disappear.  You
can always revert them later after we gained some experience.

martin





  parent reply	other threads:[~2012-12-20  9:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19  8:12 bug#13225: 24.3.50; Non-selected window has not mode-line-inactive face martin rudalics
2012-12-19 16:07 ` Eli Zaretskii
2012-12-19 18:30   ` Stefan Monnier
2012-12-19 19:16     ` Drew Adams
2012-12-19 19:28       ` Drew Adams
2012-12-19 20:07         ` Stefan Monnier
2012-12-19 20:56           ` Drew Adams
2012-12-20  0:52             ` Stefan Monnier
2012-12-19 21:36     ` Eli Zaretskii
2012-12-20  2:08       ` Stefan Monnier
2012-12-20  9:59     ` martin rudalics
2012-12-20 14:03       ` Stefan Monnier
2012-12-20 16:28         ` Eli Zaretskii
2012-12-20 17:24           ` martin rudalics
2012-12-20 17:37             ` Eli Zaretskii
2012-12-21  9:15               ` martin rudalics
2012-12-21  9:35                 ` Eli Zaretskii
2012-12-21 14:24                   ` martin rudalics
2012-12-21 14:43                     ` Eli Zaretskii
2012-12-20 17:25         ` martin rudalics
2012-12-20 18:07           ` Stefan Monnier
2012-12-21  9:16             ` martin rudalics
2012-12-22 15:52               ` Stefan Monnier
2012-12-22 16:05                 ` martin rudalics
2012-12-22 16:56                   ` Stefan Monnier
2012-12-22 17:42                     ` martin rudalics
2012-12-23 13:41                       ` Stefan Monnier
2012-12-23 14:03                         ` martin rudalics
2012-12-23 15:40                           ` Stefan Monnier
2012-12-20  9:59   ` martin rudalics [this message]
2012-12-20 17:09     ` Eli Zaretskii
2012-12-20 17:24       ` martin rudalics
2013-01-04  8:28 ` Glenn Morris

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=50D2E164.8090300@gmx.at \
    --to=rudalics@gmx.at \
    --cc=13225@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).