From: Andreas Ericsson <ae@op5.se>
To: linux@horizon.com
Cc: torvalds@osdl.org, git@vger.kernel.org
Subject: Re: Get rid of .git/branches/ and .git/remotes/?
Date: Tue, 22 Nov 2005 10:07:38 +0100 [thread overview]
Message-ID: <4382DFDA.6040306@op5.se> (raw)
In-Reply-To: <20051122041843.9436.qmail@science.horizon.com>
linux@horizon.com wrote:
>>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.
> 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.
>
>>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
next prev parent reply other threads:[~2005-11-22 9:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 3:20 Get rid of .git/branches/ and .git/remotes/? linux
2005-11-22 3:38 ` Linus Torvalds
2005-11-22 4:18 ` linux
2005-11-22 9:07 ` Andreas Ericsson [this message]
2005-11-22 19:12 ` Nikolai Weibull
2005-11-22 20:13 ` Adrien Beau
2005-11-22 8:13 ` Andreas Ericsson
2005-11-22 13:21 ` linux
2005-11-22 13:58 ` Andreas Ericsson
-- strict thread matches above, loose matches on Subject: below --
2005-11-20 17:00 Johannes Schindelin
2005-11-20 18:09 ` Linus Torvalds
2005-11-20 18:29 ` Sven Verdoolaege
2005-11-20 19:07 ` Linus Torvalds
2005-11-20 19:16 ` Andreas Ericsson
2005-11-20 19:50 ` Johannes Schindelin
2005-11-26 23:50 ` Petr Baudis
2005-11-27 0:38 ` Junio C Hamano
2005-11-20 23:26 ` Josef Weidendorfer
2005-11-20 23:58 ` Johannes Schindelin
2005-11-22 17:31 ` Josef Weidendorfer
2005-11-22 17:56 ` Johannes Schindelin
2005-11-22 19:30 ` Andreas Ericsson
2005-11-23 15:08 ` Johannes Schindelin
2005-11-23 23:21 ` Junio C Hamano
2005-11-23 23:29 ` Andreas Ericsson
2005-11-23 23:42 ` Johannes Schindelin
2005-11-24 8:05 ` Andreas Ericsson
2005-11-24 8:33 ` Junio C Hamano
2005-11-22 23:05 ` Josef Weidendorfer
2005-11-23 14:53 ` Johannes Schindelin
2005-11-23 15:39 ` Josef Weidendorfer
2005-11-23 17:22 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4382DFDA.6040306@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=linux@horizon.com \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).