From: Alp Toker <alp@atoker.com>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] urls.txt: Use substitution to escape square brackets
Date: Sat, 15 Jul 2006 00:57:04 +0100 [thread overview]
Message-ID: <44B82F50.7050106@atoker.com> (raw)
In-Reply-To: <7v8xmvok49.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Alp Toker <alp@atoker.com> writes:
>
>> Junio C Hamano wrote:
>>> Looks nicer. Alp? Does this work with your version of
>>> asciidoc?
>> I'm using asciidoc 7.0.2, which came with Ubuntu Dapper.
>>
>> The man page output now looks like this:
>>
>> · ssh://[ # [user@] # ]host.xz/path/to/repo.git/
>> · ssh://[ # [user@] # ]host.xz/~user/path/to/repo.git/
>> · ssh://[ # [user@] # ]host.xz/~/path/to/repo.git
>
> I got a bit inventive and removed the comments after #, which
> were in Jonas's version, when I tried it out. Maybe doing the
> same might help you, since I suspect the above '#' are coming
> from the comment part.
No. Removing the comments doesn't help -- the output remains broken.
>> Out of the three patches,
>>
>> (at) "ssh://[user@]host.xz/path/to/repo.git/"
>> (jc) "ssh://+++[user@+++]host.xz/path/to/repo.git/"
>> (jf) "ssh://{startsb}user@{endsb}host.xz/path/to/repo.git/"
>>
>> I'd say (at) is still most readable, not requiring +++ markup (jc) or
>> hacks to asciidoc.conf (jf).
>
> I do not think defining [attribute] is a hack; it is a
> documented feature.
"You write an AsciiDoc document the same way you would write a normal
text document, there are no markup tags or weird format notations."
asciidoc solves this problem by design and without markup, with the
prescribed syntax being to indent and quote the text verbatim, just as
it was meant to be read.
Why try to fit a square peg in a round hole by defining attributes? It's
a good indicator that there's a hack going down when three competent
programmers can't escape a square bracket after three attempts spanning
two days ;-)
next prev parent reply other threads:[~2006-07-14 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 10:24 [PATCH] Revert "Documentation: Fix ssh://[user@]host.xz URL" Alp Toker
2006-07-14 10:24 ` [PATCH] Documentation: Fix ssh:// URLs in generated documentation Alp Toker
2006-07-14 10:24 ` [PATCH] Documentation: Minor capitalization typofix Alp Toker
2006-07-14 21:46 ` [PATCH] Documentation: Fix ssh:// URLs in generated documentation Junio C Hamano
2006-07-14 21:50 ` [PATCH] urls.txt: Use substitution to escape square brackets Jonas Fonseca
2006-07-14 22:07 ` Junio C Hamano
2006-07-14 23:01 ` Alp Toker
2006-07-14 23:13 ` Junio C Hamano
2006-07-14 23:57 ` Alp Toker [this message]
2006-07-14 23:42 ` Junio C Hamano
2006-07-15 0:38 ` Alp Toker
2006-07-15 7:44 ` [PATCH] Make asciidoc related rules depend on asciidoc.conf Jonas Fonseca
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=44B82F50.7050106@atoker.com \
--to=alp@atoker.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).