Using Leo

hallo, I am completly new to leo and mostly also to python. I do not find any Leo.exe which would run on Windows(8.1) In Thonny I was able to install Leo. But how do I start it? Thanks for any help PS The above email adress does not work well for me. Instead rolfb...@ewe.net is ok. -- You receiv

Re: Using leo to _refactor_ Arduino c++ code and libraries. A bad idea ?

hough I started programming in 1987) > is to refactor a project using 8-bit RF-capable Arduinos in an IoT network. > I'm still not sure leo is the right tool for that, but it could be, as > there are several arguments for using leo : > - the most important thing to me is documen

Using leo to _refactor_ Arduino c++ code and libraries. A bad idea ?

it could be, as there are several arguments for using leo : - the most important thing to me is documentation. /* */ and // are not enough - there are about 20-30 files in the library, and 5-10 "sketches", potentially more to come - I'd like to have some more powerful motes as well

Re: Basic concepts of using Leo to organise a python program

On Monday, March 21, 2022 at 10:56:08 AM UTC-4 cve...@gmail.com wrote: > Definitely, and I appreciate your (and Edward's) responsiveness and > openness. I don't grasp everything in your message (yet), I only installed > leo on one computer yesterday and was a bit surprised to see it (pip > actu

Re: Basic concepts of using Leo to organise a python program

Definitely, and I appreciate your (and Edward's) responsiveness and openness. I don't grasp everything in your message (yet), I only installed leo on one computer yesterday and was a bit surprised to see it (pip actually) download PyQt5 just after I had manually installed PyQt6, and ... not ins

Re: Basic concepts of using Leo to organise a python program

I've used and liked mind maps very a long time, and I'm very picky about their appearance. I started with Tony Buzan's book, before there were programs to make mind maps. Mind Maps were among other things an excellent memory aid for me. I used to take meeting notes as mind maps in real time

Re: Basic concepts of using Leo to organise a python program

It doesn't surprise me. That's indeed the strength of the Brain (to me), it is basically a mindmap but with the *current thought* as the center, it's not hierarchical. In that sense it is different from an outlook. OTOH, in zettelkasten I get the impression that the focus is on the taking of not

Re: Basic concepts of using Leo to organise a python program

I fooled around with a sample Brain project on the Brain's web site. I was able to import the "thoughts" and links. The project file contains a number of .json files, although they are not actually valid json. But it's possible to work with them anyway. So yes, it's not hard to do an import.

Re: Basic concepts of using Leo to organise a python program

Actually, just the browser bookmark scripts and optionally the mind mapping visualization, would probably do it. On Friday, March 18, 2022 at 2:07:27 PM UTC-4 tbp1...@gmail.com wrote: > Having downloaded one of the example brains, and looked at a few of the > online examples, I'm coming to thi

Re: Basic concepts of using Leo to organise a python program

Having downloaded one of the example brains, and looked at a few of the online examples, I'm coming to think that a combination of the browser bookmark manager scripts I'm working on together, perhaps, with the zettelkasten-style organizing scripts I offered in a different thread, would provide

Re: Basic concepts of using Leo to organise a python program

I've tried TheBrain maybe three times over these many years. It always seems so promising, and I always abandon it with frustration. On Friday, March 18, 2022 at 11:10:22 AM UTC-4 cve...@gmail.com wrote: > ... Now, maybe leo could also import TheBrain files ? ;-) > Now there is an interesting

Re: Basic concepts of using Leo to organise a python program

> Would you (Edward or the community) be interested in a NOOB-directed > contribution ? > Sure. That's how people stop being newbies :-) PR's are always welcome. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this g

Re: Basic concepts of using Leo to organise a python program

6:37 PM UTC+1 Edward K. Ream wrote: > On Tue, Nov 21, 2017 at 9:21 AM, Edward K. Ream wrote: > >> On Tue, Nov 21, 2017 at 5:45 AM, lewis wrote: >> >>> I have been searching Leo documentation for a simple guide to using Leo >>> and to write python files bu

Re: What are some tips for using Leo as a stream of consciousness thought tool?

efactor the diagram, > it's much easier than an eraser, or drawing an entirely new diagram. > > What I've learned so far is not to sweat word order, exact phrasing of > the words, or hierarchy. Those will reveal themselves later. It's a > mindset. > > Right now my diagr

Re: What are some tips for using Leo as a stream of consciousness thought tool?

On Wed, Mar 10, 2021 at 12:08 AM Steve Litt wrote: Thanks for the info and link Ed, > You're welcome. Glad they were useful. What I've learned so far is not to sweat word order, exact phrasing of > the words, or hierarchy. Those will reveal themselves later. It's a > mindset. > Excellent. Begin

Re: What are some tips for using Leo as a stream of consciousness thought tool?

rawing an entirely new diagram. What I've learned so far is not to sweat word order, exact phrasing of the words, or hierarchy. Those will reveal themselves later. It's a mindset. Right now my diagram has outgrown an 8.5x11 landscape paper, so I'm deciding between a diagram with

Re: What are some tips for using Leo as a stream of consciousness thought tool?

I really like mind maps, too. And mostly I don't like existing mind map software. For a book I wrote, I made a simple mind map for some of the chapters. Then I started to flesh them out, which a mind map really stimulates the thinking. It worked very well. I also find that a basic mind map o

Re: What are some tips for using Leo as a stream of consciousness thought tool?

On Saturday, March 6, 2021 at 9:17:48 AM UTC-6 stevelitt wrote: I normally use outlines as a concept decomposition tool, which implies > that I already know where I'm going. > > But now I find myself needing to do stream of consciousness thought to > *discover* what I want to say in my next boo

What are some tips for using Leo as a stream of consciousness thought tool?

Hi all, I normally use outlines as a concept decomposition tool, which implies that I already know where I'm going. But now I find myself needing to do stream of consciousness thought to *discover* what I want to say in my next book. What are some tips for doing this in Leo? SteveT Steve Litt

Re: LaTex to PDF workflow using Leo

On Tue, Sep 29, 2020 at 3:01 PM Arjan wrote: > The above script used to work, but recently (after not having used it for > a long time), I noticed it errors: > > exception executing script > TypeError: afterChangeNodeContents() got an unexpected keyword argument > 'dirtyVnodeList' > The way to a

Re: LaTex to PDF workflow using Leo

Yes, the method signature has changed. It's now: def afterChangeNodeContents(self, p, command, bunch, inHead=False): """Create an undo node using d created by beforeChangeNode.""" The command argument seems to be the name of the Leo command that would cause the undoable changes. Presumably

Re: LaTex to PDF workflow using Leo

The above script used to work, but recently (after not having used it for a long time), I noticed it errors: exception executing script TypeError: afterChangeNodeContents() got an unexpected keyword argument 'dirtyVnodeList' only 6 lines line 49: p.b = s * line

Re: Leopard: using Leo as a DB and website

be fun. I took a quick look years ago. > > However, there is no great need to do so. Speed's insight is that using > Leo as a DB is a *whole lot* easier than doing a "real" DB. No need for > all the "abilities" (Reliability, Availability, Serviceability, > Servi

Re: Leopard: using Leo as a DB and website

On Mon, Sep 21, 2020 at 3:05 AM jkn wrote: Interesting stuff, thanks for this. I shall have to read more about the > 'Associative Model of Data'. > That might be fun. I took a quick look years ago. However, there is no great need to do so. Speed's insight is that using Le

Re: Started using leo from git -> feedback

I created an issue to remember to come back and clarify the docs on this workflow as I think it's an important one. https://github.com/leo-editor/leo-editor/issues/1460 If someone has gumption present they can do it; I'm pretty slammed these days and not spending much time on Leo ;-) -matt --

Re: Started using leo from git -> feedback

On Tuesday, December 17, 2019 at 10:10:17 PM UTC+1, Matt Wilkie wrote: > > For sharing Leo outlines, I suggest using three commands >> set-reference-file, update-ref-file and read-ref-file. >> > > Very interesting! I guess I wasn't paying attention when it came up > before. In the docs there's

Re: Started using leo from git -> feedback

> > For sharing Leo outlines, I suggest using three commands > set-reference-file, update-ref-file and read-ref-file. > Very interesting! I guess I wasn't paying attention when it came up before. In the docs there's a bit in the FAQ about this feature (https://leoeditor.com/FAQ.html#how-can-i-

Re: Started using leo from git -> feedback

On Sun, Dec 15, 2019 at 1:26 AM Satheesh Vattekkat wrote: >1. This is brilliant. Bunch of my myLeoSettings.leo stuff is no longer >needed with dockable panes for body and outline; and it remembers setting >too. Plus, the default look is very nice > > Glad you like it. > >1. Went

Started using leo from git -> feedback

I had some really old version of leo - I believe it was 5.x and was installed 1.5 years ago. I use Leo for collecting thoughts, writing down stuff, structuring a talk etc. Decided to get out of comfort zone and cloned git repo and dailly git pull and started using that. 1. This is brillian

Re: Who should be using Leo

Sure, you are welcome to use this. Sadly I have not been able to convince any of my co-workers to use Leo themselves, although they were impressed by some of the tasks I was able to do with Leo. I guess most people stick with the tools they already know and rarely try something new, especially w

Re: Who should be using Leo

On Wed, Jan 30, 2019 at 8:39 AM Josef wrote: > > Much has already been said, but I want to add anyway my view. > > I am a manager, physicist and perhaps an electrical engineer. I use several > different editors all the time, for different reasons, like vim and scite > sometime emacs. I use Leo

Re: Who should be using Leo

Oh - I forgot to mention, I use clones, but rarely, mostly because many of my leaf nodes are small, separate files. -- 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 email t

Re: Who should be using Leo

Much has already been said, but I want to add anyway my view. I am a manager, physicist and perhaps an electrical engineer. I use serveral differnt editors all the time, for different reasons, like vim and scite sometime emacs. I use Leo on complex projects, involving many files. I have small

Re: Who should be using Leo

Gérard, much of what you say I could have said as well. I saw a video recently where the speaker asked a question about which software tool the audience 'lived in'. I practically 'live in' Leo as I do almost all of my writing and most of my PIM stuff (except calendar and email). I use only a fr

Re: Who should be using Leo

gt; > So if you *aren't* a programmer, and you *don't* use clones, then why, > exactly, are you using Leo? You would be much better off with TheBrain > <https://www.thebrain.com/support/tutorials>. Really. > > Edward > > P.S. Imo, all programmers should

Re: Who should be using Leo

t. Neither rocket nor sports car come with instructions. But we have all the tools. Which is a long winded way of saying that I have been through the same problems. Perhaps we should start a series of focused tutorials that walk users through common information management tasks using Leo. Star

Re: Who should be using Leo

> > LEO: Love it lots, but hate not loving it enough to understand it fully. > Gérard, merci pour votre histoire honnête (thank you for the honest story) of your life with Leo. It mirrors parts of my own, especially the ongoing struggle with not knowing how to really embrace it and make it par

Re: Who should be using Leo

LEO: I love it as much as I hate it. Several years ago, I stumbled onto LEO and a screen cast that explained how to break down a complex HTML document into nodes that contained each component of the page (head, body, etc.) and further break down JS code into functions in each node, CCS stateme

Re: Who should be using Leo

> > I am not yet using leo, just trying to understand it at this time. I > program almost always in python. I wonder if leo is useful for literate > python programming? If so, how is this done? > I read about Leo and lurked on the mailing list a long time before using it in

Re: Who should be using Leo

I am not yet using leo, just trying to understand it at this time. I program almost always in python. I wonder if leo is useful for literate python programming? If so, how is this done? Neal On Sun, Jan 27, 2019 at 10:25 PM huliuhe wrote: > I 'm programer, I use leo to write do

Re: Who should be using Leo

mmers use clones to organize data. > > So if you *aren't* a programmer, and you *don't* use clones, then why, > exactly, are you using Leo? You would be much better off with TheBrain > <https://www.thebrain.com/support/tutorials>. Really. > > Edward > > P.S

Re: ***SPAM*** Re: Who should be using Leo

On 24/1/19 11:46, Edward K. Ream wrote: > On Thu, Jan 24, 2019 at 10:14 AM Offray Vladimir Luna Cárdenas > mailto:off...@riseup.net>> wrote: > > > Now that Leo is "done" and the playful dimension of the project is > resurfacing I wonder the travels to come for this community and its > members with

Re: Who should be using Leo

On Thu, Jan 24, 2019 at 10:14 AM Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > Now that Leo is "done" and the playful dimension of the project is resurfacing I wonder the travels to come for this community and its members with this tool. This is the question I'll be playing with on

Re: Who should be using Leo

> It seems to be a common theme that a fair number of us started using > Leo for its info management features and grew into coding later. (You, > Chris George, and myself come to mind immediately. I'm sure I'm > forgetting and don't know of others.) > > Matt Thanks M

Re: Who should be using Leo

> > But Leo legacy goes beyond code and this community makes a living part of > it. > Thank you for sharing the outline of your journey Offray. It's so interesting to see where people's explorations take them. It seems to be a common theme that a fair number of us started

Re: Who should be using Leo

Hi, On 17/1/19 13:13, Edward K. Ream wrote: > There are two main reasons to use Leo: > > 1. Programmers use Leo's API to write powerful scripts. > > 2. Non programmers use clones to organize data. > > So if you /aren't/ a programmer, and you /don't/ use clones

Re: Who should be using Leo

On 17/1/19 18:03, john lunzer wrote: > > Leo is a king here. emacs with outshine and ivy can give you cheap > imitation of what Leo offers. Obviously there is pharo+grafoscopio but > my work culture can't tolerate that level of unorthodoxy, it could > barely handle Leo. :-) Je, je. Yes Leo bri

Re: Who should be using Leo

> Hummm, by my chaos cnglish > Zoom.Quiet I love your chaotic cnglish. The familiar words in unfamiliar combinations reveals meanings that were always there, but out of sight. Your insight that "easy to record" is not the same at all of "easy to share with understanding" is pure gold.

Re: Who should be using Leo

El 20/01/2019 a las 1:41, rengel escribió: I'm not an evangelist for TheBrain, but just tried to point to a tool that might be useful to others... And I thank you for that, Reinhard! I didn't know TheBrain until you mentioned and I like some of its features. My contribution did not pretend t

Re: Who should be using Leo

On Saturday, January 19, 2019 at 6:46:32 PM UTC+1, Xavier G. Domingo (xgid) wrote: > > I'm a programmer, but are not yet using powerful scripts (although it's on > my plans), so I don't qualify for the first reason yet. > > I don't think TheBrain can compete with those... > > You are right, The

Re: Who should be using Leo

/01/2019 a las 15:13, Edward K. Ream escribió: There are two main reasons to use Leo: 1. Programmers use Leo's API to write powerful scripts. 2. Non programmers use clones to organize data. So if you /aren't/ a programmer, and you /don't/ use clones, then why, exactly, are you u

Re: Who should be using Leo

On Saturday, January 19, 2019 at 12:55:27 PM UTC+1, Edward K. Ream wrote: ... > I suspect that TheBrain is based on a DAG, but I do not know for sure. > > Definitely not. You can construct circles like: PARENT1 -> CHILD -> GRANDCHILD -> PARENT1 (closing the circle) Although there is a single

Re: Who should be using Leo

On Sat, Jan 19, 2019 at 1:11 AM rengel wrote: > Those who *do *use TheBrain need not justify their choice :-) Well said! But that's not what I tried to communicate. I just wanted to > clarify that the whole idea of clones is alien to TheBrain, because it's > basically a network and not a tree/da

Re: Who should be using Leo

On Friday, January 18, 2019 at 5:45:13 PM UTC+1, Edward K. Ream wrote: > > On Fri, Jan 18, 2019 at 7:42 AM rengel > wrote: > > If you *aren't* a programmer and use TheBrain *you don't need clones*, >> because an entry/item in TheBrain can have any number of parents without >> the need of cloni

Re: Who should be using Leo

On Fri, Jan 18, 2019 at 7:42 AM rengel wrote: If you *aren't* a programmer and use TheBrain *you don't need clones*, > because an entry/item in TheBrain can have any number of parents without > the need of cloning. One entry (=node) without copies or pointers suffices. > Those who *do *use TheBr

Re: Who should be using Leo

On Thursday, January 17, 2019 at 7:13:21 PM UTC+1, Edward K. Ream wrote: > > > So if you *aren't* a programmer, and you *don't* use clones, then why, > exactly, are you using Leo? You would be much better off with TheBrain > <https://www.thebrain.com/support/tut

Re: Who should be using Leo

d you don't use clones, then why, >> > exactly, are you using Leo? You would be much better off with TheBrain. >> > Really. >> > >> >> No No No No*42 > > > Hehe. It seems that you and Joe Orr agree. >> >> TheBrain-style https://www.

Re: Who should be using Leo

On Fri, Jan 18, 2019 at 5:59 AM Israel Hands wrote: Hi Edward - I don't think I'm in the target audience, at all! > Heh. I was hardly expecting all these comments. They have been eye opening. I mostly use Leo to organise things. > Passwords, account settings etc. > > But then I want to also de

Re: Who should be using Leo

On Thu, Jan 17, 2019 at 8:24 PM Zoom.Quiet wrote: and the true power reason: > 0: programmers use Leo develop and manage projects > Good point. I agree. > So if you aren't a programmer, and you don't use clones, then why, > exactly, are you using Leo? You would be much be

Re: Who should be using Leo

> > 1. Programmers use Leo's API to write powerful scripts. > > 2. Non programmers use clones to organize data. > > So if you *aren't* a programmer, and you *don't* use clones, then why, > exactly, are you using Leo? You would be much better off with TheBrain >

Re: Who should be using Leo

> > So if you aren't a programmer, and you don't use clones, then why, exactly, > are you using Leo? You would be much better off with TheBrain. Really. > No No No No*42 TheBrain-style https://www.thebrain.com/support/tutorials tools just result the fake problem for record

Re: Who should be using Leo

On Thu, Jan 17, 2019 at 5:03 PM john lunzer wrote: > I would add: you are a programmer that desires powerful code/project > organization tools. > > I'm not sure what brought me to Leo, but I stayed because I could divide > up my code into language agnostic chunks that made sense to me, no longer

Re: Who should be using Leo

:13:21 PM UTC-5, Edward K. Ream wrote: > > There are two main reasons to use Leo: > > 1. Programmers use Leo's API to write powerful scripts. > > 2. Non programmers use clones to organize data. > > So if you *aren't* a programmer, and you *don't* use clones, then

Re: Who should be using Leo

On Thu, Jan 17, 2019 at 1:29 PM Chris George wrote: > I am not a programmer...Clones are the bomb when it comes to organizing long, intricate documents. So you qualify :-) You *aren't* a programmer but you *do* use clones. Edward -- You received this message because you are subscribed to the

Re: Who should be using Leo

don't* use clones, then why, > exactly, are you using Leo? You would be much better off with TheBrain > <https://www.thebrain.com/support/tutorials>. Really. > > Edward > > P.S. Imo, all programmers should use clones, but that's a matter of the > next posting.

Who should be using Leo

There are two main reasons to use Leo: 1. Programmers use Leo's API to write powerful scripts. 2. Non programmers use clones to organize data. So if you *aren't* a programmer, and you *don't* use clones, then why, exactly, are you using Leo? You would be much better off with T

Re: seeking guidance on using Leo collaboratively with Git

On Mon, Aug 27, 2018 at 2:50 PM Terry Brown wrote: > On Mon, 27 Aug 2018 10:55:13 -0700 (PDT) > Phil wrote: > > > > I'd do something like this: > All excellent advice. The local .leo file need not ever be in sync. Being able to add new files from the plugin or a button makes a lot of sense. E

Re: seeking guidance on using Leo collaboratively with Git

018 at 10:19 AM Phil > > wrote: > > > >> I am currently collaborating on a project with one other person, > >> using Leo and Git. In addition to committing derived files to Git, > >> we have also been committing the Leo file itself. We have had some > >> occasi

Re: seeking guidance on using Leo collaboratively with Git

On Mon, Aug 27, 2018 at 12:55 PM Phil wrote: > Thanks for that, it's helpful. But the notion of a reference file begs the > question of who maintains *that* file. In my project, both my partner and > I are continually creating new content, which means that we would both need > to make changes to

Re: seeking guidance on using Leo collaboratively with Git

rote: > >> I am currently collaborating on a project with one other person, using >> Leo and Git. In addition to committing derived files to Git, we have also >> been committing the Leo file itself. We have had some occasional problems >> (a corrupted Leo file, mainly),

Re: seeking guidance on using Leo collaboratively with Git

On Mon, Aug 27, 2018 at 10:19 AM Phil wrote: > I am currently collaborating on a project with one other person, using Leo > and Git. In addition to committing derived files to Git, we have also been > committing the Leo file itself. We have had some occasional problems (a > corrup

seeking guidance on using Leo collaboratively with Git

I am currently collaborating on a project with one other person, using Leo and Git. In addition to committing derived files to Git, we have also been committing the Leo file itself. We have had some occasional problems (a corrupted Leo file, mainly), making me think that we should *not* put the

Re: First Month of Using Leo

On Mon, 20 Aug 2018 06:16:28 -0500 "Edward K. Ream" wrote: > > So far I've only really had success with simple abbreviations to > > quickly add TODO and various :tag: to Org Mode tasks. For instance, > > this one makes adding tasks a little easier to enter into a node > > header: th;;={|{x="TODO"

Re: First Month of Using Leo

On Wed, Aug 22, 2018 at 7:45 AM pds wrote: > Thanks for your detailed response. Re-writing this as a button script > makes sense as it creates the new node too. I'll study these examples and > see what else I can do. Is there a way I can explore the built in Leo > commands and see what scripts th

Re: First Month of Using Leo

Thanks for your detailed response. Re-writing this as a button script makes sense as it creates the new node too. I'll study these examples and see what else I can do. Is there a way I can explore the built in Leo commands and see what scripts they are using under the covers? I tried to use the

Re: First Month of Using Leo

On Monday, August 20, 2018 at 6:38:14 AM UTC-5, Edward K. Ream wrote: Rather than try to define a fancy abbreviation, the following (tested) > Leonine @button node works: > > @button todo > p = c.insertHeadline() > p.h = 'todo :HOME:' > c.editHeadline() > w = c.edit_widget(p) > w.setInsertPoint

Re: First Month of Using Leo

On Monday, August 20, 2018 at 6:16:30 AM UTC-5, Edward K. Ream wrote: > > On Sat, Aug 18, 2018 at 5:18 PM, pds wrote: > So far I've only really had success with simple abbreviations to quickly >> add TODO and various :tag: to Org Mode tasks. For instance, this one makes >> adding tasks a little

Re: First Month of Using Leo

On Sat, Aug 18, 2018 at 5:18 PM, pds wrote: > > I've been using Leo for just over a month, so I thought it would be good > to summarize my experiences, now, before I become a more experienced user. > Thanks for doing this. It's helpful for us all. > I wanted a tool

First Month of Using Leo

Hi, I've been using Leo for just over a month, so I thought it would be good to summarise my experiences, now, before I become a more experienced user. First of all I would like to thank this community, and in particular Edward, for creating and sustaining this unique piece of software

Re: Writing using Leo with new tree and model

Rev 4121e39 contains updated version of md_docer plugin. It now supports two new kind of nodes: - @transformer nodes - @transform-node () @transformer node define a transformer script with give

Writing using Leo with new tree and model

To test the new Leo tree in production, I have written small plugin. Actually I have just converted some scripts I've been using for writing my blog into a plugin. Recently there has been some discussion in the github issue No: 946 . I writ

Re: LaTex to PDF workflow using Leo

On Mon, Mar 12, 2018 at 5:44 PM, Arjan wrote: > Thanks, Edward! > ​You're welcome. 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 email to leo-editor+unsubscr..

Re: LaTex to PDF workflow using Leo

Thanks, 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 email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegrou

Re: LaTex to PDF workflow using Leo

On Thursday, March 8, 2018 at 10:48:28 AM UTC-6, Arjan wrote: Reviving this old topic. I made a crude attempt, hard-coded etc., to just > rewrite the section definitions via regex search and replace... > > How would I add Undo to this? Any other obvious improvements to make? > Here is a version

Re: LaTex to PDF workflow using Leo

Reviving this old topic. I made a crude attempt, hard-coded etc., to just rewrite the section definitions via regex search and replace. Works just on a single .tex file (I don't see a benefit to using multiple input files when managing things via Leo anyway), but it's still useful in my case. H

Re: Basic concepts of using Leo to organise a python program

On Tue, Nov 21, 2017 at 9:21 AM, Edward K. Ream wrote: > On Tue, Nov 21, 2017 at 5:45 AM, lewis wrote: > >> I have been searching Leo documentation for a simple guide to using Leo >> and to write python files but it seems to have disappeared or my memory is >>

Re: Basic concepts of using Leo to organise a python program

On Tue, Nov 21, 2017 at 5:45 AM, lewis wrote: > I have been searching Leo documentation for a simple guide to using Leo > and to write python files but it seems to have disappeared or my memory is > awry. > In the FAQ http://leoeditor.com/FAQ.html > "What’s the best way to l

Basic concepts of using Leo to organise a python program

I have been searching Leo documentation for a simple guide to using Leo and to write python files but it seems to have disappeared or my memory is awry. In the FAQ http://leoeditor.com/FAQ.html "What’s the best way to learn to use Leo?" at section: If you intend to use Leo for program

Re: LaTex to PDF workflow using Leo

is one single, large file. > > Most people writing large Latex documents break them down into different > chunks and then glue them together with \input. That's where the problems > start with using Leo: Leo would have to recreate the same file structure in > order to work well t

Re: LaTex to PDF workflow using Leo

Most people writing large Latex documents break them down into different chunks and then glue them together with \input. That's where the problems start with using Leo: Leo would have to recreate the same file structure in order to work well together with others, but that would mean

Re: LaTex to PDF workflow using Leo

On Wed, Apr 12, 2017 at 12:10 AM, Largo84 wrote: > Hmm, not sure how that would work. It might be relatively easy to invoke > such a script when setting up the node at first, but what happens if/when > you decide to move the node and its level changes? > ​The situation is much like the rst3 comm

Re: LaTex to PDF workflow using Leo

Hmm, not sure how that would work. It might be relatively easy to invoke such a script when setting up the node at first, but what happens if/when you decide to move the node and its level changes? What would be really useful would be a way to traverse the hierarchy after it's written and ready

Re: LaTex to PDF workflow using Leo

On Tue, Apr 11, 2017 at 8:46 AM, Arjan wrote: > > I'm using Leo to organize sections like \chapter, \section and > \subsection. Since I'm just writing latex in Leo, I need to keep track of > the right hierarchies, so I can't freely move nodes around in the h

Re: LaTex to PDF workflow using Leo

yesterday you will see how I implement that strategy. HTH Rob... > > I'm using Leo to organize sections like \chapter, \section and > \subsection. Since I'm just writing latex in Leo, I need to keep track of > the right hierarchies, so I can't freely move nodes a

Re: LaTex to PDF workflow using Leo

processing schemes, but I wasn't sure how to use those. I'm using Leo to organize sections like \chapter, \section and \subsection. Since I'm just writing latex in Leo, I need to keep track of the right hierarchies, so I can't freely move nodes around in the hierarchy or I e

Re: LaTex to PDF workflow using Leo

Thanks Rob - I've had a quick look and there's a lot there to get my head round - thanks for sharing it. The manual processing is the same in Scrivener which will compile to a Latex file but then I load that into TexStudio for processing and previewing. I haven't used @outline-data tree-abbrev

Re: LaTex to PDF workflow using Leo

No, I run processing (typesetting) in TeXNicCenter manually. Typically, I create a blank project file and open however many files required for that project. That way it's easier to clean up the extra files created during the process steps. HTH. There might be a way to invoke the LaTex commands

Re: LaTex to PDF workflow using Leo

Thanks Rob - will have a look at the example tomorrow. Can you control TexNicCenter from Leo - or do you process the file and preview process manually? Ta IH On Monday, April 10, 2017 at 6:29:26 PM UTC+1, Largo84 wrote: > > Just posted a Leo file with examples on GitHub here >

Re: LaTex to PDF workflow using Leo

Just posted a Leo file with examples on GitHub here . Regards, > Rob > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

LaTex to PDF workflow using Leo

In another post , Israel Hands asked about a straightforward Leo workflow to use LaTex to get PDF final output. So, here is mine for whatever it's worth. Readers will decide for themselves how 'straightforward' it is; it works

  1   2   3   >