From: Eli Zaretskii <eliz@gnu.org>
To: David Howells <dhowells@redhat.com>
Cc: 64439@debbugs.gnu.org
Subject: bug#64439: 28.2; auto-fill-mode gets turned on all over the place
Date: Mon, 03 Jul 2023 19:15:15 +0300 [thread overview]
Message-ID: <83h6qlm0oc.fsf@gnu.org> (raw)
In-Reply-To: <1034974.1688399705@warthog.procyon.org.uk> (message from David Howells on Mon, 03 Jul 2023 16:55:05 +0100)
> Cc: dhowells@redhat.com
> From: David Howells <dhowells@redhat.com>
> Date: Mon, 03 Jul 2023 16:55:05 +0100
>
> I'm seeing an issue in which auto-fill-mode gets turned on for all the buffers
> in a running emacs instance, including the command entry window (M-x, grep,
> compile, etc.). This is a problem as it starts mangling the code I'm working
> on and making it harder to enter long commands (such as grep or compile
> commands). I can turn it off manually on most buffers (though not the command
> window), but it immediately turns back on in a buffer if I have to reload it.
>
> The problem has happened in several emacs instances now. It shows up in the
> instances I've been using to edit C code and view patches. It takes a little
> while for the problem to manifest when it does. I'm not sure what triggers
> it.
Try evaluating this:
(defun my-watcher (_symbol new-value operation where)
(error "auto-fill-mode: %s %s %s" new-value operation where))
(add-variable-watcher 'auto-fill-function 'my-watcher)
(debug-on-entry 'my-watcher)
and run your sessions with this. Whenever auto-fill-mode is turned
on, you will get a backtrace. If you turn this mode yourself, and
don't want to be annoyed by entering the debugger each time, remove
the last line from the recipe: then you will just see a message when
auto-fill-mode is turned on, and will need to investigate which code
did that.
next prev parent reply other threads:[~2023-07-03 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:55 bug#64439: 28.2; auto-fill-mode gets turned on all over the place David Howells
2023-07-03 16:15 ` Eli Zaretskii [this message]
2023-07-03 17:48 ` David Howells
2023-07-03 18:29 ` Eli Zaretskii
2023-07-09 5:57 ` Jim Porter
2023-07-09 6:45 ` Eli Zaretskii
2023-07-09 18:00 ` Jim Porter
2023-07-10 11:59 ` Eli Zaretskii
2023-07-10 16:00 ` Jim Porter
2023-07-10 17:28 ` Michael Albinus
2023-07-10 17:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-10 20:57 ` Jim Porter
2023-07-10 21:54 ` Jim Porter
2023-07-10 23:53 ` Jim Porter
2023-07-11 11:31 ` Eli Zaretskii
2023-07-11 16:07 ` Jim Porter
2023-07-11 18:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-12 2:23 ` Jim Porter
2023-07-12 12:13 ` Eli Zaretskii
2023-07-03 18:14 ` Jim Porter
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=83h6qlm0oc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64439@debbugs.gnu.org \
--cc=dhowells@redhat.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).