unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53629@debbugs.gnu.org, "José Júnior" <jjnilton@gmail.com>
Subject: bug#53629: 27.1: add option to change face `mode-line-buffer-id` when mode-line is inactive
Date: Wed, 02 Feb 2022 22:00:41 +0200	[thread overview]
Message-ID: <86ee4lxcly.fsf@mail.linkov.net> (raw)
In-Reply-To: <874k5hur34.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 02 Feb 2022 18:16:15 +0100")

>> I'm not sure how I can customize the way I want with
>> `mode-line-buffer-identification` yet, so maybe that's why having another face to
>> customize the inactive state still makes sense. I also found this discussion:
>> https://emacs.stackexchange.com/questions/10033/change-mode-line-buffer-id-face-for-inactive-windows
>> - but I don't think there's a solution there.
>
> No, there doesn't seem to be.  I really thought there was a way to get
> at whether the window we're making the buffer line for is selected or
> not, but there doesn't seem to be?  Anybody know?

tab-line.el uses such trick:

         (face (if (eq buffer (window-buffer))
                   (if (eq (selected-window) (old-selected-window))
                       'tab-line-tab-current
                     'tab-line-tab)
                 'tab-line-tab-inactive))





  reply	other threads:[~2022-02-02 20:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 20:19 bug#53629: 27.1: add option to change face `mode-line-buffer-id` when mode-line is inactive José Júnior
2022-01-30  0:24 ` bug#53629: [External] : " Drew Adams
2022-01-30 16:46   ` José Júnior
2022-01-31 20:09     ` José Júnior
2022-01-31 20:38       ` Drew Adams
2022-01-31 20:49       ` Drew Adams
2022-01-31 20:55       ` Drew Adams
2022-01-30 16:18 ` Lars Ingebrigtsen
2022-01-30 16:48   ` José Júnior
2022-01-30 20:33     ` Lars Ingebrigtsen
2022-01-31 20:07       ` José Júnior
2022-02-02 17:16         ` Lars Ingebrigtsen
2022-02-02 20:00           ` Juri Linkov [this message]
2022-02-03 19:00             ` Lars Ingebrigtsen
2022-02-04  3:15               ` José Júnior
2022-02-04  9:58                 ` martin rudalics
2022-02-05  2:03                   ` José Júnior
2022-02-05  7:47                     ` martin rudalics
2022-02-05  7:52                       ` Lars Ingebrigtsen
2022-02-05 12:10                         ` José Júnior
2022-02-05 21:46                           ` Lars Ingebrigtsen
2022-02-05 22:11                             ` José Júnior
2022-02-06 17:59                             ` Juri Linkov
2022-02-06 22:48                               ` Lars Ingebrigtsen
2022-02-08 11:48                                 ` José Júnior
2022-02-08 18:22                                   ` martin rudalics

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=86ee4lxcly.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=53629@debbugs.gnu.org \
    --cc=jjnilton@gmail.com \
    --cc=larsi@gnus.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).