Hello, on Saturday 11 March 2017 at 16:23, Mark Janssen wrote: > I wasn't aware that the author of the current implementation was a fossil > user as well :)
Being the author really helps integrating the code into fossil paradigm, deal with licencing stuff, and adding new features efficiently. It might even take less time for me to write support for fenced code blocks than both e-mails on this mailing list :-) > On Sat, 11 Mar 2017, 16:22 Natacha Porté, <nata...@instinctive.eu> wrote: > > I never understood the appeal for code blocks, but if it's only that > > it's very easy to add to the existing implementation. > > > > Code blocks are very convenient for displaying TIP examples or other pieces > of example code. I should really clarify that it was about *fenced* code blocks, since traditional markdown code blocks are correctly supported (unless there is a serious bug in there). I do understand the use of code blocks, and use them myself frequently. But only the indented version, because the fenced one feels to me like trading a lot of ease of reading for a little bit of ease of writing (or rather cut-and-pasting, I don't think it changes much for real writing). And that's without taking into account that on top of that most of my documents (even in markdown) are read much more often than written. Of course, I'm bias by my using only decently-featured text editor. If I had to insert manually a tabulation at the beginning of every line, I would consider changing the editor before condering chaning the language. Natacha _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
