Re: Improved asciidoc, asciidoctor and pandoc support

2019-11-21 Thread jkn
On Tuesday, November 12, 2019 at 12:54:39 PM UTC, jkn wrote: > > > > On Thursday, October 17, 2019 at 11:59:49 AM UTC+1, Edward K. Ream wrote: >> >> On Thu, Oct 17, 2019 at 3:51 AM jkn wrote: >> >> Thanks for #1398. >>> >> >> You're welcome. It should happen in a few days. >> >> Edward >> > >

Re: Improved asciidoc, asciidoctor and pandoc support

2019-11-12 Thread jkn
On Thursday, October 17, 2019 at 11:59:49 AM UTC+1, Edward K. Ream wrote: > > On Thu, Oct 17, 2019 at 3:51 AM jkn wrote: > > Thanks for #1398. >> > > You're welcome. It should happen in a few days. > > Edward > Hi Edward Thanks for addressing #1398. I am getting to grips with using adoc a

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-17 Thread Edward K. Ream
On Thu, Oct 17, 2019 at 8:42 AM Chris George wrote: > > >> Oh, I suppose Leo could run the rST through the sphinx tool chain, and >> render the resulting html, or better, open the resulting page in a >> browser. Rather than reopening #333, I have just created #1388. It's >> schedule for Leo

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-17 Thread Chris George
> > Oh, I suppose Leo could run the rST through the sphinx tool chain, and > render the resulting html, or better, open the resulting page in a > browser. Rather than reopening #333, I have just created #1388. It's > schedule for Leo 6.1, but no guarantees. > > Edward > The browser based

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-17 Thread Edward K. Ream
On Thu, Oct 17, 2019 at 3:51 AM jkn wrote: Thanks for #1398. > You're welcome. It should happen in a few days. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-17 Thread jkn
On Wednesday, October 16, 2019 at 12:24:16 PM UTC+1, Edward K. Ream wrote: > > On Wed, Oct 16, 2019 at 5:04 AM jkn > > wrote: > > > I for one would appreciate a bit of an explanation of the 'very > different workflow required'; I am kinda used to using @file etc. but abit > unclear as to how

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-16 Thread Edward K. Ream
On Wed, Oct 16, 2019 at 5:04 AM jkn wrote: > I for one would appreciate a bit of an explanation of the 'very different workflow required'; I am kinda used to using @file etc. but abit unclear as to how @adoc and @pandoc change thigs (and I would like to use them) The workflow is similar to the

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-16 Thread jkn
On Thursday, October 10, 2019 at 9:18:34 PM UTC+1, Matt Wilkie wrote: > > >> For me the external file is not created. See the desktop-integration.leo >>> file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. >>> >> >> Matt, what's the status of this now? >> > > It works after

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-14 Thread Edward K. Ream
On Fri, Oct 11, 2019 at 10:03 AM Chris George wrote: While this work is fresh in your mind is there any possibility of doing > live rendering of Sphinx in the VR plugin? > As I said in #333 (now renamed) Sphinx uses reStructuredText as its markup language, and Leo already renders rST live. Oh,

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-11 Thread Chris George
> > *Live rendering of asciidoc and pandoc markup* > > The VR plugin recognizes @adoc nodes, @pandoc nodes (see below) and > @language pandoc and @language md. > > The VR plugin renders only p.b. Read on if you want render entire files... > > > While this work is fresh in your mind is there any

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-10 Thread Edward K. Ream
On Thu, Oct 10, 2019 at 3:18 PM Matt Wilkie wrote: > >> For me the external file is not created. See the desktop-integration.leo >>> file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. >>> >> >> Matt, what's the status of this now? >> > > It works after installing asiidoc3. I didn't

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-10 Thread Matt Wilkie
> > > For me the external file is not created. See the desktop-integration.leo >> file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. >> > > Matt, what's the status of this now? > It works after installing asiidoc3. I didn't understand that @adoc is fundamentally different from

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-10 Thread Edward K. Ream
On Mon, Oct 7, 2019 at 2:08 PM Matt Wilkie wrote: > Please report your experiences with these new features. >> > > For me the external file is not created. See the desktop-integration.leo > file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. > Matt, what's the status of this now?

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-07 Thread Edward K. Ream
On Mon, Oct 7, 2019 at 11:39 AM Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > Nice to see those additions. In the Leo's documentation, I would expand > about why the "pandoc tool must exist". > Done in devel. Edward -- You received this message because you are subscribed to the

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-07 Thread Matt Wilkie
> > Please report your experiences with these new features. > For me the external file is not created. See the desktop-integration.leo file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. Leo Log Window Leo 6.1-devel, devel branch, build bd1ac64b20 2019-10-07 10:51:57 -0500 Python

Re: Improved asciidoc, asciidoctor and pandoc support

2019-10-07 Thread Offray Vladimir Luna Cárdenas
Hi, Nice to see those additions. In the Leo's documentation, I would expand about why the "pandoc tool must exist". Cheers, Offray On 7/10/19 10:31 a. m., Edward K. Ream wrote: > There are several major features here, spanning several issues, both > open and closed. > > This post will be

Improved asciidoc, asciidoctor and pandoc support

2019-10-07 Thread Edward K. Ream
There are several major features here, spanning several issues, both open and closed. This post will be pre-writing for Leo's documentation. *Support for @language pandoc* leo/modes/pandoc.py is based on leo/modes/md.py. *Live rendering of asciidoc and pandoc markup* The VR plugin recognizes