unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Raffael Stocker <r.stocker@mnet-mail.de>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 72532@debbugs.gnu.org
Subject: bug#72532: [PATCH] ; lisp/progmodes/which-func.el (which-function-mode): check buffer
Date: Fri, 09 Aug 2024 21:59:46 +0200	[thread overview]
Message-ID: <yplm8qx5wjpp.fsf@mnet-mail.de> (raw)
In-Reply-To: <yplmcymh7g0a.fsf@mnet-mail.de> (Raffael Stocker's message of "Fri, 09 Aug 2024 19:39:01 +0200")

Raffael Stocker <r.stocker@mnet-mail.de> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> `buffer-list' is documented to return a list of all live buffers, so it
>> would be good to understand why buffers are getting killed in this loop.
>>
>> In other words, are we sure that your patch is not just covering up some
>> problem elsewhere?
>
> I guess it is.  I just did some trying out and found that I can reliably
> make the problem appear and disappear by enabling/disabling eglot.
>
> I will spend some more time with this and see what more I can find out.

It seems the problem comes from me putting ‘which-function-mode’ into
‘prog-mode-hook’, which I probably shouldn't have done.  Each time I
load a file in some prog-mode while eglot is active managing at least
one buffer, which-function-mode seems to get re-enabled and cause my
problems.  If I just globally enable it (as I probably should do), this
doesn't happen.

In short, seems to be a pilot error.
Why I still can't reproduce it with ‘emacs -Q’, I do not know.
Still, not worth a patch it seems, sorry for the noise.





  reply	other threads:[~2024-08-09 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 19:48 bug#72532: [PATCH] ; lisp/progmodes/which-func.el (which-function-mode): check buffer Raffael Stocker
2024-08-09  5:27 ` Eli Zaretskii
2024-08-09 17:35   ` Raffael Stocker
2024-08-09  9:45 ` Stefan Kangas
2024-08-09 17:39   ` Raffael Stocker
2024-08-09 19:59     ` Raffael Stocker [this message]
2024-08-15  8:36       ` 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=yplm8qx5wjpp.fsf@mnet-mail.de \
    --to=r.stocker@mnet-mail.de \
    --cc=72532@debbugs.gnu.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).