Add c-backslash-max-column - its default value of 72 is less than what

we set for c-backslash-column, so macros with lines longer than 72
would be formatted icorrectly.

Fix brace-list-entry - it doesn't need extra indentation.  Pointed out
by roy@.  While here use '+ instead of 8 to express "full indentation
step".

XXX: Do we really want brace-list-open indented one step?  It might
work for one-liners, but we have lots of longer init lists that are
formatted with brace-list-open of 0.
This commit is contained in:
uwe 2009-02-16 21:37:12 +00:00
parent c4605d6440
commit ac97beab45

View File

@ -1,4 +1,4 @@
;; $NetBSD: NetBSD.el,v 1.5 2007/09/24 15:38:11 christos Exp $
;; $NetBSD: NetBSD.el,v 1.6 2009/02/16 21:37:12 uwe Exp $
(defconst netbsd-knf-style
'(
@ -7,6 +7,7 @@
(c-basic-offset . 8)
;; in which column to add backslashes when macroizing a region
(c-backslash-column . 78)
(c-backslash-max-column . 78)
;; automatically compact brace-else(if)-brace on one line and
;; semi-colon after closing struct brace
(c-cleanup-list . (brace-else-brace
@ -36,8 +37,9 @@
(c-offsets-alist . ((arglist-cont-nonempty . 4)
(block-open . 0)
;; (block-open . -)
(brace-list-entry . 8)
(brace-list-open . 8)
(brace-list-open . +)
(brace-list-intro . +)
(brace-list-entry . 0)
(brace-list-close . 0)
(knr-argdecl . 0)
(knr-argdecl-intro . +)