From: Benny Halevy <bhalevy@panasas.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Richard Knutsson <ricknu-0@student.ltu.se>,
SL Baur <steve@xemacs.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Jan Engelhardt <jengelh@computergmbh.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] CodingStyle: multiple updates
Date: Mon, 03 Mar 2008 18:17:49 +0200 [thread overview]
Message-ID: <47CC24AD.1090409@panasas.com> (raw)
In-Reply-To: <m3skzb9ysw.fsf@maximus.localdomain>
On Mar. 01, 2008, 0:34 +0200, Krzysztof Halasa <khc@pm.waw.pl> wrote:
> Richard Knutsson <ricknu-0@student.ltu.se> writes:
>
>> In those cases, an only-used-as-indent-character is most preferable.
>
> It is. The problem is that the editors can't do it (yet?). Or am I
> mistaken?
"Yet" is the right answer :)
When creating a new line copying the indentation from the line above
and potentially filling more spaces as needed, according to
parenthesis or operators on the previous line should do the trick.
Benny
next prev parent reply other threads:[~2008-03-03 16:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 21:47 [RFC] CodeStyle: Use spaces when aligning/decorating ricknu-0
2008-02-26 21:54 ` Randy Dunlap
2008-02-26 22:16 ` Richard Knutsson
2008-02-27 0:14 ` Benny Halevy
2008-02-27 21:02 ` Richard Knutsson
2008-02-27 21:33 ` Bob Copeland
2008-02-27 21:47 ` Richard Knutsson
2008-02-26 22:59 ` [PATCH] CodingStyle: multiple updates Jan Engelhardt
2008-02-26 23:40 ` Guennadi Liakhovetski
2008-02-26 23:51 ` Krzysztof Halasa
2008-02-27 0:02 ` Jan Engelhardt
2008-02-27 0:16 ` Guennadi Liakhovetski
2008-02-27 0:42 ` Stefan Richter
2008-02-27 0:57 ` SL Baur
2008-02-27 5:34 ` Randy Dunlap
2008-02-27 21:33 ` SL Baur
2008-02-27 22:02 ` Richard Knutsson
2008-02-27 23:53 ` Krzysztof Halasa
2008-02-28 0:11 ` SL Baur
2008-02-28 0:18 ` Jan Engelhardt
2008-02-28 20:09 ` Richard Knutsson
2008-02-29 22:34 ` Krzysztof Halasa
2008-03-03 16:17 ` Benny Halevy [this message]
2008-03-03 21:08 ` Krzysztof Halasa
2008-03-04 10:04 ` Benny Halevy
2008-02-28 21:20 ` Alexey Dobriyan
2008-02-27 9:27 ` Bernd Petrovitsch
2008-02-27 10:02 ` Guennadi Liakhovetski
2008-02-27 10:17 ` Bernd Petrovitsch
2008-02-27 21:46 ` SL Baur
2008-02-27 0:39 ` Stefan Richter
2008-02-27 21:41 ` Richard Knutsson
[not found] <a1fQN-352-63@gated-at.bofh.it>
[not found] ` <a1g0n-3hn-17@gated-at.bofh.it>
[not found] ` <a1h64-5gC-25@gated-at.bofh.it>
[not found] ` <a1hII-67t-5@gated-at.bofh.it>
[not found] ` <a1hSu-6j3-13@gated-at.bofh.it>
[not found] ` <a1iOy-7Mq-37@gated-at.bofh.it>
[not found] ` <a1nbp-6hE-5@gated-at.bofh.it>
[not found] ` <a1CDx-5ZM-9@gated-at.bofh.it>
[not found] ` <a1EFk-Mt-9@gated-at.bofh.it>
[not found] ` <a1Yl9-6NF-161@gated-at.bofh.it>
[not found] ` <a2m3J-2EX-19@gated-at.bofh.it>
2008-03-01 0:10 ` Bodo Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47CC24AD.1090409@panasas.com \
--to=bhalevy@panasas.com \
--cc=g.liakhovetski@gmx.de \
--cc=jengelh@computergmbh.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=ricknu-0@student.ltu.se \
--cc=steve@xemacs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).