unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: file modified on opening
Date: Wed, 28 Jun 2006 14:55:41 -0600	[thread overview]
Message-ID: <e7uqdd$v1t$1@sea.gmane.org> (raw)
In-Reply-To: <20060628182441.GD24395@free.fr>

François Gannaz wrote:
> Le mer 28 jun 09:43, Mickey Ferguson a écrit :
>>> I'm using a mmm-mode for HTML and PHP files (mixing html-helper-mode,
>>> php-mode, css-mode, etc.). When I open some files, they are marked as
>>> modifed ("**" in status bar), even if I just view them from Dired. Of
>>> course, the content isn't really modified.
>> Is there any chance that something that your .emacs is doing is causing
>> the butter to be modified?  One example I can think of is if you
>> automatically enter and exit picture-mode.  A buffer that has any
>> trailing spaces at the end of a line will then be modified by trimming
>> the trailing spaces.  Now this is only one possible example, but I would
>> comment out everything in your .emacs, and then add back in, piece by
>> piece, until you might find a cause that way.

I would suspect that text properties are being added.  Mickey could
find out with `M-: (goto-char (next-property-change (point-min)))'
followed by `C-u C-x ='.

> At first, I thought it was this, but I've already narrowed my .emacs to
> 
> (require 'mmm-mode)
> (setq mmm-global-mode 'maybe)
> (mmm-add-group
>  'fancy-html
>   '(
>    (html-php-embedded
>     :submode php-mode
>     :face mmm-code-submode-face
>     :front "<\\?\\(php\\)?"
>     :back "\\?>")
>    ))
> (add-to-list 'mmm-mode-ext-classes-alist '(html-helper-mode nil fancy-html))
> 
> And with such a tiny config, my file is still tagged as modified (at
> least with Emacs22, it's OK with Emacs 21). Maybe it's because of
> Debian's initialization, but I doubt it.

It's easy enough to check: Start Emacs 22 with the -Q option, then paste
that code into *scratch* and `M-x eval-buffer'.

> I tried debugging the wole process, I even learned to use edebug as the plain
> backtracing wasn't enough, but I can't find anything for now. I'll try
> debugging once again as I can't think of anything better.

-- 
Kevin

  reply	other threads:[~2006-06-28 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 16:43 file modified on opening Mickey Ferguson
2006-06-28 18:24 ` François Gannaz
2006-06-28 20:55   ` Kevin Rodgers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-25 17:56 François Gannaz
2006-06-26 10:50 ` François Gannaz
2006-06-26 16:52 ` Ehud Karni
2006-06-27  9:28   ` François Gannaz

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='e7uqdd$v1t$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.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.
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).