From: Michael Heerdegen <michael_heerdegen@web.de>
To: Juri Linkov <juri@linkov.net>
Cc: Alexandros Prekates <aprekates@posteo.net>,
Robert Pluim <rpluim@gmail.com>,
57848@debbugs.gnu.org
Subject: bug#57848: 29.0.50; Problems with private tab-line-tab-name-function
Date: Mon, 31 Oct 2022 09:58:14 +0100 [thread overview]
Message-ID: <87h6zks72x.fsf@web.de> (raw)
In-Reply-To: <86bkptmcrx.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 30 Oct 2022 19:39:30 +0200")
Juri Linkov <juri@linkov.net> writes:
> Now this is fixed by using the same solution as used in
> `Info-set-mode-line' to escape %-constructs.
Thanks.
| +(defvar tab-line-cache-key-function #'tab-line-cache-key-default
| + "Function that adds more cache keys.
| +It has one argument with a list of tabs, and returns a list of cache keys.
| +You can use `add-function' to add more cache keys.")
There is something wrong with the second sentence of the doc string.
> Now a new function variable `tab-line-cache-key-function' is pushed,
> so you can add more cache keys with something like this:
>
> #+begin_src emacs-lisp
> (add-hook 'Info-mode-hook
> (defun my-setup-tab-line-for-Info-mode ()
> (add-function :filter-return (local 'tab-line-cache-key-function)
> (lambda (cache-keys)
> (cons mode-line-buffer-identification cache-keys)))
> (tab-line-mode +1)
> (setq-local
> tab-line-tab-name-function
> (lambda (b &optional _bs)
> [...]
> #+end_src
>
> Then visiting even such nodes as (info "(elisp) %-Constructs")
> doesn't have anymore the problem that you found above.
Very cool, thanks. I'll try it out a bit and report back.
Michael.
next prev parent reply other threads:[~2022-10-31 8:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 4:39 bug#57848: 29.0.50; Problems with private tab-line-tab-name-function Michael Heerdegen
2022-10-30 7:24 ` Juri Linkov
2022-10-30 12:02 ` Michael Heerdegen
2022-10-30 17:39 ` Juri Linkov
2022-10-31 8:58 ` Michael Heerdegen [this message]
2022-11-09 2:07 ` Michael Heerdegen
2022-11-09 7:41 ` Juri Linkov
2022-11-12 1:52 ` Michael Heerdegen
2022-11-12 18:19 ` Juri Linkov
2022-11-13 17:58 ` Juri Linkov
2022-11-14 3:49 ` Michael Heerdegen
2022-11-14 7:47 ` Juri Linkov
2022-11-15 3:43 ` Michael Heerdegen
2022-12-15 17:16 ` Juri Linkov
2022-12-17 7:35 ` Michael Heerdegen
2022-12-17 17:44 ` Juri Linkov
2022-12-18 1:16 ` Michael Heerdegen
2022-12-18 8:40 ` Juri Linkov
2023-01-10 14:06 ` Michael Heerdegen
2023-01-10 17:44 ` Juri Linkov
2022-11-18 11:49 ` Michael Heerdegen
2022-11-09 7:39 ` Juri Linkov
2022-11-09 23:30 ` Michael Heerdegen
2022-11-10 18:36 ` Juri Linkov
2022-11-12 2:44 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6zks72x.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=57848@debbugs.gnu.org \
--cc=aprekates@posteo.net \
--cc=juri@linkov.net \
--cc=rpluim@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.