Did the "asciidoc" column specifier column specifier go away?

25 views
Skip to first unread message

Ken McGlothlen

unread,
Mar 3, 2022, 1:53:11 PMMar 3
to asciidoc
I often have a need to put Asciidoc-formatted text in columns, but this has been causing Asciidoc to fail lately. For example, the following table

[cols="<.<1,<.<1",frame="none",grid="none"]
|==========================================================
|* test
* test
|test2
|==========================================================

will produce the text "* test * test" in the first column, but trying to get a bulleted list in the first column by specifying that, as in

[cols="<.<1a,<.<1",frame="none",grid="none"]
|==========================================================
|* test
* test
|test2
|==========================================================

results in an unhelpfully silent failure (exit code 1).

Is there a workaround?

(As a side note, I really do find the occasional error messages helpful; Asciidoc seems to have eliminated those lately, and I'm not sure why that choice was made.)

I'm running asciidoc 10.1.1, by the way.

Matthew Peveler

unread,
Mar 4, 2022, 7:50:21 AMMar 4
to asciidoc
Using asciidoc 9.1.1 and asciidoc 10.1.1, I get the same successfully built html for both of your examples. Are you passing in or using any flags, or a custom conf file?

> (As a side note, I really do find the occasional error messages helpful; Asciidoc seems to have eliminated those lately, and I'm not sure why that choice was made.)

This would be an unintended regression. If you notice somewhere an error message had been displaying and no longer does, please let me know as reproducible cases of "it used to do X and now does Y" are super helpful!

Reply all
Reply to author
Forward
0 new messages