On 6/28/07, Dave Young <[EMAIL PROTECTED]> wrote: >On 6/28/07, Li Yang-r58472 <[EMAIL PROTECTED]> wrote: > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Josh Triplett > > Sent: Thursday, June 28, 2007 2:59 PM > > To: Jan Engelhardt > > Cc: dave young; Chris Shoemaker; Josh Triplett; > linux-kernel@vger.kernel.org; > > [EMAIL PROTECTED] > > Subject: Re: [PATCH] CodingStyle: Add information about trailing > whitespace. > > > > Jan Engelhardt wrote: > > > On Jun 28 2007 06:29, dave young wrote: > > >> IMHO, another cause of trailing whitespace is human error, for > > >> example long lines breaking will easy to cause the first line with > one > > >> traling whitespace (original space between the last two words). > > > > > > Most common errors (to me) are: > > > > > > - hit return+tab too quickly that it interchanges, hence producing > > > the unwanted \t\n > > > - hit return+return to start a new paragraph of code; > > > the intermediate line remains indented if autoindent is on. > > > > Interestingly, emacs gets that case right: when you hit enter it > places the > > cursor at the properly indented insertion point, but if you leave the > line > > without typing anything it does not leave the indentation. I thought > I > > remembered vim doing the same thing, but I just tested and it appears > not. It > > seems to avoid leaving subsequent lines indented, but not the first > one. > > No, vim works just fine here without leaving any indentation. Maybe the > version of vim or the options matter. > Yes, vim autoindent doesn't leave tabs in blank line for me.
And for vim trailing space, there's a tip in vim.org: http://www.vim.org/tips/tip.php?tip_id=878 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
