:set cinoptions={0.5s,^-2,e-2,n-2,p2s,(0
Works most of the case.. (maybe not perfect, but..)
Thanks a lot! I just put it in the programming guidelines.
Federico
On Wed, 23 Feb 100, Miles O'Neal wrote:
[snip thought GNU style was bad but it's OK]
I still don't. Two spaces just isn't enough. Three
or four is much better. And I like space before the
paren only if it isn't after a function or procedure
name.
And I firmly believe that if God had
On Tue, 22 Feb 2000, [EMAIL PROTECTED] wrote:
On 22 Feb, Manish Singh wrote:
True, although we have a couple other inconsistencies already. The
coding style needs to be the same as the rest of gimp though.
I tried to bring it as near as possible. Of course a lot things could
be
On 22 Feb, Raphael Quinet wrote:
I did not like the GNU style at first (especially the space before the
opening parenthesis) but now I understand that it is very important
to keep a consistent coding style in each project, because it keeps
the code manageable and maintainable. So I always
Raphael Quinet said...
|
|I did not like the GNU style at first (especially the space before the
|opening parenthesis)
I still don't. Two spaces just isn't enough. Three
or four is much better. And I like space before the
paren only if it isn't after a function or procedure
name.
|but now I
On Tue, Feb 22, 2000 at 02:59:18PM +0100, Raphael Quinet [EMAIL PROTECTED] wrote:
scripts and, to a lesser extent, the Perl scripts. Is there a
recommended style for these?
Yes, just copy mine ;)
For perl-only-syntax-questions, the reference should be "perldoc
perlstyle". All the remaining
On Tue, Feb 22, 2000 at 03:56:44PM +0100, [EMAIL PROTECTED] wrote:
Okay, will turn from the Standard vi indention into GNU coding style.
"Standard vi indentation" is fine. Just follow the GNU coding style on
when to indent, and when not (and when to add spaces, when not...) ;)
The idea,
Uhm, I use vim and vim uses tabs by default and doesn't indent
the { after an if like GNU suggests. Du you have working settings to
achieve this?
I don't know if this will be useful at all, but the GNOME Programming
Guidelines has a snippet for .vimrc to set the Linux kernel
indentation
On Tue, Feb 22, 2000 at 07:59:21PM +0100, [EMAIL PROTECTED] wrote:
Uhm, I use vim and vim uses tabs by default and doesn't indent
vim, like vi and emacs, has a manual and can be configured quite freely ;)
the { after an if like GNU suggests. Du you have working settings to
achieve this?
On 22 Feb, Federico Mena Quintero wrote:
I don't know if this will be useful at all, but the GNOME Programming
Guidelines has a snippet for .vimrc to set the Linux kernel
indentation style.
This is the standard vim style.
If you tweak it a bit it may work for GNU indentation style.
No,
On Tue, Feb 22, 2000 at 11:54:03PM +0100, [EMAIL PROTECTED] wrote:
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.
Then, most probably, you have a very very
If you tweak it a bit it may work for GNU indentation style.
No, unfortunately I couldn't get vim used to GNU indention style.
Please tell me if this works or if you had to change something; I'd
like to keep that part of the programming guidelines as accurate as
possible.
On 22 February, 2000 - [EMAIL PROTECTED] sent me these 0.6K bytes:
On 22 Feb, Federico Mena Quintero wrote:
I don't know if this will be useful at all, but the GNOME Programming
Guidelines has a snippet for .vimrc to set the Linux kernel
indentation style.
This is the standard vim
On 23 Feb, Marc Lehmann wrote:
Then, most probably, you have a very very old or broken version of vim
(or maybe you use another editor, or vim in vi-emulation mode).
Actually it's the latest stable version of vim.
The whole point of these options is to make indentation automatic and
14 matches
Mail list logo
