Re: How to create a pypi distribution ?

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Donnerstag, 6. Juni 2024 um 14:40:29 UTC+2:

On Mon, Jun 3, 2024 at 2:55 PM Viktor Ransmayr  wrote:

* When I run the 'build_leo.py' script I immediately receive the following 
traceback:

[snip] 

  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/scripts/build_leo.py", line 26, 
in 
assert os.path.exists(dist_dir), dist_dir
AssertionError: /home/user/PyVE/GitHub/Leo/leo-editor/dist
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 


Hmm. I guess this is a buglet.  Build devs should create a leo-editor/dist 
directory.


This morning I re-read your feedback - and - understood that you did say: 
Leo's developer should create the 'leo-editor/dist' directory manually !

I did - but - ran into the next issue - See attached log:

###

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo/
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ cd leo-editor/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ mkdir dist
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
leo.scripts.build_leo
build_leo.py

python -m build > build_log.txt

/home/user/PyVE/GitHub/Leo/bin/python: No module named build
See build_log.txt
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 

###

Should the GH issue #3837 
<https://github.com/leo-editor/leo-editor/issues/3837> be re-opened ?

With kind regards,

Viktor

-- 
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/6d69fe4c-32a0-4e9e-9726-994854ff5bb4n%40googlegroups.com.

Re: How to create a pypi distribution ?

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Donnerstag, 6. Juni 2024 um 14:40:29 UTC+2:

On Mon, Jun 3, 2024 at 2:55 PM Viktor Ransmayr  wrote:

* When I run the 'build_leo.py' script I immediately receive the following 
traceback:

[snip] 

  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/scripts/build_leo.py", line 26, 
in 
assert os.path.exists(dist_dir), dist_dir
AssertionError: /home/user/PyVE/GitHub/Leo/leo-editor/dist
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 


Hmm. I guess this is a buglet.  Build devs should create a leo-editor/dist 
directory. 


I am not sure, that I understand your feedback completely ...

I was not relying / using the PyPI instance of Leo - but - the GitHub 
(devel branch) instance !

I  had expected, that I could follow the description from GH issue #3837 
<https://github.com/leo-editor/leo-editor/issues/3837> ( even if I am in a 
Linux environment).

Are there any pre-conditions for calling the 'build_leo.py' script, other 
than an up to date 'devel-branch' ?

With kind regards,

Viktor

-- 
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/19073d84-236d-40c6-a357-86df6b2be907n%40googlegroups.com.

Re: Leo 6.8.0 b1 coming in about a week. New read code in devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 4. Juni 2024 um 14:16:03 UTC+2:

I've just merged PR #3860 
 into all the open 
branches.

This change must be tested more thoroughly.


Leo's devel-branch is working w/o immediate issues in a Fedora Linux 39 VM 
& Unittests are passing.

Anything else that you are specifically interested in ?

With kind regards,

Viktor

-- 
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/86c7b388-fe88-40f1-ac60-6288c72312c6n%40googlegroups.com.

How to create a pypi distribution ?

[Viktor Ransmayr]

Hello Edward & Community,

Has anyone tried to create a pypi distribution of Leo following the 
description in GitHub issue #3837 ?

When I try to follow the description I already fail during Step 1 !

* I start with an up to date version of Leo's devel branch.
* The only change I make is to change the version tag of Leo in '
PKG-INFO.TXT'.
* When I run the 'build_leo.py' script I immediately receive the following 
traceback:

###

(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
leo.scripts.build_leo
build_leo.py
Traceback (most recent call last):
  File "", line 198, in _run_module_as_main
  File "", line 88, in _run_code
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/scripts/build_leo.py", line 26, 
in 
assert os.path.exists(dist_dir), dist_dir
AssertionError: /home/user/PyVE/GitHub/Leo/leo-editor/dist
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 

###

The assertion ~ flags ~ "/home/user/PyVE/GitHub/Leo/leo-editor/dist" - but 
- should it not check for "/home/user/PyVE/GitHub/Leo/leo-editor/leo/dist" ?

What am I missing ?

With kind regards,

Viktor

-- 
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/236a23b6-2eae-42a4-be86-e050ef4118f9n%40googlegroups.com.

Re: Leo 6.8.0 b1 will be delayed at least one week

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Donnerstag, 30. Mai 2024 um 13:04:30 UTC+2:

On Thursday, May 30, 2024 at 5:43:12 AM UTC-5 Edward K. Ream wrote:

Thomas has just discovered a serious recent error in Leo's read code. See 
#3957 .

The fix may be straightforward, but it must be tested for at least one week.


Still true. Happily, the error was less serious than I thought at first.

PR #3958 simply removes 
a do-nothing statement and relocates a comment.

Nevertheless, I think an extra week of testing is still justified.


Leo's devel branch is working w/o any (immediate) issues for me in a Debian 
12 & Fedora 39 VM !

>From my POV the advantage of this beta would have been to also get an early 
feedback on the Leo @ PyPI status.

Are there any reason (other than the inherent effort of creating it), why 
you are concerned of doing a pre-release to PyPI earlier ?

With kind regards,

Viktor

-- 
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/936b1403-4954-42ef-b0d5-664eb306e1cen%40googlegroups.com.

Re: The improved restart-leo command

[Viktor Ransmayr]

Hello Thomas,

Thanks a lot for your response.

Am Mi., 22. Mai 2024 um 20:02 Uhr schrieb Thomas Passin :

> What directory are you running the tests from?


As documented in the logs I'm running the tests in both PyVEs out of  "
~/PyVE/GitHub/Leo/leo-editor/leo/"

> Unless you set the right one using PYTHONPATH, you have to be in the
> *leo-editor*   directory to be able to find *leo.core.xxx*, etc.
>

I was not aware, that I have to start the unittests from the top-level
directory & not from within  ...

I did re-run the unittests from "~/PyVE/GitHub/Leo/leo-editor/" - and -
everything's working fine.

Sorry for the noise !

With kind regards,

Viktor

-- 
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/CAAeSrG%2Bw1gitRAyU-aimjHAiuFO6TyL8vp6vA2o2HBc%3D6LvAYQ%40mail.gmail.com.

Re: The improved restart-leo command

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 21. Mai 2024 um 14:07:12 UTC+2:

PR #3922  significantly 
improves Leo's restart-leo command. The command now uses the command-line 
arguments in effect when Leo started.

I have tested the latest version of Leo's devel branch in a dedicated 
Debian & Fedora VM.

The command is working fine in both !

However & FYI: When I run Leo's unit tests in both VMs I receive 43 
identical / similar errors:


   - See "Log-001" for UT @ Debian & "Log-002" for UT @ Fedora


With kind regards,

Viktor

### Log-001

(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ cd leo
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor/leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor/leo$ 
python3 -m unittest
EEE
==
ERROR: external.npyscreen 
(unittest.loader._FailedTest.external.npyscreen)
--
ImportError: Failed to import test module: external.npyscreen
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 440, in 
_find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in 
_get_module_from_name
__import__(name)
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/external/npyscreen/__init__.py", 
line 8, in 
from .wgwidget  import TEST_SETTINGS, 
ExhaustedTestInput, add_test_input_from_iterable, add_test_input_ch
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/external/npyscreen/wgwidget.py", 
line 21, in 
from leo.core import leoGlobals as g
ModuleNotFoundError: No module named 'leo'

< content deleted >

--
Ran 43 tests in 0.003s

FAILED (errors=43)
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor/leo$ 

### Log-002

(Leo) [user@fedora-leo-study-vm leo-editor]$ 
(Leo) [user@fedora-leo-study-vm leo-editor]$ cd leo
(Leo) [user@fedora-leo-study-vm leo]$ 
(Leo) [user@fedora-leo-study-vm leo]$ python -m unittest
EEE
==
ERROR: external.npyscreen 
(unittest.loader._FailedTest.external.npyscreen)
--
ImportError: Failed to import test module: external.npyscreen
Traceback (most recent call last):
  File "/usr/lib64/python3.12/unittest/loader.py", line 427, in 
_find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib64/python3.12/unittest/loader.py", line 337, in 
_get_module_from_name
__import__(name)
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/external/npyscreen/__init__.py", 
line 8, in 
from .wgwidget  import TEST_SETTINGS, 
ExhaustedTestInput, add_test_input_from_iterable, add_test_input_ch
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/external/npyscreen/wgwidget.py", 
line 21, in 
from leo.core import leoGlobals as g
ModuleNotFoundError: No module named 'leo'

< content deleted >

--
Ran 43 tests in 0.002s

FAILED (errors=43)
(Leo) [user@fedora-leo-study-vm leo]$ 

 

-- 
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/459f41d5-28c7-4152-99dc-d17d87e941cbn%40googlegroups.com.

Re: Leo from GitHub in a PyVE on Debian ?

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Donnerstag, 16. Mai 2024 um 03:30:52 UTC+2:

The PR has been merged into the devel branch.  Update your clone repo and 
you should be good to go.

 
Thanks a lot, your PR has resolved the issue !
 

There is a possibility that on some Linux systems you have to install  
*python3-enchant* using operating system installer.  Debian is one of them, 
I think.  So (untested) on debian-based distros:

sudo apt-get install python3-enchant


This was not necessary for my PyVE of Leo's GitHub version ...
 

The reason is that on Windows the binary files needed are included in the 
PyPi install of pyenchant, but on Linux you have to install a system .so 
library and get it hooked up to the Python code.  The system's package does 
all that.  There's probably something similar for non-Debian-based distros.
On Wednesday, May 15, 2024 at 6:52:48 PM UTC-4 Thomas Passin wrote:

I just created a PR to fix this bug.

On Wednesday, May 15, 2024 at 6:33:36 PM UTC-4 Thomas Passin wrote:

I'm getting a better idea of what may be going on.  Leo's spell checker 
tries to load the pyenchant module (which contains a speller and some word 
dictionaries). If that is not available, then the code branches to the code 
with the bug.  On Linux, in this condition, Leo did open its GUI window but 
it was very small.  When I expanded it an empty outline was displayed, 
although it was called "workbook".

When I fixed the bug by deleting the ".d", and made sure that enchant was 
not available, then Leo opened normally, although it did not have a 
spell-checking tab, which makes sense.

Perhaps pyenchant is not available for the Mac Python distribution?  It can 
be checked for by by activating your venv and issuing the command

python3 -m pip list |grep "pyenchant".


It was already available - See log below: 

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ python3 -m pip list | 
grep "pyenchant"
pyenchant 3.2.2
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 

I double-checked WHY - and - found out that it is part of Leo's required 
packages - See

* https://github.com/leo-editor/leo-editor/blob/devel/requirements.txt
 

If it's listed then open a Python interpreter session and try to import it:

import enchant  # Not a typo - right name is "enchant", not "pyenchant"

If it's not there, you can search on line to see if it can be obtained for 
the Mac.  In the meantime you can get Leo working right by finding the 
python file named in the error message, finding that line, and deleting the 
characters ".d".  Save the file.  Leo should then run correctly.


On Wednesday, May 15, 2024 at 5:34:11 PM UTC-4 Thomas Passin wrote:



AttributeError: 'DefaultDict' object has no attribute 'd'


Funny, that looks like a bug in the devel branch that was fixed already. 


Once again : Thanks a lot for resolving this issue !

With kind regards,

Viktor
 

-- 
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/c239baa3-e6f0-42bb-909c-b187ea598365n%40googlegroups.com.

Re: Leo from GitHub in a PyVE on Debian ?

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Mittwoch, 15. Mai 2024 um 20:57:02 UTC+2:

On Wednesday, May 15, 2024 at 2:33:08 PM UTC-4 viktor@gmail.com wrote:

Hello Thomas,
[snip]


  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/commands/spellCommands.py", line 
185, in __init__
g.app.spellDict = DefaultDict().d  # 2024/04/09: bug fix.
  ^^^

AttributeError: 'DefaultDict' object has no attribute 'd'


Funny, that looks like a bug in the devel branch that was fixed already. 

Strange, but the version of the devel branch you are running is not the 
current one, and I can't even find yours on Github.  The current commit 
is eef303a2d0fc1e41634376058fa5ace2ac9fad95.  Try updating your clone, or 
downloading a zip of the current version of the devel branch and using that 
one.


I did what you said - but - no change : -( - See log !

I'll call it a day for now - and - will restart tomorrow morning ...

With kind regards,

Viktor

### New Log

 user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo/
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ cd leo-editor/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ git branch
* devel
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ git pull
remote: Enumerating objects: 88, done.
remote: Counting objects: 100% (76/76), done.
remote: Compressing objects: 100% (19/19), done.
remote: Total 50 (delta 44), reused 37 (delta 31), pack-reused 0
Unpacking objects: 100% (50/50), 5.44 KiB | 67.00 KiB/s, done.
From https://github.com/leo-editor/leo-editor
   fb85027ea..eef303a2d  devel-> origin/devel
   18f9164ec..01d9dda87  ekr-3871-search-settings -> 
origin/ekr-3871-search-settings
 * [new branch]  ekr-3910-no-fl-ns-plugins -> 
origin/ekr-3910-no-fl-ns-plugins
 * [new branch]  ekr-3912-MacOs-crash -> 
origin/ekr-3912-MacOs-crash
   fb85027ea..eef303a2d  gh-pages -> origin/gh-pages
Updating fb85027ea..eef303a2d
Fast-forward
 leo/config/leoSettings.leo |   2 +-
 leo/core/leoCache.py   |  28 +-
 leo/core/leoFileCommands.py|   4 -
 leo/core/leoFrame.py   |   4 +-
 leo/core/leoTokens.py  |  11 +-
 leo/doc/leoAttic.txt   | 115 ++
 leo/plugins/free_layout.py |  33 +-
 leo/plugins/nested_splitter.py |   8 +-
 leo/plugins/qt_frame.py|   2 +-
 leo/plugins/viewrendered.py| 837 
+++--
 10 files changed, 550 insertions(+), 494 deletions(-)
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
leo.core.runLeo --version
Leo 6.7.9-devel, devel branch, build eef303a2d0
2024-05-14 07:59:14 -0500
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
leo.core.runLeo
setting leoID from os.getenv('USER'): 'user'
Leo 6.7.9-devel, devel branch, build eef303a2d0
2024-05-14 07:59:14 -0500
Python 3.11.2, PyQt version 6.7.0
linux
Can not load session
Traceback (most recent call last):

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line 
2307, in doPostPluginsInit
g.app.sessionManager.load_session(c1, aList)

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoSessions.py", 
line 72, in load_session
g.openWithFileName(fn, gui=g.app.gui, old_c=c)

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoGlobals.py", 
line 3238, in openWithFileName
return g.app.loadManager.openWithFileName(fileName, gui, old_c)
   

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line 
3010, in openWithFileName
return lm.openExistingLeoFile(file_name, gui, old_c)
   ^

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line 
3209, in openExistingLeoFile
c = g.app.newCommander(
^^^

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line 
1516, in newCommander
c = leoCommands.Commands(fileName,
^^

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoCommands.py", 
line 165, in __init__
c.finishCreate()  # Slightly slow.


  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoCommands.py", 

Re: Leo from GitHub in a PyVE on Debian ?

[Viktor Ransmayr]

Hello Thomas,

Am Mi., 15. Mai 2024 um 15:28 Uhr schrieb Thomas Passin :

> It's hard for me to know what you want to convey with these long
> transcripts.
>

I'm sorry !

I just realized right now , that Gmail did not keep' my selection of
"Courier New" for all parts of the logs.


> It would be better if they were edited, or at least if you would point out
> results that you don't like or don't understand.
>

Again sorry, if my msg / point was not clear enough - but - I thought I had
state it ...

"""
I'd like to understand, why the case of 'Leo from GitHub in a PyVE' is no
longer working ?  - It has worked on Linux (Debian & Fedora) up until Leo
version 6.7.7 (maybe evern 6.7.8) !
"""


> But I can see a few things, I think:
>
> 1. Installing Leo's dependencies using pip -r requirements.txt does not
> install Leo itself.  It does not create those scripts in the venv's bin
> directory.  It only installs the modules and packages that Leo needs.  You
> have to install Leo using pip for that (while the venv is active).  For
> example, in my "leo" venv, which has Leo's dependencies but into which I
> haven't installed leo using pip, there is no *leo* script:
>
> (leo) tom@thomas-xubuntu-VirtualBox:~/venv$ ls leo/bin/ |grep "leo"
> # there was no result
>

Yes, that confirms, what I stated in my logs as well.


> 2. Using python3 -m leo.core.runLeo, when you have cd'ed to your github's
> leo-editor directory, finds Leo's files because Python starts looking for
> files starting at the current directory.  If you export the PYTHONPATH
> shell variable, then Python will start by looking there.  That's why I
> recommend using a script that sets the variable.  Then you don't have to
> remember to cd to the right directory first.
>

Thanks, that was new / unkown to me - and - explains what I reported in the
previous "Log-003".


> 3. Even after you have activated your venv, the shell will not find its
> *leo* script because there isn't one. It won't be there unless you
> pip-install Leo while the venv is activated. The results from running
> *which* show that.  You could also use *whereis*, and get the same
> result.  Even if you installed Leo in the venv and started Leo using the
> venv's *leo* script, Leo would be using the Leo code in the venv, not the
> code in your github repo.
>

Could / should Leo's documentation be improved ? - I did exactly what it
says [1] now.


> 4. Your transcript shows that Leo started when you had cd'ed to its repo
> directory.  But I can only see Leo's startup output to the console. That
> output looks normal.  But it doesn't tell me if the Leo window actually
> opened and worked.  Did it?
>

No !

If I move down into "~/PyVE/GitHub/Leo/leo-editor"  - and - try to 'really'
run Leo, it fails with the following traceback - See "Log-001".

With kind regards,

Viktor

---

[1]
https://leo-editor.github.io/leo-editor/installing.html#installing-leo-from-github

### Log-001

user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo/
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ cd leo-editor/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m
leo.core.runLeo &
[1] 878
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ setting leoID
from os.getenv('USER'): 'user'
Leo 6.7.9-devel, devel branch, build fb85027eac
2024-05-13 16:10:23 -0500
Python 3.11.2, PyQt version 6.7.0
linux
Can not load session
Traceback (most recent call last):

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line
2307, in doPostPluginsInit
g.app.sessionManager.load_session(c1, aList)

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoSessions.py",
line 72, in load_session
g.openWithFileName(fn, gui=g.app.gui, old_c=c)

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoGlobals.py", line
3238, in openWithFileName
return g.app.loadManager.openWithFileName(fileName, gui, old_c)
   

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line
3010, in openWithFileName
return lm.openExistingLeoFile(file_name, gui, old_c)
   ^

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line
3209, in openExistingLeoFile
c = g.app.newCommander(
^^^

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoApp.py", line
1516, in newCommander
c = leoCommands.Commands(fileName,
^^

  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoCommands.py",
line 165, in __init__
c.finishCreate()  # Slightly slow.


  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/leoCommands.py",
line 467, in finishCreate
c.frame.log.finishCreate()

  File 

Re: Leo from GitHub in a PyVE on Debian ?

[Viktor Ransmayr]

Hello Thomas,

Thanks a lot for all the feedback & input you provided ! - I will read them 
one by one ...

tbp1...@gmail.com schrieb am Dienstag, 14. Mai 2024 um 20:05:10 UTC+2:

It can be hard to be sure what the Python search path is.  Here is what 
shows up for my system when I have activated my "Leo" VE.  This VE (on 
Windows) is contained in the directory  C:\Tom\venvs\leo. Note that on 
Windows you don't have to source the script.


Please bear with me a bit longer, as I'm sometimes stubborn ;-)

I'd like to understand, why the case of 'Leo from GitHub in a PyVE' is no 
longer working ?  - It has worked on Linux (Debian & Fedora) up until Leo 
version 6.7.7 (maybe evern 6.7.8) !

I'd like to do that, before creating an **additional personal** script, 
since I still believe it should be part of Leo's GitHub repository ...

I did use your advice to check  Python's search path, etc. - Here are the 
results for the three relevant cases in my Debian 12 VM:

* Check out Python's search path with Leo outside of any PyVE - See 
"Log-001".
* Check out search path in Leo's PyVE from PyPI - See "Log-002".
* Check out search path in Leo's PyVE from GitHub - See "Log-003".

Note 1: The first variation is necessary for me to address Leo-Integ issue 
# 299 .

Note 2: The answer to my question has to do with the fact that no 'leo' 
module is found in '/home/user/PyVE/GitHub/Leo/bin'  - See "Log-003" ...

With kind regards,

Viktor

### Log-001

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ python3 -c "import 
sys;print('\n'.join(sys.path))"

/usr/lib/python311.zip
/usr/lib/python3.11
/usr/lib/python3.11/lib-dynload
/home/user/.local/lib/python3.11/site-packages
/usr/lib/python3/dist-packages
/usr/lib/python3.11/dist-packages
user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ python3 -m leo.core.runLeo --version
Leo 6.7.8
Python 3.11.2
linux
user@debian-leo-study-vm:~$ which leo
/home/user/.local/bin/leo
user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ echo $PATH

/home/user/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
user@debian-leo-study-vm:~$ 

### Log-002

user@debian-leo-study-vm:~$ cd PyVE/PyPI/Leo/
user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ python3 -c "import 
sys;print('\n'.join(sys.path))"

/usr/lib/python311.zip
/usr/lib/python3.11
/usr/lib/python3.11/lib-dynload
/home/user/PyVE/PyPI/Leo/lib/python3.11/site-packages
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ python3 -m 
leo.core.runLeo --version
Leo 6.7.8
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ which leo
/home/user/PyVE/PyPI/Leo/bin/leo
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ echo $PATH

/home/user/PyVE/PyPI/Leo/bin:/home/user/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 

### Log-003

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ python3 -c "import 
sys;print('\n'.join(sys.path))"

/usr/lib/python311.zip
/usr/lib/python3.11
/usr/lib/python3.11/lib-dynload
/home/user/PyVE/GitHub/Leo/lib/python3.11/site-packages
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ python3 -m 
leo.core.runLeo --version
/home/user/PyVE/GitHub/Leo/bin/python3: Error while finding module 
specification for 'leo.core.runLeo' (ModuleNotFoundError: No module named 
'leo')
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ which leo
/home/user/.local/bin/leo
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ cd leo-editor/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
leo.core.runLeo --version
Leo 6.7.9-devel, devel branch, build fb85027eac
2024-05-13 16:10:23 -0500
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ which leo
/home/user/.local/bin/leo
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ echo $PATH

/home/user/PyVE/GitHub/Leo/bin:/home/user/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
(Leo) 

Re: Leo from GitHub in a PyVE on Debian ?

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Dienstag, 14. Mai 2024 um 16:03:20 UTC+2:

I wonder whether you VE activation somehow got lost during this process.  I 
noticed this:

~$ which leo
/home/user/.local/bin/leo

This says that typing "leo" uses that script, which is not one in the VE.  
Try this, and let us know what happens -

First, activate your VE environment.  Then issue

python3 -m leo.core.runLeo --version

You should get something like this:

Leo 6.7.9-devel, ekr-3892-vr-pane branch, build 8ede3fc77e
2024-05-14 05:12:23 -0500
Python 3.11.6
linux


Thanks a lot for your feedback ! - This is what the command returns in the 
first place:

user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo/
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ python3 -m 
leo.core.runLeo --version
/home/user/PyVE/GitHub/Leo/bin/python3: Error while finding module 
specification for 'leo.core.runLeo' (ModuleNotFoundError: No module named 
'leo')
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 

Only if I move a directory 'down' the command works:

(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ cd leo-editor/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
leo.core.runLeo --version
Leo 6.7.9-devel, devel branch, build fb85027eac
2024-05-13 16:10:23 -0500
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 

I guess some more ' reading' on my side is needed ...

With kind regards,

Viktor

-- 
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/9068145d-e1f6-423d-a7de-652681f49459n%40googlegroups.com.

Leo from GitHub in a PyVE on Debian ?

[Viktor Ransmayr]

Hello everyone,

Today I have started again to check out the status of Leo (devel branch) 
from GitHub within a Debian 12 VM.

I believe that I did follow the (new) recommended steps for Leo, i.e.:

* Created a new PyVE for Leo from GitHub - OK - See "Log-001".
* Installed Leo from GitHub from scratch - Not OK - See "Log-002".

Has anybody else tried such a setup - and / or - does anyone of you have an 
explanation what is going wrong / what I'm missing ?

If I try the same in a similar environment, with Leo using pip from PyPI, I 
get the following status, which I'd have expected in a similar fashion also 
for the setup from GitHub - See "Log-003".

Thanks a lot for any kind of feedback !

With kind regards,

Viktor

### Log-001

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ cd PyVE/GitHub/
user@debian-leo-study-vm:~/PyVE/GitHub$ 
user@debian-leo-study-vm:~/PyVE/GitHub$ rm -rf Leo
user@debian-leo-study-vm:~/PyVE/GitHub$ 
user@debian-leo-study-vm:~/PyVE/GitHub$ python3 -m venv Leo
user@debian-leo-study-vm:~/PyVE/GitHub$ 
user@debian-leo-study-vm:~/PyVE/GitHub$ cd Leo/
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 

### Log-002

(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ git clone 
https://github.com/leo-editor/leo-editor.git
Cloning into 'leo-editor'...
remote: Enumerating objects: 232512, done.
remote: Counting objects: 100% (848/848), done.
remote: Compressing objects: 100% (241/241), done.
remote: Total 232512 (delta 625), reused 783 (delta 607), pack-reused 
231664
Receiving objects: 100% (232512/232512), 237.68 MiB | 3.88 MiB/s, done.
Resolving deltas: 100% (184943/184943), done.
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ cd leo-editor/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ git branch
* devel
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
pip list
PackageVersion
-- ---
pip23.0.1
setuptools 66.1.1
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python3 -m 
pip install -r requirements.txt
Ignoring Send2Trash: markers 'platform_system == "Windows"' don't match 
your environment
Ignoring windows-curses: markers 'platform_system == "Windows"' don't 
match your environment
Collecting mypy
  Using cached 
mypy-1.10.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl 
(12.6 MB)
Collecting mypy-extensions
  Using cached mypy_extensions-1.0.0-py3-none-any.whl (4.7 kB)
Collecting ruff
  Using cached 
ruff-0.4.4-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (8.7 MB)
Collecting typing_extensions
  Using cached typing_extensions-4.11.0-py3-none-any.whl (34 kB)
Collecting types-docutils
  Using cached types_docutils-0.21.0.20240423-py3-none-any.whl (27 kB)
Collecting types-Markdown
  Using cached types_Markdown-3.6.0.20240316-py3-none-any.whl (18 kB)
Collecting types-paramiko
  Using cached types_paramiko-3.4.0.20240423-py3-none-any.whl (33 kB)
Collecting types-PyYAML
  Using cached types_PyYAML-6.0.12.20240311-py3-none-any.whl (15 kB)
Collecting types-requests
  Using cached types_requests-2.31.0.20240406-py3-none-any.whl (15 kB)
Collecting types-six
  Using cached types_six-1.16.21.20240513-py3-none-any.whl (15 kB)
Collecting asttokens
  Using cached asttokens-2.4.1-py2.py3-none-any.whl (27 kB)
Collecting beautifulsoup4
  Using cached beautifulsoup4-4.12.3-py3-none-any.whl (147 kB)
Collecting black
  Using cached 
black-24.4.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl 
(1.8 MB)
Collecting docutils
  Using cached docutils-0.21.2-py3-none-any.whl (587 kB)
Collecting flexx
  Using cached flexx-0.8.4-py2.py3-none-any.whl (351 kB)
Collecting markdown
  Using cached Markdown-3.6-py3-none-any.whl (105 kB)
Collecting matplotlib
  Using cached 
matplotlib-3.8.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl 
(11.6 MB)
Collecting meta
  Using cached meta-1.0.2-py3-none-any.whl
Collecting numpy
  Using cached 
numpy-1.26.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl 
(18.3 MB)
Collecting pyenchant
  Using cached pyenchant-3.2.2-py3-none-any.whl (55 kB)
Collecting pyflakes
  Using cached pyflakes-3.2.0-py2.py3-none-any.whl (62 kB)
Collecting pytest
  Using cached pytest-8.2.0-py3-none-any.whl (339 kB)
Collecting pytest-cov
  Using cached 

Re:  LeoJS Beta 0.2.13 Released

[Viktor Ransmayr]

Hello Edward,

Am Di., 30. Apr. 2024 um 16:46 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Monday, April 29, 2024 at 9:41:57 AM UTC-5 Edward K. Ream wrote:
>
> This release of LeoJS is a personal milestone. I shall work on the
> remaining *desktop* issues using LeoJS!
>
>
> I can now recommend LeoJS without reservation! LeoJS supports all of Leo's
> essential features enhanced with vs-code's stupendous capabilities.
>

I'd agree to your statement, if #80
 would have been addressed
already.

IMO Leo's essential features include / require the ability to create rST -
and / or - sphinx documents.

With kind regards,

Viktor

-- 
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/CAAeSrGKnE30ucnZkKGBtHVZnGCj6yxQEHAewH%2Bh3MRAm%2Bwmz4A%40mail.gmail.com.

Re:  LeoJS Beta 0.2.13 Released

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Dienstag, 30. April 2024 um 01:22:18 UTC+2:

Victor and Thomas (and other vscodium users)

As you can see from this link, https://open-vsx.org/extension/boltex/leojs 
the new version was successfully deployed on open-vsx, at around the same 
time I deployed it to Microsoft's marketplace.  

 
Yes, I was aware of that.
 

Not sure here, but I think the 'auto update' of vscodium's extensions might 
require a restart of vscodium. Even if you just opened it. (at startup it 
will detect a new version and download it but it will not 'restart' the 
extension with the new version.) The regular vscode also does that, but it 
does automatically update them. It's just that it needs to restart once it 
detects that a new version is available after boot up.


What was unexpected to me is that VSCodium did not notify me about the 
available update of the extension.

What ( I think ) I did, is that I had to explicitly search for 'leo' in the 
extension view - and - only then it did show the notification & allowed me 
to install the update ...

And you are right that an explicit restart of VSCodium instance IS required 
- but - at least I did not have to re-install LeoJS as Thomas has reported.

I'll look into the exact behavior details of VSCodium, when you publish the 
next version of LeoJS.
 

... Or, maybe vscodium needs their extensions to be manually updated when a 
new version is published on their market. I'm not sure because I've never 
used  vscodium personally.

I've just made a quick google search and it seems to be many issues and 
tickets about vscodium not automatically updating extensions that have 
newer versions available. 

Hope this helps...


Thanks a lot for your feedback & support !

Viktor
 

-- 
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/3687c9a9-b319-479d-9022-951f835d4fc2n%40googlegroups.com.

Re:  LeoJS Beta 0.2.13 Released

[Viktor Ransmayr]

Hello Felix,

Same situation as reported by Thomas for me as well.

That is my VSCodium (version 1.88.1) instance running w/i a Fedora-39 VM 
does  not get notified about new versions of LeoJS.

tbp1...@gmail.com schrieb am Montag, 29. April 2024 um 13:52:36 UTC+2:

Nice work and nice graphics!  VSCodium on my system doesn't know about this 
new version yet, I've still got 0.2.11.


I noticed this already when you announced LeoJS 0.2.12 - but - thought it 
was a local issue on my side, since I was in the midst of upgrading from 
Qubes OS 4.1 to 4.2 ...

Let me know if you need further info about my environment details !

With kind regards,

Viktor

-- 
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/9be43fe7-fbe2-438b-be36-d4aeefec5dd0n%40googlegroups.com.

Re: Eight more PRs merged into devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Donnerstag, 11. April 2024 um 12:30:10 UTC+2:

On Thursday, April 11, 2024 at 5:25:03 AM UTC-5 Edward K. Ream wrote:

Eight recent PRs complete all planned work involving Leo's annotations.


I doubt that the improved annotations will have much effect on LeoJS. After 
all, Typescript encourages stricter annotations than Python does.

The last thing I want is for the recent work to delay LeoJS 1.0!


I have reported a problem, when trying to update 
"leo-editor/leo-editor:devel" in my environment. - See

* https://groups.google.com/g/leo-editor/c/WK51V8i6-1Y/m/JUDU_47OAAAJ

With the new simplified installation process from Leo 6.7.8 in place, I do 
have another ~ simple ~ question:

*Is it safe to perform a 'git pull ...' operation*

*-OR - *

*is it always required to start with a 'git clone ...' & a subsequent 'pip 
install -r requirements.txt' operation ?*

With kind regards,

Viktor

-- 
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/f3ba87c5-4ebc-42f7-babc-d2e630bf35b9n%40googlegroups.com.

Re: Two more PRs merged into devel

[Viktor Ransmayr]

Hello Edward,

On Wed, 10 Apr 2024, 11:34 Viktor Ransmayr, 
wrote:

> ...
> Viktor Ransmayr schrieb am Mittwoch, 10. April 2024 um 10:04:58 UTC+2:
>
> ...
>
> Edward K. Ream schrieb am Mittwoch, 10. April 2024 um 08:01:25 UTC+2:
>
> ...
>
>
> *Summary*
>
>
> These two PRs are a milestone in Leo's history. Most of Leo's objects are
> now correctly annotated!!
>
>
> I have carefully tested the bug fixes. Please do the same :-)
>
>
> I have tried to install latest version of "leo-editor/leo-editor:devel"
> into a dedicated PyVE inside of a Fedora 39 VM.
>
> I'm able to install the dependencies from 'requirements.txt' - but - I'm
> running again into the issue that 'leo' is NOT found ...
>
> ###
>
> ...
>
> ###
>
> I've also checked the last two commit messages for 'pyroject.toml' ...
>
> * Add [project.scripts] section. Add .post3 suffix
> *
> https://github.com/leo-editor/leo-editor/commit/f9d4cb2673dc741c090a7b5a6b858b9e569b
> * Change version to 6.7.9.a1. Complete build_leo.py
> *
> https://github.com/leo-editor/leo-editor/commit/031c9ae572b3ce1b667041134870747325b40392
>
> ... but could not find / see any obvious explanation.
>
>
> For completeness I also verified that this problem does exist outside of a
> PyVE as well. - It does:
>
> ###
>
> ...
>

> ###
>

Shall I create a GitHub issue for this issue ?

With kind regards

Viktor

-- 
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/CAAeSrGJfJ8j%2BkNFMxZy6HuEJUaLc%2BPdgZrTsfyYH2FUL%3DQucXQ%40mail.gmail.com.

Re: Two more PRs merged into devel

[Viktor Ransmayr]

Hello Edward,

Viktor Ransmayr schrieb am Mittwoch, 10. April 2024 um 10:04:58 UTC+2:

Hello Edward,

Edward K. Ream schrieb am Mittwoch, 10. April 2024 um 08:01:25 UTC+2:

...


*Summary*


These two PRs are a milestone in Leo's history. Most of Leo's objects are 
now correctly annotated!!


I have carefully tested the bug fixes. Please do the same :-)


I have tried to install latest version of "leo-editor/leo-editor:devel" 
into a dedicated PyVE inside of a Fedora 39 VM.

I'm able to install the dependencies from 'requirements.txt' - but - I'm 
running again into the issue that 'leo' is NOT found ...

###

...
Installing collected packages: tk, snowballstemmer, 
PyQt6-WebEngine-Qt6, PyQt6-Qt6, pscript, meta, dialite, webruntime, 
urllib3, typing_extensions, types-six, types-PyYAML, types-Markdown, 
types-docutils, tornado, sphinxcontrib-serializinghtml, 
sphinxcontrib-qthelp, sphinxcontrib-jsmath, sphinxcontrib-htmlhelp, 
sphinxcontrib-devhelp, sphinxcontrib-applehelp, soupsieve, six, ruff, 
PyQt6-sip, Pygments, pyflakes, pyenchant, pycparser, pluggy, platformdirs, 
pathspec, packaging, mypy-extensions, MarkupSafe, iniconfig, imagesize, 
idna, docutils, coverage, click, charset-normalizer, certifi, babel, 
alabaster, types-requests, requests, pytest, PyQt6, mypy, Jinja2, flexx, 
cffi, black, beautifulsoup4, asttokens, sphinx, pytest-cov, 
PyQt6-WebEngine, PyQt6-QScintilla, cryptography, types-paramiko
Successfully installed Jinja2-3.1.3 MarkupSafe-2.1.5 PyQt6-6.6.1 
PyQt6-QScintilla-2.14.1 PyQt6-Qt6-6.6.3 PyQt6-WebEngine-6.6.0 
PyQt6-WebEngine-Qt6-6.6.3 PyQt6-sip-13.6.0 Pygments-2.17.2 alabaster-0.7.16 
asttokens-2.4.1 babel-2.14.0 beautifulsoup4-4.12.3 black-24.3.0 
certifi-2024.2.2 cffi-1.16.0 charset-normalizer-3.3.2 click-8.1.7 
coverage-7.4.4 cryptography-42.0.5 dialite-0.5.3 docutils-0.20.1 
flexx-0.8.4 idna-3.6 imagesize-1.4.1 iniconfig-2.0.0 meta-1.0.2 mypy-1.9.0 
mypy-extensions-1.0.0 packaging-24.0 pathspec-0.12.1 platformdirs-4.2.0 
pluggy-1.4.0 pscript-0.7.7 pycparser-2.22 pyenchant-3.2.2 pyflakes-3.2.0 
pytest-8.1.1 pytest-cov-5.0.0 requests-2.31.0 ruff-0.3.5 six-1.16.0 
snowballstemmer-2.2.0 soupsieve-2.5 sphinx-7.2.6 
sphinxcontrib-applehelp-1.0.8 sphinxcontrib-devhelp-1.0.6 
sphinxcontrib-htmlhelp-2.0.5 sphinxcontrib-jsmath-1.0.1 
sphinxcontrib-qthelp-1.0.7 sphinxcontrib-serializinghtml-1.1.10 tk-0.1.0 
tornado-6.4 types-Markdown-3.6.0.20240316 types-PyYAML-6.0.12.20240311 
types-docutils-0.20.0.20240406 types-paramiko-3.4.0.20240311 
types-requests-2.31.0.20240406 types-six-1.16.21.20240311 
typing_extensions-4.11.0 urllib3-2.2.1 webruntime-0.5.8
(Leo) [user@fedora-leo-study-vm leo-editor]$ 
(Leo) [user@fedora-leo-study-vm leo-editor]$ leo --version
bash: leo: command not found
(Leo) [user@fedora-leo-study-vm leo-editor]$ 

###

I've also checked the last two commit messages for 'pyroject.toml' ...

* Add [project.scripts] section. Add .post3 suffix 
* 
https://github.com/leo-editor/leo-editor/commit/f9d4cb2673dc741c090a7b5a6b858b9e569b
* Change version to 6.7.9.a1. Complete build_leo.py 
* 
https://github.com/leo-editor/leo-editor/commit/031c9ae572b3ce1b667041134870747325b40392

... but could not find / see any obvious explanation.


For completeness I also verified that this problem does exist outside of a 
PyVE as well. - It does:

###

...
Installing collected packages: tk, snowballstemmer, 
PyQt6-WebEngine-Qt6, PyQt6-Qt6, pscript, meta, dialite, webruntime, 
urllib3, typing_extensions, types-six, types-PyYAML, types-Markdown, 
types-docutils, sphinxcontrib-serializinghtml, sphinxcontrib-qthelp, 
sphinxcontrib-jsmath, sphinxcontrib-htmlhelp, sphinxcontrib-devhelp, 
sphinxcontrib-applehelp, soupsieve, ruff, PyQt6-sip, Pygments, pyflakes, 
pyenchant, pluggy, platformdirs, pathspec, mypy-extensions, iniconfig, 
imagesize, coverage, click, certifi, babel, asttokens, alabaster, 
types-requests, requests, pytest, PyQt6, mypy, flexx, black, 
beautifulsoup4, sphinx, pytest-cov, PyQt6-WebEngine, PyQt6-QScintilla, 
cryptography, types-paramiko
Successfully installed PyQt6-6.6.1 PyQt6-QScintilla-2.14.1 
PyQt6-Qt6-6.6.3 PyQt6-WebEngine-6.6.0 PyQt6-WebEngine-Qt6-6.6.3 
PyQt6-sip-13.6.0 Pygments-2.17.2 alabaster-0.7.16 asttokens-2.4.1 
babel-2.14.0 beautifulsoup4-4.12.3 black-24.3.0 certifi-2024.2.2 
click-8.1.7 coverage-7.4.4 cryptography-42.0.5 dialite-0.5.3 flexx-0.8.4 
imagesize-1.4.1 iniconfig-2.0.0 meta-1.0.2 mypy-1.9.0 mypy-extensions-1.0.0 
pathspec-0.12.1 platformdirs-4.2.0 pluggy-1.4.0 pscript-0.7.7 
pyenchant-3.2.2 pyflakes-3.2.0 pytest-8.1.1 pytest-cov-5.0.0 
requests-2.31.0 ruff-0.3.5 snowballstemmer-2.2.0 soupsieve-2.5 sphinx-7.2.6 
sphinxcontrib-applehelp-1.0.8 sphinxcontrib-devhelp-1.0.6 
sphinxcontrib-htmlhelp-2.0.5 sphinxcontrib-jsmath-1.0.1 
sphinxcontrib-qthelp-1.0.7 sphinxcontrib-serializinghtml-1.1.10 tk-0.1.0 
types-Markdown-3.6.0.20240316 types-PyYAML-6.0.12.20240311 
types-docutils-0.20.0.20240406 types-paramiko-3.4.

Re: Two more PRs merged into devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Mittwoch, 10. April 2024 um 08:01:25 UTC+2:

Both PRs strengthen Leo's mypy annotations.


- PR #3856  completes 
the annotations in leoApp.py.

- PR #3857  completes 
the annotations in leoGlobals.py


The second PR is the big one. Annotating the "g.app" ivar correctly in 
LeoApp.py unblocked mypy! Suddenly, mypy found complaints in dozens of 
other files! The diffs in all the other files arise from this one change.


*Bug fixes*


PR #3857  fixes several 
bugs in addition to adding annotations. See the PR for details. I have 
carefully tested these bug fixes.


*A breaking change*


PR #3857  also removes 
the evil "multiple" kwarg from the runOpenFileDialog method in qt_gui.py. 
This PR adds the runOpenFile*s*Dialog (plural) method. Removing the kwarg 
is a minor breaking change. It was impossible to annotate the original 
method in any helpful way.


*Summary*


These two PRs are a milestone in Leo's history. Most of Leo's objects are 
now correctly annotated!!


I have carefully tested the bug fixes. Please do the same :-)


I have tried to install latest version of "leo-editor/leo-editor:devel" 
into a dedicated PyVE inside of a Fedora 39 VM.

I'm able to install the dependencies from 'requirements.txt' - but - I'm 
running again into the issue that 'leo' is NOT found ...

###

...
Installing collected packages: tk, snowballstemmer, 
PyQt6-WebEngine-Qt6, PyQt6-Qt6, pscript, meta, dialite, webruntime, 
urllib3, typing_extensions, types-six, types-PyYAML, types-Markdown, 
types-docutils, tornado, sphinxcontrib-serializinghtml, 
sphinxcontrib-qthelp, sphinxcontrib-jsmath, sphinxcontrib-htmlhelp, 
sphinxcontrib-devhelp, sphinxcontrib-applehelp, soupsieve, six, ruff, 
PyQt6-sip, Pygments, pyflakes, pyenchant, pycparser, pluggy, platformdirs, 
pathspec, packaging, mypy-extensions, MarkupSafe, iniconfig, imagesize, 
idna, docutils, coverage, click, charset-normalizer, certifi, babel, 
alabaster, types-requests, requests, pytest, PyQt6, mypy, Jinja2, flexx, 
cffi, black, beautifulsoup4, asttokens, sphinx, pytest-cov, 
PyQt6-WebEngine, PyQt6-QScintilla, cryptography, types-paramiko
Successfully installed Jinja2-3.1.3 MarkupSafe-2.1.5 PyQt6-6.6.1 
PyQt6-QScintilla-2.14.1 PyQt6-Qt6-6.6.3 PyQt6-WebEngine-6.6.0 
PyQt6-WebEngine-Qt6-6.6.3 PyQt6-sip-13.6.0 Pygments-2.17.2 alabaster-0.7.16 
asttokens-2.4.1 babel-2.14.0 beautifulsoup4-4.12.3 black-24.3.0 
certifi-2024.2.2 cffi-1.16.0 charset-normalizer-3.3.2 click-8.1.7 
coverage-7.4.4 cryptography-42.0.5 dialite-0.5.3 docutils-0.20.1 
flexx-0.8.4 idna-3.6 imagesize-1.4.1 iniconfig-2.0.0 meta-1.0.2 mypy-1.9.0 
mypy-extensions-1.0.0 packaging-24.0 pathspec-0.12.1 platformdirs-4.2.0 
pluggy-1.4.0 pscript-0.7.7 pycparser-2.22 pyenchant-3.2.2 pyflakes-3.2.0 
pytest-8.1.1 pytest-cov-5.0.0 requests-2.31.0 ruff-0.3.5 six-1.16.0 
snowballstemmer-2.2.0 soupsieve-2.5 sphinx-7.2.6 
sphinxcontrib-applehelp-1.0.8 sphinxcontrib-devhelp-1.0.6 
sphinxcontrib-htmlhelp-2.0.5 sphinxcontrib-jsmath-1.0.1 
sphinxcontrib-qthelp-1.0.7 sphinxcontrib-serializinghtml-1.1.10 tk-0.1.0 
tornado-6.4 types-Markdown-3.6.0.20240316 types-PyYAML-6.0.12.20240311 
types-docutils-0.20.0.20240406 types-paramiko-3.4.0.20240311 
types-requests-2.31.0.20240406 types-six-1.16.21.20240311 
typing_extensions-4.11.0 urllib3-2.2.1 webruntime-0.5.8
(Leo) [user@fedora-leo-study-vm leo-editor]$ 
(Leo) [user@fedora-leo-study-vm leo-editor]$ leo --version
bash: leo: command not found
(Leo) [user@fedora-leo-study-vm leo-editor]$ 

###

I've also checked the last two commit messages for 'pyroject.toml' ...

* Add [project.scripts] section. Add .post3 suffix 
* 
https://github.com/leo-editor/leo-editor/commit/f9d4cb2673dc741c090a7b5a6b858b9e569b
* Change version to 6.7.9.a1. Complete build_leo.py 
* 
https://github.com/leo-editor/leo-editor/commit/031c9ae572b3ce1b667041134870747325b40392

... but could not find / see any obvious explanation.

With kind regards,

Viktor

-- 
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/9c8df6bb-e286-4409-a949-977728b9ab8en%40googlegroups.com.

Re: I just had successful eye surgury

[Viktor Ransmayr]

All the best for your quick recovery !

On Thu, 28 Mar 2024, 21:03 Edward K. Ream,  wrote:

> A vitrectomy
> of
> the rt eye. I'll be limited in what I can do for about a week.
>
> 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/dfd46fc2-1e03-4a4c-98af-93c36ef6c2a7n%40googlegroups.com
> 
> .
>

-- 
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/CAAeSrGJVHeRTnEqWmuKFfaHHRwmnVYJ26oO1-mOCWcyPkLujkA%40mail.gmail.com.

Re: Leo 6.7.8 released to pypi

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Donnerstag, 21. März 2024 um 12:53:13 UTC+1:

Leo 6.7.8.post3 is now available on Leo's pypi page 
.


This version installs leo.exe, leo-c.exe, and leo-console.exe in the 
"Python3.x/scripts" folder. These scripts work for me.


 Leo 6.7.8.post3 is now working as expected in an existing 'venv' w/i a 
Fedora 38 VM !

With kind regards,

Viktor

-- 
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/57215828-9630-4157-af67-eb2876f03cb8n%40googlegroups.com.

Re: Leo 6.7.8.post1 is ready for testing

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 19. März 2024 um 22:39:27 UTC+1:

You can now install Leo *6.7.8.post1* from pypi 
. This "post" release changes only 
distribution-related files. See PR #3835 
 for the details.


The "post1" prefix is required to meet the more stringent pypi naming 
conventions.


Please test the installation process immediately and report your experience.


 I installed Leo 6.7.8.post1 into an existing 'venv' on a Fedora 38 VM - 
but - I could NOT run it using the 'leo' cmd from the shell.

I also tried installing Leo 6.7.8.post1 into a completely new Fedora 38 VM 
w/o using a 'venv' - Same behaviour ...

After I installed Leo 6.7.8.post1 I gathered the following additional info, 
which might help:

[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ python --version
Python 3.11.8
[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ pip --version
pip 22.3.1 from /usr/lib/python3.11/site-packages/pip (python 3.11)
[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ pip list  | grep leo
leo   6.7.8.post1
[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ which leo
/usr/bin/which: no leo in 
(/home/user/.local/bin:/home/user/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)
[user@Test-VM2 ~]$

Please let me know if you need any further info about my environment.

With kind regards,

Viktor

-- 
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/65afdd56-3117-4c4b-a588-7ad753f090acn%40googlegroups.com.

Re: Leo 6.7.8.post1 is ready for testing

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 19. März 2024 um 22:39:27 UTC+1:

You can now install Leo *6.7.8.post1* from pypi 
. This "post" release changes only 
distribution-related files. See PR #3835 
 for the details.


The "post1" prefix is required to meet the more stringent pypi naming 
conventions.


Please test the installation process immediately and report your experience.


 I installed Leo 6.7.8.post1 into an existing 'venv' on a Fedora 38 VM - 
but - I could NOT run it using the 'leo' cmd from the shell.

I also tried installing Leo 6.7.8.post1 into a completely new Fedora 38 VM 
w/o using a 'venv' - Same behaviour ...

After I install Leo 6.7.8.post1 I gathered the following additional info, 
which might help your investigation:

[user@Test-VM2 ~]$ 
[user@Test-VM2 ~]$ python --version
Python 3.11.8
[user@Test-VM2 ~]$ 
[user@Test-VM2 ~]$ pip --version
pip 22.3.1 from /usr/lib/python3.11/site-packages/pip (python 3.11)
[user@Test-VM2 ~]$ 
[user@Test-VM2 ~]$ pip list  | grep leo
leo   6.7.8.post1
[user@Test-VM2 ~]$ 
[user@Test-VM2 ~]$ which leo
/usr/bin/which: no leo in 
(/home/user/.local/bin:/home/user/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)
[user@Test-VM2 ~]$ 

With kind regards,

Viktor

-- 
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/e6341fd2-e2c4-41f9-9ea9-6b74065cd224n%40googlegroups.com.

Re: Leo 6.7.8 released, but not to PyPi

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 15. März 2024 um 11:08:11 UTC+1:

Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on 
GitHub  but *NOT *on pypi 
. I have filed this twine issue 
.

I am enraged by the difficulties of creating a PyPi release. The point of 
this release was to simplify the installation of Leo, but that goal is on 
hold until I can update Leo on PyPi.

Any help you can give would be much appreciated.

 
Until Leo 6.7.7 (including) I was able to install & run Leo *WITHOUT* 
having to manually create a script on the Linux side. - This is no longer 
possible as of Leo 6.7.8 !

As I already explained in a separate message to Felix I'm trying to work 
with separate Python virtual environments (venv's) whenever possible ...

One for GitHub (devel branch), a second one for PyPI (released version) & a 
separate non-venv based one for LeoInteg. - Reason: see 
https://github.com/boltex/leointeg/issues/299

Here is initial 'path' & 'version' info about all three environments in a 
Debian 12 based VM:

### dedicated ~venv~ for GitHub:

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo/
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ which leo
/home/user/PyVE/GitHub/Leo/bin/leo
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ leo --version
Leo 6.7.7-devel, devel branch, build 401a78a10e
2023-12-31 12:42:43 -0600
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 

### dedicated ~venv~ for PyPI:

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ cd PyVE/PyPI/Leo/
user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 
user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ which leo
/home/user/PyVE/PyPI/Leo/bin/leo
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ leo --version
Leo 6.7.6
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 

### user-specific installation for LeoInteg:

user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ which leo
/home/user/.local/bin/leo
user@debian-leo-study-vm:~$ 
user@debian-leo-study-vm:~$ leo --version
Leo 6.7.7
Python 3.11.2
linux
user@debian-leo-study-vm:~$ 

###

I believe it is somewhat related to the differences b/w Leo's source tree / 
directory content when installed from GitHub vs. PyPI.

I hope this provides at least some additional input for your analysis to 
resolve the issue ...

With kind regards,

Viktor
 

-- 
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/edf2bedb-b80c-4d7c-bd7c-ef0b973891a2n%40googlegroups.com.

Re: Discuss: Leo 6.7.8 will install only PyQt6

[Viktor Ransmayr]

Hello Jake,

gates...@gmail.com schrieb am Sonntag, 17. März 2024 um 16:03:24 UTC-4:

My go-to ‘what package do I need’ tool is pkgs.org.  They’re showing that 
the package for Fedora 38 is called xcb-until-cursor.  Linux library 
management leaves much to be desired, in general.

https://pkgs.org/download/libxcb-cursor.so.0()(64bit)

Hope this helps!


That was the missing piece. - Leo is now starting in the newly created 
Fedora 38 Test-VM ...

###

Leo Log Window
Leo 6.7.8, devel branch, build ef60a151f1
2024-03-15 09:30:14 -0500
Python 3.11.8, PyQt version 6.6.2
linux
setting leoID from os.getenv('USER'): 'user'
  home: /home/user
leo-editor: /home/user/leo-editor
  load: /home/user/leo-editor/leo/core
config: /home/user/leo-editor/leo/config
reading settings in /home/user/leo-editor/leo/config/leoSettings.leo
unexpected error creating: None
Traceback (most recent call last):
  File "/home/user/leo-editor/leo/commands/spellCommands.py", line 65, 
in create
f = open(fn, mode='wb')
^^^
TypeError: expected str, bytes or os.PathLike object, not NoneType

###

Thanks a lot for your tip related to the ‘what package do I need’ tool !

This should help me a lot in the future.

With kind regards,

Viktor

-- 
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/e0b87fe6-e809-4bb9-93d0-a1defdddf8cdn%40googlegroups.com.

Re: Discuss: Leo 6.7.8 will install only PyQt6

[Viktor Ransmayr]

Hello Thomas,

Am So., 17. März 2024 um 15:41 Uhr schrieb Thomas Passin <
tbp100...@gmail.com>:

> Try the other suggested library in the error message:  xcb-cursor0 . I
> went through the same thing about a week ago on a different distro, and
> using the alternate suggestion solved it.  If that doesn't work either, run
> an internet search for "fedora qt.qpa.plugin: From 6.5.0, xcb-cursor0 or
> libxcb-cursor0 is needed to load the Qt xcb platform plugin." This may
> surface another library name that your distro has.
>

I tried both libraries ! - See my log ...


> On Sunday, March 17, 2024 at 3:20:17 PM UTC-4 viktor@gmail.com wrote:
>
>> Hello Edward, hello Thomas,
>>
>> tbp1...@gmail.com schrieb am Freitag, 1. März 2024 um 07:32:23 UTC-5:
>>
>> On Friday, March 1, 2024 at 5:33:34 AM UTC-5 Edward K. Ream wrote:
>>
>> My question wasn't clear. I meant to ask whether potential errors
>> concerning the missing xcb-cursor0 or libxcb-cursor0 libraries are a
>> show stopper.
>>
>> Imo, most linux users will know to run sudo apt install, so the missing
>> library isn't a significant barrier to requiring PyQt6. A new FAQ entry
>> might be all that is needed. Do you agree?
>>
>>
>> A year ago I might have said it was a show-stopper.  But now the error
>> message from Ubuntu was clear enough that running its suggested command
>> fixed the issue.  In years past I had to go to the internet and wade
>> through a lot of useless posts to find the right command (I've saved it in
>> my workbook to make it easier to find).  I do know that some non-technical
>> people will read the error message and yet not know what to do, so I agree
>> with a FAQ entry.
>>
>> BTW, Ubuntu/XUbuntu is the only distro where I've encountered this issue
>> so far.
>>
>>
>> I have encountered this problem as well, when I tried to install Leo from
>> the devel-branch into a newly created Fedora 38 VM.
>>
>> When I try to install the mentioned libraries I receive the following
>> error msg:
>>
>> ###
>>
>> [user@Test-VM1 ~]$
>> [user@Test-VM1 ~]$ ./leo &
>> [1] 1513
>> [user@Test-VM1 ~]$ setting leoID from os.getenv('USER'): 'user'
>>
>> qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to
>> load the Qt xcb platform plugin.
>> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even
>> though it was found.
>> This application failed to start because no Qt platform plugin could
>> be initialized. Reinstalling the application may fix this problem.
>>
>> Available platform plugins are: linuxfb, vnc, minimal, wayland-egl,
>> eglfs, vkkhrdisplay, offscreen, wayland, xcb, minimalegl.
>>
>> ./leo: line 2:  1517 Aborted (core dumped) python
>> ~/leo-editor/launchLeo.py $1
>>
>> [1]+  Exit 134./leo
>> [user@Test-VM1 ~]$
>> [user@fedora-38-minimal-vr ~]$ sudo dnf install libxcb-cursor0
>> Last metadata expiration check: 2:19:22 ago on Sun Mar 17 12:29:58
>> 2024.
>> No match for argument: libxcb-cursor0
>> Error: Unable to find a match: libxcb-cursor0
>> [user@fedora-38-minimal-vr ~]$
>> [user@fedora-38-minimal-vr ~]$ sudo dnf install xcb-cursor0
>> Last metadata expiration check: 2:19:56 ago on Sun Mar 17 12:29:58
>> 2024.
>> No match for argument: xcb-cursor0
>> Error: Unable to find a match: xcb-cursor0
>> [user@fedora-38-minimal-vr ~]$
>>
>> ###
>>
>> What am I missing ?
>>
>> With kind regards,
>>
>> Viktor
>>
>>
> --
> 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/a257a7e3-343e-4f9e-bfde-f3c58b9f9b72n%40googlegroups.com
> 
> .
>

-- 
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/CAAeSrGLyR7OSmHatFmn0gQGPHPj_8Ozyi4L9qt7PeKx_OZ%3DBZA%40mail.gmail.com.

Re: Discuss: Leo 6.7.8 will install only PyQt6

[Viktor Ransmayr]

Hello Edward, hello Thomas,

tbp1...@gmail.com schrieb am Freitag, 1. März 2024 um 07:32:23 UTC-5:

On Friday, March 1, 2024 at 5:33:34 AM UTC-5 Edward K. Ream wrote:

My question wasn't clear. I meant to ask whether potential errors 
concerning the missing xcb-cursor0 or libxcb-cursor0 libraries are a show 
stopper.

Imo, most linux users will know to run sudo apt install, so the missing 
library isn't a significant barrier to requiring PyQt6. A new FAQ entry 
might be all that is needed. Do you agree?


A year ago I might have said it was a show-stopper.  But now the error 
message from Ubuntu was clear enough that running its suggested command 
fixed the issue.  In years past I had to go to the internet and wade 
through a lot of useless posts to find the right command (I've saved it in 
my workbook to make it easier to find).  I do know that some non-technical 
people will read the error message and yet not know what to do, so I agree 
with a FAQ entry.

BTW, Ubuntu/XUbuntu is the only distro where I've encountered this issue so 
far.


I have encountered this problem as well, when I tried to install Leo from 
the devel-branch into a newly created Fedora 38 VM.

When I try to install the mentioned libraries I receive the following error 
msg:

###

[user@Test-VM1 ~]$ 
[user@Test-VM1 ~]$ ./leo &
[1] 1513
[user@Test-VM1 ~]$ setting leoID from os.getenv('USER'): 'user'
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to 
load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even 
though it was found.
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.

Available platform plugins are: linuxfb, vnc, minimal, wayland-egl, 
eglfs, vkkhrdisplay, offscreen, wayland, xcb, minimalegl.

./leo: line 2:  1517 Aborted (core dumped) python 
~/leo-editor/launchLeo.py $1

[1]+  Exit 134./leo
[user@Test-VM1 ~]$ 
[user@fedora-38-minimal-vr ~]$ sudo dnf install libxcb-cursor0
Last metadata expiration check: 2:19:22 ago on Sun Mar 17 12:29:58 2024.
No match for argument: libxcb-cursor0
Error: Unable to find a match: libxcb-cursor0
[user@fedora-38-minimal-vr ~]$ 
[user@fedora-38-minimal-vr ~]$ sudo dnf install xcb-cursor0
Last metadata expiration check: 2:19:56 ago on Sun Mar 17 12:29:58 2024.
No match for argument: xcb-cursor0
Error: Unable to find a match: xcb-cursor0
[user@fedora-38-minimal-vr ~]$ 

###

What am I missing ?

With kind regards,

Viktor
 

-- 
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/e40d9168-6f79-4c68-89f9-5509ed1f7ca0n%40googlegroups.com.

Re: PR 3774 completes the 6.7.8 code base

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 2. Februar 2024 um 11:15:08 UTC+1:

PR #3774  is now in 
devel. This PR cleans up Leo's unit tests and fixes a crasher in Leo's new 
beautifier.

The only remaining issue is #3767 
: Distribute Leo only 
on GitHub. The corresponding PR is a work in progress. I'll say more about 
this issue in another post.

*Summary*

Please test devel and report any problems immediately. 

The only remaining changes for 6.7.8 concern distribution.

I'll alert you when the new distribution model is ready for testing.


I tested the latest version of Leo's devel branch inside a Fedora 38 VM

Running the unit tests reveals the following error:

==
FAIL: test_blank_lines_after_function_3 
(unittests.core.test_leoTokens.TestTokenBasedOrange.test_blank_lines_after_function_3)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/core/test_leoTokens.py", 
line 327, in test_blank_lines_after_function_3
self.assertEqual(results, expected)
AssertionError: "\\\n[122 chars]omment 1.\n# Trailing comment 
2.\nprint('3')\n" != "\\\n[122 chars]omment 1.\n# Trailing 
comment 2.\nprint('3')\n"
  \
  def writeAsisNode(self, p):
  print('1')

  def put(s):
  print('2')

  # Trailing comment 1.
  # Trailing comment 2.
- print('3')
+ print('3')
? 


--
Ran 931 tests in 7.797s

FAILED (failures=1, skipped=5)
(Leo) [user@fedora-leo-study-vm leo]$ 


With kind regards,

Viktor
 

-- 
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/70cea672-3905-495f-9390-b46dba0b04ffn%40googlegroups.com.

Re: LeoInteg using Leo's Null GUI ?

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Mittwoch, 24. Januar 2024 um 08:26:44 UTC+1:

On Wed, Jan 24, 2024 at 12:06 AM Viktor Ransmayr wrote:

Viktor, as an experiment, you could try the following:


- git clone leo, that is: git clone 
https://github.com/leo-editor/leo-editor.git

- Create your own version of requirements.txt that omits anything related 
to guis.

- Install the dependencies: pip install -r requirements.txt.


I'll spend some time on the weekend & will report back my results.


 So far I tried out several variations of your proposal - but - did not 
have any success:

* Variation #1: use requirements.txt w/o an '--editable .' entry
* Variation #2: use requirements.txt with '--editable .' as last entry
* Variation #3: use requirements.txt with 'leo == 6.7.7' as last entry

Either the 'leo' package was not included in the install at all - or - the 
'leo' package was added with its 'PyQt' dependencies ...

It is time for me to start reading the 'pip' documentation in detail !

With kind regards,

Viktor

-- 
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/202ad374-037c-44e3-8569-58ee9c63f383n%40googlegroups.com.

Re: LeoInteg using Leo's Null GUI ?

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Mittwoch, 24. Januar 2024 um 08:26:44 UTC+1:

On Wed, Jan 24, 2024 at 12:06 AM Viktor Ransmayr wrote:

Viktor, as an experiment, you could try the following:


- git clone leo, that is: git clone 
https://github.com/leo-editor/leo-editor.git

- Create your own version of requirements.txt that omits anything related 
to guis.

- Install the dependencies: pip install -r requirements.txt.


I'll spend some time on the weekend & will report back my results.


 So far I tried out several variouts - but - did not succeed:

* Variation #1: requirements.txt w/o an '--editable .' entry
* Variation #2: requirements.txt with '--editable .' as last entry
* Variation #3: requirements.txt with 'leo == 6.7.7' as last entry

Either 'leo' was not included at all - or - 'leo' was added with its 'PyQt' 
dependencies.

Not that I used 'setup.py' unchanged ...

It looks like its time for me to start reading the 'pip' documentation in 
detail ;-)

With kind regards,

Viktor

-- 
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/4821e7bb-db61-4a8b-ae8b-47ca164305f8n%40googlegroups.com.

Re: LeoInteg using Leo's Null GUI ?

[Viktor Ransmayr]

Hello Edward,

Am Mo., 22. Jan. 2024 um 21:49 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> > What effort would it be to package a version of Leo providing
> ~everything~ but the GUI?
>
>
> Thanks for this timely question.
>
>
> *tl;dr:* Making things work as I am guessing you would like should be
> straightforward.
>
>
>
>
> *...*
>
> Viktor, as an experiment, you could try the following:
>
>
> - git clone leo, that is: git clone
> https://github.com/leo-editor/leo-editor.git
>
> - Create your own version of requirements.txt that omits anything related
> to guis.
>
> - Install the dependencies: pip install -r requirements.txt.
>

I'll spend some time on the weekend & will report back my results.

Thanks a lot for your detailled feedback !

With kind regards,

Viktor

-- 
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/CAAeSrGKXS1VdUXj%3DpSTbTijHC4bK4AxDHX200-WODE%2BZDnbV4g%40mail.gmail.com.

LeoInteg using Leo's Null GUI ?

[Viktor Ransmayr]

Hello Edward, hello Felix,

Currently whenever I'd like to install LeoInteg on any non-Windows host I 
have to install Leo with PyQt. - This is sometimes quite difficult / tricky 
...

AFAIK LeoInteg  is relying solely on the GUI provided through VS Code.

What effort would it be to package a version of Leo providing ~everything~ 
but the GUI ?

With kind regards,

Viktor

-- 
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/f1c6eee1-81a3-41dd-a401-4492b0a34534n%40googlegroups.com.

Re:  LeoInteg 1.0.17 Released

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Freitag, 29. Dezember 2023 um 00:54:50 UTC+1:

You referring to needing to use *--break-system-packages*, is that right? 


Yes.
 

I don't see this as a Leo issue.  


 It is an issue between 'LeoInteg' & 'Leo', if the underlying Linux distro 
has adopted PEP 668.

This is why addressed both Felix - and - Edward in my initial feedback - 
but - obviously failed to provide the necessary additional context / 
information ...

You are installing Leo into the system's Python install, and the OS is 
touchy about that.  Some package that the OS relies on might get updated in 
an incompatible way as part of the installation of Leo, but the system 
can't know if that will happen.  So it prefers not to install some Python 
packages.  I have seen the same warning myself when trying to install or 
upgrade certain packages.  I can't remember which ones, though.

I didn't even know there was a  *-break-system-packages option. *But it's 
probably not a good idea to use it unless you have some reason to know that 
it would not harm the system.  Overall, a venv would be safer, or, as I 
generally have done, install a different Python version from the system's 
and use that for everything you want to do.


I did not know about this option either ;-)

I only applied it, since it was mentioned in the error msg as a possibly ~ 
dangerous ~ workaround - and - I could not get 'LeoInteg' working together 
with Leo, if Leo is installed in a Python virtual environment (venv).

See my previous answer to Felix. - Have you been able to get 'LeoInteg' 
working in such a setup ?

With kind regards,

Viktor 

-- 
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/17b55639-73d8-4494-bd0f-464f1e47841en%40googlegroups.com.

Re:  LeoInteg 1.0.17 Released

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Freitag, 29. Dezember 2023 um 00:01:48 UTC+1:


...

Concerning the upgrade/installation of Leo itself, It is directly related 
to Leo, and thus you should file an issue with Leo itself if you think this 
can help other users in the future. 


It is not that easy - and - I should have provided this additional context 
/ information already in my initial feedback:

* I can & have installed Leo in a Python virtual environment (venv) - both 
in Debian as well as Fedora Linux VMs.
* What I have not been able to achieve is to configure 'Leo Editor Path' in 
the LeoInteg extension & have it recognize it.
* -> In other words I provide the right location of Leo in the venv - but - 
LeoInteg fails to connect to server !

Fedora 38 so far does not complain about the issue - but - Debian 12 is the 
first Linux variant that I use, which has adopted PEP 668 ...

With kind regards,

Viktor 

-- 
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/afd08348-2d07-46a2-ac9f-7573adaf8cfbn%40googlegroups.com.

Re: leoJS Seems To Work With VSCodium

[Viktor Ransmayr]

Hello Thomas,

Yes, that's the variant [ of Code / Codium / Theia ]I have been using as
well.

Great things need more than one implementation ...

With kind regards

Viktor

On Fri, 22 Dec 2023, 21:18 Thomas Passin,  wrote:

> VSCodium is a version of VSCode that does not include Microsoft-specific
> additions like telemetry.  It's the same code base so everything *ought* to
> work the same.
>
> I've installed VSCodium, and leoJS seems to be working the same as on
> VSCode.
>
> --
> 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/7f4a8218-2093-447a-bc1d-4ece9278da70n%40googlegroups.com
> 
> .
>

-- 
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/CAAeSrGK7mDaeuYBwByn0rt0hXrme9oyXNqS%2BA178-fgmDK%2B5iw%40mail.gmail.com.

Re: ✨LeoJS beta 0.2.0 Released!

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Montag, 11. Dezember 2023 um 02:43:15 UTC+1: 

...

*Join the Beta Release Journey*

I invite you to be part of this exciting phase: Your feedback and bug 
reports  are invaluable in refining 
LeoJS for a full release!

Many thanks to Edward for creating Leo, and thanks to you, for trying it 
out and helping squash the remaining bugs! 


Thanks a lot for this first public release ! - I finally found some time to 
look into it ...

For a first beta it is already in a very good shape, as I was able to work 
on a given outline with all three variants of Leo in sequence.

Here are some notes from my log:

###

Install latest version of Leo [1 & 2]  - OK - See "Log-001".

Check out list of installed extensions in VS Codium - See "Log-002".

* Re-open this outline in LeoInteg [3 & 4] - OK? - See "Log-003".

**Result: Yes, i.e. outline can be read, node can be filled - and - 'rst3' 
command is working.**

* Re-open this outline in LeoJS [5 & 6] - OK? - See "Log-004".

**Result: Almost, i.e. outline can be read & node can be filled - but - 
'rst3' command is not working.**

###

Since I'm using Leo mostly as an outliner,  I'd be very interested to see 
'rst3'  - or a variation of it - working in LeoJS as well.

Are you aware of this problem / restriction - or - shall I create a GH 
issue for it ?

With kind regards,

Viktor

-- 
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/3820149e-cafd-41ff-8a84-6dfba241eadfn%40googlegroups.com.

Re: Leo 6.7.4 released

[Viktor Ransmayr]

Hello Edward,

Am Sa., 19. Aug. 2023 um 16:31 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Sat, Aug 19, 2023 at 2:45 AM Viktor Ransmayr 
> wrote:
>
> > Something has definitely changed, because there were times, when unit
> tests were running w/o errors in such a setup as well ...
>
> Yes, something has changed. Otoh, all unit tests pass for me on both
> Ubuntu and Windows, so it's not easy to see what the problem is.
>

*AFAICT its (always?) related to the two variants of how Leo is distributed
!*

*It is (almost always?) working, i.e. offering all functionality, when
installed from GitHub - but -*

*it is (much more?) restricted in functionality, when being installed from
PyPI.*

Is it time to make this really clear to "user-only" - as compared to -
"developer+user" ?

 IMO it may be clear(er) for people who follow Leo in this group for a long
time - but - for new users this area of Leo is defintiely confusing !

Is there a chance to work on this in a timeframe > 6.7.5 ?

With kind regards,

Viktor

-- 
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/CAAeSrGKuvHxkX_fe4dG3qoVV%2B0p6n9Cz0jmB8etWaeHOV1OJxg%40mail.gmail.com.

Re: Leo 6.7.4 released

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 18. August 2023 um 23:50:16 UTC+2:


>> Viktor, please run your tests in the ekr-3497-Viktors-unit-tests 
branch.  Do you still see any failures?

> The unit test errors occur ONLY, if I install Leo 6.7.4 directly from 
PyPI into a Debian or Fedora VM.
> They do NOT occur, if I install Leo's master branch from GitHub into a 
Debian or Fedora VM.

Thanks for the clarification. I think I'll just merge PR #3498 
into devel and call it 
good enough :-)


I tried the same also for Leo 6.7.4, installed from PyPI, to a Windows 10 
PC.

This results in a logfile with 2300+ lines. - I'm just copying the last 
ones:


Second list contains 2 additional elements.
First extra element 3:
'@language xml\n'

- ['@others\n', '@language xml\n', '@tabwidth -4\n']
+ ['\n',
+  '\n',
+  '@others\n',
+  '@language xml\n',
+  '@tabwidth -4\n'] : FAIL in node 0

--
Ran 871 tests in 19.816s

FAILED (failures=48, errors=23, skipped=4)
PS C:\Users\VR\PyVE\PyPI\Leo\lib\site-packages\leo>

Something has definitely changed, because there were times, when unit tests 
were running w/o errors in such a setup as well ...

With kind regards,

Viktor

-- 
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/0fcb4fe0-9b88-43c3-b062-c73155caeea1n%40googlegroups.com.

Re: Leo 6.7.4 released

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 18. August 2023 um 14:54:10 UTC+2:

On Friday, August 18, 2023 at 6:11:03 AM UTC-5 Edward K. Ream wrote:

> Thanks for this report. See #3497 
.

PR #3498  contains 
suppresses some unit tests in certain situations.

Viktor, please run your tests in the ekr-3497-Viktors-unit-tests branch.  
Do you still see any failures?


I guess my explanation was not precise enough.

The unit test errors occur ONLY, if I install Leo 6.7.4 directly from PyPI 
into a Debian or Fedora VM.

They do NOT occur, if I install Leo's master branch from GitHub into a 
Debian or Fedora VM.

* I explicitly verified another time ;-)

With kind regards,

Viktor

-- 
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/e70a5de3-845f-4003-b050-26185ee52f63n%40googlegroups.com.

Re: Leo 6.7.4 released

[Viktor Ransmayr]

Hello Edward

Edward K. Ream schrieb am Donnerstag, 17. August 2023 um 20:14:16 UTC+2:

On Thu, Aug 17, 2023 at 1:12 PM Edward K. Ream wrote:

Leo https://leo-editor.github.io/leo-editor/ 6.7.4 is now available on 
GitHub  and pypi 
.


I'll delay more public announcements until Monday. Please continue your 
testing ;-)


 I installed Leo 6.7.4 from PyPI also into a Debian 11 VM.

When I run the unit tests there, I receive similar errors. - See attached 
log:

(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ cd 
lib64/python3.9/site-packages/leo
(Leo) 
user@debian-leo-study-vm:~/PyVE/PyPI/Leo/lib64/python3.9/site-packages/leo$ 
(Leo) 
user@debian-leo-study-vm:~/PyVE/PyPI/Leo/lib64/python3.9/site-packages/leo$ 
python -m unittest





...FF...

s...s...







F...

...s

..s.

.cursesGui2.py: 
Tk module required for clipboard handling.
s...s.
==
FAIL: test_diff_two_branches 
(unittests.commands.test_editFileCommands.TestEditFileCommands)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/leo/unittests/commands/test_editFileCommands.py",
 
line 67, in test_diff_two_branches
self.assertEqual(c.lastTopLevel().h, expected_last_headline)
AssertionError: '@file leoGlobals.py' != 'git-diff-branches master 
devel'
- @file leoGlobals.py
+ git-diff-branches master devel


==
FAIL: test_diff_two_revs 
(unittests.commands.test_editFileCommands.TestEditFileCommands)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/leo/unittests/commands/test_editFileCommands.py",
 
line 121, in test_diff_two_revs
self.assertEqual(c.lastTopLevel().h.strip(), expected_last_headline)
AssertionError: 'root' != 'git diff revs: HEAD'
- root
+ git diff revs: HEAD


==
FAIL: test_per_commander_data 
(unittests.core.test_leoGlobals.TestGlobals)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/leo/unittests/core/test_leoGlobals.py",
 
line 294, in test_per_commander_data
self._test_per_commander_data()
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/leo/unittests/core/test_leoGlobals.py",
 
line 178, in _test_per_commander_data
self.assertTrue(os.path.exists(z), msg=repr(z))
AssertionError: False is not true : 
'/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/launchLeo.py'

--
Ran 871 tests in 8.914s

FAILED (failures=3, skipped=6)
(Leo) 
user@debian-leo-study-vm:~/PyVE/PyPI/Leo/lib64/python3.9/site-packages/leo$ 

With kind regards,

Viktor

-- 
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/c078e568-4283-49af-bbf0-d58a0ec288c8n%40googlegroups.com.

Re: Leo 6.7.4 released

[Viktor Ransmayr]

Hello Edward

Edward K. Ream schrieb am Donnerstag, 17. August 2023 um 20:14:16 UTC+2:

On Thu, Aug 17, 2023 at 1:12 PM Edward K. Ream wrote:

Leo https://leo-editor.github.io/leo-editor/ 6.7.4 is now available on 
GitHub  and pypi 
.


I'll delay more public announcements until Monday. Please continue your 
testing ;-)


I installed the current development branch from Leo into this Fedora 38 VM 
as well - and - did NOT receive any unittest errors.

For the record see attached log:

(Leo) [user@fedora-leo-study-vm Leo]$ 
(Leo) [user@fedora-leo-study-vm Leo]$ cd leo-editor/leo
(Leo) [user@fedora-leo-study-vm leo]$ 
(Leo) [user@fedora-leo-study-vm leo]$ python -m unittest

















...s
.
(python:1837): Gdk-CRITICAL **: 22:14:57.617: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

(python:1837): Gdk-CRITICAL **: 22:14:57.617: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

.s..
cursesGui2.py: Tk module required for clipboard 
handling.
s.
--
Ran 871 tests in 7.239s

OK (skipped=3)
(Leo) [user@fedora-leo-study-vm leo]$ 

With kind regards,

Viktor

-- 
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/aa1acb90-d5f9-4f2c-af35-9fd1e4196444n%40googlegroups.com.

Re: Leo 6.7.4 released

[Viktor Ransmayr]

Hello Edward

Edward K. Ream schrieb am Donnerstag, 17. August 2023 um 20:14:16 UTC+2:

On Thu, Aug 17, 2023 at 1:12 PM Edward K. Ream wrote:

Leo https://leo-editor.github.io/leo-editor/ 6.7.4 is now available on 
GitHub  and pypi 
.


I'll delay more public announcements until Monday. Please continue your 
testing ;-)


I installed Leo 6.7.4 from PyPI into a Fedora 38 VM. - When I run the 
unittests I receive errors. - See attached log:

(Leo) [user@fedora-leo-study-vm Leo]$ 
(Leo) [user@fedora-leo-study-vm Leo]$ cd 
lib64/python3.11/site-packages/leo
(Leo) [user@fedora-leo-study-vm leo]$ 
(Leo) [user@fedora-leo-study-vm leo]$ python -m unittest




...fatal: invalid object name 'master'.
fatal: invalid object name 'devel'.
.fatal: ambiguous argument 'HEAD': unknown revision or path not in the 
working tree.
Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'











F...

...s
.
(python:2354): Gdk-CRITICAL **: 22:31:27.506: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

(python:2354): Gdk-CRITICAL **: 22:31:27.506: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

.s..
cursesGui2.py: Tk module required for clipboard 
handling.
s...s.
==
FAIL: test_per_commander_data 
(unittests.core.test_leoGlobals.TestGlobals.test_per_commander_data)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.11/site-packages/leo/unittests/core/test_leoGlobals.py",
 
line 294, in test_per_commander_data
self._test_per_commander_data()
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.11/site-packages/leo/unittests/core/test_leoGlobals.py",
 
line 178, in _test_per_commander_data
self.assertTrue(os.path.exists(z), msg=repr(z))
AssertionError: False is not true : 
'/home/user/PyVE/PyPI/Leo/lib64/python3.11/site-packages/launchLeo.py'

--
Ran 871 tests in 6.838s

FAILED (failures=1, skipped=4)
(Leo) [user@fedora-leo-study-vm leo]$ 

With kind regards,

Viktor

-- 
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/1bc8bb96-e7b6-46f4-b3f9-b5022d4d3d31n%40googlegroups.com.

Re: ENB: Ahas re paste-retaining-clones

[Viktor Ransmayr]

Hello Edward,

On Sun, 13 Aug 2023, 21:06 Félix,  wrote:

> Edward, I also want to join my voice to the group in wishing you a happy
> birthday! :D


Another one joining late - but - still in time ;-)

Enjoy your birthday exactly the way you prefer to !

>

-- 
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/CAAeSrGKV2JgbCSV1a-2%2BoOyC6V38U15evDsXiMmRtYGUBA0P7A%40mail.gmail.com.

Re: PR #3468 merged into devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Sonntag, 30. Juli 2023 um 16:54:09 UTC+2:

PR #3468  (auto-correct 
link problems) resolves the last release blocker for Leo 6.7.4.

A few localized (and minor) issues remain.

Please continue to test the devel branch!


I have successfully tested Leo's devel branch in a Debian 11 & a Fedora 38 
Linux-VM.

I have not noticed anything unusual so far ...

With kind regards,

Viktor
 

-- 
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/4c43e926-b8c8-4e6f-9d02-d03de01df59an%40googlegroups.com.

Re: Leo 6.7.4 is code complete. Please test

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Samstag, 15. Juli 2023 um 14:22:47 UTC+2:

*...*

6.7.4 is code complete. Please test the devel branch.


I have successfully tested Leo's devel branch in a Debian 11 & a Fedora 38 
Linux-VM.

Other than the larger number of skipped unit tests, I have not noticed 
anything ...

With kind regards,

Viktor

-- 
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/2038031e-7f5c-4f1b-99c2-577724abf953n%40googlegroups.com.

Re: PR #3389 (in devel) concludes work on handling options

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 16. Juni 2023 um 23:37:42 UTC+2:

PR #3389  defines four 
simple helper functions in leoGlobals.py.

Imo these four functions do more than the entire argparse module. They are 
simpler, easier and more flexible.

Thanks again to Thomas for his careful reading of the code.


I tested the 'leo-editor:devel' branch again in a Fedora 37 VM.

Running Leo's unit tests reports one error:

::

(Leo) [user@fedora-leo-study-vm Leo]$ 
(Leo) [user@fedora-leo-study-vm Leo]$ cd leo-editor/leo
(Leo) [user@fedora-leo-study-vm leo]$ python -m unittest















..F.

s...
.
(python:1804): Gdk-CRITICAL **: 08:03:14.903: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

(python:1804): Gdk-CRITICAL **: 08:03:14.903: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

.s..
cursesGui2.py: Tk module required for clipboard 
handling.
s.
==
FAIL: test_recursive_import 
(unittests.core.test_leoImport.TestLeoImport.test_recursive_import)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/core/test_leoImport.py", 
line 106, in test_recursive_import
self.assertEqual(root.h, expected)
AssertionError: 'path: ekr-mypy2/mypy' != 'path: mypy'
- path: ekr-mypy2/mypy
+ path: mypy


--
Ran 851 tests in 5.954s

FAILED (failures=1, skipped=3)
(Leo) [user@fedora-leo-study-vm leo]$ 

 With kind regards,

Viktor

-- 
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/6d2f6741-05ef-43ab-b9ea-95e681668fb9n%40googlegroups.com.

Re: Another mass update: PR #3367

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 9. Juni 2023 um 20:04:31 UTC+2:

PR #3367  imports 
Callable from collections.abc instead of typing.  typing.Callable is 
deprecated, but is not presently scheduled for removal. Nevertheless I 
thought it best to do the replacement.

To my knowledge no further changes to Leo's mypy-related code are needed.

Please report any problems.


 I've tested the 'leo-editor:devel' branch in a Fedora 37 VM.

Running Leo's unit tests reports two errors:

::

(Leo) [user@fedora-leo-study-vm Leo]$ 
(Leo) [user@fedora-leo-study-vm Leo]$ cd leo-editor/leo
(Leo) [user@fedora-leo-study-vm leo]$ python -m unittest








..Missing visitor: 
TokenOrderGenerator.TryStar

F..F





.s..
..
(python:1814): Gdk-CRITICAL **: 07:30:49.345: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

(python:1814): Gdk-CRITICAL **: 07:30:49.345: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

.s..
..cursesGui2.py: Tk module required for clipboard 
handling.
s.
==
FAIL: test_visitors_exist 
(unittests.core.test_leoAst.TestTokens.test_visitors_exist)
Ensure that visitors for all ast nodes exist.
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/core/test_leoAst.py", 
line 2745, in test_visitors_exist
assert not errors, msg
AssertionError: 63 node types, 32 op types, 1 errors

==
FAIL: test_bug_3270_at_path 
(unittests.core.test_leoAtFile.TestAtFile.test_bug_3270_at_path)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/core/test_leoAtFile.py", 
line 102, in test_bug_3270_at_path
self.assertEqual(path, expected)
AssertionError: 
'/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/c:/temp/leo/at_file_test.py' 
!= 'c:/temp/leo/at_file_test.py'
- 
/home/user/PyVE/GitHub/Leo/leo-editor/leo/core/c:/temp/leo/at_file_test.py
+ c:/temp/leo/at_file_test.py


--
Ran 848 tests in 5.994s

FAILED (failures=2, skipped=3)
(Leo) [user@fedora-leo-study-vm leo]$ 

Leo's unit tests should not make the assumption, that everyone is running 
them on Windows ;-)

With kind regards,

Viktor

-- 
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/2bbe94a2-b136-4f94-9db3-95ff9a970623n%40googlegroups.com.

Re: Unable to create Leo's Documentation locally

[Viktor Ransmayr]

Hello Thomas,
Viktor Ransmayr schrieb am Samstag, 18. März 2023 um 18:28:05 UTC+1:

tbp1...@gmail.com schrieb am Freitag, 17. März 2023 um 14:39:46 UTC+1:

The following script will build everything except the slides.  Either it 
needs to be run from the *leo/doc* directory or the path needs to be added 
to the script instead of the "." in the last line:

#see https://github.com/leo-editor/leo-editor/issues/1566
import sys
import subprocess
pyexe=sys.executable
cmd=[pyexe,'-m','sphinx','-C',
'-D', 'master_doc=html/leo_toc',
'-D', 'source_suffix=.html.txt',
'-D', 'html_theme=sphinx_rtd_theme',
'-D', 'project=LeoDocs',
'.', r'c:\temp\result']

subprocess.call(cmd)

To use the theme, IIRC, it needs to be installed from PyPi first.  Run the 
script with the usual CNTL-b.

I first worked this up in 2020.  I just now tried it out to see if it still 
works by pasting it into a new node at the top of the LeoDocs outline.  
Change the "result" location in the last line to suit yourself.


I used a slightly simpler version, since I did not want to add any 
dependency & make it non-windows specific:

import sys
import subprocess
pyexe = sys.executable
cmd = [pyexe, '-m', 'sphinx', '-C', 
  '-D', 'master_doc=html/leo_toc',
  '-D', 'source_suffix=.html.txt',
  '-D', 'project=Leo Docs',
  '.', 'result']

subprocess.call(cmd)

It works kind of OK - but - did reveal, that Leo's Documentation Outline is 
still assuming that development & release work is done on Windows ...


I should have made the issue more explicit ...

The problem is that  Leo's Documentation Outline is still using backslashes 
"\" , which are kept / visible even on Linux, i.e. 

###

user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor/leo/doc/result$ ls
 genindex.html'html\tutorial-basics.html'
 html 'html\tutorial.html'
'html\cheatsheet.html''html\tutorial-pim.html'
'html\coloring.html'  'html\tutorial-rst3.html'
'html\console-gui.html'   'html\tutorial-scripting.html'
'html\debuggers.html' 'html\tutorial-tips.html'
'html\emacs.html' 'html\vimBindings.html'
'html\FAQ.html'   'html\writingPlugins.html'
'html\IPythonBridge.html'  _images
'html\leoBridge.html'  objects.inv
'html\leonine-world.html'  search.html
'html\leo_toc.html'searchindex.js
'html\leo-university.html' _sources
'html\scripting-miscellany.html'   _static
user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor/leo/doc/result$ 

###

With kind regards,

Viktor

-- 
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/43ca87f8-9b14-48de-bf27-59f8a8aea4c4n%40googlegroups.com.

Re: Unable to create Leo's Documentation locally

[Viktor Ransmayr]

Hello Thomas

tbp1...@gmail.com schrieb am Freitag, 17. März 2023 um 14:39:46 UTC+1:

The following script will build everything except the slides.  Either it 
needs to be run from the *leo/doc* directory or the path needs to be added 
to the script instead of the "." in the last line:

#see https://github.com/leo-editor/leo-editor/issues/1566
import sys
import subprocess
pyexe=sys.executable
cmd=[pyexe,'-m','sphinx','-C',
'-D', 'master_doc=html/leo_toc',
'-D', 'source_suffix=.html.txt',
'-D', 'html_theme=sphinx_rtd_theme',
'-D', 'project=LeoDocs',
'.', r'c:\temp\result']

subprocess.call(cmd)

To use the theme, IIRC, it needs to be installed from PyPi first.  Run the 
script with the usual CNTL-b.

I first worked this up in 2020.  I just now tried it out to see if it still 
works by pasting it into a new node at the top of the LeoDocs outline.  
Change the "result" location in the last line to suit yourself.


I used a slightly simpler version, since I did not want to add any 
dependency & make it non-windows specific:

import sys
import subprocess
pyexe = sys.executable
cmd = [pyexe, '-m', 'sphinx', '-C', 
  '-D', 'master_doc=html/leo_toc',
  '-D', 'source_suffix=.html.txt',
  '-D', 'project=Leo Docs',
  '.', 'result']

subprocess.call(cmd)

It works kind of OK - but - did reveal, that Leo's Documentation Outline is 
still assuming that development & release work is done on Windows ...

Below are my logs w/ more details.

With kind regards,

Viktor

###

Execute this button on the "Leo's Documentation" node of the outline - OK - 
See "Log-002".

* Check out the result ...
* 
file:///home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/result/html%5Cleo_toc.html 
<- ?
* -> 
file:///home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/result/html/leo_toc.html 
<- !
* ... and compare it with
* https://leo-editor.github.io/leo-editor/leo_toc.html

### Log-002

(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor/leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor/leo$ 
Running Sphinx v4.3.1
loading pickled environment... done
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 49 source files that are out of date
updating environment: [config changed ('project')] 133 added, 0 
changed, 0 removed
reading sources... [100%] html/writingPlugins   


/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/intermediatetopics.html.txt:7:
 
WARNING: toctree contains reference to nonexisting document 
'html/unitTesting'
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/leo_toc.html.txt:24: 
WARNING: toctree contains reference to nonexisting document 
'html/toc-more-links'
looking for now-outdated files... none found
pickling environment... done
checking consistency... 
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/FAQ.html.txt: WARNING: 
document isn't included in any toctree
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/cheatsheet.html.txt: 
WARNING: document isn't included in any toctree
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/glossary.html.txt: 
WARNING: document isn't included in any toctree
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/history.html.txt: 
WARNING: document isn't included in any toctree
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/leoLinks.html.txt: 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/screen-shots.html.txt: 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/screencasts.html.txt: 
WARNING: document isn't included in any toctree
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/slides.html.txt: 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/slides/basics/basics.html.txt:
 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/slides/clones-and-views/clones-and-views.html.txt:
 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/slides/external-files/external-files.html.txt:
 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/slides/minibuffer/minibuffer.html.txt:
 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/slides/scripting-leo/scripting-leo.html.txt:
 
WARNING: document isn't included in any toctree

/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html/what-is-new.html.txt: 
WARNING: document isn't included in any toctree
done
preparing documents... done
writing output... [100%] html/writingPlugins   
 
generating indices... genindex done
writing additional pages... search done
copying images... [100%] html/screen-shots/leo-workbook.png 
  

Unable to create Leo's Documentation locally

[Viktor Ransmayr]

Should it still be possible to create Leo's Documentation locally on Linux 
from "LeoDocs.leo"?

I'm failing to do so inside a Debian 11 - based VM.

I verified this both on the master branch / PyPI - and - devel branch / 
from GitHub ...

Below are my logs w/ more details.

With kind regards,

Viktor

###

Open the 'correct' (see below) outline containing Leo's documentation - Not 
OK - See "Log-001".

* 
unl:///home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/leo/doc/LeoDocs.leo#Leo%27s
 
Documentation

Execute the 'make-sphinx' button on the "Leo's Documentation" node in this 
outline - Not OK - See "Log-002".

Close & re-open this outline in '~/PyVE/GitHub/Leo'.

Open the 'correct' (see below) outline containing Leo's documentation - OK 
- See "Log-003".

* unl:///home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/LeoDocs.leo#Leo%27s 
Documentation

Execute the 'make-sphinx' button on the "Leo's Documentation" node in this 
outline as well - Not OK - See "Log-004".

### Log-001

Leo Log Window
Leo 6.7.2
Python 3.9.2, PyQt version 5.15.2
linux
can not open 
/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/docs/redirect_index.html
can not open 
/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/docs/index.html
read 10 files in 0.48 seconds
read outline in 0.61 seconds

### Log-002

Run `make-sphinx` from `gh-pages` branch

### Log-003

Leo Log Window
Leo 6.7.2-devel
Python 3.9.2, PyQt version 5.15.2
linux
read 10 files in 0.49 seconds
read outline in 0.67 seconds

### Log-004

Run `make-sphinx` from `gh-pages` branch

-- 
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/a2884114-9cf1-4fdb-8854-f933bd4fbd16n%40googlegroups.com.

Re: In hospital for severe abdominal pains

[Viktor Ransmayr]

> Worst is behind now . Feeling better .
>

Get well soon !

Viktor

-- 
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/CAAeSrG%2BeEKkEWTohZAXOZsFXK3gw4Az02nq72Ng1%3DM2csFqOBQ%40mail.gmail.com.

Re: Failing unit test in devel branch

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Mittwoch, 28. Dezember 2022 um 19:47:10 UTC+1:

> " I also double-checked & saw that 'setup.py' has added "tk" as an install 
> requirement."
>
> I wonder if Leo needs tk at all any more.  Maybe it can be removed as a 
> requirement.
>

Here's the complete output from my second attempt to run unit tests on 
Debian:

 (Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ 
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ cd leo-editor/
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ python -m 
unittest







...s

s...









s...


...cursesGui2.py: Tk 
module required for clipboard handling.
E.
==
ERROR: test_cursesGui2 (leo.unittests.test_plugins.TestPlugins)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/test_plugins.py", line 
114, in test_cursesGui2
import leo.plugins.cursesGui2 as cursesGui2
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/plugins/cursesGui2.py", line 50, 
in 
from tkinter import Tk
ModuleNotFoundError: No module named 'tkinter'

--
Ran 941 tests in 7.338s

FAILED (errors=1, skipped=3)
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 

If I read the info correctly, than at least the cursesGui2 plugin - and/or 
- the unit tests for it, still require the 'tkinter' module ...

Let's wait & see what Edward thinks.

With kind regards,

Viktor

-- 
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/5d3f355d-e95b-4ab4-b006-1c0c1c3c60f2n%40googlegroups.com.

Re: Failing unit test in devel branch

[Viktor Ransmayr]

Hello Edward & Thomas,

As an additional info Leo's unit tests are working fine in version 6.7.1 on 
both Debian- & Fedora Linux.

With kind regards,

Viktor

-- 
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/9c01-8171-4435-8299-5d8c037f231dn%40googlegroups.com.

Re: Failing unit test in devel branch

[Viktor Ransmayr]

Hello Thomas,

Thanks for this explanation / info.

tbp1...@gmail.com schrieb am Mittwoch, 28. Dezember 2022 um 16:16:37 UTC+1:

> You have to install it using the package manager.  Here is what I have 
> found (quoted from the Users' Guide for my GF4 project)::
>
> "On Debian/Ubuntu, tkinter has to be installed by 
> the package manager:
>
> sudo apt-get install python3-tk
>

I also double-checked & saw that 'setup.py' has added "tk" as an install 
requirement.

As I initially only did a 'git pull' on Leo's devel branch - and - did NOT 
perform a subsequent 'pip install --editable 
/home/user/PyVE/GitHub/Leo/leo-editor' I re-tried running the unit tests 
afterwards & the same failure occurred ...

Who is to 'blame' for treating Linux as a second-class citizen?

Leo's 'setup.py' script - or - the Python Packagers of Debian & Fedora 
Linux ...

With kind regards,

Viktor

-- 
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/c27e360f-b6f1-4210-aa74-1d208dd40cben%40googlegroups.com.

Failing unittest in devel branch

[Viktor Ransmayr]

Hello Edward,

When I run the unit tests for the latest version of the devel branch, I 
receive the following error:

###

==
ERROR: test_cursesGui2 (leo.unittests.test_plugins.TestPlugins)
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/test_plugins.py", line 
114, in test_cursesGui2
import leo.plugins.cursesGui2 as cursesGui2
  File 
"/home/user/PyVE/GitHub/Leo/leo-editor/leo/plugins/cursesGui2.py", line 50, 
in 
from tkinter import Tk
ModuleNotFoundError: No module named 'tkinter'

--
Ran 941 tests in 7.309s

FAILED (errors=1, skipped=3)
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo/leo-editor$ 

###

This happens in a Debian 11 - as well as - a Fedora 36 VM.

With kind regards,

Viktor

-- 
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/5b2bc06c-a401-4d12-b309-51c25a87cd11n%40googlegroups.com.

Re: Leo 6.7.1 coming Friday, Nov. 4

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 28. Oktober 2022 um 14:37:59 UTC+2:

> This release features a changes to leoserver.py, which it should be 
> released soon.
>
> Please keep testing devel :-)
>

A short confirmation, that Leo's 'devel' branch is working fine for me, 
running in a Debian 11 VM - as well as - a Fedora 36 VM.

With kind regards,

Viktor

-- 
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/219b90a6-ea1f-48a5-983f-0704b45dc571n%40googlegroups.com.

Re: macos 10.13 - leo 6.7.0 with miniconda

[Viktor Ransmayr]

Hello Edward,

Am So., 16. Okt. 2022 um 13:49 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Sunday, October 16, 2022 at 6:36:53 AM UTC-5 Edward K. Ream wrote:
>
> I don't remember how Leo 5.7 worked, but I am able to take a look at the
>> old code.
>>
>
> I should have mentioned that the old code created so-called "SDI" windows
> . To
> repeat, I have no recollection of how Leo switched between open documents.
>

Is this "single-document interface (SDI) windows" something Microsoft
specific?

Viktor

-- 
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/CAAeSrGK%3DW07cH_TFzk_N_%2B457%3Dbc0%2BvURMTkPGC-07BqYeKY5g%40mail.gmail.com.

Re: Two more PRs merged into devel

[Viktor Ransmayr]

Hello Edward,

Am So., 18. Sept. 2022 um 21:53 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Sun, Sep 18, 2022 at 2:47 PM Viktor Ransmayr wrote:
>
> > It looks like the 'test-all' command does no longer work ...
>
> Correct. I removed those commands recently.
>

OK, I was only surprised, that the removal of ~ 50 (test-* & cover-*)
commands did not warrant an own msg.

With kind regards,

Viktor

-- 
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/CAAeSrG%2BfSaQ8DLLcn-PgFT_dS_A%2B9rRdaYG-FfEaAeZP4%3D5YcQ%40mail.gmail.com.

Re: Two more PRs merged into devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Sonntag, 18. September 2022 um 12:05:13 UTC+2:

> devel now contains PR #2871 
>  (icons) and PR #2873 
>  (leoserver 
> annotations).
>
> Please continue your testing of devel. The icons issues was unexpectedly 
> tricky, and deserves more testing.
>
> We are still on track to release Leo 6.7.0 on Friday, September 30, but 
> I'll be happy to push back that date if necessary.
>

It looks like the 'test-all' command does no longer work ...

Does it mean that you already have removed all test-* commands as announced 
in 

* Infor issue #2867 contains my development scripts
* https://groups.google.com/g/leo-editor/c/ioqLuQQBkds

already?

If this is the case, then IMHO this would have deserved an individual msg 
to the users ;-)

With kind regards,

Viktor

-- 
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/940eaa39-9079-44e3-b898-7a13636fe37an%40googlegroups.com.

Re: All bugs scheduled for 6.7.0 have been fixed. Please test devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 13. September 2022 um 22:58:53 UTC+2:

> The only remaining issue involves unit tests.
>
> I'll accept no PRs for new features until after 6.7.0 goes out the door.
>
> Please do keep up your testing :-)
>

A confirmation that the latest version of Leo's development branch is 
working fine in a Debian 11 - as well as - a Fedora 35 VM.

With kind regards,

Viktor
 

-- 
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/6afd2672-22ce-490a-98b0-6ab9c836e371n%40googlegroups.com.

Re: Leo 6.6.4 released

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Donnerstag, 1. September 2022 um 05:20:49 UTC+2:

> Leo http://leoeditor.com 6.6.4 is now available on GitHub 
>  and pypi 
> . Many thanks to all who have contributed. 
>
> I'll wait until Friday to announce this release widely.
>
A confirmation that Leo 6.6.4 is working properly, when installed from PyPI 
into a Debian 11 - as well as - a Fedora 35 VM.

With kind regards,

Viktor

-- 
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/eb1cd644-3b1f-4b4c-8bec-d29136f84e43n%40googlegroups.com.

Re: Leo 6.6.3 coming this Friday, July 22

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 19. Juli 2022 um 12:57:51 UTC+2:

> Leo 6.6.3 is ready for final testing! Please test devel and report any 
> problems immediately. 
>

I've tested the latest version of Leo's devel branch  in a Fedora 35 - as 
well as - a Debian 11 VM.

The 'test-all' command reported 927 tests as OK 

* w/ 2 skipped tests on Debian &
* w/o any skipped tests on Fedora.

With kind regards,

Viktor

-- 
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/fe841876-3d2b-4ab0-8c78-d70b117b5ed1n%40googlegroups.com.

Re: FYI: I have closed most Leo issues

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 24. Mai 2022 um 17:04:30 UTC+2:

> At present, all 26 open issues 
>  
> have been delegated to others. 
>

It looks like 

* https://github.com/leo-editor/leo-editor/issues/1566

is 'orphaned'?

I'd like to investigate it further myself - and - hopefully have something 
available in time for Leo-6.6.3 ...

With kind regards,

Viktor

-- 
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/eaf73071-7868-4128-9635-badc6b44392en%40googlegroups.com.

Re: Updated Leo 6.6.2 released

[Viktor Ransmayr]

Hello Edward & Thomas,

Edward K. Ream schrieb am Mittwoch, 25. Mai 2022 um 12:33:32 UTC+2:

> An updated version Leo 6.6.2 is now available on GitHub 
>  and pypi 
> . The updated version runs on Python 
> 3.6. The previous version didn't.
>
> This will be the official 6.6.2 version unless truly serious problems 
> arise. We'll fix minor problems in the 6.6.3 cycle. Nevertheless, I'll wait 
> until Friday to announce 6.6.2 publicly.
>

I've tested the combination of 'devel' at GitHub & '6.6.2-2' at PyPI in a 
Debian 11 & a Fedora 34 VM.

The 'test-all' command is working everywhere.

Thanks a lot to both of you!

With kind regards,

Viktor

-- 
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/e4c8c0af-80f9-4c22-8c76-06a84730f011n%40googlegroups.com.

Re: It *is* possible to run unit tests from pip-installed Leo

[Viktor Ransmayr]

Hello Edward,

Am Mo., 23. Mai 2022 um 13:58 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> #2668  has passed
> by-hand tests. It should be completed later today.
>

Looking forward to test #2668
,  once it's
available,  in all environments available to me ...

I'm happy, that I was able to provide the initial trigger for this
improvement - and - more importantly, I'd like to thank Thomas for making
the initial suggestion for it to you !

With kind regards,

Viktor

-- 
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/CAAeSrGJ3YpmewmE0RS3sEp%3DR%3DAhqNOtg1ZorhisYugjut0N99Q%40mail.gmail.com.

Re: Different results of 'test-all' cmd

[Viktor Ransmayr]

Hello Edward,

Am Sa., 21. Mai 2022 um 13:24 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Fri, May 20, 2022 at 3:32 PM Edward K. Ream 
> wrote:
>
>>
>> 1. I am not going to change Leo's test-all command so that it works in
>> python/site-packages/leo. The workaround is easy: run `python -m unittest`
>> from python/site-packages/leo.
>>
>
> The workaround won't work :-) Indeed, many unit tests contain the line:
>
> import leo.core.leoGlobals as g
>
> Alas, this import assumes that the cwd is the parent directory of the leo
> directory. After `pip install leo`, the parent directory is
> python/Lib/sitecustomize, and we definitely should not (can not) run
> `python -m unittest` from there!
>
> In short, none of Leo's test (or cover) commands will work when using `pip
> install leo`.
>
> Altering sys.path before running each test would pollute *every* test
> file, including leoTest2.py. I'm not going to do it.
>
> *Summary*
>
> setup.py installs leo, not leo-editor. We can't run unit tests from the
> site-packages folder!
>
> Installing leo-editor instead of leo would be a major change to Leo's pypi
> distribution. I'm not going to even consider such a change.
>
> In short, there is no feasible way to run Leo's test and cover commands
> after `pip install leo`.
>

I believe, that this difference b/w **Leo-Editor** from GitHub - and -
**Leo** from PyPI should be documented.

I'm not sure, if "Downloading, Installing & Running Leo" [1] is the right
place, but IMO it would be a pitty if this info would be 'buried' only here
...

With kind regards,

Viktor

---

 [1] https://leoeditor.com/getting-started.html

-- 
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/CAAeSrGJFuaFZ_UcssbPXavsEQ%3DUHA5L9R3_%3DS_X19%3DWF7poq-g%40mail.gmail.com.

Re: F5 Key Opens New Leo Session?

[Viktor Ransmayr]

Hello Thomas,

gates...@gmail.com schrieb am Sonntag, 1. Mai 2022 um 16:22:13 UTC+2:

> I cannot replicate this on Win 10, latest devel commit.  F5 happily does 
> nothing on my machine.
>
> On Sun, May 1, 2022 at 4:01 AM jkn  wrote:
>
>> doesn't happen for me on Linux FWIW (although the action is something I 
>> have wondered about, whether it would be useful...)
>>
>> On Saturday, April 30, 2022 at 11:15:09 PM UTC+1 tbp1...@gmail.com wrote:
>>
>>> I just discovered that hitting the F5 key while in leo opens a new leo 
>>> window with only the workbook open.  but why?  it's not in the list of 
>>> bindings or commands. i don't define it in any @shortcuts node.In fact, the 
>>> string "f5" does not occur at all in myLeoSettings.leo.  This action does 
>>> not happen when the leo window is not focused.
>>>
>>> The os is Windows 10.
>>>
>>> I'd like to bind the key to some other command, but i'd like to 
>>> understand what is going on here first.  Anyone know?
>>>
>>
I can't replicate this behavior of Leo in a Fedora 34 VM either!  

With kind regards,

Viktor

-- 
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/6ff55b2c-dbe9-4f87-983a-2c1072110dfen%40googlegroups.com.

Re: Different results of 'test-all' cmd

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Sonntag, 1. Mai 2022 um 15:04:14 UTC+2:

> On Sun, May 1, 2022 at 3:54 AM Viktor Ransmayr wrote:
>
> Lately I have adapted my defaults a bit - and - execute 'test-all' cmd 
>> whenever I modify / upgrade any Leo instance.
>>
>
> Thanks for your continued testing, which is one of the most important 
> tasks in maintenance mode.
>

I'm happy, that I can give back at least a little bit this way.
 

> Doing this now also with versions I downloaded directly from PyPI I 
>> noticed that 'test-all' cmd returns failures & errors.
>>
>> * See "Log-001" for the results of the 'test-all' cmd ...
>>
>
> The log probably reveals two issues:
>
> 1. Make sure you `pip install pytest` before running unit tests. I'm not 
> sure exactly how this dependency has crept in.
>

 I guess my intro was to short - and/or - completely missing ;-)

What I noticed is that the two **major** variants of how (many! /most?) 
people install Leo nowadays behave differently:

* Running 'test-all' cmd on a Leo version 6.6* installed from GitHub 
returns **without** any failures & errors 
* Running 'test-all' cmd on a Leo version 6.6* installed from PyPI returns 
**with** failures & errors

Based on your feedback I assume that for a given **released** version of 
Leo, it's variants **should** behave identical.

That is, no matter whether I install it from GitHub or from PyPI **all** 
cmds (applicable for a given OS) should work without the user having to 
install any additional packages.

Is my assumption correct?

If yes, than the answer to the question in my initial mail is: It can be 
considered a bug. - Right?

With kind regards,

Viktor

-- 
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/eee0d1a2-2c9d-441b-bb99-ded7b219cc21n%40googlegroups.com.

Different results of 'test-all' cmd

[Viktor Ransmayr]

Hello Edward,

Lately I have adapted my defaults a bit - and - execute 'test-all' cmd 
whenever I modify / upgrade any Leo instance.

Doing this now also with versions I downloaded directly from PyPI I noticed 
that 'test-all' cmd returns failures & errors.

* See "Log-001" for the results of the 'test-all' cmd ...

I've started to compare the list of installed packages - but - that did 
also revealed a surprise (at least for me):

The variant of Leo installed from GitHub uses less packages than the one 
installed from PyPI.

* See "Log-002" for the installed package details & differences ...

Is this different behavior expected - or - is this a bug?

With kind regards,

Viktor




E.E.E...

..s...s.

sss.

...s..FFs...



E..F









.FFF
..
(python:1317): Gdk-CRITICAL **: 08:37:04.625: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

(python:1317): Gdk-CRITICAL **: 08:37:04.626: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

Fs.s.sss

ssss..FFF..EE...s..FFF..EEss

s...EE...E..EE.EEsssEEEE

...EEE.EE..EEE.E.ssEEE..EExxEExx

EExxxE.EExEExEEs

EEEE

EEE.

...E..s.s...EEE.

...F.s..s...s...

.s..s...s.s.

..s...ss

..s..s..s.ss..s.

s.s.s...s.s...s.



...ss..s..s.

ss.sss..

s...

..ss..s.s.s.ECHARACTER
 
MATCH 'a'

...E
==
ERROR: astroid.test_utils (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: astroid.test_utils
Traceback (most recent call last):
  File "/usr/lib64/python3.9/unittest/loader.py", line 436, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib64/python3.9/unittest/loader.py", line 377, in 
_get_module_from_name
__import__(name)
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/astroid/test_utils.py", 
line 20, in 
import pytest
ModuleNotFoundError: No module named 'pytest'

5000+ lines deleted !!!

==
FAIL: test_readFromStdin (pyflakes.test.test_api.IntegrationTests)
If no arguments are passed to C{pyflakes} then it reads from stdin.
--
Traceback (most recent call last):
  File 
"/home/user/PyVE/PyPI/Leo/lib/python3.9/site-packages/pyflakes/test/test_api.py",
 
line 816, in test_readFromStdin
self.assertEqual(d, ("%s%s" % (expected, os.linesep), '', 1))
AssertionError: Tuples differ: ('', 
"/home/user/PyVE/PyPI/Leo/bin/python:[135 chars]", 2) != (":1:1 
'contraband' imported but unused\n", '', 1)

First differing element 0:
   

Re: All completed 6.6.2 work has been merged into devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 29. April 2022 um 15:23:56 UTC+2:

> On Thu, Apr 28, 2022 at 11:35 PM Viktor Ransmayr wrote:
>>
>> I did again apply the latest changes to the 'devel' branch of Leo in a 
>> Fedora 34 VM running on Qubes-OS.
>>
>> Executing the 'test-all' cmd the following test failure is still reported:
>>
>
>  Fixed in devel at rev b82ddf8 
> <https://github.com/leo-editor/leo-editor/commit/b82ddf8693e98dce2b45db80dbe0678a29044ae2>.
>  
> The failure was in the unit test itself, not the code under test.
>

Running the 'test-all' cmd on this revision passes  w/o failures in a 
Fedora 34 - as well as - a Debian 11 VM running on Qubes-OS.

Thanks a lot for your quick response!

With kind regards,

Viktor

-- 
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/3b2a40f4-982a-4162-b893-27c3e591cf54n%40googlegroups.com.

Re: All completed 6.6.2 work has been merged into devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Donnerstag, 28. April 2022 um 12:11:29 UTC+2:

> Leo's devel branch now contains all completed work for Leo 6.6.2, 
> scheduled for Friday, May 27. The highlights of the new work are two mass 
> updates to Leo's code base: 
>
> PR #2604 : Annotate 
> important files.
> PR #2622 : Remove 
> hanging indents using cvt-comments script.
>
> These mass updates are likely to be the last. Or so I hope :-)
>
> Please test devel and report any problems.  Thanks.
>

I did again apply the latest changes to the 'devel' branch of Leo in a 
Fedora 34 VM running on Qubes-OS.

Executing the 'test-all' cmd the following test failure is still reported:

###

...s...s.ssss.ss.F.
==
FAIL: test_create_html_links (leo.unittests.test_gui.TestQtGui)
--
Traceback (most recent call last):
  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/test_gui.py", 
line 127, in test_create_html_links
self.assertEqual(result, expected, msg=repr(s))
AssertionError: False != True : 'leo\\unittest\\test_file.py:1326:8: W0101: 
Unreachable code (unreachable)\n'

--
Ran 923 tests in 9.156s

FAILED (failures=1, skipped=8)

###

With kind regards,

Viktor

-- 
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/63b81485-c7ee-4e5d-97b7-b89049120bccn%40googlegroups.com.

Re: Improved links code now in both the devel and ekr-ann branches

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Mittwoch, 20. April 2022 um 19:02:44 UTC+2:

> For reasons that I do not entirely understand, recent changes to 
> put_html_links suddenly make it more robust than before. I have not seen 
> failures recently. #2609 
>  might be fixed! 
>
> I have just merged (by hand), the latest version of put_html_links from 
> ekr-ann into devel, so everyone can test it.
>
> I'll leave #2609  
> open for at least several more days,Please report any problems 
> immediately.  Thanks.
>

I did apply the latest changes to the 'devel' branch of Leo in a Fedora 34 
VM running on Qubes-OS.

Executing the 'test-all' cmd the following test failure is reported:

###

...s...s.ssss.s..ss...s.ssss
(python:1850): Gdk-CRITICAL **: 20:22:22.724: gdk_atom_intern: assertion 
'atom_name != NULL' failed

(python:1850): Gdk-CRITICAL **: 20:22:22.724: gdk_atom_intern: assertion 
'atom_name != NULL' failed
.F.
==
FAIL: test_create_html_links (leo.unittests.test_gui.TestQtGui)
--
Traceback (most recent call last):
  File "/home/user/PyVE/GitHub/Leo/leo-editor/leo/unittests/test_gui.py", 
line 127, in test_create_html_links
self.assertEqual(result, expected, msg=repr(s))
AssertionError: False != True : 'leo\\unittest\\test_file.py:1326:8: W0101: 
Unreachable code (unreachable)\n'

--
Ran 923 tests in 9.984s

FAILED (failures=1, skipped=14)

###

With kind regards,

Viktor
 

-- 
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/3e6a3aa1-df53-42d6-88cd-5d7d274707f5n%40googlegroups.com.

Re: Please test Leo's pylint command in devel

[Viktor Ransmayr]

Hello Thomas,

Am Sa., 9. Apr. 2022 um 18:03 Uhr schrieb tbp1...@gmail.com <
tbp100...@gmail.com>:

> Thanks, @lewis, @viktor, this is very helpful.  We have identified the
> cause: The pylint command is run using subprocess.Popen and writes output
> (stdout) to a pipe.  When there is a lot of output, the output pipe fills
> up and the source has to wait until it has room again.  So the process
> never finishes.  You can read the pipe, the the read causes Leo to block
> until there is more output again.  The size of the pipe would be
> os-dependent, so one installation could have success and another remain
> stalled forever.
>
> It's a tricky thing to get this working without blocking Leo.
>
> On Saturday, April 9, 2022 at 11:09:19 AM UTC-4 viktor@gmail.com
> wrote:
>
>> Hello everyone,
>>
>> lewis schrieb am Samstag, 9. April 2022 um 06:11:29 UTC+2:
>>
>>> I tested with a large file - running pylint on leoGlobals.py gives lots
>>> of output.
>>>
>>
>> Trying to to the same on a Leo 'devel' instance in a Fedora VM does not
>> return any output at all.
>>
>
Thanks for your quick feedback & update.

I'll stop applying the latest changes on the development branch until I
hear from you or Edward again.

With kind regards,

Viktor

-- 
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/CAAeSrGJie9wBGWnR7odqinVR%3DqqELMV3hmucAyA96dkDss1Bhw%40mail.gmail.com.

Re: Please test Leo's pylint command in devel

[Viktor Ransmayr]

Hello everyone,

lewis schrieb am Samstag, 9. April 2022 um 06:11:29 UTC+2:

> I tested with a large file - running pylint on leoGlobals.py gives lots of 
> output.
>

Trying to to the same on a Leo 'devel' instance in a Fedora VM does not 
return any output at all.

With kind regards,

Viktor
 

-- 
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/0bd18eb0-b4b9-4271-851d-fe887e6eeba7n%40googlegroups.com.

Re: 6.6 coming this Thursday, March 31

[Viktor Ransmayr]

Hello Edward,

Viktor Ransmayr schrieb am Sonntag, 27. März 2022 um 19:47:17 UTC+2:

> Am So., 27. März 2022 um 19:31 Uhr schrieb Edward K. Ream <
> edre...@gmail.com>:
>
>>
>> On Sun, Mar 27, 2022 at 11:09 AM Viktor Ransmayr  
>> wrote:
>>
>> > Do you still plan to create a release candidate & upload it to PyPI 
>> before?
>>
>> No.  The present plan is to upload 6.6 (final) to PyPI on Thursday.
>>
>
> OK, then I'll perform a final test of the 'devel' branch on the platforms 
> that I have access to.
>

The 'devel' branch is working fine for Debian 11 and Fedora 34 VMs on 
Qubes-OS.

With kind regards,

Viktor

-- 
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/f58aa51e-9c56-45f4-8de6-f3c843503095n%40googlegroups.com.

Re: I have cleaned Leo's branches and updated info issue #1058

[Viktor Ransmayr]

Hello Felix,

Am So., 27. März 2022 um 20:11 Uhr schrieb Félix :

> Salutations Viktor,
>
> The felix-server4 branch is specifically where I push development progress
> for the 'leoserver.py' file in leo/core.
>
> Indeed, most of the time it is equal to 'devel', but when I'm working on
> new server features, that's the branch where you can see and test those new
> server features, until they are judged stable and 'clean', after which I
> usually make a pull request for it to be merged in 'devel'.
>
> In other words it's the dedicated 'feature' branch for leoserver.py
> development :)
>
> Thanks for your interest! And don't hesitate to make suggestions, remarks
> or anything else!
>

Thanks a lot for your quick feedback.

The main reason for asking is related to the question raised by Thomas (see
https://groups.google.com/g/leo-editor/c/iMU6Wv8EgDg).

I'm interested to understand, where the main activity will / might take
place ...

However now the next important step is the release of Leo 6.6.

With kind regards,

Viktor

-- 
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/CAAeSrGJfZPYFt6aEH42F3W6w6HYcP2XGmbjae7qxkfk1Bxqk%2BQ%40mail.gmail.com.

Re: I have cleaned Leo's branches and updated info issue #1058

[Viktor Ransmayr]

Hello Edward & Felix,

Am So., 27. März 2022 um 14:19 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> Leo's Github branch page
>  now contains only
> three branches: master, devel and felix-server4. All three branches are
> protected. None can be deleted.
>
> I have deleted all other branches, including all release branches.
>
> Leo's Github release page
>  contains the
> references to permanent revision and tag info. In other words, release
> branches are temporary (throwaways).
>
> I have just updated info issue #1058
>  (Info about
> branches) accordingly.
>

What's the longer-term plan for the "felix-server4" branch?

Will it be merged into the "devel" branch soon - or - does it have a
particular focus, that does not 'fit' into the "devel" branch?

With kind regards,

Viktor

-- 
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/CAAeSrGJW6RpEqMLifHM%2BCfQENP6m7EZzJzVgLmy4Y1%2BPgWFdyQ%40mail.gmail.com.

Re: 6.6 coming this Thursday, March 31

[Viktor Ransmayr]

Hello Edward,

Am So., 27. März 2022 um 19:31 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

>
> On Sun, Mar 27, 2022 at 11:09 AM Viktor Ransmayr <
> viktor.ransm...@gmail.com> wrote:
>
> > Do you still plan to create a release candidate & upload it to PyPI
> before?
>
> No.  The present plan is to upload 6.6 (final) to PyPI on Thursday.
>

OK, then I'll perform a final test of the 'devel' branch on the platforms
that I have access to.

With kind regards,

Viktor

-- 
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/CAAeSrGJjaRFCKvwh_y6dUkucyf84ZsRaOT8b2SDt3exQ2avH0Q%40mail.gmail.com.

Re: 6.6 coming this Thursday, March 31

[Viktor Ransmayr]

Hello Edward,

On Sun, 27 Mar 2022, 14:03 Edward K. Ream,  wrote:

> Leo 6.6 is code complete. Absent something completely unexpected, Leo 6.6
> final will go out the door this Thursday, March 31.


Do you still plan to create a release candidate & upload it to PyPI before?

With kind regards

Viktor

-- 
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/CAAeSrGLoSz6n3dTNH9bTpxodvamiJNOpc6Xsf9dE%3DobDxuTmYQ%40mail.gmail.com.

Re: Please test devel and PR #2523

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 25. März 2022 um 18:21:22 UTC+1:

> Today's work should complete Leo 6.6.
>
> Please test *both* the devel and ekr-leoid2 
>  branches.
>
> PR #2523  (ekr-leoid2 
> branch) is experimental. It has not been merged into devel. It should 
> affect only Leo's bridge, including leoserver.py. Although the PR's changes 
> seem small, it's difficult for me to be sure of their consequences.  I'll 
> wait until I hear from Félix before merging this PR into devel.
>
> Work already merged into devel should (finally!!) make cff and cfa work as 
> intended.
>

FYI: 'devel' is working fine for Fedora 34 and Debian 11 VMs on Qubes-OS.

Running the 'test-all' cmd returns the following results:

Debian: OK (skipped=6)

Fedora: OK (skipped=11) - and - in addition it reported the following 
failed assertions ...

###

.
(python:1832): Gdk-CRITICAL **: 09:37:44.401: gdk_atom_intern: 
assertion 'atom_name != NULL' failed

(python:1832): Gdk-CRITICAL **: 09:37:44.401: gdk_atom_intern: 
assertion 'atom_name != NULL' failed
..
--
Ran 819 tests in 9.372s

###

Please let me know if I should provide any further information.

With kind regards,

Viktor 

-- 
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/0e6426a2-5bb6-401a-8b40-a15d917f9e1fn%40googlegroups.com.

Re: Remote Leo Files - Security Issues

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Samstag, 12. März 2022 um 23:00:34 UTC+1:

> Since we are looking at getting Leo to work with files on a remote 
> computer, we should discuss the security aspect.  I think there are 
> basically two kinds of things we'd like to prevent.  My terminology here is 
> that the "host" computer is the one that contains a Leo file that we'd like 
> to work on in an instance of Leo running on a different computer;  The 
> "remote" computer is the one where we want to be able have Leo open that 
> host file.
>
> 1) Exfiltration of arbitrary files from the host computer.  We don't want 
> someone to use our host's leoserver to retrieve any arbitrary file by 
> pretending to be a remote Leo instance.
>
> 2) Replacement or corruption of arbitrary files - or even just Leo files - 
> on the host computer.
>
> Now, I realize that I've been picturing this remote usage as being 
> entirely within the local LAN, and even then you'd have to get the firewall 
> on the host machine to let our webchannel connections through.  Even so, I 
> think we should be thinking about the issues.
>

Definitely it should be done now / in parallel - and - not as an 
afterthought.
 

>
> I don't have a general solution to suggest here.  And I don't know much 
> about how the Windows firewall can be configured (not for Linux, either, 
> but I think at least there one can do almost anything).  But here are some 
> measures that could be done, probably for not too much effort:
>
> a. Get the firewall to only allow connections from the one specific 
> IP:port combination you want to use for the remote computer;
> b. Have leoserver only send and receive Leo outlines;
> b1.  Have leoserver validate that a file really is a proper Leo file;
> c. Have leoserver only save files from the remote that it had previously 
> sent to the remote.
> d. Have leoserver only send and receive files that have been specified in 
> a config file.
>

I think those are the bare minimal measures to get the implementation 
started - and - are needed as soon as leo-client 'leaves' localhost in real 
life usage.

I believe that transport layer security (e.g. support & usage of wss:// 
instead of only ws://) - as well as - proper authentication (e.g. login (w/ 
2FA?)) should be taken into account as well.

IMO both authentication & encryption should be made available, at least as 
opt-in extensions, for the leo-server environment on the host machine.
 

> Yes, it's true, someone could modify the leoserver python file to get 
> around these kinds of restrictions.  But to do that, they would have to 
> have local access already, and if that is the case they would already be 
> able to drop or retrieve any files they want anywhere on the machine.  So I 
> don't think we need to worry much about this particular possibility.
>

Agreed.

Looking forward to hear what Edward & Felix think about this topic.

With kind regards,

Viktor

-- 
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/2e88a390-25e9-406c-adae-434e31d4933bn%40googlegroups.com.

Re: Leo 6.6b2 released

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 25. Februar 2022 um 15:16:26 UTC+1:

> Leo http://leoeditor.com 6.6b2 is now available on GitHub 
>  and pypi 
> .
>

FYI: Installation of Leo 6.6b2 from PyPI is working fine for Fedora 34 and 
Debian 11 VMs on Qubes-OS.

With kind regards,

Viktor

-- 
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/2e094d4e-40f4-4d1f-a512-ff885c5d73c5n%40googlegroups.com.

Re: save file menu confusion

[Viktor Ransmayr]

Am Do., 13. Jan. 2022 um 20:10 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Thu, Jan 13, 2022 at 2:06 PM Félix  wrote:
>
>> Suggestion:
>> In photoshop and other mainstream and popular software packages, this
>> action is labeled as : "Save as Copy"
>>
>
> Or maybe "Save a Copy" ?  Either way, I think the new name is clearer.
>
> Rev a4bb2a1 in devel now uses "Save A Copy" as the menu name, and puts
> "Save A Copy" just below "Save As".
>

IMO this - and - the previous changes improve the readability of Leo's GUI
file menu a lot. - Thanks a lot!

With kind regards,

Viktor

-- 
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/CAAeSrG%2BLzawZwKoTBwJ%2BfnYR-%2BQNLp_FD1%3DBZ%2BAC-w9yO_pNxQ%40mail.gmail.com.

Re: save file menu confusion

[Viktor Ransmayr]

Am Do., 13. Jan. 2022 um 20:06 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Wed, Jan 12, 2022 at 2:52 PM Viktor Ransmayr 
> wrote:
>
>>
>> Minor correction: It should be SQLite. - See https://www.sqlite.org/
>>
>
> Fixed at rev c74db46 in devel.
>

Thanks for the quick fix.

With kind regards,

Viktor

-- 
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/CAAeSrGKxsdADbE-nQkw%2Bf0aL6VHJd3fWtaP5k4ayCY05zA38VA%40mail.gmail.com.

Re: save file menu confusion

[Viktor Ransmayr]

Hello Edward,

I know I'm late to the discussion, but here are my 2 cents.

Edward K. Ream schrieb am Mittwoch, 12. Januar 2022 um 17:08:06 UTC+1:

> On Tue, Jan 11, 2022 at 10:15 AM tbp1...@gmail.com  
> wrote:
>
>> 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)*.
>>
>
> Good suggestions.
>

Minor correction: It should be SQLite. - See https://www.sqlite.org/

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.
>>
>
> "Save As" and "Save To" are different. I think the terminology is fairly 
> widespread.
>
> "Save As" saves the outline to a different name, and also changes the name 
> of the outline to that new name so that a later "Save" will save the 
> outline to the new name. "Save To" saves the outline to a different name, 
> but leaves the name of the outline unchanged.
>
> I don't want to change the name of these menu items.
>

Searching for "Save As [and/or/versus] Save To" does not return any 
relevant results for me ...

I re-read your explanation multiple time - but - failed to get the use 
case, when & why  "Save To" is really needed :-(

Can you please explain the need for it once more. - TIA!

 With kind regards,

Viktor

-- 
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/4a56dd33-7995-417d-8a5a-57b3ee017858n%40googlegroups.com.

Re: Leo 6.6b1 released

[Viktor Ransmayr]

Edward K. Ream schrieb am Donnerstag, 11. November 2021 um 17:49:30 UTC+1:

> Leo 6.6b1 is now available (a day early) on GitHub 
> .
>
> I'll announce b1 more widely on Saturday.  Please test and report any 
> problems.
>

Leo 6.6b1 is running on a Debian 10 VM as well.

However if you start in a completely new environment, you still have to use 
the workaround to first install Leo 6.1 - and - then perform the explicit 
upgrade to 6.6b1 ...

With kind regards,

Viktor

-- 
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/c5398be0-793c-4b72-aafe-ad6908a170a2n%40googlegroups.com.

Re: Leo 6.6b1 released

[Viktor Ransmayr]

Edward K. Ream schrieb am Donnerstag, 11. November 2021 um 17:49:30 UTC+1:

> Leo 6.6b1 is now available (a day early) on GitHub 
> .
>
> I'll announce b1 more widely on Saturday.  Please test and report any 
> problems.
>

 Leo 6.6b1 is running fine on a Fedora 33 VM. - I tested it via Git as well 
as via PyPI.

With kind regards,

Viktor

-- 
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/1927f289-cf7c-4dc6-afb2-2c5e836a07c1n%40googlegroups.com.

Re: Please test devel

[Viktor Ransmayr]

Am Di., 12. Okt. 2021 um 23:45 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Tuesday, October 12, 2021 at 4:25:51 PM UTC-5 Edward K. Ream wrote:
>
> I'll fix these glitches asap. Many thanks for your thorough testing.
>>
>
> I have just fixed #2263
> , with an
> associated PR. Please reopen #2263 if necessary.
>

I updated my Debian VM - and - the reported issues are all gone.

Thanks a lot for the quick fix.

With kind regards,

Viktor

-- 
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/CAAeSrGL5zedYmvEFq7R9f9X2h7G02ihvKOKD%2BOjVM4Od%2BxSTpA%40mail.gmail.com.

Re: Please test devel

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 12. Oktober 2021 um 10:19:27 UTC+2:

> I've made many (hopefully) minor changes recently. They need to be tested 
> as thoroughly as possible.
>
> Except for adding unit tests, I plan no further work on Leo until Leo 6.5 
> goes out the door. So please test the devel branch with either Qt5 or Qt6.
>

I'm running the latest version of the 'devel' brunch successfully on a 
Fedora 33 VM as well as a Debian 10 VM on top of Qubes OS.

I did try to open Leo's own outlines from the GUI-menu, with the following 
result:.

* Open 'CheatSheet.leo' - OK. 
* Open 'LeoDocs.leo' - Not OK. - See "Log-004".
* -> file not found: 
/home/user/PyVE/GitHub/Leo/leo-editor/leo/doc/html\conf.py
* Open 'LeoDist.leo' - OK.
* Open 'LeoPy.leo' - Not OK. - See "Log-006".
* Open 'LeoPyRef.leo' - Not OK. - See "Log-007".
* -> can not open 
/home/user/PyVE/GitHub/Leo/leo-editor/leo/plugins/trace_keys.py
* Open 'myLeoSettings.leo' - OK.
* Open 'quickstart.leo' - OK.
* Open 'scripts.leo' - OK.
* Open 'leoSettings.leo' - OK.
* Open 'unittest.leo' - Not OK. - See "Log-012".
* -> no command function for 'open-unittest-leo'

You might consider fixing those glitches.

With kind regards,

Viktor

-- 
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/d554e531-e6bf-4cc8-8452-90d2094ead86n%40googlegroups.com.

Re: Naming commands in LeoInteg?

[Viktor Ransmayr]

Hello Felix,

Am Mi., 29. Sept. 2021 um 07:03 Uhr schrieb Félix :

> Thanks Viktor for trying out leoInteg! BTW I've just released 1.0.2 which
> fixes some 'rough edges' which will now help with basic usage - but I've
> also noticed the command naming may need a little cleanup too.
>
> So I guess your comment about naming of commands comes at the right time !
> :)
>
> *>Why did you decide to change this name?*
> First of all, I think the level at which you refer to the concept of
> 'commands' is from the 'Leo minibuffer' accessed normally with alt-x right?
>

Yes.

I guess so, because I have not added any 'indent' related commands to
> vscode itself. See the list of commands I added to vscode via U.I. or
> [ctrl+shift+P] palette here:
> https://github.com/boltex/leointeg/blob/master/src/constants.ts#L518 (the
> block starting at line 518)
>
> So for the commands available through the Leo minibuffer (alt+x) which I
> carried over to vscode in a manner similar to the command palette itself
> (ctrl+shift+P) have their total list gathered from Leo by a method that
> Edward wrote, that gets the list of all commands normally available through
> the Leo's minibuffer.
>

I'll look into this list.

*>Same question in a more general way: Which approach did you take with
> offering all/ most Leo commands using the same - or - a different name?*
>  It is then filtered with the help of 'good_command' / 'bad_command'
> lists. See
> https://github.com/leo-editor/leo-editor/blob/master/leo/core/leoserver.py#L1704
> for those two lists of banned/white-listed commands. This process was a bit
> rushed, and not very much tough of deeply *so careful revision of those 2
> lists is needed!* (Also, leointeg tries to spot commands that need user
> input -not all have been tested/stable - see last block starting at
> line698:
> https://github.com/boltex/leointeg/blob/master/src/constants.ts#L698 )
>
> About some of those commands that manipulate body text, like indent
> region, the vscode version of the functionality is preferred and the Leo
> equivalent command is not visible nor available by choice.
>
> As a workaround, for text-editing functionality, try ctrl+shift+P, which
> opens vscode's equivalence of leo's minibuffer to 'quickly find' any
> command from vscode 'normal' list of commands to perform a
> 'body-pane-editing' task.
>
> All other commands not-related to text-editing (what vscode already does
> as a simple text editor) are meant to be exposed.
>
> So please do signal any commands that you still think are missing. Or that
> you think are misplaced in leointeg's minibuffer 'good'/'bad' command
> filter lists!
>
> Testing, suggestions and comments are very much appreciated!  Thanks again
> Victor! :)
>

Thanks a lot for your feedback ! - I'll continue to provide feedback &
questions concerning my LeoInteg experience here ...

Viktor

-- 
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/CAAeSrGLKQ2nSaYs51dd%3Dj10iS5KDjSfmo2dcg1Cs-4P4FZb-3A%40mail.gmail.com.

Re: Vacation starts today

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 28. September 2021 um 12:47:28 UTC+2:

> I'll be back in about a week.
>

Enjoy your vacation.

With kind regards,

Viktor

-- 
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/ac8a0c16-d8b4-4927-ad65-b5e6325f360an%40googlegroups.com.

Naming commands in LeoInteg?

[Viktor Ransmayr]

Hello Felix,

Now that I try to use LeoInteg more & more, I noticed that there are 
sometimes subtle differences b/w LeoInteg & Leo concerning command names.

The first time when I noticed this, was with 'indent-region (Leo)' vs. 
'always-indent-region (LeoInteg)'. - Why did you decide to change this name?

Same question in a more general way: Which approach did you take with 
offering all/ most Leo commands using the same - or - a different name?

With kind regards,

Viktor

-- 
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/5da87049-6756-4658-99a9-c6d24e54fad4n%40googlegroups.com.

Re: #2220 fixed in devel and 6.4 branches. Pls test!!!

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 24. September 2021 um 13:46:52 UTC+2:

> I have just pushed the fix for #2220 
>  to the devel and 
> 6.4 branches. See PR # 
> .
>
> * The fixes were non-trivial. Please test the 6.4 today!!!* 
>
> In keeping with the new era in unit testing, I did most of the work in 
> devel using a strong new unit test. I then carefully merged the changed 
> code into the 6.4 branch, ran all the unit tests in unitTest.leo and did 
> some more hand tests.
>
> It's unpleasant to make such major changes just before 6.4, but i see no 
> good alternative. The new code is *much* better than the old. Not only 
> does the new code fix the reported problem, but for the first time (ever? 
> in years?) undo works in headlines. It's amazing that these bugs have been 
> around so long!
>
> *Summary*
>
> The 6.4 branch contains fixes to several *serious* bugs involving 
> headlines. I see no alternative but to include these fixes in the 6.4 
> release.
>
> Please test the 6.4 branch today.  Leo 6.4 is going out the door 
> tomorrow!!!
>

Works for me on both 'master' & 'devel' branch using a Fedora 33 VM on 
Qubes OS.

With kind regards,

Viktor

-- 
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/2b94b4d0-704a-4893-a7e1-aefb3afddaddn%40googlegroups.com.

Re: Please test Leo 6.4 at pypi

[Viktor Ransmayr]

Hello Thomas,

Am Do., 23. Sept. 2021 um 18:02 Uhr schrieb tbp1...@gmail.com <
tbp100...@gmail.com>:

> Still getting those error messages when opening LeoPyRef.leo:
>
> can not open
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/leo_to_html.xsl
> can not open
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_travis_unit_tests.py
> file not found:
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/launchLeo.py
> can not open
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_pytest_tests.py
> can not open
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/setup.py
> can not open
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/flake8-leo.py
> can not open
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pyflakes-leo.py
> can not open
> C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pylint-leo.py
>

This is all related to the fact that anything in the root folder of the
leo-editor code repository is not installed when using pip.

It has been reported by me a long time ago & analyzed by Matt Wilkie in
detail. - See

* https://github.com/leo-editor/leo-editor/issues/603

With kind regards,

Viktor

-- 
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/CAAeSrG%2Bw-SdkcnWWYvpPeQLnAptxKWez1UPv0vWh%2BuFczZTROA%40mail.gmail.com.

Re: Leo 6.4b3 released

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Samstag, 18. September 2021 um 18:18:14 UTC+2:

> On Friday, September 17, 2021 at 10:48:51 AM UTC-5 Edward K. Ream wrote:
>
> > I'll be working on a pypi distribution in the next day or so.
>
> Done in the 6.4 branch. Please test as follows:
>
> python -m pip install --index-url https://pypi.org/simple/ --no-deps 
> leo==6.4b3
>

Worked w/o any issues in a Fedora 33 VM w/i qubes OS R4.0

Thanks a lot for also testing the PyPI variant for Leo up front !

With kind regards,

Viktor

-- 
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/6a7ec26f-f105-42c6-b894-e4c60c97cba9n%40googlegroups.com.

Re: Current Line Highlighting Is Now Available In The Devel Branch

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Mittwoch, 15. September 2021 um 15:30:25 UTC+2:

> For those interested in how the background color is computed, here is the 
> algorithm:
>
> 1. Parse the Leo theme's style sheet and extract the body text foreground 
> and background colors.
> 2. If the theme has a light background, use a slightly darker color; if 
> the theme bg is dark, use a slightly lighter color.  Keep the hue the same, 
> only changing the intensity (change only V in the HSV triple).  If the bg 
> color is not specified, guess based on the fg color (currently this is a 
> very simple minded guess)..
> 3. If the theme's bg color is very dark, use a larger change in intensity 
> than otherwise (because the minimum perceptible change seems to be larger 
> in the V value for very dark colors).
>
> Please let us know how the highlighting works for you!
>

Works like a charm for me.

On Wednesday, September 15, 2021 at 9:13:40 AM UTC-4 tbp1...@gmail.com 
> wrote:
>
>> Highlighting of the body line the cursor is now in the latest version of 
>> the *devel* branch. Highlighting is turned off by default.  To turn it 
>> on, add a setting to myLeoSettings.leo, or to an outline in which you want 
>> to try it out.  The setting is:
>>
>> @bool highlight-body-line = True
>>
>> By default, the highlight color will be computed based on the background 
>> color of your theme.  If you do not like the computed color, you can 
>> override it with another setting:
>>
>> @string line-highlight-color = yourcolor
>>
>> Instead of *yourcolor*,  use the CSS color you want.  Valid css colors 
>> are standard css color names like *aliceblue*, *lightgrey*, etc. You can 
>> also use css rgb color values like *#1253da*. If the color is not a 
>> valid css color, black will be used, which is not likely to be a good 
>> highlight color. (Note that the allowed color names are those known to Qt, 
>> and may not include the full range used by browsers).
>>
>> The *Help/Open Help topics* menu has a new entry 
>> *Help-For-Highlight-Current-Line*  that displays this information about 
>> the color settings.
>>
>
Thanks a lot for adding this visual improvement.

With kind regards,

Viktor

-- 
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/93a73d68-2002-471f-8643-45488800a528n%40googlegroups.com.

Re: Please Test Current Line Highlighting

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Freitag, 27. August 2021 um 23:36:40 UTC+2:

> The attached Leo outline contains a script to highlight the line in the 
> body that has the cursor.  You can activate it by selecting the top-most 
> node, then pressing CTRL-b.  After this, the cursor line should become 
> highlighted anywhere in the outline.  Other outlines will not be affected.
>
> If you want to try it out in another outline, copy the script, paste it 
> into the other outline, and run it with CTRL-b.
>
> Activating the highlighting this way is a bit strange, but lets you try it 
> out without needing to modify Leo itself or install a different version.  
> Eventually, the code would be included and activated when the body pane is 
> constructed.
>
> I'd like to know how you like the effect, and whether you think the 
> highlight color works well enough.  
>
> Note that the highlight color will be different for different Leo themes 
> (and no-theme color schemes).  The script tries to calculate reasonable 
> colors.  If the background is light, the highlight will be the same hue but 
> darker.  If the background is dark, the highlight will be the same hue but 
> lighter.  If the background is very light or very dark, different rules may 
> be applied.
>
> I have tried this out on every theme in Leo's theme directory.  The colors 
> seem to work acceptably to me.  If you have your own theme that isn't one 
> of the standard ones, I'm especially interested in how that works out.  
> And, of course, post here if you notice any bugs or anomalies.
>

I did a quick test in my default environment with "theme_name = None" and 
it looks good to me.

I have not done any own theming work so I can't provide feedback on your 
other request.

With kind regards,

Viktor

-- 
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/827699df-da82-42da-a19d-2949eb76f40dn%40googlegroups.com.

Re: Release dates for Leo 6.4

[Viktor Ransmayr]

Hello Edward,

On Mon, 23 Aug 2021, 19:47 Edward K. Ream,  wrote:

> Félix and I are comfortable with the following schedule:
>
> *Friday, August 27*: Release Leo 6.4b2.
>

Did you mean 6.4b3 ?


> *Friday, September 3*: Release Leo 6.4 final.
>
> *Notes*
>
> Félix expects to release leoInteg 0.1.18 beta very soon.
>
> From my perspective, Leo 6.4 is code complete. Félix might change
> leoserver.py; I will change documentation and release files.
>
> If significant problems arise I'll release 6.4b3 on Sept 3, and 6.4 final
> one week later.
>
> *Summary*
>
> leoInteg 1.0 and Leo 6.4 will be released together. Leo is code complete;
> leoInteg nearly so.
>
> This dual release will likely be one of the most significant milestone in
> Leo's history.  Félix and I want to ensure this release is as close to
> perfect as we can make it.
>

With kind regards,

Viktor

>

-- 
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/CAAeSrGKqSDe3Vqq1XR3ggc-w_F9tboconpE5tErRtYkPGwVRyA%40mail.gmail.com.

Re: Leo for VSCode: LeoInteg 0.1.17 (second beta) Released!

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Montag, 16. August 2021 um 07:48:00 UTC+2:

> *Leonistas of the world can now try out the second beta release!*
>
> I'm delighted to announce that leointeg  
> (Leo for VSCode) is 
> now at its second 'beta' release, and offered as an '.vsix' extension file, 
> where most features are present -- but in dire need of some user testing to 
> finalize and polish before a launch on the official vscode/microsoft store!
>

I successfully tested the 'rst3' command in the second beta release.

Thanks a lot for the quick fix of this reported issue !

With kind regards,

Viktor

-- 
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/068d913b-e005-4398-8e39-e343d59360b2n%40googlegroups.com.