On 22 Feb, Marc Lehmann wrote: > vim, like vi and emacs, has a manual and can be configured quite > freely ;) Yes, I read the manual and tried a whole hour to get it the GNU way but I couldn't manage to get that. > set formatoptions=croql cindent cinkeys={,},:,0#,!^F,o,O,e > cinoptions={.5s,}0,g0,^-2 sw=2 comments=sr:/*,mb:*,el:*/,:// > (However, that's not exactly gnu-style). Well, that the thing I'm talking about. I tried this options and think that it doesn't match it very good. After the first { of a function the source isn't indented for example. -- Servus, Daniel
- Re: Coding style (was: PROPOSAL: New i18n solution) Raphael Quinet
- Re: Coding style (was: PROPOSAL: New i18n solu... Daniel . Egger
- Re: Coding style (was: PROPOSAL: New i18n ... Marc Lehmann
- Re: Coding style (was: PROPOSAL: New i... Daniel . Egger
- Re: Coding style (was: PROPOSAL: N... Federico Mena Quintero
- Re: Coding style (was: PROPOS... Daniel . Egger
- Re: Coding style (was: PR... Federico Mena Quintero
- Re: Coding style (was: PR... Tomas Ogren
- Re: Coding style (was... Federico Mena Quintero
- Re: Coding style (was: PROPOSAL: N... Marc Lehmann
- Re: Coding style (was: PROPOS... Daniel . Egger
- Re: Coding style (was: PR... Marc Lehmann
- Re: Coding style (was... Daniel . Egger
- Re: Coding style (was: PROPOSAL: New i18n solu... Marc Lehmann
- Re: Coding style Sven Neumann
- Re: Coding style (was: PROPOSAL: New i18n solu... Miles O'Neal
- Re: Coding style (was: PROPOSAL: New i18n ... Glyph Lefkowitz
- Re: Coding style (was: PROPOSAL: New i... Jon A. Cruz