Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
Sometime between April and now, an apparent bug was introduced in to the system which meant that syntax looking like:
* list
1.
is unacceptable to Instiki. The precise error is rather weird, and you wouldn’t guess from looking at it what the problem was!
So … don’t do it!
I’ve found three cases of this on the ’lab: at enriched bicategory, ideal completion, and sketch and corrected them all. If you want to see the error, try enriched bicategory (doriath). All three cases were the same: someone had a one-element unordered list of a reference which ended with the year and for some reason, the year (with its following full-stop) had been put on a newline, with an explicit newline character (not just normal word-wrapping). That is, something like:
* Joe Extrovert. _My fantastic paper_
2005.
The fix was simply to remove the newline character.
Currently, Instiki won’t let you save a page with this “bad” syntax on it. The three cases I found were of old pages with that on which must have been saved before the bug appeared (which is how I can date it to more recently than April). So this should no longer affect looking at pages, and now that you know to avoid it, it shouldn’t affect editing pages. (It’s still a bug, and hopefully will get fixed soon.)
To be clear, the list syntax:
* unordered list
1. ordered list
does work.
(I’ve reported this to Jacques, and thanks are due to Finn Lawler for spotting this one.)
thanks are due to Finn Lawler for spotting this one
To be fair, all I did was stumble upon an error message – it was Andrew who diagnosed and fixed the problem, and overnight too. So extra super thanks are due to him.
To be clear, the list syntax:
* unordered list 1. ordered list
does work.
So to break enriched bicategory (doriath), we must remove the second list
. I see that now. (I also see that whitespace there is not sufficient.)
Jacques has fixed this now and it should be in the next update (early tomorrow morning, UTC).
1 to 4 of 4