git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Habouzit <madcoder@madism.org>
To: Henrik Tidefelt <tidefelt@isy.liu.se>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Problem with "dashless options"
Date: Thu, 10 Sep 2009 00:49:30 +0200	[thread overview]
Message-ID: <20090909224930.GC29776@artemis.corp> (raw)
In-Reply-To: <4EEF55B5-46E1-4C06-AA60-62F700F7B279@isy.liu.se>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

On Wed, Sep 09, 2009 at 11:12:12PM +0200, Henrik Tidefelt wrote:
> No, but it is mapped to WHITE FROWNING FACE; I guess I defined it so
> to avoid the trouble I was previously experiencing from accidentally
> typing the &nbsp; instead of space without being able to see the
> difference on screen.  Why would it matter?

well because then one of your space could have been that, and the shell
doesn't consider non breakable space as .. breakable, hence you can read
something where you believe there is (n+1) arguments but the shell (and
git) see only n.

It often yields errors really hard to grasp like the dreaded:

$ ls | grep
zsh: command not found:  grep
notice the              ^

sorry then I don't really know what happened...

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-09-09 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 13:21 Problem with "dashless options" Henrik Tidefelt
2009-09-09 14:34 ` Jeff King
2009-09-09 16:26   ` Henrik Tidefelt
2009-09-09 16:30     ` Pierre Habouzit
2009-09-09 21:12       ` Henrik Tidefelt
2009-09-09 22:49         ` Pierre Habouzit [this message]
2010-04-27 17:55 ` Problem with &quot;dashless options&quot; Christopher Cameron
2010-04-27 21:28   ` Andreas Schwab

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=20090909224930.GC29776@artemis.corp \
    --to=madcoder@madism.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=tidefelt@isy.liu.se \
    /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).