On Aug 29, 2015, at 8:58 AM, Baptiste Daroussin <baptiste.darous...@gmail.com> wrote: > > the number 2 major complaints I heard from user
Really? What’s #1 and #3? :) I find that setting the “block formatting” option in Admin/Settings/Timeline solves most of my problems in this area. I don’t mind that Fossil’s block formatting rules assume single hard LFs are soft line breaks, or that it only inserts hard paragraph breaks on double LF. This is the same rule used by Markdown, so it’s not even something I have to actively think about any more; it’s just how plain text -> web text works in my brain now. In fact, I’d welcome a feature that allowed Markdown-formatted checkin comments. Not because I spend a lot of time making my checkin comments pretty, but because it would occasionally [be helpful](http://www.wikihow.com/Be-Helpful). :) Actually, I think my main use of Markdown-formatted checkin comments would be bullet lists, for those really complicated checkins that do several related things. And while I’m wishing, an option for Markdown-formatted tickets would be nice, too. Wiki markup is a bit overkill when all you want is the occasional `literal`, and it’s confusing to switch between Markdown and Wiki links, since their order of URL/text is opposite. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users