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

The Wanderer inverseparadox
Fri Jan 13 21:59:34 CET 2006

On 01/13/2006 03:43 PM, M?ns Rullg?rd wrote:

> The Wanderer <inverseparadox at comcast.net> writes:
>> On 01/13/2006 02:44 PM, M?ns Rullg?rd wrote:

>>> 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?

There's not much "elaborating" to do; the problem is very simple, and
I'm not sure how to describe it much further without sounding extremely

Put simply: when navigating around a file (moving the cursor from one
point to another), I want to be able to have the cursor at the correct
indentation level for the surrounding code at all times - even if there
is no code on the current line. It helps me remain focused on a
particular part of the code, sometimes, and helps me keep the "current"
level of indentation (and hence the bounds of the current scope) clear
in my head. It's also convenient on the (admittedly rare) occasions when
I want to add new text on an existing blank line, rather than inserting
additional lines. I don't honestly see how people who spend any
significant amount of time in the depths of source code can stand to get
by without it...

For the record, I use nano for general text editing, because it's
lightweight. and jed for almost all of my code editing (I would use
emacs, but I've never had the necessary impetus to get over the initial
learning-curve hurdle) because it provides syntax highlighting and
auto-indentation. However, the exact same "behaviour" (if that's even an
applicable word) has been present in every editor I've ever used, down
to MS Word and Notepad; it doesn't really seem to be an "editor" thing.

>>> 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.

Sorry about that.

> Let's try a different way: a newline character may not be immediately
> preceded by a non-newline whitespace character.  Satisfied?

As a description of the rule you're advocating, yes, that would be

>>> 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.

If it were not for the last part, I could turn that argument right back
around on you. Since there *are* two classes of people involved here,

       The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.

More information about the ffmpeg-cvslog mailing list