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
I wasn't aware that the author of the current implementation was a fossil
user as well :)
On Sat, 11 Mar 2017, 16:22 Natacha Porté, 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.
>
Hello,
on Saturday 11 March 2017 at 15:07, Mark Janssen wrote:
> Recently I have been looking to use fossil as a backend for managing the
> Tcl tip collection.
> An obvious format for the new tip format would be markdown, but currently
> the fossil markdown support is fairly limited (for example
On Sat, Mar 11, 2017 at 8:08 AM, Mark Janssen wrote:
> Good questions. Currently it replaces the existing markdown parser which
> can break existing files. This is why I suggested the repo wide setting.
>
Sorry, I missed that part.
> There are other possible solutions
Good questions. Currently it replaces the existing markdown parser which
can break existing files. This is why I suggested the repo wide setting.
There are other possible solutions (switch on extension being one as well)
but having different markdown flavours in one repo just feels wrong to me.
On Sat, Mar 11, 2017 at 7:07 AM, Mark Janssen wrote:
>
> My question to you all is, would there be any interest in adding
> commonmark support?
>
I like the idea of a more fully featured markdown implementation. Would
this replace the existing markdown support or be in
Recently I have been looking to use fossil as a backend for managing the
Tcl tip collection.
An obvious format for the new tip format would be markdown, but currently
the fossil markdown support is fairly limited (for example there are no
code blocks)
I have made a version of fossil which
7 matches
Mail list logo