Re: discuss: Use markdown for Leo's documentation #1147

It seems to me that moving from rst to asciidoc for documentation in Leo is a good move. It adds features and provides a stable path into the future. Rst seems to have "lost" to markdown in the quick and easy markup space. But markdown seems to still be somewhat of a moving target. I don't see

Re: discuss: Use markdown for Leo's documentation #1147

On Tue, 14 May 2019 20:26:47 -0700 (PDT) Matt Wilkie wrote: > > > > > What I like about AsciiDoc is the code snippets support and the way > > it declares tables. But Pandoc can read ASCIIDoc [...] > > > > (?) This seems to be in the air or incomplete according to >

Re: discuss: Use markdown for Leo's documentation #1147

On Tue, May 14, 2019 at 6:34 PM Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > I agree on plain Markdown as a bad option for complex documentation, but > almost nobody uses plain Markdown for that but some superset of > CommonMark[1], as happens with Pandoc My next post will

Re: discuss: Use markdown for Leo's documentation #1147

Since we're discussing documentation and have stretched into scholarly writing and book writing, Pollen is worth a serious look. Not for Leo, I don't think, it's too different, but the reasoning and thinking which went into it resonates strongly with me. Plus it's just a damn good read. ;-)

Re: discuss: Use markdown for Leo's documentation #1147

> > What I like about AsciiDoc is the code snippets support and the way it > declares tables. But Pandoc can read ASCIIDoc [...] > (?) This seems to be in the air or incomplete according to https://github.com/jgm/pandoc/issues/1456. (From the ycombinator thread, which by the way also

Re: discuss: Use markdown for Leo's documentation #1147

Hi, I agree on plain Markdown as a bad option for complex documentation, but almost nobody uses plain Markdown for that but some superset of CommonMark[1], as happens with Pandoc, which, BTW, has an Abstract Syntax Tree that enables high programmability an personalization[2] from several 

Re: discuss: Use markdown for Leo's documentation #1147

On Tue, May 14, 2019 at 4:07 PM Kent Tenney wrote: > I don't use a lot of rst capability, but really depend on > .. contents:: > Leo will always support the rst3 command, so you should have no worries. Edward -- You received this message because you are subscribed to the Google Groups

Re: discuss: Use markdown for Leo's documentation #1147

On Tue, 14 May 2019 16:07:15 -0500 Kent Tenney wrote: > I don't use a lot of rst capability, but really depend on > .. contents:: > > to generate links to sections in a document > anyone found a way to do that in Markdown? I think pandoc will generate tocs from markdown, I know it will if the

Re: discuss: Use markdown for Leo's documentation #1147

I don't use a lot of rst capability, but really depend on .. contents:: to generate links to sections in a document anyone found a way to do that in Markdown? Thanks, Kent On Tue, May 14, 2019 at 3:12 PM Matt Wilkie wrote: > Hi Terry! thanks for chiming in > > The problem is that markdown's

Re: discuss: Use markdown for Leo's documentation #1147

Hi Terry! thanks for chiming in The problem is that markdown's what everyone uses / expects. So the > downside to anything that's not markdown is that people won't know it, > whereas they would know markdown. > A salve for this is Markdown compatibility, via AsciiDoctor, though it remains

Re: discuss: Use markdown for Leo's documentation #1147

On Tuesday, May 14, 2019 at 5:50:46 AM UTC-5, Edward K. Ream wrote: > The code blocks feature is something that Leo must have. The other features look useful as well. For example, the various tables features would moot #433

Re: discuss: Use markdown for Leo's documentation #1147

On Tue, May 14, 2019 at 8:46 AM Terry Brown wrote: Thanks for these comments. I think it's easy to argue that there are better (more expressive / > extensible) text dialects than markdown. restructuredText is an obvious > example. > That's what Leo uses at present. The big win for

Re: discuss: Use markdown for Leo's documentation #1147

On Tue, 14 May 2019 03:50:46 -0700 (PDT) "Edward K. Ream" wrote: > Anyone think AsciiDoctor is a bad idea? I think it's easy to argue that there are better (more expressive / extensible) text dialects than markdown. restructuredText is an obvious example. The problem is that markdown's what

Re: discuss: Use markdown for Leo's documentation #1147

On Monday, May 13, 2019 at 3:11:24 PM UTC-5, Matt Wilkie wrote: AsciiDoc as syntax with AsciiDoctor for handling is smarter and on my >> shortlist. See Stop Using Markdown For Documentation >> (read >> conclusion first then go back for

Re: discuss: Use markdown for Leo's documentation #1147

On Monday, May 13, 2019 at 3:11:24 PM UTC-5, Matt Wilkie wrote: *Re: https://github.com/leo-editor/leo-editor/issues/1147 > . Posting as a thread > in groups to keep the issue short and clean.* > AsciiDoc as syntax with AsciiDoctor for

discuss: Use markdown for Leo's documentation #1147

*Re: https://github.com/leo-editor/leo-editor/issues/1147. Posting as a thread in groups to keep the issue short and clean.* Edward: > I much prefer markdown syntax, but there questions about using markdown: > >1. Replacing Sphinx .css. This css >