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.
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
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
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
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
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
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
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
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
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,
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
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
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
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
15 matches
Mail list logo
