git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: quote double-dash in "<commit> -- <filename>" for AsciiDoc
Date: Tue, 28 Jun 2011 14:22:45 -0700	[thread overview]
Message-ID: <7vaad1tzve.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20110628171748.GA11485@elie> (Jonathan Nieder's message of "Tue, 28 Jun 2011 12:17:49 -0500")

Jonathan Nieder <jrnieder@gmail.com> writes:

> As explained in v1.7.3-rc0~13^2 (Work around em-dash handling in newer
> AsciiDoc, 2010-08-23), outside of verbatim environments, newish
> versions of AsciiDoc will convert double hyphens to en dashes.  Use
> the litdd syntax introduced by that patch to avoid such misformatting
> in sentences where "--" represents the two-character "end of options"
> argument that separates revision names from filename patterns.

Thanks.

This looks very bad:

    $ cd $git/share/man
    $ grep -l '(em ' */*.?

even though we do want em-dash for some hits in the above output.  And
even worse, there seem to be exceptions to this rule, like ...

> diff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt
> index ac10cfbb..a516d577 100644
> --- a/Documentation/git-revert.txt
> +++ b/Documentation/git-revert.txt
> @@ -23,7 +23,7 @@ throw away all uncommitted changes in your working directory, you
>  should see linkgit:git-reset[1], particularly the '--hard' option.  If

... the one before "hard" above.

  reply	other threads:[~2011-06-28 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 17:17 [PATCH] Documentation: quote double-dash in "<commit> -- <filename>" for AsciiDoc Jonathan Nieder
2011-06-28 21:22 ` Junio C Hamano [this message]
2011-06-29  4:15   ` Jonathan Nieder
2011-06-28 22:47 ` Jeff King
2011-06-29  5:31 ` [PATCH v2 0/2] Documentation: quote double-dash " Jonathan Nieder
2011-06-29  5:35   ` [PATCH 1/2 maint] " Jonathan Nieder
2011-06-29  5:36   ` [PATCH 2/2] Documentation/i18n: " Jonathan Nieder
2011-06-29 10:42     ` Ævar Arnfjörð Bjarmason
2011-06-29 16:44     ` [PATCH] fixup! " Jonathan Nieder

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=7vaad1tzve.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    /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).