On Thu, 2 Oct 2014 14:43:50 +0200 Stephan Beal <sgb...@googlemail.com> wrote:
> i hear you ;), but as i said at the start of this thread, i am > ambivalent about which format(s) fossil supports, which may be > interpreted as "i don't care, as long as someone else implements > it" ;). Well, I am thinking along these words of you: "If you like, as a repayment for saving me weeks of work writing/debugging another ncurses script binding (by introducing me to termbox), we can try to get one set up for you with Asciidoc." considering few people showed interest for it and assuming it's not too hard 'cause it has to support *only* rendering of Asciidoc(tor) files and no support for it in the tickets etc. > That said... If you have suggestions for a generic api for arbitrary > wiki parsers/filters for libfossil, i am all ears. :) As I wrote above, no intention for providing general api nor support for arbitrary markups...if rendering Asciidoc(tor) can be done with not too much pain by taking advantage of Asciidoctor.js, then it's fine, otherwise forget about it. Sincerely, Gour -- A person who is not disturbed by the incessant flow of desires — that enter like rivers into the ocean, which is ever being filled but is always still — can alone achieve peace, and not the man who strives to satisfy such desires. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
