From: Juri Linkov <juri@linkov.net>
To: Jared Finder <jared@finder.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>,
68334@debbugs.gnu.org
Subject: bug#68334: 29.1; tool-bar-make-keymap-1 does not work on terminals
Date: Wed, 10 Jan 2024 09:24:35 +0200 [thread overview]
Message-ID: <86wmshoglk.fsf@mail.linkov.net> (raw)
In-Reply-To: <2620b07ece7042ee685f1a596ffe70d9@finder.org> (Jared Finder via's message of "Tue, 09 Jan 2024 11:28:17 -0800")
> If this goes in core, I'd like to make window-tool-bar-mode and
> tab-line-mode work nicely together. Right now they both just overwrite
> tab-line-format, but I think a better implementation would result in them
> both appears in the tab-line side by side when both are enabled. In other
> words, if both are enabled tab-line-format would have a value like
>
> ((:eval (tab-line-format)) " " (:eval (window-tool-bar-string))).
>
> I'm also happy to also add an additional line. At that point there'd be
> three lines, so would it be worth it to add an option to control the order
> of the lines? I can imagine a variable that contains lines / prefix events
> for lines above a buffer and controls the order. I certainly would
> appreciate this flexibility.
Instead of asking the users to set tab-line-format to the expression above
adding a simple option would be nice. Such option could define
how to combine the window tool-line with the tab-line.
next prev parent reply other threads:[~2024-01-10 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 21:39 bug#68334: 29.1; tool-bar-make-keymap-1 does not work on terminals Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-08 23:04 ` bug#68334: window-tool-bar (bug#68334) Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-09 13:06 ` Eli Zaretskii
2024-01-09 4:57 ` bug#68334: 29.1; tool-bar-make-keymap-1 does not work on terminals Stefan Kangas
2024-01-09 7:58 ` Juri Linkov
2024-01-09 13:13 ` Eli Zaretskii
2024-01-09 18:39 ` Stefan Kangas
2024-01-09 18:57 ` Eli Zaretskii
2024-01-09 19:08 ` Stefan Kangas
2024-01-09 19:28 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-09 19:56 ` Eli Zaretskii
2024-01-10 7:24 ` Juri Linkov [this message]
2024-01-09 12:40 ` Eli Zaretskii
2024-01-10 22:59 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 10:51 ` Eli Zaretskii
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=86wmshoglk.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=68334@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jared@finder.org \
--cc=stefankangas@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 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).