Re: [PATCH v8 1/3] unit tests: Add a project plan document
From: Oswald Buddenhagen <hidden>
Date: 2023-10-11 23:05:28
Possibly related (same subject, not in this thread)
- 2023-11-01 · Re: [PATCH v8 1/3] unit tests: Add a project plan document · Junio C Hamano <hidden>
On Wed, Oct 11, 2023 at 02:14:03PM -0700, Josh Steadmon wrote:
On 2023.10.10 10:57, Oswald Buddenhagen wrote:quoted
On Mon, Oct 09, 2023 at 03:21:20PM -0700, Josh Steadmon wrote:quoted
+=== Comparison + +[format="csv",options="header",width="33%"] +|===== +Framework,"<<license,License>>","<<vendorable-or-ubiquitous,Vendorable or ubiquitous>>","<<maintainable-extensible,Maintainable / extensible>>","<<major-platform-support,Major platform support>>","<<tap-support,TAP support>>","<<diagnostic-output,Diagnostic output>>","<<runtime--skippable-tests,Runtime- skippable tests>>","<<parallel-execution,Parallel execution>>","<<mock-support,Mock support>>","<<signal-error-handling,Signal & error handling>>","<<project-kloc,Project KLOC>>","<<adoption,Adoption>>"the redundancy seems unnecessary; asciidoc should automatically use each target's section title as the xreflabel.Hmm, this doesn't seem to work for me. It only renders as "[anchor-label]".
i thought https://docs.asciidoctor.org/asciidoc/latest/attributes/id/#customize-automatic-xreftext is pretty clear about it, though. maybe the actual tooling uses an older version of the spec? or is buggy? or the placement of the titles is incorrect? or this applies to different links or targets only? or am i misreading something? or ...? regards