GNU bug report logs - #64439
28.2; auto-fill-mode gets turned on all over the place

Previous Next

Full log

View this message in rfc822 format

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: dhowells <at> redhat.com, Jim Porter <jporterbugs <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>, 64439 <at> debbugs.gnu.org, Noam Postavsky <npostavs <at> gmail.com>
Subject: bug#64439: 28.2; auto-fill-mode gets turned on all over the place
Date: Mon, 10 Jul 2023 13:28:22 -0400

[ Adding Noam, because this seems related to
  https://github.com/joaotavora/yasnippet/issues/919.  ]

> Stefan, are there any other situations where setting a buffer-local
> variable will actually set its default value?

Depends what you mean, but if you do:

    (let ((auto-fill-function #'foo))
      [...]
      (setq auto-fill-function #'bar)
      [...])

then `auto-fill-function` will not be made buffer-local.  But that won't
set the toplevel default value either (that default value will be
reverted to nil when we leave the `let`).

Interactions between buffer-local values and let-bindings can be tricky,
tho, so there might still be bugs in there.

Jim, did you collect various backtraces?  Do you still have them?
Can you check more thoroughly to try and see what they all have in common
(in addition to `ask-user-about-supersession-threat` and "Tramp")?

Can you get an interactive backtrace buffer?  If so, I'd be curious to
know the values that

    e (list auto-fill-function (default-value 'auto-fill-function)) RET

returns and more importantly, how it varies from frame to frame.


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.