[web2py] Re: MARKMIN change of behavior
Hmm, unless you mention what the 'better behaviour' is, it is difficult to agree as this change does result in broken content. In any case, I also believe that 'better behaviour' should also be to try to retain compatibility with Markdown. There are now two departures from Markdown with regards header tags. The other one is this: Markmin:#Head > head Markdown: #Head > head Many users started using Markmin as a substitute to Markdown. In fact my company now uses both and the staff have to remember any nit-picking differences like this. Where it doesn't hurt, it would be great to harmonise the behaviour, not introduce more differences. Best regards, David On Wednesday, August 8, 2012 8:23:49 PM UTC+1, Massimo Di Pierro wrote: > > There is a manor change of behavior in MARKMIN. > > Before: > > - markmin > # title > aaa > > bbb > -- end markmin > > would render as > > titleaaa > > After: > > the same markmin would render > > title aaa > > In other words now headers (#, ##, ###) can be continued to the next line > and need an empty new line to be separated from the first paragraph. > I think the new behavior is better and previous behavior should be > considered a bug. > > Anyway. I just wanted people to know, in case there are major objections. > > Massimo > > > --
[web2py] Re: MARKMIN change of behavior
The #head is now fixed. Please check it. On Saturday, 11 August 2012 11:35:57 UTC-5, villas wrote: > > Hmm, unless you mention what the 'better behaviour' is, it is difficult > to agree as this change does result in broken content. > > In any case, I also believe that 'better behaviour' should also be to try > to retain compatibility with Markdown. There are now two departures from > Markdown with regards header tags. The other one is this: > > Markmin:#Head > head > Markdown: #Head > head > > Many users started using Markmin as a substitute to Markdown. In fact my > company now uses both and the staff have to remember any nit-picking > differences like this. Where it doesn't hurt, it would be great to > harmonise the behaviour, not introduce more differences. > > Best regards, David > > > On Wednesday, August 8, 2012 8:23:49 PM UTC+1, Massimo Di Pierro wrote: >> >> There is a manor change of behavior in MARKMIN. >> >> Before: >> >> - markmin >> # title >> aaa >> >> bbb >> -- end markmin >> >> would render as >> >> titleaaa >> >> After: >> >> the same markmin would render >> >> title aaa >> >> In other words now headers (#, ##, ###) can be continued to the next line >> and need an empty new line to be separated from the first paragraph. >> I think the new behavior is better and previous behavior should be >> considered a bug. >> >> Anyway. I just wanted people to know, in case there are major objections. >> >> Massimo >> >> >> --
[web2py] Re: MARKMIN change of behavior
1. I still don't understand why you departed from the behaviour of markdown to now create a single header line from multi-line text. The behaviour does not seem natural to me, especially as it introduces a new incompatibility with markdown. 2. I tested the change with regards the space between the # and header. That nows works fine and the same as markdown. Thanks for fixing that. Regards, David --
[web2py] Re: MARKMIN change of behavior
I did not. markmin2html.py was rewritten to add new functionality and that was an epiphenomenon. I guess we can revert it. I will talk to Vladyslav and see what it involves. On Wednesday, 15 August 2012 11:31:05 UTC-5, villas wrote: > > 1. I still don't understand why you departed from the behaviour of > markdown to now create a single header line from multi-line text. The > behaviour does not seem natural to me, especially as it introduces a new > incompatibility with markdown. > > 2. I tested the change with regards the space between the # and header. > That nows works fine and the same as markdown. Thanks for fixing that. > > Regards, > David > --
[web2py] Re: MARKMIN change of behavior
Well some epiphenomena may be serendipitous, but probably not this one. Let's face it, a change which breaks page content would always be unwelcome, unless delivering some other benefit. On Wednesday, August 15, 2012 5:48:56 PM UTC+1, Massimo Di Pierro wrote: > > I did not. markmin2html.py was rewritten to add new functionality and that > was an epiphenomenon. I guess we can revert it. > I will talk to Vladyslav and see what it involves. > > > > On Wednesday, 15 August 2012 11:31:05 UTC-5, villas wrote: >> >> 1. I still don't understand why you departed from the behaviour of >> markdown to now create a single header line from multi-line text. The >> behaviour does not seem natural to me, especially as it introduces a new >> incompatibility with markdown. >> >> 2. I tested the change with regards the space between the # and header. >> That nows works fine and the same as markdown. Thanks for fixing that. >> >> Regards, >> David >> > --
[web2py] Re: MARKMIN change of behavior
You make a good point. We will investigate. technically markmin in in contrib. We do not fully guarantee backward compatibility of stuff in contrib, even if it is written us. Anyway, because it is written by us and because this change was not intentional we'll look into reverting it. massimo On Wednesday, 15 August 2012 18:53:28 UTC-5, villas wrote: > > Well some epiphenomena may be serendipitous, but probably not this one. > > Let's face it, a change which breaks page content would always be > unwelcome, unless delivering some other benefit. > > > > On Wednesday, August 15, 2012 5:48:56 PM UTC+1, Massimo Di Pierro wrote: >> >> I did not. markmin2html.py was rewritten to add new functionality and >> that was an epiphenomenon. I guess we can revert it. >> I will talk to Vladyslav and see what it involves. >> >> >> >> On Wednesday, 15 August 2012 11:31:05 UTC-5, villas wrote: >>> >>> 1. I still don't understand why you departed from the behaviour of >>> markdown to now create a single header line from multi-line text. The >>> behaviour does not seem natural to me, especially as it introduces a new >>> incompatibility with markdown. >>> >>> 2. I tested the change with regards the space between the # and header. >>> That nows works fine and the same as markdown. Thanks for fixing that. >>> >>> Regards, >>> David >>> >> --
