[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1204104420.17396.2.camel@tara.firmix.at>
Date: Wed, 27 Feb 2008 10:27:00 +0100
From: Bernd Petrovitsch <bernd@...mix.at>
To: Guennadi Liakhovetski <g.liakhovetski@....de>
Cc: Jan Engelhardt <jengelh@...putergmbh.de>,
Randy Dunlap <randy.dunlap@...cle.com>,
ricknu-0@...dent.ltu.se, khc@...waw.pl, bhalevy.lists@...il.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] CodingStyle: multiple updates
On Mit, 2008-02-27 at 00:40 +0100, Guennadi Liakhovetski wrote:
> On Tue, 26 Feb 2008, Jan Engelhardt wrote:
>
> > +Continuation lines are always shorter than the initial one and are
> > +(1) indented as much as the initial line, plus (2) alignment spaces.
> > +Spaces are used so as to not cause odd aligning for users wishing to
> > +display tabs at sizes other than 8. In the example below, the
> > +continuation line of the printk call therefore has two tabs of logical
> > +indent, followed by a number of spaces to align it up.
>
> Now, I think, I am not the only one using emacs. Until now the "linux"
> C-style fitted perfectly with the CodingStyle, now it no longer will.
> Namely, emacs puts as many tabs to indent the continuation line as fit
> (i.e., at tab width = 8 spaces it's just (extra indent / 8) tabs plus
> (extra indent % 8) spaces. Is there a way to make emacs behave compatibly
> to this proposal? If not, I would not like to have to re-indent every such
Unless I'm misunderstanding something completely: Add "indent-tabs-mode:
nil" in a "Local Variables:" section.
But since Linux-style has that since ages (if not ever), that should be
set for am emacs'ens linux-mode anyway.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists