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

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.

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 *

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

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

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.

Re: LaTex to PDF workflow using Leo

Josef, I work with large LaTex files also and have for several years; almost all of which contain multiple \input files. My system may not work for you, but it works well for me. A few things to note about my system: 1. My master document outline is a shell only (no actual content). It

Re: LaTex to PDF workflow using Leo

Hello Edward, much of my work involves editing LaTeX files, but I do have to work together with others. I tried Leo's @shadow and @thin nodes, for minimal interference, with mixed success. The main problem is the way Latex uses multi-file input. As you may remember, the way the rst plugin

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

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

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 hierarchy > or I

Re: LaTex to PDF workflow using Leo

Thanks, Arjan for the compile code, will have to try it out on my system. I had a similar experience, sometimes finding that I had Leo's node structure out of sync with LaTex structure tags. I sort of solved that by putting all content in separate input files (I use .txi as an extension to

Re: LaTex to PDF workflow using Leo

Thanks, interesting to see what people are using for LaTeX. I'll describe my process, I'd be happy to hear about improvements. This is all just hardcoded and hacked together, as I currently work on just one LaTeX project. I believe there are older threads which discuss more elaborate processing

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

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

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