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: ENB: 20 years of lint removed from leoAtFile.py

On Mon, Apr 10, 2017 at 12:38 PM, Edward K. Ream wrote: *tl;dr:* Many switches in methods of the AtFile class were confusing or > unnecessary. The new code is now as simple as I can make it. Afaik, there > are no more "huh?"s left. > ​To repeat something I've said several times recently, this

ENB: 20 years of lint removed from leoAtFile.py

This is an engineering notebook post. It will be of interest primarily to devs. The js branch contains the new code. I created this branch to fix bugs in the javascript importer, but the changes needed quickly resulted in the massive housekeeping I am about to describe. This housekeeping was

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

Re: leo-editor-contrib on GitHub

On Mon, 10 Apr 2017 07:29:36 -0700 (PDT) Largo84 wrote: > Would it be appropriate to add example .leo files to this repo > (such as my > Leo->LaTex->PDF workflow examples or lists of abbreviations)? There > isn't any recent activity and I wasn'

leo-editor-contrib on GitHub

Would it be appropriate to add example .leo files to this repo (such as my Leo->LaTex->PDF workflow examples or lists of abbreviations)? There isn't any recent activity and I wasn't sure it is still considered active and/or relevant. If so, whe

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

Re: Ideas for writing for Word (or similar)

Thanks for the suggestion, Israel. I looked at Scrivener in the past and it is a very powerful program with a great feature set (may take another look for this project). However, it's not Leo. I will post my Leo->LaTEx->PDF workflow in a separate post. Rob... On Monday, April 10, 2017 at 7

Re: Copying and pasting subtrees with cloned child nodes

Thanks, Edward. I have tried using paste-retaining-clones (from the minibuffer, since I wasn't able to find it in any menu), but then all nodes in the copied subtrees are pasted as clones, not just the ones that where clones already. Perhaps I am doing this wrong? In the attached pic, only the

Re: Copying and pasting subtrees with cloned child nodes

On Mon, Apr 10, 2017 at 6:21 AM, alacnorr wrote: > > I assume (perhaps incorrectly?) that subtrees containing clones among > their child nodes, once copied and pasted, should retain these child nodes > as clones; instead, clones are transformed into regular nodes that can be > modified independen

Re: simple script query

On Mon, Apr 10, 2017 at 5:23 AM, lewis wrote: > The script below works in both Leo's python console and IDLE. But doesn't > execute with Ctrl-B or with script-button; I don't get any errors to log, > or output to console. > > import os > os.listdir(path="C:/Users/") > > Can anyone explain why? >

Copying and pasting subtrees with cloned child nodes

Hello, I'm a not sure this is a bug or normal Leo behavior so I am asking here rather than reporting it as an issue on GitHub. I assume (perhaps incorrectly?) that subtrees containing clones among their child nodes, once copied and pasted, should retain these child nodes as clones; instead, clo

Re: Ideas for writing for Word (or similar)

Hi Largo, Apologies for being a bit off topic but have a look at Scrivener which uses rtf files but can compile to .doc and .docx (though I have never used these). Scrivener is excellent for a master document with multiple sub documents - allowing great flexibility. That is exactly what Scriven

simple script query

The script below works in both Leo's python console and IDLE. But doesn't execute with Ctrl-B or with script-button; I don't get any errors to log, or output to console. import os os.listdir(path="C:/Users/") Can anyone explain why? *Leo 5.5, Git repo info: branch = master, commit = 7280e1fa