From: Josh Triplett <josh@kernel.org>
To: dave young <hidave.darkstar@gmail.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Chris Shoemaker <c.shoemaker@cox.net>,
Josh Triplett <josht@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] CodingStyle: Add information about trailing whitespace.
Date: Wed, 27 Jun 2007 23:08:07 -0700 [thread overview]
Message-ID: <46835047.8080600@kernel.org> (raw)
In-Reply-To: <a8e1da0706272300q3aee30der5349e85055f62a8e@mail.gmail.com>
dave young wrote:
> 2007/6/27, Jan Engelhardt <jengelh@computergmbh.de>:
>> On Jun 27 2007 14:05, Chris Shoemaker wrote:
>>> What I'd really like to see is, _why_ is trailing whitespace
>>> considered harmful?
>> Consumes bytes you'll never see :)
>>
>>> Something about MUAs not preserving it or something?
>> Well, there is format=flowed. text/plain mails with a trailing blank at the end
>> of line indicates the paragraph continues -- as a curtesy for mail readers with
>> non-fixed-font to display the paragraph coherently rather than breaking it at
>> 72/80 columns.
>>
>>
>> Jan
>> --
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
> There's more potential to cause lines end with whitespace. How about
> remove the "Some editors with ..." like this :
>
> +Do not leave trailing whitespace at the ends of lines.
> +
[...]
Many other causes for trailing whitespace exist. However, I wanted to mention
one of the common causes. If you have other common causes in mind, and even
better if you have ways to avoid them, we should add those too.
It might make sense to put a paragraph break after the first sentence, though,
and split the information about editors into its own paragraph, adding more
paragraphs if people suggest other possibilities.
- Josh Triplett
next prev parent reply other threads:[~2007-06-28 6:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 17:59 [PATCH] CodingStyle: Add information about trailing whitespace Josh Triplett
2007-06-27 18:05 ` Chris Shoemaker
2007-06-27 18:17 ` Josh Triplett
2007-06-27 19:32 ` Chris Shoemaker
2007-06-27 22:18 ` Jan Engelhardt
2007-06-28 6:00 ` dave young
2007-06-28 6:08 ` Josh Triplett [this message]
2007-06-28 6:29 ` dave young
2007-06-28 6:52 ` Jan Engelhardt
2007-06-28 6:58 ` Josh Triplett
2007-06-28 7:08 ` Li Yang-r58472
2007-06-28 7:10 ` Dave Young
2007-06-28 7:20 ` Dave Young
2007-06-29 3:11 ` [OT] Vim highlighting for trailing spaces Kyle Moffett
2007-06-29 7:39 ` Jan Engelhardt
2007-06-29 7:53 ` Josh Triplett
2007-06-29 8:01 ` Jan Engelhardt
2007-06-29 8:42 ` Josh Triplett
2007-06-29 9:21 ` Björn Steinbrink
2007-06-29 9:26 ` Dave Young
2007-06-29 12:40 ` Michael Tokarev
2007-06-29 12:49 ` Dmitry Torokhov
2007-06-30 0:00 ` Kyle Moffett
2007-06-29 2:03 ` [PATCH] CodingStyle: Add information about trailing whitespace Andy Isaacson
2007-06-27 19:31 ` Andrew Morton
2007-06-27 22:14 ` Jan Engelhardt
2007-06-27 22:14 ` Oleg Verych
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=46835047.8080600@kernel.org \
--to=josh@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=c.shoemaker@cox.net \
--cc=hidave.darkstar@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=josht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.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