unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [christopher.ian.moore@gmail.com: Emacs very slow opening file]
Date: Thu, 29 Sep 2005 21:24:43 +0900	[thread overview]
Message-ID: <E1EKxSt-0006ls-00@etlken> (raw)
In-Reply-To: <20050929095157.GA6233@kenny.sha-bang.local> (message from Sascha Wilde on Thu, 29 Sep 2005 11:51:57 +0200)

In article <20050929095157.GA6233@kenny.sha-bang.local>, Sascha Wilde <wilde@sha-bang.de> writes:

> So, I would conclude, that there is no bug at all.  Emacs can't
> possibly know, that the "Local Variables:" block isn't meant to be
> interpreted in the diff file.  

> And I wouldn't consider the fact, that c-mode fontification takes so
> long on a big file, which isn't valid c-code at all, a bug.

> Workaround: turn of global-font-lock-mode or set
> enable-local-variables to nil, before opening a file like that.

Perhaps, Emacs has to detect that the file is a patch before
checking "-*- ... -*-" and "Local Variables".

---
Kenichi Handa
handa@m17n.org

  reply	other threads:[~2005-09-29 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 17:11 [christopher.ian.moore@gmail.com: Emacs very slow opening file] Richard M. Stallman
2005-09-29  9:51 ` Sascha Wilde
2005-09-29 12:24   ` Kenichi Handa [this message]
2005-09-29 12:38     ` Sascha Wilde
2005-09-29 19:44       ` Stefan Monnier
2005-09-29 20:55         ` Juri Linkov
2005-09-30 17:33           ` Richard M. Stallman
2005-09-29 21:03         ` Andreas Schwab
2005-09-29 23:31   ` Richard M. Stallman
2005-09-30  6:39     ` David Kastrup
2005-09-30  7:58       ` Sascha Wilde
2005-09-30 23:50       ` Richard M. Stallman
2005-10-02 14:48         ` Stefan Monnier
2005-09-30  7:43     ` Sascha Wilde
2005-10-02 20:22       ` Juri Linkov
2005-10-03 15:35         ` Richard M. 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

  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=E1EKxSt-0006ls-00@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).