From: Juri Linkov <juri@linkov.net>
To: Valtteri Vuorikoski <vuori@notcom.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 40225@debbugs.gnu.org
Subject: bug#40225: 27.0.90; abort with apparent stack explosion in lsp-mode
Date: Thu, 10 Feb 2022 20:50:25 +0200 [thread overview]
Message-ID: <86a6eyr3lr.fsf@mail.linkov.net> (raw)
In-Reply-To: <20220210090948.5nnlwnsa2qmmjmmy@donburi.himad.notcom.org> (Valtteri Vuorikoski's message of "Thu, 10 Feb 2022 11:09:48 +0200")
> So with regard to the subject of this issue I think it's fine to close
> this. Not having tab-line-mode call tab-line-tabs-buffer-list-function
> on pretty much every possible event might be a worthwhile improvement
> at some point though (I haven't checked whether things improved in
> Emacs 28).
Pretty much every event can kill buffers, and the list of buffers
displayed on the tab line should reflect the change of the buffer list.
The existing optimization takes care only to not redraw the tab line
on every event when the buffer list is unchanged.
next prev parent reply other threads:[~2022-02-10 18:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 14:03 bug#40225: 27.0.90; abort with apparent stack explosion in lsp-mode Valtteri Vuorikoski
2020-03-25 16:20 ` Eli Zaretskii
2020-03-25 16:25 ` Valtteri Vuorikoski
2020-03-25 16:29 ` Eli Zaretskii
2020-03-26 15:42 ` Valtteri Vuorikoski
2020-03-26 18:49 ` Eli Zaretskii
2020-03-31 13:59 ` Valtteri Vuorikoski
2020-03-31 15:53 ` Eli Zaretskii
2020-03-31 18:39 ` Valtteri Vuorikoski
2020-04-12 10:40 ` Valtteri Vuorikoski
2020-05-15 7:28 ` Valtteri Vuorikoski
2022-02-10 7:21 ` Lars Ingebrigtsen
2022-02-10 9:09 ` Valtteri Vuorikoski
2022-02-10 11:36 ` Lars Ingebrigtsen
2022-02-10 18:50 ` Juri Linkov [this message]
2022-02-10 19:49 ` Valtteri Vuorikoski
2022-02-11 8:34 ` Juri Linkov
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=86a6eyr3lr.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=40225@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=vuori@notcom.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).