From: Yuri Khan <yuri.v.khan@gmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Operation of format-mode-line
Date: Thu, 25 Jul 2024 22:26:01 +0700 [thread overview]
Message-ID: <CAP_d_8XV3qskKJogzZY4X_+h1wzfR5Q9KYnJKdA504CcG0TvmA@mail.gmail.com> (raw)
In-Reply-To: <ct3r-DS_knVmOlOCFGzqE7-EZyNzHpRPYvr7TTkpm83DWs6ggCvRkenWdLCAxZTlCmyBFFYmMGRtAmHeL1VWRtrVZQH17UOLirJbvYF7zAk=@protonmail.com>
On Thu, 25 Jul 2024 at 20:20, Heime <heimeborgia@protonmail.com> wrote:
> I understand. propertized-buffer-identification has hardwired keymap etc
It hardwires the keymap to the value of the variable
‘mode-line-buffer-identification-keymap’, but you are allowed to
modify that variable.
> and calling it only sets the format used for the buffer identification
> name.
I’m pretty sure it will set the format for whatever modeline
constructs you pass in.
That said, the function ‘propertized-buffer-identification’ is not
very complex; you can copy it and adapt for your custom modeline
parts.
(For myself, I’m not bothering with mouse bindings. Switching buffers
one step at a time only really works when you have three or so, and
that just does not happen. Switching between a few hundred buffers is
better done via IBuffer anyway.)
next prev parent reply other threads:[~2024-07-25 15:26 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 21:58 Operation of format-mode-line Heime
2024-07-22 23:35 ` Heime
2024-07-23 11:11 ` Eli Zaretskii
2024-07-23 11:08 ` Eli Zaretskii
2024-07-23 16:37 ` Heime
2024-07-23 17:48 ` Eli Zaretskii
2024-07-23 18:56 ` Heime
2024-07-23 19:07 ` Eli Zaretskii
2024-07-23 19:13 ` Heime
2024-07-24 2:25 ` Eli Zaretskii
2024-07-24 2:26 ` Eli Zaretskii
2024-07-24 10:18 ` Heime
2024-07-24 11:47 ` Eli Zaretskii
2024-07-24 12:21 ` Heime
2024-07-24 12:33 ` Eli Zaretskii
2024-07-24 12:45 ` Heime
2024-07-24 12:49 ` Eli Zaretskii
2024-07-24 13:08 ` Heime
2024-07-24 13:23 ` Eli Zaretskii
2024-07-24 14:01 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-07-24 15:40 ` Heime
2024-07-24 16:07 ` Yuri Khan
2024-07-24 16:30 ` Heime
2024-07-25 7:18 ` Eli Zaretskii
[not found] ` <xcc1gVM6XKE-ico4XNriwG861wQPgutbXkfzbmOm-zJodpgHcHGR1huyU9K6BxLKj74YmoIgW1gJ=5FKLijHm5xBpeE8=5FZOS0Gt004N88wyoI=3D@protonmail.com>
[not found] ` <CAP=5Fd=5F8W6kgSQeeG2j2M3=5Fb1tt+x1wFWRvbYGhhO+SiUKy8DBoQ@mail.gmail.com>
[not found] ` <ct3r-DS=5FknVmOlOCFGzqE7-EZyNzHpRPYvr7TTkpm83DWs6ggCvRkenWdLCAxZTlCmyBFFYmMGRtA mHeL1VWRtrVZQH17UOLirJbvYF7zAk=3D@protonmail.com>
[not found] ` <CAP=5Fd=5F8XV3qskKJogzZY4X=5F+h1wzfR5Q9KYnJKdA504CcG0TvmA@mail.gmail.com>
2024-07-25 12:39 ` Heime
2024-07-25 12:50 ` Yuri Khan
2024-07-25 13:20 ` Heime
2024-07-25 15:26 ` Yuri Khan [this message]
2024-07-25 16:01 ` Heime
2024-07-25 17:27 ` Heime
2024-07-25 18:18 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-07-25 19:23 ` Heime
2024-07-26 11:38 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-07-26 12:47 ` Heime
2024-07-26 13:26 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-07-26 14:18 ` Heime
2024-07-26 14:40 ` Yuri Khan
2024-07-26 15:03 ` Heime
2024-07-26 17:32 ` Heime
2024-07-26 20:30 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-07-27 6:01 ` Eli Zaretskii
2024-07-27 11:08 ` Heime
2024-07-27 12:06 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-07-28 11:00 ` Heime
2024-07-28 15:30 ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-07-28 16:14 ` Heime
2024-07-28 16:53 ` Heime
2024-07-28 17:29 ` Heime
2024-07-28 17:46 ` Christopher Dimech
2024-07-28 17:59 ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-07-28 18:39 ` Heime
2024-07-28 20:48 ` [External] : " Drew Adams
2024-07-29 10:26 ` Michael Heerdegen
2024-07-24 16:35 ` Eli Zaretskii
2024-07-24 16:45 ` Heime
[not found] <RHkfCJX8r5At5BX=5Ff30hL2EoYH6qQXzEbjBXr0Lw1DL94KYNXjJsdaLrB-r8fd6-DTqkNbsw1fFi-QzBBtR-lcJGJ5cz22QjLYYhCqqgfvg=3D@protonmail.com>
[not found] ` <f-AU6lFTwKIVxp95wzU6pdhSaxX45u25TLr7ozfvGH=5FDr7B2IhDHVhKR92YDxgzwiaR99n6190RVjtknhebwf8vMT60so-OqhThZdeIzLhs=3D@protonmail.com>
[not found] ` <CAP=5Fd=5F8V7KJr3kji6rhVAA-+6cYjxeQBkYJkSjz4cPt-QDwWWig@mail.gmail.com>
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=CAP_d_8XV3qskKJogzZY4X_+h1wzfR5Q9KYnJKdA504CcG0TvmA@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@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.
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).