From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: 13225@debbugs.gnu.org
Subject: bug#13225: 24.3.50; Non-selected window has not mode-line-inactive face
Date: Sat, 22 Dec 2012 11:56:28 -0500 [thread overview]
Message-ID: <jwvvcbukp1l.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <50D5DA43.1070008@gmx.at> (martin rudalics's message of "Sat, 22 Dec 2012 17:05:23 +0100")
>>> ... and while we compute the mode line we don't care whether
>>> selected_frame-> selected_window equals selected_window.
>> What makes you think so?
> So we do?
I believe we always do, especially when (potentially) running Elisp
code, which can in turn run pretty much any code.
>>> Wouldn't it be more correct to handle this as in
>>> run_window_configuration_change_hook?
>> I don't know how run_window_configuration_change_hook handles "this".
> Hmmm... that's your code so I can only provide my interpretation of it:
> run_window_configuration_change_hook uses select_window_norecord (which
> preserves the selected_frame->selected_window = selected_window property
> we, according to your question above, do care about. display_mode_lines
> does only XSETWINDOW (selected_window, w) which does not preserve that
> property IIUC.
Oh, that's what you mean. Yes, maybe we could/should just use
select_window(_norecord) (which is not just the way
run_window_configuration_change_hook does it, but is more generally the
normal way to do it). My recent change already brings display_mode_lines
closer to what select_window does.
Stefan
next prev parent reply other threads:[~2012-12-22 16:56 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 [this message]
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
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=jwvvcbukp1l.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13225@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).