Re: Nodetags plugin errors

[Largo84]

I can't located that commit. It doesn't show up in master. Is this related 
to issue #526 <https://github.com/leo-editor/leo-editor/issues/526>?

Rob...

On Saturday, March 24, 2018 at 2:35:56 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Fri, Mar 23, 2018 at 2:13 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> Now, I'm also getting a slightly different error in other files when I 
>> copy/paste nodes.
>>
>
> ​Rev​
>  1f40d97 adds a guard.  How does that work for you?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Nodetags plugin errors

[Largo84]

I'm only pulling from the master branch and the last commit was March 3, 
6c2eef2. Where is that rev?

Rob...

On Saturday, March 24, 2018 at 2:35:56 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Fri, Mar 23, 2018 at 2:13 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> Now, I'm also getting a slightly different error in other files when I 
>> copy/paste nodes.
>>
>
> ​Rev​
>  1f40d97 adds a guard.  How does that work for you?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Nodetags plugin errors

[Largo84]

Now, I'm also getting a slightly different error in other files when I 
copy/paste nodes.

hook failed: command2, >, 
leo.plugins.nodetags
Traceback (most recent call last):

  File "D:\Synced\github repos\leo\leo\core\leoPlugins.py", line 342, in 
callTagHandler
result = handler(tag, keywords)

  File "D:\Synced\github repos\leo\leo\plugins\nodetags.py", line 437, in 
command2_hook
self.update_all()

  File "D:\Synced\github repos\leo\leo\plugins\nodetags.py", line 412, in 
update_all
self.update_list()

  File "D:\Synced\github repos\leo\leo\plugins\nodetags.py", line 394, in 
update_list
n = gnxDict[gnx]

KeyError: 'largo84.20180323121353.1'

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Use Leo as database

[Largo84]

In Leo's online documentation for Advanced Topics>>The Leonine World 
, I am intrigued by the last topic:

*Databases*: Leo’s clones create new opportunities for scriptable 
databases. In my brother Speed’s outlines, suboutlines *are* SQL queries!

I would like to know more about how that is done. Are there any sample 
database.leo files that demonstrate that use case?

   - Are tables represented by external files? If so, what format?
   - Are nodes individual records?
   - How are attributes (fields) stored? YAML? Other?

Rob...


-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Nodetags plugin errors

[Largo84]

Getting the following errors when re-opening a file with nodes tagged using 
the nodetags plugin:

hook failed: after-create-leo-frame, , 
leo.plugins.nodetags
Traceback (most recent call last):

  File "D:\Synced\github repos\leo\leo\core\leoPlugins.py", line 342, in 
callTagHandler
result = handler(tag, keywords)

  File "D:\Synced\github repos\leo\leo\plugins\nodetags.py", line 122, in 
onCreate
theTagController = TagController(c)

  File "D:\Synced\github repos\leo\leo\plugins\nodetags.py", line 138, in 
__init__
self.ui.update_all()

  File "D:\Synced\github repos\leo\leo\plugins\nodetags.py", line 412, in 
update_all
self.update_list()

  File "D:\Synced\github repos\leo\leo\plugins\nodetags.py", line 394, in 
update_list
n = gnxDict[gnx]

KeyError: 'largo84.20180323113211.1'

There is a @persistence node to store this information as many of these 
nodes are in @auto-md external files. Running the cft command suggests that 
the nodes are indeed tagged. However, the nodes no longer show up in the 
Tags list window. In case it matters, my environment:

Leo 5.8 devel, build 20180303100141, Sat Mar  3 10:01:41 CST 2018
Git repo info: branch = master, commit = 6c2eef28ef1e
Python 3.4.3, PyQt version 5.4.1
Windows 8 AMD64 (build 6.2.9200) 
isPython3: True
caching enabled

Anyone else seeing this? Shall I file a issue on GitHub?

Rob

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Leo's active to-do lists

[Largo84]

Not exactly a core Leo thing, but fix the web site internal search (still 
broken). Referenced in this post in December 
. 
Shall I file an issue on GitHub?

Rob...

On Tuesday, March 6, 2018 at 6:06:46 AM UTC-5, Edward K. Ream wrote:
>
> We have added lots of new items recently.  This post clarifies the 
> priorities.
>
> *Priority 1*: 16 items with 5.7.1 milestone 
> 
> .
>
> Only these items have any real expectation of being done "soon".
>
> *Priority 2*: All other items, including:
>
> - 21 items with 5.8 milestone 
> 
> .
> - 80+ items with no milestone 
> 
> .
>
> The next "real" milestone will probably be 5.7.2.
>
> Please let me know if you think an item should get higher priority.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: I love Leo, but... Scrivener and Org-Mode

[Largo84]

Wow, reading Israel's post made me me think I wrote it (except the org-mode 
part). Probably 80+% of my work in Leo is writing content w/ LaTEX output. 
Most of the rest is variations of markdown and RST. I tried moving my work 
to Scrivener and really like it a lot. However, I like Leo better (plus 
it's free and open source) and once I figured out how to link to external 
resources, I never went back to Scrivener. I don't like using LaTEX content 
auto-generated from something else. I end up spending too much time 
cleaning it up. For what it's worth, my work flow with LaTEX content is:

   1. I mostly write content directly in LaTEX syntax (it's cleaner and 
   easier to edit directly). I created many Leo abbreviations to speed up the 
   process (lists, sections, etc.)
   2. I wrote several outline-data-tree abbreviations to create 'wrapper' 
   shells for different kinds of documents (preambles, etc). Then I simply 
   input the LaTEX content files (\input{content.tex}}.
   3. Since I'm mostly on Windows, I use the excellent TeXnic Center 
    compiler to create the PDF output. (I 
   never use it to edit, only to compile.)
   4. Rarely, if I need to export to something else (xxx.docx or xxx.rtf or 
   xxx.html), I write in multi-markdown and use Pandoc to output.

Excellent post and I'd love to share ideas with other Leo/LaTEX users on 
work flow. Perhaps I can steal a few better ideas or trade for some of my 
own.

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: VBA language

[Largo84]

Perfect, thanks!

Rob...

On Thursday, February 22, 2018 at 10:49:08 PM UTC-5, Terry Brown wrote:
>
> On Thu, 22 Feb 2018 19:12:48 -0800 (PST) 
> Largo84 <lar...@gmail.com > wrote: 
>
> > Doing a little work in Microsoft VBA ('cuz I have to, not 'cuz I want 
> > to). Is there an @language directive already set up for that type of 
> > code? I tried vba and basic, but neither worked. 
> > 
> > Rob... 
>
> vbscript 
>
> not sure if it's relevant or not 
>
> Cheers -Terry 
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

VBA language

[Largo84]

Doing a little work in Microsoft VBA ('cuz I have to, not 'cuz I want to). 
Is there an @language directive already set up for that type of code? I 
tried vba and basic, but neither worked.

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How did I came across Leo?

[Largo84]

I found Leo when I was looking for a replacement for ECCO (anyone remember 
that program?) I used ECCO for 15 years after it wasn't supported anymore 
and the core group of diehard users finally lost hope the program owners 
would open source the code.

Anyway, I don't remember how long ago that was; at least 10 years ago, as I 
recall. In most respects, Leo is a *major* improvement over ECCO and I 
don't regret the switch. However, the one thing I still miss about ECCO and 
wish there was a good Leo integration is the calendar. ECCO could print 
almost any kind of calendar, in practically any format on any size. I 
really miss that. There's no other PIM on the market that I know of that 
has that kind of flexibility.

Perhaps other Leo users figured out how to integrate their calendar(s) with 
Leo; I haven't and would love to know how (if it's possible).

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: A Recent Article by Me

[Largo84]

Chris, that's a great article! Much of that mirrors how I use and benefit 
from Leo. I do some HTML and CSS stuff, but 90+% of my time in Leo is 
either writing in LaTEX or Markdown. Good stuff!

Rob...

On Thursday, February 15, 2018 at 2:50:11 PM UTC-5, Chris George wrote:
>
> https://refiction.com/resource-reviews/leo-editor-for-writers
>
> The constraint was 650 words, no images.
>
> Hopefully this will bring a few more writers to Leo.
>
> Chris
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Anaconda and Leo

[Largo84]

Yes, got it, thanks for clarifying. That's kinda what I thought, but wasn't 
sure.

Rob...

On Tuesday, February 13, 2018 at 3:30:03 AM UTC-5, Edward K. Ream wrote:
>
>
>
> On Mon, Feb 12, 2018 at 8:44 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> So, is there an Anaconda update command that will pull in a more recent 
>> 'official' release?
>>
>
> ​`conda update leo` should do this.  However, what you are calling the 
> latest "official" release is the latest Anaconda package for Leo.  This has 
> nothing whatever to do with the latest git rev.  Clear?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Anaconda and Leo

[Largo84]

So, is there an Anaconda update command that will pull in a more recent 
'official' release? Or, is her machine stuck with whichever version was 
installed initially? Or would I need to manually update her Leo package in 
Anaconda whenever I think it's advantageous to do so?

Rob...
 

>
>>1. On my own machine, I always run Leo from a GitHub directory so I 
>>can run the most current version. What about on her machine? How does 
>>Anaconda work to keep Leo updated?
>>
>> ​It doesn't.  If you install Leo from Anaconda you are using the last 
> version of Leo that Anaconda knows about, not the latest github version.  
> So if you are using git to keep Leo up to date (as you should ;-) you 
> should *not* install Leo using Anaconda.​
>
> HTH
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Anaconda and Leo

[Largo84]

I recently had to reinstall Leo on my assistant's PC after a computer 
upgrade. I was sorta dreading the experience, but found that the Anaconda 
route was actually pretty easy. However, I have a documentation comment and 
a question:

   1. Following the instructions, I tried the pip install leo command in 
   the Anaconda console, but got a permissions error. I had to run the Console 
   command as an Administrator (right-cick and select). Perhaps that should be 
   added to the Leo docs as it may not be obvious to others (it wasn't to me 
   at first)?
   2. On my own machine, I always run Leo from a GitHub directory so I can 
   run the most current version. What about on her machine? How does Anaconda 
   work to keep Leo updated?

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Searching on LeoEditor site is broken

[Largo84]

No. As Chris George mentioned, searching from within the documentation does 
not work.

Rob...

On Monday, December 18, 2017 at 7:07:25 AM UTC-5, Edward K. Ream wrote:
>
>
>
> On Fri, Dec 8, 2017 at 7:47 AM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> Try doing a search for any topic on Leo's main web site and you will 
>> likely get something like this (searched for 'mark'):
>>
>
> ​It looks like this is working now.  Is it working for you?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Searching on LeoEditor site is broken

[Largo84]

Try doing a search for any topic on Leo's main web site and you will likely 
get something like this (searched for 'mark'):



-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: @outline-data tree-abbreviations stopped working

[Largo84]

Thanks for your reply, Edward. Maybe I'll submit an enhancement request to 
allow multiple instances. It's not an urgent issue, but nice to know what 
caused the apparent failure.

Rob..

On Friday, September 8, 2017 at 4:15:43 PM UTC-4, Edward K. Ream wrote:
>
>
> ​I suppose you could call it an accident of the implementation, but tree 
> abbrevs are significantly more difficult to implement, so the "accident" 
> isn't too surprising.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: @outline-data tree-abbreviations stopped working

[Largo84]

The problem was that I also had a @outline-data tree-abbreviations node in 
the file's @settings tree. Apparently, that disables anything from the 
myLeoSettings.leo file. This raises another question; the other 
abbreviation settings can have gobal and local abbreviations, but 
@outline-data tree-abbreviations cannot. Is there a design reason for the 
limitation?

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

@outline-data tree-abbreviations stopped working

[Largo84]

I have many abbreviations using @outline-data tree-abbreviations and they 
worked fine yesterday. None work today after updating Leo from GitHub. 
Ideas? Or shall I file a bug report?

Rob

PS The abbreviations listed in @data global-abbreviations and @data 
abbreviations appear to work as expected.

Leo Log Window
Leo 5.5, build 20170908112958, Fri Sep  8 11:29:58 CDT 2017
Git repo info: branch = master, commit = 03e42a390862
Python 3.4.3, PyQt version 5.4.1
Windows 8 AMD64 (build 6.2.9200) 
isPython3: True
caching enabled

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Tags, uA's and @persistence

[Largo84]

Done here .

Rob...

On Thursday, July 13, 2017 at 6:16:06 AM UTC-4, Edward K. Ream wrote:
>
>
>  
> ​Not if create-at-persistence-nodes-automatically is True.
>
> Please file a bug report.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Tags, uA's and @persistence

[Largo84]

I have that as well as bool-enable-persistence set to True in 
myLeoSettings.leo; shouldn't that override?

Rob..

On Wednesday, July 12, 2017 at 10:22:40 AM UTC-4, Edward K. Ream wrote:
>
> On Wed, Jul 12, 2017 at 8:50 AM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> There was some discussion about this topic a while back here 
>> <https://groups.google.com/d/msg/leo-editor/vSlFHEbJqHc/S1ICGyv2538J> and 
>> I thought I understood that if I add tags  (uA's) to nodes in @auto-xxx 
>> files, they are somehow preserved in the @persistence tree. That doesn't 
>> appear to be the case. 
>>
>
> ​The default in leoSettings.leo is:
>
> bool create-at-persistence-nodes-automatically = False
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Tags, uA's and @persistence

[Largo84]

There was some discussion about this topic a while back here 
 and I 
thought I understood that if I add tags  (uA's) to nodes in @auto-xxx 
files, they are somehow preserved in the @persistence tree. That doesn't 
appear to be the case. My @persistence tree appears to have some 
information stored referencing the GNX's and the uA's, but it's just a 
series of random-seeming numbers which might make sense internally, but not 
to a human reader. After closing and reopening the .leo file, none of the 
tags are associated to their respective nodes. Am I missing a step 
somewhere?

Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

trace_idle_focus in log pane

[Largo84]

On only one of systems I see the following long list in the log pane 
(abbreviated text, it's actually much longer):

trace_idle_focus 19 no focus
trace_idle_focus 19 no focus
trace_idle_focus 19 no focus
...
trace_idle_focus 19 no focus
trace_idle_focus 19 no focus
trace_idle_focus 20 no focus
...

This suggests a few questions:

   1. Is there a setting in myLeoSettings.leo that is different from my 
   other systems?
   2. If so, which setting is it and what is the recommended setting and 
   should I change it? (A nav search for trace_idle_focus came up with 0 hits.)
   3. It doesn't appear to do anything harmful, but it makes me wonder what 
   is the purpose of the message?
   4. Anyone else seeing this?

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

>
>
> I think a descriptive text would be good.  There's a cheap way to do 
> it, and a more complicated way. 
>
> Cheap 
>
> http://www.example.com/##For example 
>
> just decide that anything following a double hash in the URL is the 
> descriptive string.  This could be pointed out by the popup into which 
> URLs are entered.  It would display as 
>
> For example http://www.example.com/ 
>
> To change an URL or it's description, you'd have to delete and replace, 
> when you click a link it appears in the Log pane, so you can copy from 
> there if you're replacing something existing. 
>
> Complicated 
>
> Store URL and description separately and add UI for editing. 
>
> Kind of think if you're comfortable with getting UNLs (text) from other 
> files, the ## way is probably sufficient. 
>

I think the 'cheap' way should work fine.
 

>
> So I could do that and remove any attempt to guess the most informative 
> part of the URL (what it does now with basename @ full url) and leave 
> descriptions up to the user. 
>
> I think though when it automatically creates the reverse link in the 
> target file, it should use the node name in the source file as the 
> descriptive text for the reverse link. 
>
> Sound reasonable? 
>
> Yes, that works for me.

Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

Hmm, didn't think about what it would look like in small screen mode. I 
usually run maximized. Just wondering about possibilities, would it be 
useful (and doable) to ask for descriptive text in addition to the URL when 
creating the link? I envision for some node that might have multiple links 
that would be very helpful. Don't want to over complicate it, as it's a 
really cool new feature as it is.

Rob.

On Monday, June 19, 2017 at 5:26:45 PM UTC-4, Terry Brown wrote:
>
>
> Sure, I usually run backlinks in a small window and thought it would be 
> easier to see: 
>
> Manfrotto.html @ https://www.bhp 
> Nikon_D70.html @ https://www.bhp 
> Canon_A600_SLR.html @ https://ww 
>
> as opposed to 
>
> https://www.bhphotovideo.com/c/p 
> https://www.bhphotovideo.com/c/p 
> https://www.bhphotovideo.com/c/p 
>
> In either case you can scroll or hover the mouse for a tool tip of the 
> whole URL. 
>
> Trying to think what the best option is - a @setting to control 
> formatting of the text?  Maybe defaults to 
>
>   {basename} @ {fullurl} 
>
> but can be changed to 
>
>   {fullurl} 
>
> or 
>
>   {site}/{path} 
>
> or something like that? 
>
> Cheers -Terry 
>
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

For URLs (http://and https://) links, is there a way to edit the string in 
the Links tab to be either more descriptive or eliminated altogether? A few 
examples to illustrate the point:

http://leoeditor.com/

customizing.html @ http://leoeditor.com/customizing.html

Manfrotto_143BKT_143BKT_Camera_Platform_for.html @ 
https://www.bhphotovideo.com/c/product/5184-REG/Manfrotto_143BKT_143BKT_Camera_Platform_for.html

Apparently, the URL address is preceded by whatever text follows the last 
`/` if there is any plus `@`.

It seems that the preceding text doesn't add any useful information, but 
simply makes the string longer, for no good reason. Looking at the code in 
the plugin, it seems that string text is created in the updateTabInt 
section (name = "%s @ %s" % (name, url)). Thoughts?

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

Terrific, thanks!

On Sunday, June 18, 2017 at 10:25:42 PM UTC-4, Terry Brown wrote:
>
> On Sun, 18 Jun 2017 17:48:41 -0700 (PDT) 
> Largo84 <lar...@gmail.com > wrote: 
>
> > I usually use a script that Edward wrote a while back: 
> > g.es(p.get_UNL(with_proto=True)) 
> > 
> > It generates something like: 
> > unl://g:\Shared%20Workbook.leo#Reference:6-->Pandoc%20Instructions:0 
> > 
> > As opposed to what is in the status bar below: 
> > g:\Shared Workbook.leo#Reference-->Pandoc Instructions 
> > 
> > Is there a script version (or additional parameters) that would 
> > generate a UNL that would 'play nicer' with the plugin? 
>
> g.es(p.get_UNL(with_proto=False)) 
>
> :) 
>
> Or just 
>
> g.es(p.get_UNL()) 
>
> But maybe this is better still 
>
> from leo.core.leoQt import QtWidgets 
> clipboard = QtWidgets.QApplication.clipboard() 
> unl = p.get_UNL() 
> clipboard.setText(unl) 
> g.es("'%s' copied to clipboard" % unl) 
>
> so the best form of UNL's on the clipboard and you can just go to the 
> other outline and do the link to URL / UNL bit. 
>
> Cheers -Terry 
>
> > Rob... 
> > 
> > On Sunday, June 18, 2017 at 11:13:38 AM UTC-4, Terry Brown wrote: 
> > > 
> > > 
> > > 
> > > How are you generating the UNL that you link to?  It's best to just 
> > > enter something like 
> > > 
> > > "c:\leo\git\leo-editor\leo\plugins\leoPlugins.leo#Plugins-->Files 
> > > and nodes-->@file backlink.py-->class 
> > > backlinkController-->updateTabInt" 
> > > 
> > > without quotes, i.e. the text shown by default at the bottom of 
> > > Leo's main window.  As opposed to the indexed form: 
> > > 
> > > 
> > > 
> > 
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

Small initial testing using the file link copied from the bottom shows the 
backlink is created in both files; the target and the source. It's slightly 
less convenient than the script button to create the UNL (I didn't know 
there was difference in form as they always worked either way), but this is 
a truly incredible addition to Leo! This makes annotating external research 
a breeze. Thanks

Rob

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

I usually use a script that Edward wrote a while back:
g.es(p.get_UNL(with_proto=True))

It generates something like:
unl://g:\Shared%20Workbook.leo#Reference:6-->Pandoc%20Instructions:0

As opposed to what is in the status bar below:
g:\Shared Workbook.leo#Reference-->Pandoc Instructions

Is there a script version (or additional parameters) that would generate a 
UNL that would 'play nicer' with the plugin?

Rob...

On Sunday, June 18, 2017 at 11:13:38 AM UTC-4, Terry Brown wrote:
>
>
>
> How are you generating the UNL that you link to?  It's best to just 
> enter something like 
>
> "c:\leo\git\leo-editor\leo\plugins\leoPlugins.leo#Plugins-->Files and 
> nodes-->@file backlink.py-->class backlinkController-->updateTabInt" 
>
> without quotes, i.e. the text shown by default at the bottom of Leo's 
> main window.  As opposed to the indexed form: 
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

I get some errors when I click on certain nodes that already had some kind 
of link already (not exactly sure what). Maybe this helps:

hook failed: select3, >, 
leo.plugins.backlink
Traceback (most recent call last):
  File "e:\GitHub Repos\Leo\leo\core\leoPlugins.py", line 341, in 
callTagHandler
result = handler(tag, keywords)
  File "e:\GitHub Repos\Leo\leo\plugins\backlink.py", line 654, in updateTab
self.updateTabInt()
  File "e:\GitHub Repos\Leo\leo\plugins\backlink.py", line 716, in 
updateTabInt
for url in v.u['_bklnk']['urls']:
KeyError: 'urls'

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: --session-restore glitch

[Largo84]

I closed the bug today as I was unable to duplicate the behavior on the 
target machine.

Rob

On Tuesday, May 30, 2017 at 10:07:56 AM UTC-4, Largo84 wrote:
>
> Done here <https://github.com/leo-editor/leo-editor/issues/498>.
>
> On Tuesday, May 30, 2017 at 9:50:23 AM UTC-4, Edward K. Ream wrote:
>>
>>  
>> ​Of course it's a bug, and a serious one.  Please file a bug report.
>>
>> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

Terry, that would be awesome! Sorry that I'm such a dunce w/ Python 
programming. I started by looking at the plugin code, but quickly realized 
I didn't have a clue what was going on. Just wondering; would it benefit to 
put in an enhancement request on a specific plugin like this?

Rob..

On Sunday, June 4, 2017 at 9:27:36 PM UTC-4, Terry Brown wrote:
>
> On Sun, 4 Jun 2017 12:42:10 -0700 (PDT) 
> Largo84 <lar...@gmail.com > wrote: 
>
> [snip] 
>
> > Are there any technical, design or practical reasons why the 
> > backlinks plugin is limited to 'internal' links? I thought about 
>
> Sort of.  The backlinks plugin uses GNXs (node IDs) for persistence.  I 
> think - I wrote it, but haven't touched that part of it for a long time. 
> GNXs don't include any file info, so you can only interpret them in the 
> context of the current file. 
>
> I suspect the backlinks plugin could be extended to use UNLs too, might 
> be a bit fiddly because the graphviz plugin depends on backlinks, so 
> that would need tweaking too.  But probably makes more sense than 
> creating a new but very similar plugin.  I'll try and remember to 
> investigate, but won't be for a few days. 
>
> (UNLs can include file info. and thus make cross file links, like Lewis 
> said) 
>
> Cheers -Terry 
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

Thanks, Lewis, but that's not what I'm looking for. I don't want the URL 
text to be in the body text at all. Consider this use case:


   - I write some content (LaTex, MarkDown or whatever) and I want to 
   create several links to other references (for example, citations or further 
   research). In Scrivener, I can link to other content, external URLs (web) 
   or other files or folders. There's no limit to how many links I can create, 
   or what type of links.
   - None of those actual link addresses are visible in the body text. They 
   only exist as 'attributes' of the text content, much like keyword tags.
   - The backlinks plugin does most of that as long as the links are to 
   other content nodes within the same .leo file.
   - What is needed is a way to create any type of link and any number of 
   them that are visible in a different tab (much like how the backlinks 
   plugin works).
   - Currently, the only option I have is to include the link URLs in the 
   body text and comment them out since they're not native LaTex; not very 
   clean and neat.

Are there any technical, design or practical reasons why the backlinks 
plugin is limited to 'internal' links? I thought about creating a new 
plugin based on the backlink plugin, but I don't have the faintest notion 
of where to begin.

Rob...

On Sunday, June 4, 2017 at 6:07:19 AM UTC-4, lewis wrote:
>
> You can use the bookmarks plugin to create links to other nodes *within* a 
> single .leo file. Simply edit the bookmark node's body text to include the 
> node name:
> N:/path/to/file/my_file.leo#node_name
> and for multi-level nodes:
> N:/path/to/file/my_file.leo#node_name-->child_node
>
> Regards
> Lewis
>
> On Saturday, June 3, 2017 at 12:56:31 AM UTC+10, Largo84 wrote:
>>
>> [snip
>>
>  
>
>> ] The bookmarks plugin doesn't really do what I need either. Any 
>> suggestions on how to create links to nodes in other .leo 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 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Cross-file links

[Largo84]

Thanks, but that doesn't really solve the problem. unl:// links work just 
fine as they are, but I'm trying to not clutter the body pane with a long 
path. Replacing "unl://" with "file://" doesn't accomplish that.

Rob...

On Friday, June 2, 2017 at 12:49:28 PM UTC-4, xgid wrote:
>
> > Any suggestions on how to create links to nodes in other .leo files? 
> I've been using a simple alternative with good success since the last 
> changes made by EKR to the handleUrl logic some months ago: just use the 
> UNL as is but replacing "unl://" by "file://". 
>
> Best regards, 
> Xavier 
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Cross-file links

[Largo84]

I use the backlinks plugin which works well to create links to other nodes 
*within* a single .leo file. However, it won't create links to nodes in 
other .leo files. The bookmarks plugin doesn't really do what I need 
either. Any suggestions on how to create links to nodes in other .leo 
files? Of course, I can add the UNL in the body pane, but then it clutters 
up the body pane. Maybe I'm missing something obvious.

Rob..

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: --session-restore glitch

[Largo84]

Done here .

On Tuesday, May 30, 2017 at 9:50:23 AM UTC-4, Edward K. Ream wrote:
>
>  
> ​Of course it's a bug, and a serious one.  Please file a bug report.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

--session-restore glitch

[Largo84]

I recently had a new PC built w/ Win10 at my office. After installing 
Anaconda3 as my Python environment and installing Leo from GitHub as usual, 
I was unable to get Leo to start beyond displaying the splash screen. After 
much gnashing of teeth and experimentation, I figured out what the problem 
was. I had copied my original desktop shortcut to Leo, which included the 
two command line options; --session-save and --session restore.

So, apparently, Leo will fail startup if there is no leo.session file, 
which doesn't get created until after a session is saved at least once. So, 
I had to run the launch with -session-save and *not* --session-restore 
first, then exit which creates the leo.session file. Then I could add back 
the --session-restore switch and Leo launched successfully as before.

Would this be considered a bug or expected (though somewhat surprising) 
behavior?

Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: LaTex to PDF workflow using Leo

[Largo84]

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 
   contains only the preamble, document class and anything else that helps to 
   determine what the document will look like. It's usually auto-created from 
   a set of standard templates.
   2. *All* content resides in separate file outline nodes that might be 
   anywhere and almost never is in the same place as the master document file. 
   I generally use either @file (if sentinels are OK) or @clean (if not) for 
   the content files.
   3. The master document outline nodes will have a sectioning environment, 
   maybe \section{Some Section} followed by \input{"\path\Some_Section.tex"}. 
   This pulls in the content from Some_File.tex wherever it happens to be.
   4. I prefer to *not* include sectioning environments in the content 
   files because for one document, Some_Section content might be a 
   \section{Some Section}, where another document might have the same content 
   as a \subsection{Some Section}.

Good luck and maybe we can share some other ideas to make this work better. 
I'm not a Leo expert, but I depend on it a lot for my writing. HTH

Rob


On Monday, May 29, 2017 at 12:16:14 PM UTC-4, Josef wrote:
>
> 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 automatically translates the 
> Leo hierarchy into headings came from a tiny piece of code I once 
> contributed. So, naturally I also thought about creating a latex plugin 
> with automatic hierarchy translation to headings. That would work well as 
> long as the Latex file 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 together with others, but that would mean one @file 
> statement per .tex file. These @file headings do not necessarily correspond 
> to the document structure. The \input can appear anywhere in the text. An 
> \input may correspond to a new (sub-)section but it also may not. Not every 
> heading will have a corresponding \input either. The Leo tree therefore 
> will not only contain section headings, but also @file nodes corresponding 
> to \input statements and not necessarily corresponding to the document 
> structure. 
>
> Also, one must find the master tex file in order to see the complete 
> hierarchy. Since the files may be distributed over different directories, 
> the importer would have to be told about the master file and would then 
> have to look for all the \input statements recursively (and ignoring 
> commented out \inputs).
>
> I don't know how to solve this problem yet.
>
> - Josef
>
> On Wednesday, 12 April 2017 17:35:21 UTC+2, Edward K. Ream wrote:
>>
>> On Wed, Apr 12, 2017 at 12:10 AM, Largo84 <lar...@gmail.com> 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 command. I envisage invoking the 
>> script manually whenever you change the source tree.  That would at least 
>> be a good prototype.
>>
>> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Leo as wiki replacement

[Largo84]

Chris, I'm curious about your workflow from RST to .odt w/ docutils. Last 
time I looked at it several years ago, I couldn't get it to work. Do you 
mind sharing details?

Rob.

On Friday, May 12, 2017 at 4:50:27 PM UTC-4, Chris George wrote:
>
> I use Leo strictly for writing, restructured text to .odt using docutils. 
> I also use it as my data bank for quotes, snippets of interesting info, 
> bookmarks, recipes, etc. It makes it easy to keep information organized and 
> simple to find again when I need it.
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Leo as wiki replacement

[Largo84]

Sounds a lot like how I use Leo. I'm not a programmer either (unless you 
count minimal scripting in LaTex). I write extensively in Leo (LaTex, HTML 
and markdown mostly). I recently tried Scrivener, but quickly came back to 
Leo after seeing that Pandoc will be easy enough for me to use. Don't 
hesitate to ask, it's a great group and usually somebody can and will help.

If you haven't yet, try out the linking capabilities.

Rob.

On Friday, May 12, 2017 at 3:12:46 PM UTC-4, Lang Hurst wrote:
>
> Thanks for the response. Nothing special about vimwiki, it's just a wiki I 
> use for organization and writing. Substitute any wiki for the use. More 
> interested in the linking and moving back and forth. I'm feeling like I 
> just have to change my thinking style and this should be pretty awesome. 
> Nothing like changing up workflow 1/2 way through a Masters, but it seems 
> to be the way that I always work. Anyway, thanks again.
>
> -Lang
>
> On Friday, May 12, 2017 at 12:00:26 PM UTC-7, Terry Brown wrote:
>>
>> On Fri, 12 May 2017 11:11:03 -0700 (PDT) 
>> Lang Hurst  wrote: 
>>
>> > Hello. I just spent a few days looking at Leo after seeing a post of 
>> > Mr. Reams on the npyscreen group. Leo looks pretty damn cool. The 
>> > problem is I don't do much coding anymore. I mostly just use vimwiki 
>> > to manage my website, but mostly for organizing my notes and writing 
>> > papers. I've been writing the papers in LaTex while in vimwiki and 
>> > then compiling it from there. Seems like I could use Leo to do most 
>> > of this. Before I spend more time though, am I using this tool in a 
>> > way that doesn't make sense? Is there anyone who does this? I can see 
>> > how awesome Leo could be for straight up writing, but just wondering 
>> > how or if people utilize it outside of that or just python 
>> > programming. 
>>
>> I think a lot of people use Leo for non-coding / writing type 
>> purposes.  I've been writing papers via Leo -> markdown -> pandoc, 
>> which uses LaTeX for PDF output. 
>>
>> Not familiar with vimwiki so not sure how much automation that's 
>> bringing to the LaTeX writing process.  Leo's abbreviations can be 
>> helpful, e.g. expanding something like fig;; to 
>>
>> \begin{figure}\end{figure} 
>>
>> Not aware of any particular pre-view apparatus, but it's very easy to 
>> write button scripts that generate a doc. being viewed in PDF preview 
>> or whatever. 
>>
>> Cheers -Terry 
>>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: @drawer and @ua directives

[Largo84]

If I understand this correctly, it seems like a good idea to me as it would 
make it easier to add, edit and view uA's associated with a node. I don't 
use Emacs, so I don't really know what 'drawers' are, or have any 
experience with them (other than from reading from link).

Rob

On Monday, May 8, 2017 at 6:36:04 AM UTC-4, Edward K. Ream wrote:
>
> Perhaps Emacs-style drawers (and 
> their contents) and Leo's own uA's need not always be hidden.  The @drawer 
> and @ua directives would be followed by text:
>
> @drawer key: value  # same as :key: value :end:
> @ua outer-key: inner-key: value
>
> Leo's execute-script command ignores *all* directives, which is what we 
> want.  These directives would set v.drawer and v.ua respectively, 
> probably on startup. @drawer would be equivalent to @ua leo_drawer: key: 
> value, so it too would set v.ua.
>
> Advantages: Explicit, can easily be changed, and would create string(_str) 
> uA's, no need for an Easter-Egg interface (attrib_edit or similar).
>
> Disadvantage: Might clutter nodes, unless a we add toggle-drawer-visible 
> and toggle-ua-visible commands.
>
> Not sure whether, or how, to implement multi-line drawer entries.
>
> Your comments please. 
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: cff vs bff

[Largo84]

I would see myself using both, can't wait to see it (bff, that is).

Rob

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Aha: think process, not knowledge

[Largo84]

Excellent post, Edward! There are many analogies in other domains. For 
example, one of my passions is coaching volleyball. We have a saying; '*the 
game teaches the game*'. No amount of technical 'knowledge' about 
volleyball (or any sport, for that matter) will make someone a good player. 
Thanks for everything you do for the Leo 'community'.

Rob..

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Windows state

[Largo84]

OK, good. I'll add that to the command-line options. Thanks!

Rob

The following command-line options apply:
>
>  --maximized   start maximized
>   --minimized   start minimized
>   --window-size=WINDOW_SIZE initial window size (height x width)​
>
> Afaik, there have been no recent changes to any of these.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Tab and other errors in @auto read

[Largo84]

Yes, will send them to you privately (I think I have your email address).

Rob.

On Friday, April 14, 2017 at 4:24:43 PM UTC-4, Edward K. Ream wrote:
>
>
>
> On Fri, Apr 14, 2017 at 1:11 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> I know there's been a lot of work on the @auto read code lately. Just 
>> today I got the following long list errors from 3 @auto files (attached 
>> file with log report). I can send the original files if necessary.
>>
>
> ​Please do.  Did these files previously​
>  
> ​import correctly?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Tab and other errors in @auto read

[Largo84]

I know there's been a lot of work on the @auto read code lately. Just today 
I got the following long list errors from 3 @auto files (attached file with 
log report). I can send the original files if necessary.

Rob..

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
reading: @auto email-sender.php
tabs found with @tabwidth -4 in @auto email-sender.php
changed leading tabs to blanks in 27 lines in @auto email-sender.php
reading: @auto basic-style.css
reading: @auto colorblocks-style.css
reading: @auto normalize.css
reading: @auto basic-internal.html
tabs found with @tabwidth -4 in @auto basic-internal.html
changed leading tabs to blanks in 22 lines in @auto basic-internal.html
mismatched closing tag: head link
mismatched closing tag: a img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: header img
mismatched closing tag: body script
mismatched closing tag: html script
reading: @auto basic.html
tabs found with @tabwidth -4 in @auto basic.html
changed leading tabs to blanks in 7 lines in @auto basic.html
mismatched closing tag: head link
mismatched closing tag: a img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: header img
mismatched closing tag: body script
mismatched closing tag: html script
reading: @auto email-sender.php
tabs found with @tabwidth -4 in @auto email-sender.php
changed leading tabs to blanks in 27 lines in @auto email-sender.php
reading: @auto index.html
tabs found with @tabwidth -4 in @auto index.html
changed leading tabs to blanks in 538 lines in @auto index.html
mismatched closing tag: head link
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: form input
mismatched closing tag: li input
mismatched closing tag: ul input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: form input
mismatched closing tag: li input
mismatched closing tag: ul input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: a img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: li img
mismatched closing tag: ul img
mismatched closing tag: li img
mismatched closing tag: ul img
mismatched closing tag: div input
mismatched closing tag: form input
mismatched closing tag: li input
mismatched closing tag: ul input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: nav input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: div input
mismatched closing tag: header input
mismatched closing tag: div input
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div img
mismatched closing tag: div 

Re: LaTex to PDF workflow using Leo

[Largo84]

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 for compiling to verify that each node is labeled correctly. I can't 
even imagine how that would be possible with a script (I do it manually 
now). But, I suppose just about anything is possible with enough ingenuity.

Rob.

>
> ​This would be an interesting enhancement.
>
> Leo's rst3 command does exactly this, but the code in leo/core/leoRst.py 
> might induce heart palpitations.  There are reasons for all that 
> complexity, and probably none of them relate to latex.
>
> In fact, it should be relatively simple to write a script or plugin to do 
> something useful.  Define the *latex level* of a node p to be p.level() - 
> root.level(), where root is the root node of your hierarchy or latex 
> markup. Use this computed level to choose the latex markup.
>
> HTH.  Feel free to ask questions or to create an enhancement request.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: LaTex to PDF workflow using Leo

[Largo84]

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 
avoid confusion) and only using LaTex structure elements in the final 
output shell. Since I mix and match content a lot, this makes it a lot 
easier for me. It's still possible to have the structure not match up, but 
it's easier to fix now. If you look at the example Leo file I posted 
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 around in the hierarchy 
> or I end up with \subsection at the same level as \section, etc. It would 
> be great to be able to let Leo handle this.
> Arjan
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: LaTex to PDF workflow using Leo

[Largo84]

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 
through Leo, but that's way above my pay grade.

Rob...

On Monday, April 10, 2017 at 5:32:49 PM UTC-4, Israel Hands wrote:
>
> 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 
>> <https://github.com/leo-editor/snippets/tree/master/examples/workflow/latex-pdf>
>> .
>>
>>
>> Regards,
>>> Rob
>>>
>>>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: LaTex to PDF workflow using Leo

[Largo84]

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 stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

leo-editor-contrib on GitHub

[Largo84]

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, where in the directory structure would make the most sense?

Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

LaTex to PDF workflow using Leo

[Largo84]

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 for me and I 
use it a lot. Maybe others will get some benefit from it and maybe some 
will offer suggestions to improve it. If there's interest, I can attach a 
minimal .leo file that demonstrates some of the following techniques.

*Typical Use case*

I teach a variety of classes in a business environment and need handouts, 
teaching aids, worksheets and training manuals that are specifically 
customized for each client. These documents are easier to manage, print and 
protect using standard PDFs.

*Workflow Overview*

   1. Document content comes from a primary resource directory arranged by 
   topic (not client specific).
   2. I have a Resources.leo file that helps me keep that directory 
   organized.
   3. All of the content files are written in LaTex (I use a .txi file 
   extension of my own invention to indicate the file is an 'input' file only, 
   not the main output file which uses .tex).
   4. I have a Client.leo file for each client in their own directory to 
   organize work specific to each client.
   5. For each document needed for a client project, I create a 
   Document.tex file from a standard template and change the document 
   properties as needed for the specific client, project and document.
   6. The Document.tex file acts as the presentation 'shell' for the 
   document and I simply add \input{"\ResourcePath Content.txi"} after the 
   \begin{document} statement (\ResourcePath is a shortcut command to the 
   location of the content resource). This shell determines such things as the 
   document title, document type, client name, header/footer information and 
   revision date.
   7. Since I work primarily in Windows, I use TeXNicCenter 
    to process (typeset) the Document.tex 
   file to create PDF output. (I do not use TeXNicCenter for editing, only 
   file processing).

*Workflow Notes and Shortcuts*

   1. Years ago, I discovered the incredible exam class for LaTex 
    and now use it almost 
   exclusively. It makes it much easier to create student and teacher versions 
   of the same content (eg. handout for students and training manual with 
   speaking notes for the teacher).
   2. I use the new @outline-data tree-abbreviations in Leo to create each 
   new Document.tex file from a template with variables (very cool!)
   3. I created many @data abbreviations in Leo to speed up typing of 
   standard LaTex structures (would be happy to share them if anyone is 
   interested).
   4. All document content stays in the Resources directory and only 
   'shell' documents are in the client directories.
   5. These shell documents allow for client-specific information to be 
   added to the headers, footers and in some cases as variables inside the 
   content area itself (using \theClient variable that I define).

*Software Needed*

   1. Leo (of course, and its dependencies).
   2. MiKTex for the LaTex distribution and package management (I have it 
   set to auto-update as needed).
   3. TeXNicCenter for processing (typesetting) to PDF output.

Regards,
Rob

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Ideas for writing for Word (or similar)

[Largo84]

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:15:48 AM UTC-4, Israel Hands wrote:
>
> 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 Scrivener is 
> designed to do. There's a free 30 day trial and it runs on MacOs and 
> Windows. And now my question. 
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Ideas for writing for Word (or similar)

[Largo84]

Thanks for the suggestions. I messed around several years ago w/ docutils, 
but since command line tools are always a struggle for me, I didn't stick 
with it. Not sure why CLI is so hard for me. I'll take a look at the plugin 
also.

Rob.

On Friday, April 7, 2017 at 9:12:35 PM UTC-4, Edward K. Ream wrote:
>
> On Fri, Apr 7, 2017 at 1:42 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
> Any suggestions on how I can use Leo's organizational strengths to write 
>> this knowing that when done, it will need to export to Word (LibreOffice 
>> ODT and maybe RTF would be OK too)?
>>
>
> ​Dan Rahmel wrote the leo_to_rtf.py plugin several years ago.  It's listed 
> as experimental.
>
> I just tried this plugin.  With Python 3 there is the usual porting 
> problem: bytes instead of strings.  With Python 2, the plugin writes an 
> .rtf file, but Open Office complains about the format.  It's probably worth 
> a close look.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How to install pyEnchant w/ Anaconda on Windows?

[Largo84]

>
>
>
> So just replace Win-10 with a Linux system and you should be good to 
> go... 
>

Ha! Not really an option here (work computer, it's not even mine). 

>
> Sorry it wasn't a more helpful outcome.  You can install it from here: 
> http://pythonhosted.org/pyenchant/download.html 
>
> I think PyEnchant is just a wrapper around a C(?) library, so a binary 
> install is needed and just not covered by conda for Win platforms. 
>
> Cheers -Terry 
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

How to install pyEnchant w/ Anaconda on Windows?

[Largo84]

Just now setting up a new machine and I thought I would try the Anaconda 
route (Win10). So far so good, at least getting Leo to run. However, I 
can't figure out how to install the pyEnchant package. I intentionally 
chose the 32 bit version of Anaconda as I understood that's what pyEnchant 
needs.

>From here  I inferred that I 
should simply use in the command prompt:

`conda install -c dan_blanchard pyenchant=1.6.5`

I get:

`PackageNotFoundError: Package not found: Conda could not find '

Has anyone else successfully installed pyEnchant with Anaconda on Windows? 
If so, any suggestions on what to do? Thanks in advance.

Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Installing PyQt on Windows

[Largo84]

Thanks for that, Edward. I looked at Anaconda a few days ago, but found it 
a little overwhelming. Maybe it will be easier than I think once I get 
started. I'd like to revert one of my Win10 machines to 32 bit version so I 
can install pyenchant. Would it be best to uninstall everything and start 
over from scratch with Anaconda? Leo works fine on that machine now (except 
for no spell check).

Rob

On Monday, March 27, 2017 at 6:05:41 PM UTC-4, Edward K. Ream wrote:
>
>
>
> On Mon, Mar 27, 2017 at 10:06 AM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> I am trying to set up Leo for a colleague on his Windows PC and see that 
>> it's much more difficult than I recall, especially for non-programmers. 
>> Apparently, PyQt no longer provides Windows binary installation 
>> executables. Not really knowing what else to try, I opened the Python 
>> command shell and typed `pip3 install PyQt5` and got a syntax error.
>>
>
> ​PyQt5 seems to be a moving target.  It's possible to screw up a 
> previously working Qt5 installation, as I demonstrated several times today.
>
> My suggestion is to start with a Python 3 version of Anaconda.  I also 
> recommend installing 32-bit versions, even on 64-bit systems.  That way you 
> can install ​
>  
> ​pyenchant.
>
> I have been successful in installing 4.1.1 on both Python 2 and 3. The 
> installers are:
>
> - Anaconda2-4.1.1-Windows-x86.exe and​
> - Anaconda3-4.1.1-Windows-x86.exe
>
> According to my notes, Anaconda 4.2 was buggy: it does not handle 
> QTreeWidget properly.  This was several months ago.  Perhaps things are 
> better now.
>
> Once you get Anaconda installed and working, you should be able to use 
> conda install. If you have multiple Anaconda installations, you will need 
> to use the proper conda script, in either Anaconda2/scripts or 
> Anaconda3/scripts.
>
>>
>> Sorry if the answer is obvious or easy, but for me it's neither. Any help 
>> or suggestions appreciated.
>>
>
> ​Clearly, installing both python and pyqt (and especially pyqt5) is made 
> more difficult by qt bugs. But in the long run, I think using Anaconda is 
> the best bet.
>
> Having said that, Lewis's suggestions might be enough.  
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Installing PyQt on Windows

[Largo84]

Will have to wait a few days to try again, but thanks for the suggestion. 
Better documentation on this process would be helpful at the PyQt site. 
Simply to suggest running `pip3 install PyQt` without directing from where 
is not helpful at all.

Rob.

On Monday, March 27, 2017 at 4:43:11 PM UTC-4, lewis wrote:
>
> Open console or use windows cmd.exe
>
> Locate your python3 folder and cd to /lib/site-packages
>
> Type pip3 install PyQt5
>
> Pip will proceed to download and install and you should be set.
> Regards
> Lewis
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Installing PyQt on Windows

[Largo84]

I am trying to set up Leo for a colleague on his Windows PC and see that 
it's much more difficult than I recall, especially for non-programmers. 
Apparently, PyQt no longer provides Windows binary installation 
executables. Not really knowing what else to try, I opened the Python 
command shell and typed `pip3 install PyQt5` and got a syntax error.

Sorry if the answer is obvious or easy, but for me it's neither. Any help 
or suggestions appreciated.

Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: What are your favorite abbreviations?

[Largo84]

Ha, that's a good one. It's the comment delimiter for LaTex, I use that a 
lot. Maybe I will find p;; easier as well.

Rob...


>>
> I've just added:
>
> p;;=%
>
> Yes, that's right.  I would rather type p;; than the percent sign.  It's 
> my least favorite character on the keyboard.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: In praise of @outline-data tree-abbreviations

[Largo84]

One observation that might help others and also the documentation. In a 
'regular' abbreviation, to create a new line, the syntax is:

foobar;;=<|Foo|> hangs out at the <|Bar|>
\:Another line of <|baz and blah|>
\:Yet another line of <|blah|>.

Quite a different story in @outline-data tree-abbreviations, as in:

In the child node that defines the template, the proper syntax for foobar;; 
is:

<|Foo|> hangs out at the <|Bar|>
Another line of <|baz and blah|>
Yet another line of <|blah|>.

Otherwise the `\:` characters are written as if they are part of the 
expansion.

It's not a big deal once I figured that out, but it is a different approach.

Rob

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: In praise of @outline-data tree-abbreviations

[Largo84]

Some small tests suggest it will work fine. That was fast, excellent work!

Rob..

On Wednesday, March 15, 2017 at 6:59:25 PM UTC-4, Edward K. Ream wrote:
>
> On Wednesday, March 15, 2017 at 11:03:04 AM UTC-5, Largo84 wrote:
>>
>> I'm so busted, can't sneak anything by you:-) 
>>
>
> Fixed at e4e2fb8 of the abbrev branch.  Let me know how it works for you.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: In praise of @outline-data tree-abbreviations

[Largo84]

I'm so busted, can't sneak anything by you:-) 

On Wednesday, March 15, 2017 at 11:32:47 AM UTC-4, Edward K. Ream wrote:
>
>
> On Tue, Mar 14, 2017 at 10:07 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
> Now if only the node headlines can be created from placeholder variables, 
>> it would be perfect. I believe there's a ticket on git for that very thing.
>>
>
> ​Hehe.  I know what you're doing--trying to get this into 5.5b1 using the 
> nefarious tactic of sincere praise.  I'll see what I can do.
>
> No guarantees though, messing with headlines is tricky due to focus 
> problems.  I'll do the work in an abbrev branch so you wont' have to wait 
> for an official release.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

In praise of @outline-data tree-abbreviations

[Largo84]

Not sure if this abbreviation/template has been around awhile and I just 
missed it, or if it's new, but it's almost exactly what I've been looking 
for to create template documents. It will save me a lot of time over my 
previous method of copying template nodes, then manually editing the 
variables.

Now if only the node headlines can be created from placeholder variables, 
it would be perfect. I believe there's a ticket on git for that very thing.

If you haven't seen this in action, check it out, it's pretty cool!

Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Chapters: [Main v] button - chapter order

[Largo84]

I do as that's how I order them in my outline.
Rob

On Thursday, March 9, 2017 at 12:58:14 PM UTC-5, Edward K. Ream wrote:
>
>
>
>> ​So you think outline order is more natural than alphabetical order?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Chapters: [Main v] button - chapter order

[Largo84]

They appear by alphabetical order (confirmed for all of mine); if true, 
don't know if/how to change that to something else.

Rob.

On Thursday, March 9, 2017 at 8:42:22 AM UTC-5, lewis wrote:
>
> If you have a @chapter node with 3 chapters One, Two, Three, note that 
> selecting the Chapters: [Main v] button displays the chapters out of order.
> They display vertically as:
> main
> One
> Three
> Two
>
> I've noticed this issue in several files. I haven't investigated any 
> possible reasons such as order of creation etc
>
> Regards
> Lewis
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rev 112b14f: unl:// syntax creates clickable links between .leo files

[Largo84]

Good, finally figured out what that means, so I created a '@button 
get-unl`. That places the UNL in the log pane. What script command would 
copy it to the clipboard?

On Monday, February 27, 2017 at 3:11:14 PM UTC-5, Edward K. Ream wrote:
>
>
> ​Use p.get_UNL​(), in an @command or @button node. Here are some tested 
> examples:
>
> g.es(p.get_UNL(with_proto=True)) 
>
> yields:
>
> unl://C:\Users\edreamleo\ekr.leo#@button%20get_UNL:8
>
> Setting with_proto=False (the default) gives:
>
> C:\Users\edreamleo\ekr.leo#@button get_UNL:8
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Abbreviation default text

[Largo84]

Just answered my own question. Instead of typing text to replace the 
default, simply press right arrow key before `,,` to advance to the next 
field.


On Tuesday, February 28, 2017 at 2:24:30 PM UTC-5, Largo84 wrote:
>
> Here's another abbreviation question. Is there a way to populate the 
> variable field with default text that remains after moving to the next 
> field? For example:
>
> foobar;;=Use <|foo|> and <|bar|> in a sentence.
>
> When the abbreviation is expanded (executed) the text `foo` is highlighted 
> and I can add new text to replace it, then hit `,,` and go the the next 
> field and `bar` is selected. Is it possible to leave `foo` and `bar` in 
> place as defaults without having to retype them?
>
> If not, would this be an appropriate enhancement request?
>
> Rob...
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How to escape \n in abbreviations?

[Largo84]

It works, thanks!

On Tuesday, February 28, 2017 at 12:27:48 PM UTC-5, Terry Brown wrote:
>
> Ok, \\n should work in 9e9539d, there was special handling of \n in the 
> code already that made \newcommand etc. impossible.  I think it unavoidably 
> breaks theoretically possible abbreviations in people's local settings, but 
> (a) they probably don't exist, and (b) better that than have the code 
> unable to represent text needed for a demonstrated use case (\newcommand 
> etc. in LaTeX).
>
> Cheers -Terry
>
> ------
> *From:* Largo84 <lar...@gmail.com >
> *To:* leo-editor <leo-e...@googlegroups.com > 
> *Cc:* terry_...@yahoo.com 
> *Sent:* Tuesday, February 28, 2017 10:10 AM
> *Subject:* Re: How to escape \n in abbreviations?
>
> Yes, and I also tried '\n' and "\n" to no avail.
>
> Rob.
>
> On Tuesday, February 28, 2017 at 10:52:58 AM UTC-5, Terry Brown wrote:
>
> Sorry, didn't read carefully enough.  Have you tried \\n ?
>
> Cheers -Terry
>
> --
> *From:* Largo84 <lar...@gmail.com>
> *To:* leo-editor <leo-e...@googlegroups.com> 
> *Sent:* Tuesday, February 28, 2017 9:47 AM
> *Subject:* Re: How to escape \n in abbreviations?
>
> That doesn't really answer the question. I use the `\:` syntax often to 
> create new lines in abbreviations as you demonstrate. What I need is the 
> text output to be `\n`. I need to somehow escape the `\n` such that when 
> executed it doesn't generate a new line and strip out the `\n' string 
> literal.
>
> Rob
>
> On Tuesday, February 28, 2017 at 9:05:59 AM UTC-5, Terry Brown wrote:
>
>
>
> leo-editor/leo/config/ leoSettings.leo#@settings--> Abbreviations-->@data 
> global-abbreviations 
>
> illustrates this: 
>
> # type html;; to insert template and ,, to select next <|placeholder|> 
> html;;= 
> \: 
> \:<|title|> 
> \: 
> \: 
> \: 
> \: 
> \:<|content|> 
> \: 
> \: 
>
> -- 
> 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+...@ googlegroups.com.
> To post to this group, send email to leo-e...@googlegroups.com.
>
> Visit this group at https://groups.google.com/ group/leo-editor 
> <https://groups.google.com/group/leo-editor>.
> For more options, visit https://groups.google.com/d/ optout 
> <https://groups.google.com/d/optout>.
>
>
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Abbreviation default text

[Largo84]

Here's another abbreviation question. Is there a way to populate the 
variable field with default text that remains after moving to the next 
field? For example:

foobar;;=Use <|foo|> and <|bar|> in a sentence.

When the abbreviation is expanded (executed) the text `foo` is highlighted 
and I can add new text to replace it, then hit `,,` and go the the next 
field and `bar` is selected. Is it possible to leave `foo` and `bar` in 
place as defaults without having to retype them?

If not, would this be an appropriate enhancement request?

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How to escape \n in abbreviations?

[Largo84]

Done

On Tuesday, February 28, 2017 at 11:35:24 AM UTC-5, Edward K. Ream wrote:
>
>
> ​Please file an enhancement request.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How to escape \n in abbreviations?

[Largo84]

Yes, and I also tried '\n' and "\n" to no avail.

Rob.

On Tuesday, February 28, 2017 at 10:52:58 AM UTC-5, Terry Brown wrote:
>
> Sorry, didn't read carefully enough.  Have you tried \\n ?
>
> Cheers -Terry
>
> ------
> *From:* Largo84 <lar...@gmail.com >
> *To:* leo-editor <leo-e...@googlegroups.com > 
> *Sent:* Tuesday, February 28, 2017 9:47 AM
> *Subject:* Re: How to escape \n in abbreviations?
>
> That doesn't really answer the question. I use the `\:` syntax often to 
> create new lines in abbreviations as you demonstrate. What I need is the 
> text output to be `\n`. I need to somehow escape the `\n` such that when 
> executed it doesn't generate a new line and strip out the `\n' string 
> literal.
>
> Rob
>
> On Tuesday, February 28, 2017 at 9:05:59 AM UTC-5, Terry Brown wrote:
>
>
>
> leo-editor/leo/config/ leoSettings.leo#@settings--> Abbreviations-->@data 
> global-abbreviations 
>
> illustrates this: 
>
> # type html;; to insert template and ,, to select next <|placeholder|> 
> html;;= 
> \: 
> \:<|title|> 
> \: 
> \: 
> \: 
> \: 
> \:<|content|> 
> \: 
> \: 
>
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to leo-e...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How to escape \n in abbreviations?

[Largo84]

That doesn't really answer the question. I use the `\:` syntax often to 
create new lines in abbreviations as you demonstrate. What I need is the 
text output to be `\n`. I need to somehow escape the `\n` such that when 
executed it doesn't generate a new line and strip out the `\n' string 
literal.

Rob

On Tuesday, February 28, 2017 at 9:05:59 AM UTC-5, Terry Brown wrote:
>
>
>
> leo-editor/leo/config/leoSettings.leo#@settings-->Abbreviations-->@data 
> global-abbreviations 
>
> illustrates this: 
>
> # type html;; to insert template and ,, to select next <|placeholder|> 
> html;;= 
> \: 
> \:<|title|> 
> \: 
> \: 
> \: 
> \: 
> \:<|content|> 
> \: 
> \: 
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

How to escape \n in abbreviations?

[Largo84]

Suppose I create an abbreviation for a LaTex construct such as:

newcom;;=\newcommand{\SomethingNew}{<|INSERT-TEXT|>}

When executed, the `\n` is interpreted as a Python line feed and I end up 
with:

ewcommand{...

How can I escape the `\n` so that it doesn't create a line feed, but the 
string literal value of `\n`? I looked here 
, but didn't see anything 
helpful.

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rev 112b14f: unl:// syntax creates clickable links between .leo files

[Largo84]

Excellent! Now, still wondering if there's a more 'Leonine' way to capture 
the node UNL such an alt-X command or keyboard shortcut. Just curious, how 
do you typically do that?

Rob.

>
>
> Many thanks, Rob, for your help in smoothing the rough edges.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: A sprint (real or virtual) about Leo 5.6

[Largo84]

One feature of Notepad++ that I would love to see emulated in Leo is auto 
word completion. Maybe that's already available, but it's not obvious to me 
where or how to enable it.

Rob


> And any other topics you might want to discuss.
>
> Yes, I've declared this to be quiet time, but *short *comments will be 
> welcome now.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rev 112b14f: unl:// syntax creates clickable links between .leo files

[Largo84]

In the address bar (lower right) I see the address of the current node, 
such as:

G:\Shared Workbook.leo#File Directories

If I right-click the bar, there are shown 3 options: Copy, Select All, *Toggle 
UNL mode*. If I select the latter, the address bar now shows:

file://G:\Shared%20Workbook.leo#File%20Directories:16

That's what I copy/paste to create a UNL link to that node. Is there a 
better (faster, maybe keyboard shortcut) way to capture the UNL?

Rob.
 

> ​I have no idea what you mean by "toggle in UNL mode".
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rev 112b14f: unl:// syntax creates clickable links between .leo files

[Largo84]

A few things about this change:

   1. Previously, for nodes within the same Leo file, I could truncate 
   everything before the `#' and the right-click `Open URL' would take me 
   there. That no longer works. That's not too big deal, I can now prepend the 
   `#' with unl:// and it works (except for no. 2 below).
   2. If I replace file:// with unl:// the right-click menu option is no 
   longer available. Can that be added back?
   3. The address in the bottom bar still uses `file://...' when I toggle 
   in UNL mode (that's where I usually get the node address, not sure if 
   there's a quicker way). It seems that it would make more sense for that to 
   be `unl://...'
   
Generally, I like the change; maybe it will make cross file linking easier.

Rob

On Saturday, February 25, 2017 at 6:34:46 PM UTC-5, Edward K. Ream wrote:
>
> Leo now supports the unl:// syntax.  Leo colors from unl:// to the end of 
> the line.
>
> More importantly, control-clicking on an unl:// link will open a .leo file 
> (if specified) and will select a node, if specified.
>
> The syntax is:  unl://(optional-path-to-a-.leo-file)(#)(optional unl).
>
> The '#' is required if both parts are given.
>
> Examples:
>
> 1. unl://leoSettings.leo
>
>   Opens leoSettings.leo
> 
> 2. unl://leoSettings.leo#@settings-->Plugins-->wikiview plugin
>
>   Opens leoSettings.leo, and selects the wikiview plugin node.
>
> 3. When clicked in leoSettings.leo itself, these all select a node:
>
>   unl://@settings-->Plugins-->wikiview plugin-->@bool wikiview-active = 
> True
>   unl://#@settings-->Plugins-->wikiview plugin-->@bool wikiview-active = 
> True
>   unl://@settings-->Plugins-->wikiview plugin-->@bool wikiview-active
>   unl://@settings-->Plugins-->wikiview plugin
>
> This is a superb feature.  In fact, it has existed for quite some time, 
> but the links used (abused) the file:// notation for URL's. The new 
> notation explicitly shows that the target will be a .leo file on the 
> current machine.
>
> The wikiview plugin (via its settings) is now aware of the unl:// notation.
>
> Yes, some people may have to change file:// links to unl:// links. I'm 
> good with that.  The old notation (and the old code) was intolerably wonky.
>
> All comments and questions are 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...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: New Qt geometry error

[Largo84]

Here's the log window information from the offending PC:

Leo 5.4, build 20170221043749, Tue Feb 21 04:37:49 CST 2017
Git repo info: branch = master, commit = f860468937d5
Python 3.4.3, PyQt version 5.4.1
Windows 8 AMD64 (build 6.2.9200) 

For some reason, it reports as Windows 8, but it's Windows 10.
Rob..


> ​I don't usually see this on Windows 10, ​
>  
> ​PyQt version 5.6.2, or any other combination of Python/Qt versions.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: New Qt geometry error

[Largo84]

On another computer (Windows 7, Python 3.3.2, PyQt version 4.8.4), I don't 
see this error message. The PC that has the error is Windows 10. They may 
also have different PyQt installations, will have to check when I get back 
home.

Rob.

On Tuesday, February 21, 2017 at 9:29:36 AM UTC-5, Largo84 wrote:
>
> The message comes up in the terminal window before any of the tabs open. 
> Subsequent resizing of the windows doesn't trigger the warning.
>
> HTH
> Rob
>
> On Monday, February 20, 2017 at 5:00:43 PM UTC-5, Edward K. Ream wrote:
>>
>> On Mon, Feb 20, 2017 at 2:32 PM, Largo84 <lar...@gmail.com> wrote:
>>
>>> I was opening Leo (launching) for the first time today.
>>>
>>
>> ​Does resizing the window make the message go away?
>>
>> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: New Qt geometry error

[Largo84]

The message comes up in the terminal window before any of the tabs open. 
Subsequent resizing of the windows doesn't trigger the warning.

HTH
Rob

On Monday, February 20, 2017 at 5:00:43 PM UTC-5, Edward K. Ream wrote:
>
> On Mon, Feb 20, 2017 at 2:32 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> I was opening Leo (launching) for the first time today.
>>
>
> ​Does resizing the window make the message go away?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: New Qt geometry error

[Largo84]

I was opening Leo (launching) for the first time today.

Rob.


> What were you doing when this message appeared?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

New Qt geometry error

[Largo84]

This is the first time I've seen this error (latest commit, 74ac3cebc298):

QWindowsWindow::setGeometryDp: Unable to set geometry 1920x1017+0+23 on 
QWidgetWindow/'LeoTabbedTopLevelClassWindow'. Resulting geometry: 
 1916x1017+0+23 (frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum 
size: 0x0, maximum size: 16777215x16777215).

Anyone else seeing this?
Rob.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: What are your favorite abbreviations?

[Largo84]

That would be awesome to create new abbreviations and use them immediately.

I have many that I use a lot, mostly either LaTex or HTML constructs, like:

ol;;=\n<|item|>\n
li;;=<|ITEM|>
link;;=<|TEXT|>
and

enum;;=\begin{enumerate}\n\item <|item|>\n\end{enumerate}

Rob.

On Monday, February 20, 2017 at 10:23:25 AM UTC-5, Edward K. Ream wrote:
>
> On Mon, Feb 20, 2017 at 8:33 AM, john lunzer  > wrote:
>
> > I still wish I could reload my abbreviations after startup.
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: About org mode

[Largo84]

I would love to be able to do most of what he demonstrated in that video 
with Leo and org-mode. Maybe I can now, but just haven't figured out how 
yet. Great stuff!

BTW, search the Leo web site documentation for `org-mode` and nothing comes 
up. However, search for `org mode' and several results come up. Very 
weird...

Rob..

On Friday, February 10, 2017 at 5:21:20 PM UTC-5, Edward K. Ream wrote:
>
> I finished watching this superb video about org-mode 
>  earlier today.  I took 
> copious notes.
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Colorizer errors

[Largo84]

Leo 5.4, build 20170203053942, Fri Feb  3 05:39:42 CST 2017
Git repo info: branch = master, commit = 7bbcda816253
Python 3.4.3, PyQt version 5.4.1
Windows 8 AMD64 (build 6.2.9200)

These errors show up in the terminal window, not in the Leo Log Window. I 
don't see any problems working with files or the actual colorizing (at 
least not yet):

Traceback (most recent call last):
  File "D:\Synced\github repos\leo\leo\core\leoColorizer.py", line 2055, in 
highlightBlock
self.colorizer.recolor(s)
  File "D:\Synced\github repos\leo\leo\core\leoColorizer.py", line 1886, in 
recolor
self.mainLoop(n, s)
  File "D:\Synced\github repos\leo\leo\core\leoColorizer.py", line 1837, in 
mainLoop
n = f(self, s, i)
  File "D:\Synced\github repos\leo\leo\core\leoColorizer.py", line 1004, in 
match_doc_part
self.setRestart(self.restartDocPart)
  File "D:\Synced\github repos\leo\leo\core\leoColorizer.py", line 1737, in 
setRestart
n = self.computeState(f, keys)
  File "D:\Synced\github repos\leo\leo\core\leoColorizer.py", line 1682, in 
computeState
result = [self.languageTag(self.language)]
  File "D:\Synced\github repos\leo\leo\core\leoColorizer.py", line 1923, in 
languageTag
name = name.replace(pattern, s)
AttributeError: 'NoneType' object has no attribute 'replace'

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Warning: file contains @+middle sentinel

[Largo84]

I got this error message from Leo reading several @files, should I be 
worried about losing data?

Rob..

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: TEX doc colors changed

[Largo84]

OK, good to know, thanks! BTW, I added the new setting at your suggestion 
and it's working again as before.

Rob..

On Thursday, February 2, 2017 at 12:33:45 PM UTC-5, Edward K. Ream wrote:
>
> On Thu, Feb 2, 2017 at 11:24 AM, Largo84 <lar...@gmail.com > 
> wrote:
>
> Does this screen shot help?
>>
>>
>> <https://lh3.googleusercontent.com/-JHBiAtIzhEw/WJNrOxvyKgI/YcQ/k9vyzp5UrrYq4LDYEAElRwcTEZep_sBIQCLcB/s1600/Leo%2Btext%2Bcolorizer.PNG>
>>
> ​Yes.  Thanks.
> ​ ​
> This is what I would expect with the new colorizing of @doc parts.​
>
> Everything up to the @ gets colorized as Tex. Everything between @ and @c 
> is an @doc part. With the new behavior, this will be colorized as @language 
> text. Which means "black" unless there are constructs such as **bold** or 
> *italics*.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: TEX doc colors changed

[Largo84]

Does this screen shot help?

<https://lh3.googleusercontent.com/-JHBiAtIzhEw/WJNrOxvyKgI/YcQ/k9vyzp5UrrYq4LDYEAElRwcTEZep_sBIQCLcB/s1600/Leo%2Btext%2Bcolorizer.PNG>


On Thursday, February 2, 2017 at 12:09:27 PM UTC-5, Edward K. Ream wrote:
>
> On Thu, Feb 2, 2017 at 10:49 AM, Largo84 <lar...@gmail.com > 
> wrote:
>
> why would the text color be different for comments after the stock TEX 
>> comment character (%) than for after @ block?
>>
>
> ​I have no idea ;-)  I would have to see the actual text.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: TEX doc colors changed

[Largo84]

Great, thanks!

Just curious, though; why would the text color be different for comments 
after the stock TEX comment character (%) than for after @ block?


On Thursday, February 2, 2017 at 11:45:54 AM UTC-5, Edward K. Ream wrote:
>
> On Thu, Feb 2, 2017 at 9:17 AM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> I work with @language TEX a lot and now see that all doc parts after @ 
>> are black text, not red as before. If I use the stock TEX comment character 
>> (%), the following text is red as before and as expected.
>>
>> I see there has been much work recently on the colorizers so I don't know 
>> if this issue is related to that, and if so, if this was intentional or an 
>> unintended consequence.
>>
>
> ​The change was intentional, but I had no idea anyone would want red text 
> ;-)
> ​
>  
>
>> My preference is to keep the red text for comments following @, but don't 
>> know how to get that back.
>>
>
> ​Alright.  This will involve a new setting.  I do this immediately.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

TEX doc colors changed

[Largo84]

I work with @language TEX a lot and now see that all doc parts after @ are 
black text, not red as before. If I use the stock TEX comment character 
(%), the following text is red as before and as expected.

I see there has been much work recently on the colorizers so I don't know 
if this issue is related to that, and if so, if this was intentional or an 
unintended consequence. My preference is to keep the red text for comments 
following @, but don't know how to get that back.

Rob...

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: OT: What's a raspberry pi good for?

[Largo84]

Our model railroad club uses several of these for a variety of useful 
purposes. I haven't yet worked with them personally to program them, but 
I'm really intrigued by what we've been able to do with them. For example, 
we use one to emulate the master command stations that send digital signals 
to the tracks to control the locomotives on the layout. We're also building 
a master signaling control system using another one. They're pretty cool!

Rob...

On Friday, January 20, 2017 at 10:02:44 AM UTC-5, Edward K. Ream wrote:
>
> I was given a raspberry pi 3 for Christmas.  It's still unopened.  Anyone 
> know a real use for it?
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Where are uA's (links and tags?) stored?

[Largo84]

Edward, thanks for the clarification. I've been struggling with this for a 
while (losing uA's and backlinks), but didn't realize the solution was 
@persistence. Looking at the docs just now, I see that it is an optional 
feature, but it's not obvious how to enable it. Is it simply a matter of 
creating an empty @persistence node somewhere in the .leo file or is it 
enabled in the MyLeoSettings.leo file? Or something else I haven't thought 
of? Regards,

Rob.

On Saturday, January 21, 2017 at 9:51:59 AM UTC-5, Edward K. Ream wrote:
>
>
> On Tue, Jan 3, 2017 at 12:33 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
> After some further experimenting, links are *not* lost w/ @clean files, 
>> but *are* lost w/ @auto-x files. I suppose that's because the .leo file 
>> keeps a full copy of the @clean file inside, while the @auto-x data is read 
>> into the .leo on load. Am I correct?
>>
>
> ​Yes, mostly. The data reside in the root node. The data refer to gnx's.  
> These gnx's are preserved for @auto nodes only if your outline has an 
> @persistence node, as documented here 
> <http://leoeditor.com/tutorial-programming.html#using-persistence>.
>
> As I write this, I see that @persistence is difficult to find.  I'll 
> remedy this today.
>
> 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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Find/Replace weirdness with '\' character

[Largo84]

Hmmm, that's good to know. That explains why other combinations of \xxx 
work as expected. Thanks!

Rob

On Thursday, January 5, 2017 at 6:40:01 PM UTC-5, Edward K. Ream wrote:
>
>
>
> On Thu, Jan 5, 2017 at 2:44 PM, Largo84 <lar...@gmail.com > 
> wrote:
>
>> I work with a lot of LaTeX files, so the back slash ('\') is quite 
>> common. I needed to do a document-wide Find-Replace, so using the Find tab, 
>> I entered:
>>
>> Find: \smallsbh
>> Replace: \tinysbh
>>
>> Finding works fine, but what gets entered as a replacement is a tab 
>> character and 'inysbh' (not the quotes). 
>>
>
> ​When you find/replace back-slashes, double the back-slash.  Otherwise, 
> you are finding or replacing the corresponding python escape.  \t is the 
> tab character.
>
> EKR
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Find/Replace weirdness with '\' character

[Largo84]

I work with a lot of LaTeX files, so the back slash ('\') is quite common. 
I needed to do a document-wide Find-Replace, so using the Find tab, I 
entered:

Find: \smallsbh
Replace: \tinysbh

Finding works fine, but what gets entered as a replacement is a tab 
character and 'inysbh' (not the quotes). Shall I file a bug report on this 
or is this somehow expected behavior with the '\' character? Of course, in 
this particular case, I could have simply used the text and not included 
the \, but I still believe it should work as expected.

Rob..

PS BTW, in case you're wondering, these are not standard LaTeX commands, I 
created them for my own use.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Hybrid @ type?

[Largo84]

Thanks for posting at gist, I'll take a look.

Rob.

On Wednesday, January 4, 2017 at 3:11:43 PM UTC-5, Terry Brown wrote:
>
> Here's one I was using with coffeescript / R code, can't find the one that 
> was markdown focused.  Basically it updates all nodes to have their 
> headline as the first line of the body like this:
>
>   ###  
>
> updating / inserting as needed, also puts exactly two newlines at the end 
> of each body, I think that was so the external file looked better.
>
> For markdown you'd have to track depth to control the number of # at the 
> start, and put none at the end.  
>
> Depth of a position is p.level(), so you probably need
>
> nd.level() - p.level() + 1
>
> hashes at the start of the line
>
> Code: https://gist.github.com/tbnorth/eb913fcab82f6a4b37734b5156543308
>
> Cheers -Terry
>
>
>
> --
> *From:* Largo84 <lar...@gmail.com >
> *To:* leo-editor <leo-e...@googlegroups.com > 
> *Cc:* terry_...@yahoo.com 
> *Sent:* Wednesday, January 4, 2017 10:58 AM
> *Subject:* Re: Hybrid @ type?
>
> Sounds like that would be useful. Do you mind sharing the script?
>
> Rob.
>
> On Wednesday, January 4, 2017 at 11:48:25 AM UTC-5, Terry Brown wrote:
>
> Something I've done as a workaround is a script button to push headlines 
> into body text when using @clean. So for a node "Discussion", if the first 
> line of the body starts with "# ", make it be "# Discussion", otherwise 
> insert a line like that.
>
> Cheers -Terry
>
>
> --
> *From:* Largo84 <lar...@gmail.com>
> *To:* leo-editor <leo-e...@googlegroups.com> 
> *Sent:* Wednesday, January 4, 2017 9:18 AM
> *Subject:* Hybrid @ type?
>
> Over the last year or so, I have used @auto-x more and more (in 
> particular, @auto-md) because I like the 'clean' external files that 
> replicate the organization of the nodes in Leo. However, more recently as I 
> began relying on tagging, back links and clones, I am running into major 
> limitations with @auto-x (and to a lesser extent with @clean). (See also 
> the recent post on uA storage.)
>
> What would be really beneficial would be a 'hybrid' @ type that 
> writes and maintains org structure  (node headline text) in the external 
> file based on @language (md, org-mode, rst, etc.) while also utilizing the 
> tagging, linking and cloning features of Leo. As I see it (please correct 
> me if this assumptions are wrong):
>
>- @file maintains all of the Leo features described, but the external 
>file includes sentinels.
>- @clean keeps uA information (tags, links, etc), but loses cloning 
>information. Also, @clean *does not* write node headline text to external 
>files.
>- @auto-x loses both uA and cloning information, but *does* write node 
>headline text into external files (based on type).
>
>
> Thoughts or ideas?
>
> Rob..
> -- 
> 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+...@ googlegroups.com.
> To post to this group, send email to leo-e...@googlegroups.com.
>
> Visit this group at https://groups.google.com/ group/leo-editor 
> <https://groups.google.com/group/leo-editor>.
> For more options, visit https://groups.google.com/d/ optout 
> <https://groups.google.com/d/optout>.
>
>
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to leo-e...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Hybrid @ type?

[Largo84]

Sounds like that would be useful. Do you mind sharing the script?

Rob.

On Wednesday, January 4, 2017 at 11:48:25 AM UTC-5, Terry Brown wrote:
>
> Something I've done as a workaround is a script button to push headlines 
> into body text when using @clean. So for a node "Discussion", if the first 
> line of the body starts with "# ", make it be "# Discussion", otherwise 
> insert a line like that.
>
> Cheers -Terry
>
>
> --
> *From:* Largo84 <lar...@gmail.com >
> *To:* leo-editor <leo-e...@googlegroups.com > 
> *Sent:* Wednesday, January 4, 2017 9:18 AM
> *Subject:* Hybrid @ type?
>
> Over the last year or so, I have used @auto-x more and more (in 
> particular, @auto-md) because I like the 'clean' external files that 
> replicate the organization of the nodes in Leo. However, more recently as I 
> began relying on tagging, back links and clones, I am running into major 
> limitations with @auto-x (and to a lesser extent with @clean). (See also 
> the recent post on uA storage.)
>
> What would be really beneficial would be a 'hybrid' @ type that 
> writes and maintains org structure  (node headline text) in the external 
> file based on @language (md, org-mode, rst, etc.) while also utilizing the 
> tagging, linking and cloning features of Leo. As I see it (please correct 
> me if this assumptions are wrong):
>
>- @file maintains all of the Leo features described, but the external 
>file includes sentinels.
>- @clean keeps uA information (tags, links, etc), but loses cloning 
>information. Also, @clean *does not* write node headline text to external 
>files.
>- @auto-x loses both uA and cloning information, but *does* write node 
>headline text into external files (based on type).
>
>
> Thoughts or ideas?
>
> Rob..
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to leo-e...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Hybrid @ type?

[Largo84]

Over the last year or so, I have used @auto-x more and more (in particular, 
@auto-md) because I like the 'clean' external files that replicate the 
organization of the nodes in Leo. However, more recently as I began relying 
on tagging, back links and clones, I am running into major limitations with 
@auto-x (and to a lesser extent with @clean). (See also the recent post on 
uA storage.)

What would be really beneficial would be a 'hybrid' @ type that 
writes and maintains org structure  (node headline text) in the external 
file based on @language (md, org-mode, rst, etc.) while also utilizing the 
tagging, linking and cloning features of Leo. As I see it (please correct 
me if this assumptions are wrong):

   - @file maintains all of the Leo features described, but the external 
   file includes sentinels.
   - @clean keeps uA information (tags, links, etc), but loses cloning 
   information. Also, @clean *does not* write node headline text to external 
   files.
   - @auto-x loses both uA and cloning information, but *does* write node 
   headline text into external files (based on type).


Thoughts or ideas?

Rob..

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Where are uA's (links and tags?) stored?

[Largo84]

After some further experimenting, links are *not* lost w/ @clean files, but 
*are* lost w/ @auto-x files. I suppose that's because the .leo file keeps a 
full copy of the @clean file inside, while the @auto-x data is read into 
the .leo on load. Am I correct?

Rob..

On Tuesday, January 3, 2017 at 1:20:45 PM UTC-5, Largo84 wrote:
>
> I get the following messages when reopening a .leo file:
>
> backlink: link to xyz overview from ??? lost
> backlink: link from abc to ??? lost
>
> The lost links are nodes inside @auto-md files, so can I assume that the 
> link information (are these considered uA's?) is lost because these files 
> are 'clean' of Leo sentinels? Should I further infer from this that all 
> linking (or tagging) information will be lost for nodes in @clean or any 
> other @auto-x files?
>
> Anyone else seeing this or have suggestions to work around?
>
> Rob..
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Where are uA's (links and tags?) stored?

[Largo84]

I get the following messages when reopening a .leo file:

backlink: link to xyz overview from ??? lost
backlink: link from abc to ??? lost

The lost links are nodes inside @auto-md files, so can I assume that the 
link information (are these considered uA's?) is lost because these files 
are 'clean' of Leo sentinels? Should I further infer from this that all 
linking (or tagging) information will be lost for nodes in @clean or any 
other @auto-x files?

Anyone else seeing this or have suggestions to work around?

Rob..

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.