all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 21:29:38 +0300	[thread overview]
Message-ID: <837crgn90u.fsf@gnu.org> (raw)
In-Reply-To: <1211099.1688406521@warthog.procyon.org.uk> (message from David Howells on Mon, 03 Jul 2023 18:48:41 +0100)

> From: David Howells <dhowells@redhat.com>
> Cc: dhowells@redhat.com, 64439@debbugs.gnu.org
> Date: Mon, 03 Jul 2023 18:48:41 +0100
> 
> Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > 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.
> 
> I restarted emacs and added the above.  I was editing some C code, pressed
> enter and got:
> 
> 	Debugger entered--entering a function:
> 	* my-watcher(auto-fill-function nil set nil)
> 	  newline(nil 1)
> 	  funcall-interactively(newline nil 1)
> 	  command-execute(newline)

Hmm...

> auto-fill-mode didn't seem to turn on, though

Because the function newline only let-binds auto-fill-function
locally.

I guess tracking down this problem will be harder, then.  I hope I at
least gave you some ideas with which you will be able to construct a
suitable trap and find the culprit.  Good luck!





  reply	other threads:[~2023-07-03 18:29 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
2023-07-03 17:48 ` David Howells
2023-07-03 18:29   ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837crgn90u.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 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.