|Linebreak?||Thomas Wagner||7/24/12 1:23 AM|
I'm having a hard time getting most any markdown to work. One that I'd really like to use is line break. Any hints on how to get this to work?
|Re: [appledoc] Linebreak?||Tomaz Kragelj||7/24/12 1:24 AM|
Is 3+ spaces at the end of the line not working?
|Re: [appledoc] Linebreak?||Thomas Wagner||7/24/12 1:29 AM|
Nope. Can't get definition lists to work either. Or lists using - or * though + seemed to work. Am I missing something? A special command line switch I have to use or something?
|Re: [appledoc] Linebreak?||Tomaz Kragelj||7/24/12 1:35 AM|
Could you post example comment or better, attach whole file you're documenting...
|Re: [appledoc] Linebreak?||Thomas Wagner||7/24/12 1:41 AM|
Example attached. The only thing that worked for me is the list.
|Re: [appledoc] Linebreak?||Tomaz Kragelj||7/24/12 2:33 AM|
As for the line break, appledoc is trimming the text while processing it. Will see if it's a quick fix, then I'll add it, otherwise it'll come with next major release (currently on experimental branch on GitHub). Similar with definitions.
You can create a new issue on appledoc GitHub page if you want - then you'll be automatically informed on progress.
Appledoc is using discount library for Markdown processing, take a look at the supported syntax on their site:
As discount is more or less black box, I'm switching to different library on next release, so not all syntax elements may be supported...
|Re: [appledoc] Linebreak?||Thomas Wagner||7/24/12 2:46 PM|
Ok, cool. Thanks for the quick response. At least I know I'm not crazy.
|Re: [appledoc] Linebreak?||Tomaz Kragelj||7/24/12 10:02 PM|
Existing code was patched many times, especially Markdown processing; originally I implemented the whole thing, but then changed to third party parser (discount library). While this allowed more Markdown features, it made appledoc specific ones more difficult and some right down hacky (cross references for example). Hopefully this should become much more stable with next major release...
So it's not you :)