From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: [christopher.ian.moore@gmail.com: Emacs very slow opening file] Date: Thu, 29 Sep 2005 23:55:14 +0300 Organization: JURTA Message-ID: <87psqrim7w.fsf@jurta.org> References: <20050929095157.GA6233@kenny.sha-bang.local> <20050929123820.GC31770@kenny.sha-bang.local> <87achvll8q.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1128034285 31654 80.91.229.2 (29 Sep 2005 22:51:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2005 22:51:25 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, handa@m17n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 30 00:51:20 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EL7EC-0005w8-Fx for ged-emacs-devel@m.gmane.org; Fri, 30 Sep 2005 00:50:12 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EL7EB-0003SD-Vq for ged-emacs-devel@m.gmane.org; Thu, 29 Sep 2005 18:50:11 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EL77I-0000k2-IM for emacs-devel@gnu.org; Thu, 29 Sep 2005 18:43:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EL77B-0000ga-Go for emacs-devel@gnu.org; Thu, 29 Sep 2005 18:43:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EL77A-0000fA-QL for emacs-devel@gnu.org; Thu, 29 Sep 2005 18:42:56 -0400 Original-Received: from [194.126.101.111] (helo=mail.neti.ee) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EL762-0000Fc-4L; Thu, 29 Sep 2005 18:41:46 -0400 Original-Received: from mail.neti.ee (80-235-41-77-dsl.mus.estpak.ee [80.235.41.77]) by Relayhost1.neti.ee (Postfix) with ESMTP id 6C31516BE; Fri, 30 Sep 2005 01:41:50 +0300 (EEST) Original-To: Stefan Monnier In-Reply-To: <87achvll8q.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 29 Sep 2005 15:44:53 -0400") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at neti.ee X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:43371 Archived-At: > E.g. major modes could set a "local-variables-prefix-regexp" which > the text leading to the "Local Variables" should match. E.g. c-mode > could set it to "\\`[ \t]*\\(//\\|/?\\*)[ \t]*\\'" Problem is: > in order for this to be useful for the OP, the test should be done > *after* using the Local-Variables's section (i.e. after switching to > C mode). Still, it doesn't sound unfeasible, and would help reduce > the likelihood of mistakenly using a Local-Variables section. Recently I ran into the problem when Emacs tried to interpret the Local Variables section in the "htmlized" file. I suggested to the author of htmlize.el to replace `Local Variables:' in the output by its HTML equivalent `Local Variables:' that Emacs doesn't recognize. With a new special variable HTML mode could set it to a value that matches the Local Variables section only inside HTML comments, and such problems of mistakenly using a Local Variables section wouldn't occur in packages that convert files to other representations. -- Juri Linkov http://www.jurta.org/emacs/