git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 1/2] Documentation: fix linkgit references

From
Lars Schneider <larsxschneider@gmail.com>
Date
May 3, 2016, 08:30 UTC
Message-ID
<E4A56B4E-6F2E-44E3-870B-D1D3A71B2869@gmail.com>
In-Reply-To
<20160502203445.GA19509@sigill.intra.peff.net>
On 02 May 2016, at 22:34, Jeff King <peff@peff.net> wrote:
Show 10 quoted lines
> On Mon, May 02, 2016 at 10:20:04PM +0200, larsxschneider@gmail.com wrote:
> 
>> From: Lars Schneider <larsxschneider@gmail.com>
>> 
>> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
>> ---
> 
> Fix how? Your commit message doesn't say why this is a good idea. Since
> this is v3, I'm guessing that reasoning is on the list, but it needs to
> be summarized here in the commit message.

You are right, I should have explained my thinking a bit more detailed. A few of the fixed linkgit references are just typos, e.g.:

-linkgit:gitconfig[5] +linkgit:git-config[5]

-values the `--date` option to linkgit::git-rev-list[1] takes). +values the `--date` option to linkgit:git-rev-list[1] takes).

- the Netscape/Mozilla cookie file format (see linkgit:curl[1]). + the Netscape/Mozilla cookie file format (see `curl(1)`).

I mistakenly assumed the "{litdd}" was a typo/bad search replace, too. I checked this website and thought my change would fix it, too:

https://git-scm.com/docs/git-config

There it is rendered as "(See git-web{litdd}browse[1].)" and the link is broken.

Show 31 quoted lines
>> diff --git a/Documentation/config.txt b/Documentation/config.txt
>> index c7bbe98..c5f1d6b 100644
>> --- a/Documentation/config.txt
>> +++ b/Documentation/config.txt
>> @@ -894,7 +894,7 @@ branch.<name>.description::
>> browser.<tool>.cmd::
>> 	Specify the command to invoke the specified browser. The
>> 	specified command is evaluated in shell with the URLs passed
>> -	as arguments. (See linkgit:git-web{litdd}browse[1].)
>> +	as arguments. (See linkgit:git-web--browse[1].)
> 
> The existing code renders fine for me with "make git-config.1". But with
> your patch, I get a unicode emdash, which is wrong:
> 
> --- old	2016-05-02 16:27:53.242050262 -0400
> +++ new	2016-05-02 16:27:57.742050360 -0400
> @@ -978,7 +978,7 @@
> 
>        browser.<tool>.cmd
>            Specify the command to invoke the specified browser. The specified command is evaluated in shell with the
> -           URLs passed as arguments. (See git-web--browse(1).)
> +           URLs passed as arguments. (See git-web—browse(1).)
> 
>        browser.<tool>.path
>            Override the path for the given tool that may be used to browse HTML help (see -w option in git-help(1))
> 
> In case it's hard to see with your font, the generated roff looks like
> this:
> 
> -\fBgit-web--browse\fR(1)\&.)
> +\fBgit-web\(embrowse\fR(1)\&.)
I can confirm. Sorry, I indeed missed that.
Show 7 quoted lines
> So I think that's a step backwards. I did check the asciidoctor
> rendering on git-scm.com, though, and it gets the {litdd} case wrong. So
> I think it does need fixing, but we need a solution that looks correct
> in both cases. Maybe linkgit:`git-web--browse`[1] would work; it seems
> OK with my version of asciidoc, but I have a feeling it will run into
> the same problem with asciidoctor (if it's not respecting {litdd} in
> that context, it's probably also not respecting backticks).

I will play with this to find a solution. Would it be an option to replace "--" with "-"? Why do we need two dashes if they cause trouble?

Thanks for the review, Lars

Previous: Jeff KingNext: Junio C Hamano
Message 13 of 53 in “travis-ci: build documentation”
  1. travis-ci: build documentationlarsxschneider@gmail.com, Apr 29, 2016
  2. Jeff KingApr 29, 2016
  3. Matthieu MoyApr 29, 2016
  4. Lars SchneiderApr 29, 2016
  5. Jeff KingApr 29, 2016
  6. Stefan BellerApr 29, 2016
  7. Matthieu MoyApr 29, 2016
  8. Lars SchneiderApr 29, 2016
  9. Junio C HamanoApr 29, 2016
  10. 0/2 travis-ci: build documentationlarsxschneider@gmail.com, May 2, 2016
  11. 1/2 Documentation: fix linkgit referenceslarsxschneider@gmail.com, May 2, 2016
  12. Jeff KingMay 2, 2016
  13. Lars SchneiderMay 3, 2016
  14. Junio C HamanoMay 3, 2016
  15. Jeff KingMay 3, 2016
  16. Jeff KingMay 3, 2016
  17. 0/2 travis-ci: build documentationlarsxschneider@gmail.com, May 4, 2016
  18. 1/2 Documentation: fix linkgit referenceslarsxschneider@gmail.com, May 4, 2016
  19. Lars SchneiderMay 4, 2016
  20. Jeff KingMay 4, 2016
  21. Ramsay JonesMay 4, 2016
  22. Junio C HamanoMay 4, 2016
  23. Junio C HamanoMay 4, 2016
  24. Junio C HamanoMay 4, 2016
  25. Jeff KingMay 4, 2016
  26. Junio C HamanoMay 4, 2016
  27. Jeff KingMay 4, 2016
  28. Junio C HamanoMay 4, 2016
  29. Jeff KingMay 4, 2016
  30. Junio C HamanoMay 4, 2016
  31. Jeff KingMay 4, 2016
  32. Junio C HamanoMay 4, 2016
  33. Jeff KingMay 4, 2016
  34. Junio C HamanoMay 4, 2016
  35. Junio C HamanoMay 4, 2016
  36. Junio C HamanoMay 4, 2016
  37. Jeff KingMay 4, 2016
  38. Jeff KingMay 4, 2016
  39. Ævar Arnfjörð BjarmasonMay 4, 2016
  40. Jeff KingMay 4, 2016
  41. 2/2 travis-ci: build documentationlarsxschneider@gmail.com, May 4, 2016
  42. Junio C HamanoMay 10, 2016
  43. Lars SchneiderMay 13, 2016
  44. 2/2 travis-ci: build documentationlarsxschneider@gmail.com, May 2, 2016
  45. Junio C HamanoMay 2, 2016
  46. Lars SchneiderMay 3, 2016
  47. Junio C HamanoMay 3, 2016
  48. Lars SchneiderMay 4, 2016
  49. Eric WongMay 4, 2016
  50. Junio C HamanoMay 4, 2016
  51. Christian CouderMay 4, 2016
  52. Matthieu MoyMay 4, 2016
  53. Matthieu MoyApr 29, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.