On Sat, Mar 11, 2017 at 8:08 AM, Mark Janssen <mpc.jans...@gmail.com> 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 (switch on extension being one as well) > but having different markdown flavours in one repo just feels wrong to me. > I'm torn on the two. I think I'd prefer the repo wide setting myself, or even just replacing wholesale, but I can appreciate why people who've already starting using the existing markdown might not like that. Switching on an extension feels ugly to me, but it would allow people to gradually change their repo over to using commonmark over time rather than having to do it all at once. In any case, I'm all for it.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
