[Ffmpeg-cvslog] CVS: CVSROOT style.sh, NONE, 1.1 commitinfo, 1.1, 1.2

Måns Rullgård mru
Fri Jan 13 21:43:26 CET 2006

The Wanderer <inverseparadox at comcast.net> writes:

> On 01/13/2006 02:44 PM, M?ns Rullg?rd wrote:
>> The Wanderer <inverseparadox at comcast.net> writes:
>>> On the other side, I'm against considering "lines which consist
>>> only of whitespace" to be "trailing whitespace", which if I'm not
>>> mistaken this script would do. It's not likely to affect me unless
>>> and until such time as I reach the point of actually writing new
>>> code myself, instead of just modifying existing files (and mostly
>>> documentation files at that), but it's still very aggravating just
>>> in principle.
>> I find lines consisting entirely of whitespace very aggravating.
> And I find not having the indentation already in place on "blank" lines
> when navigating around a file very aggravating. If you can find some way
> of avoiding that without whitespace-only lines, I'd be interested to
> hear about it.

I don't know what editor you use.  I use xemacs, and it has never
occurred to me that this could be an issue.  Could you elaborate a bit
on the problems you are experiencing?

>> The rule is "the last character before a newline must be
>> non-whitespace".
> Since a newline is itself whitespace, this does not allow blank lines at
> all.

OK, so you're nitpicking.  Let's try a different way: a newline
character may not be immediately preceded by a non-newline whitespace
character.  Satisfied?

>> If this is against your definition of "trailing", suggest a more
>> suitable word.  The rule isn't changing.
> I didn't (and don't) really expect it to. Doesn't change how I feel
> about the matter, though.

You are obviously entitled to hold whatever opinions you wish.  Just
don't try to enforce them on others, and especially not on those who
actually write the code.

M?ns Rullg?rd
mru at inprovide.com

More information about the ffmpeg-cvslog mailing list