git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Grimm <koreth@midwinter.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: David Kastrup <dak@gnu.org>, git@vger.kernel.org
Subject: Re: Stupid quoting...
Date: Wed, 13 Jun 2007 18:06:19 -0700	[thread overview]
Message-ID: <4670948B.7070407@midwinter.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706131316390.4059@racer.site>

Johannes Schindelin wrote:
> The recommended way is not using spaces to begin with. I mean, does 
> "David" contain spaces? People seem not to see the problem, and fail to 
> blame Microsoft for all the damage they have done, introducing that 
> stupid, stupid concept of filenames containing spaces, and _enforcing_ it.
>   

To be fair, Microsoft did not invent the concept of filenames with 
spaces. Even UNIX has, I believe, always allowed them, though you risked 
running into buggy scripts misbehaving if you used them. And really, 
filenames with spaces are only a nuisance in a text-based command line 
scripting environment, and only then because someone early on decided to 
use space rather than some other metacharacter as the only available 
delimiter between command arguments in scripts.

For regular users who aren't writing shell scripts, long-form filenames 
mean a document's name is the same as its title, which is hugely helpful 
from a user interface point of view: "February Marketing Budget" is much 
more self-documenting as a filename than "febmkbgt" or whatever they 
would have had to choose in the old days (and remember, UNIX had a 
14-character filename size limit in the early days; long filenames 
weren't introduced until BSD.)

I view filenames as primarily for human consumption, so they should act 
the way humans expect names to act. Computers can just use inode numbers 
or file IDs to refer to files (like, say, SHA1 hashes) -- the pretty 
names are all for the benefit of us meat-brained entities.

Then again, that means I also think case sensitivity in filenames was a 
bad design choice. To use your "people's names" analogy, if you ask any 
random person whether "Billy-bob Thornton" and "Billy-Bob Thornton" are 
the same name, they'll almost always say yes; most people don't consider 
capital letters and lower-case letters to be different letters, just 
different forms of the same letters. And I know how popular *that* 
opinion is around here...

-Steve

  parent reply	other threads:[~2007-06-14  1:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 11:30 Stupid quoting David Kastrup
2007-06-13 12:06 ` Alex Riesen
2007-06-13 12:21 ` Johannes Schindelin
     [not found]   ` <86ejkgvxmb.fsf@lola.quinscape.zz>
2007-06-14  0:51     ` Johannes Schindelin
2007-06-14  6:12       ` David Kastrup
2007-06-14  7:06         ` Alex Riesen
     [not found]           ` <86hcpb6lr6.fsf@lola.quinscape.zz>
2007-06-14  8:51             ` Alex Riesen
2007-06-14  1:06   ` Steven Grimm [this message]
2007-06-14  1:12     ` Johannes Schindelin
2007-06-14  1:19       ` Steven Grimm
2007-06-14  1:34         ` Johannes Schindelin
2007-06-14  8:49   ` Junio C Hamano
2007-06-16 21:03 ` Jakub Narebski
2007-06-18  8:00   ` David Kastrup
2007-06-18 16:19     ` Jeff King
2007-06-19  1:00     ` Johannes Schindelin
2007-06-19  7:44       ` David Kastrup
2007-06-19  9:50         ` Johannes Schindelin
2007-06-19 20:53           ` Olivier Galibert
     [not found]           ` <86645kutow.fsf@lola.quinscape.zz>
2007-06-20  2:19             ` Johannes Schindelin
2007-06-20  6:19               ` Junio C Hamano
2007-06-20  7:49                 ` David Kastrup
2007-06-20  8:40                   ` Jakub Narebski
2007-06-20  8:59                     ` David Kastrup
2007-06-24  6:50                 ` Jan Hudec
2007-06-24 11:14                   ` Robin Rosenberg
2007-06-24 11:47                     ` Junio C Hamano
2007-06-24 11:58                       ` David Kastrup
2007-06-24 12:19                         ` Junio C Hamano
2007-06-24 12:41                           ` Jeff King
2007-06-24 16:25                     ` Jan Hudec
2007-06-24 19:39                       ` Robin Rosenberg
2007-06-24 19:47                         ` David Kastrup
2007-06-24 20:17                           ` Robin Rosenberg
2007-06-24 20:25                             ` David Kastrup

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4670948B.7070407@midwinter.com \
    --to=koreth@midwinter.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.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.
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 NNTP newsgroup(s).