Re: .js importer still has problems

2020-01-31 Thread Edward K. Ream
On Mon, Jan 27, 2020 at 8:14 AM 'tfer' via leo-editor < leo-editor@googlegroups.com> wrote: > Changing the @auto node to an @file node and manually doing the sectioning is acceptable, but we probably want to yield an at auto import to give us a result that, upon being saved, still generates a diff

Re: .js importer still has problems

2020-01-27 Thread 'tfer' via leo-editor
On Monday, January 27, 2020 at 6:57:46 AM UTC-5, Edward K. Ream wrote: > > On Monday, January 27, 2020 at 5:22:41 AM UTC-6, Edward K. Ream wrote: > > ​I see the same message as you reported. This should be enough to fix the >> problem. >> > > I think I can see how the following could occur: >

Re: .js importer still has problems

2020-01-27 Thread Edward K. Ream
On Monday, January 27, 2020 at 5:22:41 AM UTC-6, Edward K. Ream wrote: ​I see the same message as you reported. This should be enough to fix the > problem. > I now remember the general problem: it's difficult/impossible to use section references in some situations, but without section reference

Re: .js importer still has problems

2020-01-27 Thread Edward K. Ream
​On Mon, Jan 27, 2020 at 1:22 AM 'tfer' via leo-editor wrote: ​> ​the import should be under the effect of a "@tabwidth 2" directive, which actually was hard to have happen​. I do see an import failure with @tabwidth 2.​​ I did so as follows: dir_ = r'C:\leo.repo\reveal.js\js' c.tab_width = 2 t

Re: .js importer still has problems

2020-01-26 Thread 'tfer' via leo-editor
I wrote an earlier reply, but it did not post, ah web interfaces... The error with the mixed up line numbers below, is from the console from which I'm running Leo and have to do with the import, the don't exist in any file. On Sunday, January 26, 2020 at 4:48:56 AM UTC-5, Edward K. Ream wrote:

Re: .js importer still has problems

2020-01-26 Thread Edward K. Ream
On Wednesday, January 22, 2020 at 3:36:08 PM UTC-5, tfer wrote: > To this end I tried import the main engine of reveal, the file reveal.js, > Leo creates an @auto node, and creates a subtree. I get the following in > the cmd shell I started Leo from: > > > --

Re: .js importer still has problems

2020-01-25 Thread Edward K. Ream
On Wed, Jan 22, 2020 at 3:36 PM 'tfer' via leo-editor < leo-editor@googlegroups.com> wrote: I've hung out with Leo since early days, discovered it when exploring > Literate Programming, always liked the focus management outline provides, > but I've yet to get the benefits I was looking for from it

.js importer still has problems

2020-01-22 Thread 'tfer' via leo-editor
I've hung out with Leo since early days, discovered it when exploring Literate Programming, always liked the focus management outline provides, but I've yet to get the benefits I was looking for from it. Maybe that is due to what my envisioned use case is, I'm not looking to write my own origi