On Wed, May 15, 2019 at 2:37 PM Matt Wilkie wrote:
> Disambiguation: there is AsciiDoc the format specification and original
> python tool/library implementation, and AsciiDoctor the ruby tool/library.
> AsciiDoctor is basically a super-successful fork of asciidoc.
>
>- py2 -
>
> I'm learning as I write. At this point I don't know what the aims of py3
> are vis a vis Dr (ie: do they hope to be python equivalent or are they
> oriented to different end goals?)
>
https://github.com/asciidoc/asciidoc-py3/issues/67
--
You received this message because you are
Disambiguation: there is AsciiDoc the format specification and original
python tool/library implementation, and AsciiDoctor the ruby tool/library.
AsciiDoctor is basically a super-successful fork of asciidoc.
- py2 - https://github.com/asciidoc/asciidoc
- py3 -
On Wednesday, May 15, 2019 at 11:41:12 AM UTC-5, Edward K. Ream wrote:
The code should scan the root node looking for the regex "^="
>
Done at rev 9bd84b.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group
On Wednesday, May 15, 2019 at 11:41:12 AM UTC-5, Edward K. Ream wrote:
> The present code does not handle file encodings.
None are needed. AD handles only utf-8 or utf-16 encoded files, which
saves a lot of bother.
Edward
--
You received this message because you are subscribed to the Google
Rev a9b0aa in devel demonstrates Leo's new adoc command. It converts an
@adoc tree to AsciiDoctor sources. All parts of this code are experimental,
and subject to change.
The @adoc node should have the form: `@adoc x.adoc`. Relative file names
are assumed relative to c.frame.openDirectory.
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
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
>
I like Matt's "Discuss" prefix. It's apt here.
This post will discuss how Leo can support AsciiDoctor (AD). This is *not *a
discussion of...
- Preferences. Leo will retain its support for rST.
- The merits of AsciiDoctor. I'm convinced that Leo should support AD.
- How Leonistas "should"
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
On Tue, May 14, 2019 at 6:06 PM Edward K. Ream wrote:
#1146 has now been fixed.
>
This took several days. The actual fix was to set an ivar in Leo's core!
Ultimately, the work was gratifying. LeoWapp now has standardized traces,
and an old, forgotten, focus-related hack went away.
So this is
11 matches
Mail list logo
