Re: Leo won't start

[Félix]

Devel doesnt work for me neither.

I switched to commit f85c47489eb7dc769b73370d1d8b7abd9b9f6028 from devel in 
the meantime
--
Félix

On Tuesday, January 11, 2022 at 7:19:14 PM UTC-5 tbp1...@gmail.com wrote:

> Upstream means the original repo, the Leo-editor repo on Github in this 
> case.  Origin means one's own clone, if any.  *Upstream* and *Origin* are 
> standard terms.  Git Extensions is a Windows program, nothing to do with 
> Python or anaconda, which I find easier to work with than just git itself 
> (although it has its own learning curve).
>
> Don't feel bad, I get confused about git/GitHub all the time. I'm not 
> really the person to ask abut git questions, I'm afraid.  I think I know 
> this much: if you are using git from the command line, you would want to 
> start by checking out the devel branch.  You want to cd to the top 
> directory where git stores the Leo-editor repository on your computer. Then 
>
> git checkout devel
>
> That should get you the latest version of the devel branch.  Then you have 
> to make sure that Python uses it.  I don't know how you have been doing 
> that.  How I do it, without Anaconda, is to set the PYTHONPATH 
> environmental variable:
>
> set PYTHONPATH=c:\tom\git\leo-editor
>
> Then start Leo by running it from the command line:
>
> python -m leo.core.runLeo
>
> If you are not using git from the command line, someone else (or Prof. 
> Google) will have to help you.
> On Tuesday, January 11, 2022 at 6:45:32 PM UTC-5 Rob wrote:
>
>> Not sure I understand that (what does `Upstream` mean?). I don't know 
>> about Git Extensions on Windows (I'm in an Anaconda environment, in case 
>> that matters). I'm not pulling from Origin. When I switch back to the devel 
>> branch, I get the same error and when I switch again to master, Leo starts 
>> fine.
>>
>> Do I need to delete my repo altogether and start over again? Sorry I'm 
>> such a GH dunce, it's just not intuitive to me.
>>
>> Rob...
>>
>> On Tuesday, January 11, 2022 at 6:19:54 PM UTC-5 tbp1...@gmail.com wrote:
>>
>>> I use Git Extensions on Windows, and after checking out devel, ran the 
>>> *Pull/Fetch* command, which I imagine is (behind the scene) the same 
>>> command as what you did.  You do have to make sure you are pulling from 
>>> Upstream (the Leo git repo) and not Origin (your clone, if you've got 
>>> one).  I don't know what state master is in, but 6.6b1 is not the current 
>>> version in devel.  Here's what I have right now:
>>>
>>> Leo 6.6b2-devel, devel branch, build bdd9ba7442
>>> 2022-01-10 17:30:14 -0500
>>>
>>>
>>> On Tuesday, January 11, 2022 at 5:51:51 PM UTC-5 Rob wrote:
>>>
 I switched to the `Master` branch in GitHub for Windows and `fetched`. 
 Leo opens as before showing Leo 6.6b1, master branch, build 383d6776d1.

 I guess problem solved, just not sure why the devel branch doesn't 
 work, though.

 Rob...

 On Tuesday, January 11, 2022 at 5:40:16 PM UTC-5 Rob wrote:

> Hmm, how did you 'fetch' it? I did what I always do, from my repo CLI, 
> I type `git pull` and update my devel branch. I also tried 'fetching' 
> using 
> GitHub for Windows. What else should I try?
>
> Rob...
>
> On Tuesday, January 11, 2022 at 5:36:31 PM UTC-5 tbp1...@gmail.com 
> wrote:
>
>> I got that too, but it turned out that it wasn't the latest devel 
>> branch, but only the latest zip of 6.6b1 that Github was offering.  When 
>> I 
>> fetched the actual latest using git yesterday (not the zip file), which 
>> was 
>> some version of 6.6b2, that error had gone away.
>>
>> On Tuesday, January 11, 2022 at 5:26:23 PM UTC-5 Rob wrote:
>>
>>> After pulling in the latest devel branch, I get this:
>>> ~~~
>>> 'type' object is not subscriptable
>>>
>>> *** Leo could not be started ***
>>> Please verify you've installed the required dependencies:
>>> https://leoeditor.com/installing.html
>>> ~~~
>>>
>>> Before posting as an issue on GitHub, anyone else seeing this or 
>>> know why Leo won't start?
>>>
>>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/88998245-3386-4430-8dde-d617dbe42d26n%40googlegroups.com.

Re: Aha: how to find the next juicy problem

[tbp1...@gmail.com]

I can picture it:  you start to work on some cool project, and of course 
you will want to use Leo.  Right away, you find that you want to enhance 
Leo to work better on your new project-specific things!

On Tuesday, January 11, 2022 at 8:15:51 AM UTC-5 Edward K. Ream wrote:

> For several years (at least) I have been worrying about what to do when 
> Leo is complete.
>
> Aha: just look for *already-existing* open source projects that interest 
> me.
>
> Amazingly obvious in retrospect!  This isn't the 1980's, where research 
> meant xeroxing articles in the University of Wisconsin Engineering Library.
>
> This Aha is a big deal for me. I see now how stressed I have been about 
> where to go from here. No more need for beach walks and daydreaming. I just 
> need to explore the myriad of cool projects that already exist. Perhaps 
> I'll contribute to a project. Perhaps a project will suggest a spin off.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/12651f5b-ed35-4cf1-ac5e-10c3de76abcfn%40googlegroups.com.

Re: Leo won't start

[tbp1...@gmail.com]

Upstream means the original repo, the Leo-editor repo on Github in this 
case.  Origin means one's own clone, if any.  *Upstream* and *Origin* are 
standard terms.  Git Extensions is a Windows program, nothing to do with 
Python or anaconda, which I find easier to work with than just git itself 
(although it has its own learning curve).

Don't feel bad, I get confused about git/GitHub all the time. I'm not 
really the person to ask abut git questions, I'm afraid.  I think I know 
this much: if you are using git from the command line, you would want to 
start by checking out the devel branch.  You want to cd to the top 
directory where git stores the Leo-editor repository on your computer. Then 

git checkout devel

That should get you the latest version of the devel branch.  Then you have 
to make sure that Python uses it.  I don't know how you have been doing 
that.  How I do it, without Anaconda, is to set the PYTHONPATH 
environmental variable:

set PYTHONPATH=c:\tom\git\leo-editor

Then start Leo by running it from the command line:

python -m leo.core.runLeo

If you are not using git from the command line, someone else (or Prof. 
Google) will have to help you.
On Tuesday, January 11, 2022 at 6:45:32 PM UTC-5 Rob wrote:

> Not sure I understand that (what does `Upstream` mean?). I don't know 
> about Git Extensions on Windows (I'm in an Anaconda environment, in case 
> that matters). I'm not pulling from Origin. When I switch back to the devel 
> branch, I get the same error and when I switch again to master, Leo starts 
> fine.
>
> Do I need to delete my repo altogether and start over again? Sorry I'm 
> such a GH dunce, it's just not intuitive to me.
>
> Rob...
>
> On Tuesday, January 11, 2022 at 6:19:54 PM UTC-5 tbp1...@gmail.com wrote:
>
>> I use Git Extensions on Windows, and after checking out devel, ran the 
>> *Pull/Fetch* command, which I imagine is (behind the scene) the same 
>> command as what you did.  You do have to make sure you are pulling from 
>> Upstream (the Leo git repo) and not Origin (your clone, if you've got 
>> one).  I don't know what state master is in, but 6.6b1 is not the current 
>> version in devel.  Here's what I have right now:
>>
>> Leo 6.6b2-devel, devel branch, build bdd9ba7442
>> 2022-01-10 17:30:14 -0500
>>
>>
>> On Tuesday, January 11, 2022 at 5:51:51 PM UTC-5 Rob wrote:
>>
>>> I switched to the `Master` branch in GitHub for Windows and `fetched`. 
>>> Leo opens as before showing Leo 6.6b1, master branch, build 383d6776d1.
>>>
>>> I guess problem solved, just not sure why the devel branch doesn't work, 
>>> though.
>>>
>>> Rob...
>>>
>>> On Tuesday, January 11, 2022 at 5:40:16 PM UTC-5 Rob wrote:
>>>
 Hmm, how did you 'fetch' it? I did what I always do, from my repo CLI, 
 I type `git pull` and update my devel branch. I also tried 'fetching' 
 using 
 GitHub for Windows. What else should I try?

 Rob...

 On Tuesday, January 11, 2022 at 5:36:31 PM UTC-5 tbp1...@gmail.com 
 wrote:

> I got that too, but it turned out that it wasn't the latest devel 
> branch, but only the latest zip of 6.6b1 that Github was offering.  When 
> I 
> fetched the actual latest using git yesterday (not the zip file), which 
> was 
> some version of 6.6b2, that error had gone away.
>
> On Tuesday, January 11, 2022 at 5:26:23 PM UTC-5 Rob wrote:
>
>> After pulling in the latest devel branch, I get this:
>> ~~~
>> 'type' object is not subscriptable
>>
>> *** Leo could not be started ***
>> Please verify you've installed the required dependencies:
>> https://leoeditor.com/installing.html
>> ~~~
>>
>> Before posting as an issue on GitHub, anyone else seeing this or know 
>> why Leo won't start?
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/5fb9ef17-d28b-4e97-8f9d-750855e45e72n%40googlegroups.com.

Re: Leo won't start

[Rob]

Not sure I understand that (what does `Upstream` mean?). I don't know about 
Git Extensions on Windows (I'm in an Anaconda environment, in case that 
matters). I'm not pulling from Origin. When I switch back to the devel 
branch, I get the same error and when I switch again to master, Leo starts 
fine.

Do I need to delete my repo altogether and start over again? Sorry I'm such 
a GH dunce, it's just not intuitive to me.

Rob...

On Tuesday, January 11, 2022 at 6:19:54 PM UTC-5 tbp1...@gmail.com wrote:

> I use Git Extensions on Windows, and after checking out devel, ran the 
> *Pull/Fetch* command, which I imagine is (behind the scene) the same 
> command as what you did.  You do have to make sure you are pulling from 
> Upstream (the Leo git repo) and not Origin (your clone, if you've got 
> one).  I don't know what state master is in, but 6.6b1 is not the current 
> version in devel.  Here's what I have right now:
>
> Leo 6.6b2-devel, devel branch, build bdd9ba7442
> 2022-01-10 17:30:14 -0500
>
>
> On Tuesday, January 11, 2022 at 5:51:51 PM UTC-5 Rob wrote:
>
>> I switched to the `Master` branch in GitHub for Windows and `fetched`. 
>> Leo opens as before showing Leo 6.6b1, master branch, build 383d6776d1.
>>
>> I guess problem solved, just not sure why the devel branch doesn't work, 
>> though.
>>
>> Rob...
>>
>> On Tuesday, January 11, 2022 at 5:40:16 PM UTC-5 Rob wrote:
>>
>>> Hmm, how did you 'fetch' it? I did what I always do, from my repo CLI, I 
>>> type `git pull` and update my devel branch. I also tried 'fetching' using 
>>> GitHub for Windows. What else should I try?
>>>
>>> Rob...
>>>
>>> On Tuesday, January 11, 2022 at 5:36:31 PM UTC-5 tbp1...@gmail.com 
>>> wrote:
>>>
 I got that too, but it turned out that it wasn't the latest devel 
 branch, but only the latest zip of 6.6b1 that Github was offering.  When I 
 fetched the actual latest using git yesterday (not the zip file), which 
 was 
 some version of 6.6b2, that error had gone away.

 On Tuesday, January 11, 2022 at 5:26:23 PM UTC-5 Rob wrote:

> After pulling in the latest devel branch, I get this:
> ~~~
> 'type' object is not subscriptable
>
> *** Leo could not be started ***
> Please verify you've installed the required dependencies:
> https://leoeditor.com/installing.html
> ~~~
>
> Before posting as an issue on GitHub, anyone else seeing this or know 
> why Leo won't start?
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/b52f30ab-c456-46bd-8926-26387c1e7175n%40googlegroups.com.

Re: Leo won't start

[tbp1...@gmail.com]

I use Git Extensions on Windows, and after checking out devel, ran the 
*Pull/Fetch* command, which I imagine is (behind the scene) the same 
command as what you did.  You do have to make sure you are pulling from 
Upstream (the Leo git repo) and not Origin (your clone, if you've got 
one).  I don't know what state master is in, but 6.6b1 is not the current 
version in devel.  Here's what I have right now:

Leo 6.6b2-devel, devel branch, build bdd9ba7442
2022-01-10 17:30:14 -0500


On Tuesday, January 11, 2022 at 5:51:51 PM UTC-5 Rob wrote:

> I switched to the `Master` branch in GitHub for Windows and `fetched`. Leo 
> opens as before showing Leo 6.6b1, master branch, build 383d6776d1.
>
> I guess problem solved, just not sure why the devel branch doesn't work, 
> though.
>
> Rob...
>
> On Tuesday, January 11, 2022 at 5:40:16 PM UTC-5 Rob wrote:
>
>> Hmm, how did you 'fetch' it? I did what I always do, from my repo CLI, I 
>> type `git pull` and update my devel branch. I also tried 'fetching' using 
>> GitHub for Windows. What else should I try?
>>
>> Rob...
>>
>> On Tuesday, January 11, 2022 at 5:36:31 PM UTC-5 tbp1...@gmail.com wrote:
>>
>>> I got that too, but it turned out that it wasn't the latest devel 
>>> branch, but only the latest zip of 6.6b1 that Github was offering.  When I 
>>> fetched the actual latest using git yesterday (not the zip file), which was 
>>> some version of 6.6b2, that error had gone away.
>>>
>>> On Tuesday, January 11, 2022 at 5:26:23 PM UTC-5 Rob wrote:
>>>
 After pulling in the latest devel branch, I get this:
 ~~~
 'type' object is not subscriptable

 *** Leo could not be started ***
 Please verify you've installed the required dependencies:
 https://leoeditor.com/installing.html
 ~~~

 Before posting as an issue on GitHub, anyone else seeing this or know 
 why Leo won't start?

 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/dfa46c07-db0a-46a0-981f-201faebe5d4dn%40googlegroups.com.

Re: Leo won't start

[Rob]

I switched to the `Master` branch in GitHub for Windows and `fetched`. Leo 
opens as before showing Leo 6.6b1, master branch, build 383d6776d1.

I guess problem solved, just not sure why the devel branch doesn't work, 
though.

Rob...

On Tuesday, January 11, 2022 at 5:40:16 PM UTC-5 Rob wrote:

> Hmm, how did you 'fetch' it? I did what I always do, from my repo CLI, I 
> type `git pull` and update my devel branch. I also tried 'fetching' using 
> GitHub for Windows. What else should I try?
>
> Rob...
>
> On Tuesday, January 11, 2022 at 5:36:31 PM UTC-5 tbp1...@gmail.com wrote:
>
>> I got that too, but it turned out that it wasn't the latest devel branch, 
>> but only the latest zip of 6.6b1 that Github was offering.  When I fetched 
>> the actual latest using git yesterday (not the zip file), which was some 
>> version of 6.6b2, that error had gone away.
>>
>> On Tuesday, January 11, 2022 at 5:26:23 PM UTC-5 Rob wrote:
>>
>>> After pulling in the latest devel branch, I get this:
>>> ~~~
>>> 'type' object is not subscriptable
>>>
>>> *** Leo could not be started ***
>>> Please verify you've installed the required dependencies:
>>> https://leoeditor.com/installing.html
>>> ~~~
>>>
>>> Before posting as an issue on GitHub, anyone else seeing this or know 
>>> why Leo won't start?
>>>
>>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/acc0761b-701e-41f1-a543-72a6e8afddb7n%40googlegroups.com.

Re: Leo won't start

[Rob]

Hmm, how did you 'fetch' it? I did what I always do, from my repo CLI, I 
type `git pull` and update my devel branch. I also tried 'fetching' using 
GitHub for Windows. What else should I try?

Rob...

On Tuesday, January 11, 2022 at 5:36:31 PM UTC-5 tbp1...@gmail.com wrote:

> I got that too, but it turned out that it wasn't the latest devel branch, 
> but only the latest zip of 6.6b1 that Github was offering.  When I fetched 
> the actual latest using git yesterday (not the zip file), which was some 
> version of 6.6b2, that error had gone away.
>
> On Tuesday, January 11, 2022 at 5:26:23 PM UTC-5 Rob wrote:
>
>> After pulling in the latest devel branch, I get this:
>> ~~~
>> 'type' object is not subscriptable
>>
>> *** Leo could not be started ***
>> Please verify you've installed the required dependencies:
>> https://leoeditor.com/installing.html
>> ~~~
>>
>> Before posting as an issue on GitHub, anyone else seeing this or know why 
>> Leo won't start?
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/5cbc020e-719c-43de-9a55-8f5dc17c9ddan%40googlegroups.com.

Re: Leo won't start

[tbp1...@gmail.com]

I got that too, but it turned out that it wasn't the latest devel branch, 
but only the latest zip of 6.6b1 that Github was offering.  When I fetched 
the actual latest using git yesterday (not the zip file), which was some 
version of 6.6b2, that error had gone away.

On Tuesday, January 11, 2022 at 5:26:23 PM UTC-5 Rob wrote:

> After pulling in the latest devel branch, I get this:
> ~~~
> 'type' object is not subscriptable
>
> *** Leo could not be started ***
> Please verify you've installed the required dependencies:
> https://leoeditor.com/installing.html
> ~~~
>
> Before posting as an issue on GitHub, anyone else seeing this or know why 
> Leo won't start?
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/d18de6b8-a89b-4f79-af5e-0f353ff0e343n%40googlegroups.com.

Leo won't start

[Rob]

After pulling in the latest devel branch, I get this:
~~~
'type' object is not subscriptable

*** Leo could not be started ***
Please verify you've installed the required dependencies:
https://leoeditor.com/installing.html
~~~

Before posting as an issue on GitHub, anyone else seeing this or know why 
Leo won't start?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/980d0123-1744-4f30-9e20-31aa6489e3e1n%40googlegroups.com.

Re: generic JSON importer fails

[tbp1...@gmail.com]

Yes, I think you will need to know the schema of the JSON files to be able 
to import them in a useful way..  For example, Jupyter notebooks are JSON 
files, but your files are probably very different.  Leo can import XML 
files, but they are imported into a single Leo node.

On Tuesday, January 11, 2022 at 10:26:06 AM UTC-5 Josef wrote:

> I'll have a look. All I wanted to do for now is edit some already existing 
> JSON files.
>
> I think all the @auto should always behave essentially the same way,
> and that means for me that I can use it to read in any arbitrary file,
> not just one that was created by Leo.
>
> I was using @clean already, but was hoping the @auto would be able to 
> represent the JSON structure in the outline somehow. 
> I realize this is hardly possible, because Leo can't know what to write 
> into the headlines, or even to which level of nodes to go.
>
> I guess I will need write a custom importer for this, since I need to edit 
> (some large) JSON files quite often.
>
> On Monday, January 10, 2022 at 11:05:36 PM UTC+1 Edward K. Ream wrote:
>
>> On Tue, Jan 4, 2022 at 5:40 AM Josef  wrote:
>>
>>> import with at_auto afile.json fails: the body remains empty, at least 
>>> when the top level entity is an object (e.g. a pair of curly braces). For 
>>> example this fails:
>>
>>
>> The problem you are having could be called a confusing result of 
>> featuritis. If all you want to do is represent json in an outline, you can 
>> just use @clean x.json.
>>
>> @auto x.json or (alternatively) @auto-json x.txt creates a json 
>> representation of the outline, complete with a representation of gnx's, 
>> uA's, etc. To see this in action, create the original file with @auto 
>> x.json, write the external file, and take a look at the result.
>>
>> HTH. Please feel free to ask more questions.
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/99c82dc5-4753-4ef1-85b9-e9ce4dae4e79n%40googlegroups.com.

Re: generic JSON importer fails

[Josef]

I'll have a look. All I wanted to do for now is edit some already existing 
JSON files.

I think all the @auto should always behave essentially the same way,
and that means for me that I can use it to read in any arbitrary file,
not just one that was created by Leo.

I was using @clean already, but was hoping the @auto would be able to 
represent the JSON structure in the outline somehow. 
I realize this is hardly possible, because Leo can't know what to write 
into the headlines, or even to which level of nodes to go.

I guess I will need write a custom importer for this, since I need to edit 
(some large) JSON files quite often.

On Monday, January 10, 2022 at 11:05:36 PM UTC+1 Edward K. Ream wrote:

> On Tue, Jan 4, 2022 at 5:40 AM Josef  wrote:
>
>> import with at_auto afile.json fails: the body remains empty, at least 
>> when the top level entity is an object (e.g. a pair of curly braces). For 
>> example this fails:
>
>
> The problem you are having could be called a confusing result of 
> featuritis. If all you want to do is represent json in an outline, you can 
> just use @clean x.json.
>
> @auto x.json or (alternatively) @auto-json x.txt creates a json 
> representation of the outline, complete with a representation of gnx's, 
> uA's, etc. To see this in action, create the original file with @auto 
> x.json, write the external file, and take a look at the result.
>
> HTH. Please feel free to ask more questions.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/307f6ee3-a72a-47cf-8882-652a4de1b254n%40googlegroups.com.

Re: save file menu confusion

[tbp1...@gmail.com]

With the latest devel version, I see you've removed the "File as" wording, 
thank you very much.  I think that more improvement can be made, though.

1. *Save As XML* would be better as *Save as .leo (XML)*.  Many users will 
not realize that a .leo file is an XML file.
2. *Save As Zipped* is misleading because it does not produce a zip 
archive.  Better: *Save as .db (SQLLite)*.
3. Is there a difference between *Save As...* and *Save to...*? If so, *Save 
To ...* needs some wording to make it clear what it will do that's 
different.  If not, the latter should be removed.
4. *Save As Zipped* retains a lock on the saved file, such that the file 
can't be deleted (or, I speculate, moved) until Leo is closed.
On Tuesday, January 11, 2022 at 8:18:46 AM UTC-5 Edward K. Ream wrote:

> On Tue, Jan 11, 2022 at 12:31 AM tbp1...@gmail.com  
> wrote:
>
>> That's good to hear.  I find I would like these items to read "Save 
>> Outline as ..." instead of "Save File as ...".  I usually think of 
>> "outlines" and "files" as being different things even though I know that a 
>> Leo outline is saved as a file.  Operationally, though, a file that I would 
>> work on in Leo is an @file, @clean, etc. tree and not an outline.  Seeing 
>> "Files" in those menu items confuses me.
>>
>
> Could you be more specific? Which menu items would you like to change.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/406e9705-8d99-4223-bcfd-5a5ff06a802bn%40googlegroups.com.

Re: Useful tip request - How to refer to nodes from other nodes?

[Edward K. Ream]

On Sun, Jan 2, 2022 at 3:00 PM Terrence-Monroe: Brannon <
thequietcen...@gmail.com> wrote:

> IMHO the Useful tips part of the documentation should teach a user how to
> refer to a node from another node.


Thanks for this suggestion.  I have just created #2376
for this issue.

Are you referring to Leo's "startup tips" in leoTips.py, or the tips in
quickstart.leo?  Or something else?

I have also assigned #1842
 and #1868
 to Leo 6.6.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0BcMMYF8xQgs9koOGkJmckoydym4kF8z242DHqbyXy8g%40mail.gmail.com.

Re: save file menu confusion

[Edward K. Ream]

On Tue, Jan 11, 2022 at 12:31 AM tbp1...@gmail.com 
wrote:

> That's good to hear.  I find I would like these items to read "Save
> Outline as ..." instead of "Save File as ...".  I usually think of
> "outlines" and "files" as being different things even though I know that a
> Leo outline is saved as a file.  Operationally, though, a file that I would
> work on in Leo is an @file, @clean, etc. tree and not an outline.  Seeing
> "Files" in those menu items confuses me.
>

Could you be more specific? Which menu items would you like to change.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS09rvePa7NDXiC79X6vXuK%2Bij0PfqfFFC2aNROkTBgyjA%40mail.gmail.com.

Aha: how to find the next juicy problem

[Edward K. Ream]

For several years (at least) I have been worrying about what to do when Leo 
is complete.

Aha: just look for *already-existing* open source projects that interest me.

Amazingly obvious in retrospect!  This isn't the 1980's, where research 
meant xeroxing articles in the University of Wisconsin Engineering Library.

This Aha is a big deal for me. I see now how stressed I have been about 
where to go from here. No more need for beach walks and daydreaming. I just 
need to explore the myriad of cool projects that already exist. Perhaps 
I'll contribute to a project. Perhaps a project will suggest a spin off.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/96ba1605-215d-440c-9fc9-631c3ea81b9fn%40googlegroups.com.