From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: bug-cc-mode@gnu.org
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: CC mode 5.31.4: c-{beginning, end}-of-defun try to modify buffer
Date: Tue, 08 Jan 2008 21:14:25 +0100 [thread overview]
Message-ID: <4783D9A1.7070503@gmail.com> (raw)
In-Reply-To: <20080108200301.GA2238@muc.de>
Alan Mackenzie wrote:
> Hi, Andreas!
>
> On Tue, Jan 08, 2008 at 06:13:40PM +0100, Andreas Schwab wrote:
>> c-{beginning,end}-of-defun try to modify the buffer and thus trigger
>> ask-user-about-supersession-threat. To reproduce load a C file and
>> touch the underlying file. Then type C-M-e repeatedly. After some
>> tries you will be asked whether you want to edit the buffer.
>
> Ouch!
>
> Yes, I can reproduce this. At a guess, it's happening because of CC
> Mode's extensive use of text properties. I don't (yet) see why it only
> happens after a several C-M-e's rather than the first. Applying text
> properties counts as modifying the buffer (I think this is a Bad Thing),
> and the primitive function which applies the text properties seems to be
> checking for the file having been modified. Or something like that.
Are you talking about the text properties that font lock applies? I
believe those does not mark the buffer as modified.
next prev parent reply other threads:[~2008-01-08 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jed4sci6kb.fsf@sykes.suse.de>
2008-01-08 20:03 ` CC mode 5.31.4: c-{beginning, end}-of-defun try to modify buffer Alan Mackenzie
2008-01-08 20:14 ` Lennart Borgman (gmail) [this message]
2008-01-08 20:17 ` martin rudalics
2008-01-08 20:22 ` Lennart Borgman (gmail)
2008-01-08 21:38 ` martin rudalics
2008-01-08 21:58 ` Lennart Borgman (gmail)
2008-01-08 22:39 ` martin rudalics
2008-01-08 22:47 ` Alan Mackenzie
2008-01-09 9:02 ` Alan Mackenzie
2008-01-09 9:16 ` martin rudalics
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=4783D9A1.7070503@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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).