Re: Get rid of .git/branches/ and .git/remotes/?

From: Andreas Ericsson <ae@op5.se>
Date: Nov 22, 2005, 09:07 UTC
Message-ID: <4382DFDA.6040306@op5.se>
In-Reply-To: <20051122041843.9436.qmail@science.horizon.com>

linux@horizon.com wrote:

Show 12 quoted lines

>>This is like Makefiles: if you have spaces in the wrong place, it may all 
>>_look_ fine, but the Makefile just doesn't work. Really irritating.
> 
> 
> Makefiles are more annoying because spaces instead of tabs can cause
> them to work *differently*.  It's hard to write syntax that will
> actually do that, but the parser ahs to go past the problem a bit to
> really figure it out, so it can't print a nice error message.
> 
> With the strict prefix convention, the parser can produce excellent
> error messages.
>

Excellent error messages aren't good enough. It's ok for Python, since that's a programming language. We can expect infinitely more from programmers than we can from users.

> It irritates you the first few times until you learn to do it right in 
> first place, just like it irritates most beginning C programmers that the
> compiler keeps complaining about missing semicolons.
>

If I'm trying out some new stuff that annoys me three times without me seeing an obvious error on my part (in the editor of my choice) I usually write it down as broken and move on.

Show 5 quoted lines

> Computers will be annoying about syntax until they learn to do what
> I want them to do rather than what I tell them to do, at which point
> they'll be smart enough to start being annoying by doing what they want
> to to instead of what I want them to do.
>

That's not the point. If everything looks good it should work good, regardless of which editor or tab-setting one's using.

Show 10 quoted lines

> 
>>Of course, since I believe that tabs are always exactly 8 characters, I'd 
>>also be perfectly happy to just declare that anybody who disagrees with me 
>>is a moron and deserves to die (*).
> 
> 
> Seriously, you could always have it print warning messages but try to
> keep going by assuming 8 space tabs so that at least you can postpone
> fixing the problem until your current train of thought has pulled into
> the station.

There used to be $TABSIZE (or some such). Check it if you implement this. Or just skip it entirely. I would prefer the latter.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231