From: Michael J Gruber <git@drmicha•warpmail.net>
To: unlisted-recipients:; (no To-header on input)
Cc: wmpalmer@gmail•com, Jeff King <peff@peff•net>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: RFD: tables in documentation
Date: Sun, 02 May 2010 17:27:47 +0200 [thread overview]
Message-ID: <4BDD99F3.9000305@drmicha.warpmail.net> (raw)
In-Reply-To: <4BDD956F.5070800@drmicha.warpmail.net>
Michael J Gruber venit, vidit, dixit 02.05.2010 17:08:
> Will Palmer venit, vidit, dixit 02.05.2010 16:51:
>> sorry about that, apparently "shift+enter" means "send" to this thing...
>>
>> On Sun, 2010-05-02 at 15:43 +0100, Will Palmer wrote:
>>> On Sun, 2010-05-02 at 15:31 +0200, Michael J Gruber wrote:
>>>> Jeff King venit, vidit, dixit 02.05.2010 07:06:
>>>>> On Sat, May 01, 2010 at 08:37:39PM +0200, Michael J Gruber wrote:
>>>>> Did you put the source up anywhere? I didn't see it, but it would be
>>>>> interesting to see how painful it is to write.
>>>>
>>>> http://repo.or.cz/w/git/mjg.git/shortlog/refs/heads/doc-use-tables
>>>>
>>>> Tough guess, I know ;)
>>>>
>>>> Michael
>>>
>>
>> that looks suspiciously like a format that's intended to be readable in
>> both plaintext and eventually-generated form. This is me speaking in
>> pure ignorance, but would something like (though I assume not exactly):
>>
>> [cols="1,3*5,8"]
>> |=====================
>> | |I |H |M |Result
>> | 0 |nothing |nothing |nothing |(does not happen)
>> | 1 |nothing |nothing |exists |use M
>> | 2 |nothing |exists |nothing |remove path from index
>> .2+| 3 .2+|nothing .2+|exists |exists, H == M |use M if "initial checkout", keep index otherwise
>> exists, H != M |fail
>> |=====================
>>
>> work as intended?
>>
>
> Uhm, how is that different from my patch (except for spaces which I
> didn't bother with for this p-o-c)? [This is AsciiDoc - you know, do
> you? ;)]
>
> Jeff doesn't like the ascii art in the roff output (.1, as can be seen
> in the .1.txt file). It looks very "strong", just like the content.
>
> Further experimentation (editing the xml) indicates that with my
> toolchain, I can either shut off all borders (between cells as well as
> outer) or none. Why does working with the toolchain always frustrate me?
> It's often a hindrance for improvements.
>
> So, we could shut off all borders by adding an output dependent table
> definition in asciidoc.conf, copying current asciidoc's own and
> modifying it for docbook-man output. Is it worth it? Maybe others like
> the strong ascii borders...
For completeness, it results in this:
I H M Result
0 nothing nothing nothing (does not happen)
1 nothing nothing exists use M
2 nothing exists nothing remove path from index
3 nothing exists exists, H ==M use M if "initial
checkout", keep index
exists, H != M fail otherwise
[Same unealt rowspan issue, of course.]
Michael
next prev parent reply other threads:[~2010-05-02 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 18:37 RFD: tables in documentation Michael J Gruber
2010-05-02 5:06 ` Jeff King
2010-05-02 13:31 ` Michael J Gruber
2010-05-02 14:43 ` Will Palmer
2010-05-02 14:51 ` Will Palmer
2010-05-02 15:08 ` Michael J Gruber
2010-05-02 15:27 ` Michael J Gruber [this message]
2010-05-02 17:53 ` Jonathan Nieder
2010-05-02 19:23 ` Michael J Gruber
2010-05-25 9:46 ` Jeff King
2010-05-25 11:59 ` Michael J Gruber
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=4BDD99F3.9000305@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
--cc=wmpalmer@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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