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: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 3:40:38 PM UTC-5, Edward K. Ream wrote: > HTH. We'll get to the bottom of this. And be sure to verify that your tool chain is actually updating the files you think it is. The symptom that you must reload Leo to see changed files is quite strange. It argues that

Re: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 3:34:35 PM UTC-5, Edward K. Ream wrote: As I noted in #472 , > everything works for me on Windows. So this is the typical long-distance > debugging mystery. Here are my suggestions. > And here are a few more:

Re: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 3:34:35 PM UTC-5, Edward K. Ream wrote: > > On Tuesday, April 11, 2017 at 10:36:30 AM UTC-5, Edward K. Ream wrote: > > > I'll attempt a fix later today. > > As I noted in #472 , > everything works for me on

Re: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 10:36:30 AM UTC-5, Edward K. Ream wrote: > I'll attempt a fix later today. As I noted in #472 , everything works for me on Windows. So this is the typical long-distance debugging mystery. Here are my

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: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 5:08:58 AM UTC-5, Edward K. Ream wrote: > Please file a bug report here Never mind. I just created #472

Re: ENB: 20 years of lint removed from leoAtFile.py

Looking forward to it! On Mon, Apr 10, 2017 at 4:04 PM, Edward K. Ream wrote: > > 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

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: #385: problems when switching git branches

On Tuesday, April 11, 2017 at 5:57:04 AM UTC-5, Edward K. Ream wrote: > There is a better workaround, namely, use a separate local leoPy.leo for each branch: [big snip] > I'll be using (testing) this today. All went very well, without any surprises at all. This workaround is probably good

Important: c9a2db7 merges the js branch. It contains new read/write code

Leo's master branch now contains the new, simpler, code that reads and writes external files. This code appears safe and solid. It passes all tests, including new ones. This is a major change in Leo. Please report any problem immediately. Imo, these changes had to be made. Some were needed

Re: #385: problems when switching git branches

On Tuesday, April 11, 2017 at 5:57:04 AM UTC-5, Edward K. Ream wrote: > > > There is a better workaround, namely, use a separate local leoPy.leo for > each branch: > > - Create a directory, *not tracked by git*, to hold the copies, say > ~/LeoPy-Copies. This is the *copies folder*. > The data

Re: #385: problems when switching git branches

On Saturday, April 8, 2017 at 11:29:37 PM UTC-5, Edward K. Ream wrote: ..it is difficult to switch between branches in such a way that > Ctrl+Shift+W, write-at-file-nodes, doesn't change files when the branch > changes outline structure. > There is a better workaround, namely, use a separate

Re: leo-editor-contrib on GitHub

On Mon, Apr 10, 2017 at 10:25 AM, Terry Brown wrote: I've been using this repo. https://github.com/leo-editor/snippets > > which (I think) I created because GitHub Organizations (like > ​ ​ > leo-editor) can't have GitHub Gists. ​The "Code Snippets" link​ ​at the left

Re: @clean nodes stopped updating

On Tue, Apr 11, 2017 at 4:59 AM, Joe Orr wrote: > I tried rolling back to the commit before b7638799d6, no luck. > > In fact, now it is worse, when I make a change in Webstorm and then go to > Leo, not only is there no warning, any changes I then make via Leo clobber > the

Re: @clean nodes stopped updating

I tried rolling back to the commit before b7638799d6, no luck. In fact, now it is worse, when I make a change in Webstorm and then go to Leo, not only is there no warning, any changes I then make via Leo clobber the Webstorm file with no warning. And it is still doing this after I reset to the

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