Re: Coding style for emacs - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Coding style for emacs
Date
Msg-id 20060902215935.GL84229@nasby.net
Whole thread Raw
In response to Re: Coding style for emacs  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Coding style for emacs  (Bruce Momjian <bruce@momjian.us>)
Re: Coding style for emacs  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Sat, Sep 02, 2006 at 07:22:45PM +0100, Gregory Stark wrote:
> "Jim C. Nasby" <jim@nasby.net> writes:
> 
> > Has anyone considered adding vi/vim options to the files themselves?
> > Granted, not a trivial task, but it would ensure anyone using vim would
> > have the correct settings. I don't know if emacs has the same ability
> > (I've seen the "Hey emacs, this is a C file" stuff...)
> 
> Certainly it does; it even knows that certain variables are safe to allow
> files to set without warning the user and it has the indention marked as such.
> 
> I think this would be what you would want.
> 
> /*
>  * Local variables:
>  * eval: (c-set-style "bsd")
>  * tab-width: 4
>  * c-basic-offset: 4
>  * End:
>  */
> 
> But it would have to be on the end of every single file which would be pretty
> heavyweight.

Yeah, which is the real question... do people think it's worth it enough
to move towards doing that? Of course the nice thing is that *anyone*
(even me :) ) could produce a patch to do that.
-- 
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Prepared statements considered harmful
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Use of backslash in tsearch2