all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: [n_schumacher@web.de: modification hooks called only once in c-mode]
Date: Sun, 12 Aug 2007 00:14:43 -0400	[thread overview]
Message-ID: <E1IK4qh-0006Qx-1J@fencepost.gnu.org> (raw)
In-Reply-To: <874pj6j3te.fsf@stupidchicken.com> (message from Chong Yidong on Fri, 10 Aug 2007 20:46:37 -0400)

    One simple fix is to bind inhibit-modification-hooks in
    c-after-change.

    A deeper fix would be to make report_overlay_modification check if it
    is being called in a modification hook, and take steps to prevent
    scheduled hooks from being rubbed out.  I'm not sure this behavior is
    significantly more "correct" than the existing one, however; it may be
    better to leave it as is.

It seems to me that the cleanest kind of fix is to save the relevant
data around actually invoking the hooks.  How hard or ugly is that?

  reply	other threads:[~2007-08-12  4:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  4:55 [n_schumacher@web.de: modification hooks called only once in c-mode] Richard Stallman
2007-08-11  0:46 ` Chong Yidong
2007-08-12  4:14   ` Richard Stallman [this message]
2007-08-12  5:50   ` Stefan Monnier
2007-08-13  0:52     ` Richard Stallman
2007-08-13  4:10       ` Stefan Monnier
2007-08-13  5:59         ` David Kastrup
2007-08-16 20:46           ` Stefan Monnier
2007-08-13  9:40         ` martin rudalics
2007-08-13 14:01           ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2007-07-31 20:22 Richard Stallman
2007-07-24 22:17 Richard Stallman
2007-08-01  9:16 ` Johan Bockgård
2007-08-02 15:45   ` Richard Stallman
2007-07-17 15:06 Richard Stallman

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=E1IK4qh-0006Qx-1J@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.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 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.