This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Fix gcc/config.in
- To: Per Bothner <per at bothner dot com>
- Subject: Re: PATCH: Fix gcc/config.in
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Sun, 30 Sep 2001 17:48:23 -0400
- Cc: "H . J . Lu" <hjl at lucon dot org>, gcc-patches at gcc dot gnu dot org
- References: <20010930112607.A4330@lucon.org> <3BB76907.5060901@bothner.com>
On Sun, Sep 30, 2001 at 11:48:39AM -0700, Per Bothner wrote:
> In Kawa, a few Java files are generated from java.in files. To stop
> myself from
> editing a generated file I had it start with this header:
>
> // DO NOT EDIT! -*- buffer-read-only: t -*-
> // This file is automatically generated from Sequence.java.in.
>
> Notice the 'buffer-read-only: t'. When Emacs sees it, it marks the
> buffer read-only, so it will complain if I try to modify it.
Likewise, vim (the widely-accepted successor to vi) allows both of
// vim:ro:
// vim:readonly:
to do the same. It's always annoyed me that Emacs hooks can be placed in
GCC files, but hooks for That Other Editor aren't allowed. :-)
Phil
--
"You have to wonder what kind of life you have when your list of personal
rules begins with, '#3: No drowning in your own mucus,' and '#4: Don't
ask what happened to rules 1 and 2.'"