Re:  LeoJS Beta 0.2.13 Released

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

Re:  LeoJS Beta 0.2.13 Released

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!

Re: Eight more PRs merged into devel

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

Re: Two more PRs merged into devel

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* > > &

Re: Two more PRs merged into devel

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

Re: Two more PRs merged into devel

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

Re: I just had successful eye surgury

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

Re: Leo 6.7.8 released to pypi

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

Re: Leo 6.7.8.post1 is ready for testing

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

Re: Leo 6.7.8.post1 is ready for testing

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

Re: Leo 6.7.8 released, but not to PyPi

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

Re: Discuss: Leo 6.7.8 will install only PyQt6

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.

Re: Discuss: Leo 6.7.8 will install only PyQt6

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

Re: Discuss: Leo 6.7.8 will install only PyQt6

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

Re: PR 3774 completes the 6.7.8 code base

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

Re: LeoInteg using Leo's Null GUI ?

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

Re: LeoInteg using Leo's Null GUI ?

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

Re: LeoInteg using Leo's Null GUI ?

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

LeoInteg using Leo's Null GUI ?

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

Re:  LeoInteg 1.0.17 Released

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

Re:  LeoInteg 1.0.17 Released

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 -

Re: leoJS Seems To Work With VSCodium

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

Re: ✨LeoJS beta 0.2.0 Released!

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

Re: Leo 6.7.4 released

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

Re: Leo 6.7.4 released

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

Re: Leo 6.7.4 released

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

Re: Leo 6.7.4 released

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

Re: Leo 6.7.4 released

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

Re: Leo 6.7.4 released

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

Re: ENB: Ahas re paste-retaining-clones

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

Re: PR #3468 merged into devel

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

Re: Leo 6.7.4 is code complete. Please test

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

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

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

Re: Another mass update: PR #3367

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

Re: Unable to create Leo's Documentation locally

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

Re: Unable to create Leo's Documentation locally

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

Unable to create Leo's Documentation locally

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,

Re: In hospital for severe abdominal pains

> 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

Re: Failing unit test in devel branch

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

Re: Failing unit test in devel branch

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

Re: Failing unit test in devel branch

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

Failing unittest in devel branch

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)

Re: Leo 6.7.1 coming Friday, Nov. 4

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

Re: macos 10.13 - leo 6.7.0 with miniconda

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

Re: Two more PRs merged into devel

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. >

Re: Two more PRs merged into devel

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

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

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

Re: Leo 6.6.4 released

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. > >

Re: Leo 6.6.3 coming this Friday, July 22

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

Re: FYI: I have closed most Leo issues

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 *

Re: Updated Leo 6.6.2 released

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 >

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

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

Re: Different results of 'test-all' cmd

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

Re: F5 Key Opens New Leo Session?

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

Re: Different results of 'test-all' cmd

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. >> > >

Different results of 'test-all' cmd

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

Re: All completed 6.6.2 work has been merged into devel

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. >> >

Re: All completed 6.6.2 work has been merged into devel

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

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

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 >

Re: Please test Leo's pylint command in devel

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

Re: Please test Leo's pylint command in devel

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

Re: 6.6 coming this Thursday, March 31

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: >> >> >

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

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

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

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

Re: 6.6 coming this Thursday, March 31

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 &

Re: 6.6 coming this Thursday, March 31

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

Re: Please test devel and PR #2523

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

Re: Remote Leo Files - Security Issues

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

Re: Leo 6.6b2 released

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

Re: save file menu confusion

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" ?

Re: save file menu confusion

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.

Re: save file menu confusion

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,

Re: Leo 6.6b1 released

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

Re: Leo 6.6b1 released

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

Re: Please test devel

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 >

Re: Please test devel

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

Re: Naming commands in LeoInteg?

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

Re: Vacation starts today

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

Naming commands in LeoInteg?

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

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

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 # > . > > *

Re: Please test Leo 6.4 at pypi

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 >

Re: Leo 6.4b3 released

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

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

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

Re: Please Test Current Line Highlighting

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

Re: Release dates for Leo 6.4

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

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

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'

Re: Leo for VSCode: LeoInteg beta 0.1.16 released

Hello Felix, Félix schrieb am Sonntag, 15. August 2021 um 22:17:26 UTC+2: > how are you invoking this command in Leo? keybinding, from the menu? or > the alt-x minibuffer? Alt-x minibuffer. With kind regards, Viktor -- You received this message because you are subscribed to the Google

Re: Leo for VSCode: LeoInteg beta 0.1.16 released

Hello Felix, Félix schrieb am Sonntag, 15. August 2021 um 21:55:45 UTC+2: > Hi Viktor, > > This may seem silly, but I dont know anything about rst or what the rst3 > command is/does/how it's invoked, ...is it from a plugin ect...? > > Can you give me a 10 word sentence refresher about what it

Re: Leo for VSCode: LeoInteg beta 0.1.16 released

Hello Felix, Viktor Ransmayr schrieb am Mittwoch, 21. Juli 2021 um 07:20:50 UTC+2: > Félix schrieb am Montag, 19. Juli 2021 um 01:50:50 UTC+2: > >> *Hello to all of you in the Leonine world! * >> I'm glad to announce that leointeg >> <https://github.com/boltex/leo

Re: Leo for VSCode: LeoInteg beta 0.1.16 released

Hello Felix, Félix schrieb am Montag, 19. Juli 2021 um 01:50:50 UTC+2: > > *[image: banner-blur-narrow.png]* > > > *Hello to all of you in the Leonine world! * > > I'm glad to announce that leointeg > (Leo for VSCode) is > now at the 'beta'

Re: Last step before leointeg 1.0

Hello Félix, Félix schrieb am Freitag, 4. Juni 2021 um 22:31:12 UTC+2: > > Are you aware of any obstacles, if I would like to try out 0.1.14 in a > Fedora 33 - based Linux VM? > No i don't foresee any problems trying to test the vscode+leo+leointeg > combination on a VM. I develop on both

Re: Last step before leointeg 1.0

Hello Félix, Am Fr., 4. Juni 2021 um 06:30 Uhr schrieb Félix : > > Hey you guys, > > I just pushed 0.1.14 with a bunch of new features (Find-panel, > import-file(s), and many more) along with bug fixes on the master branch! > > *One last step:* I'm now going to finish re-writing/de-bugging the >

Re: First draft: documentation for leoservers.py

Hello Edward, Edward K. Ream schrieb am Samstag, 15. Mai 2021 um 18:01:12 UTC+2: > On Sat, May 15, 2021 at 10:52 AM Alexander wrote: > > Thanks for these comments. > > Because it was documented as not being part of core and I was not >> familiarized with the code of recent years, I was also

Re: Location of 'leoserver.py' & 'leoclient.py' in Leo's directory structure?

Hello Félix, hello Edward, Félix schrieb am Freitag, 21. Mai 2021 um 04:05:14 UTC+2: > > Now something that popped in my mind a second ago is intriguing me very > much: If someone had installed Leo with pip, would then it be possible for > that person to just start Leo, open leopyref.leo, hit

Re: Location of 'leoserver.py' & 'leoclient.py' in Leo's directory structure?

Hello Félix Félix schrieb am Dienstag, 18. Mai 2021 um 00:55:18 UTC+2: > > I don't know much at all about those python system specific issues. > (although I wonder how the other python files that import parts of leo do > exist in the root of the leo folder without problem, such as

Location of 'leoserver.py' & 'leoclient.py' in Leo's directory structure?

Hello Edward & Félix, Looking into the sources I also noticed, that we'll run into a similar problem as already documented in issue #603. In other words, both files should be moved from the top-level, i.e. * https://github.com/leo-editor/leo-editor/blob/devel/leoserver.py *

Re: First draft: documentation for leoservers.py

Hello Félix, Félix schrieb am Samstag, 15. Mai 2021 um 21:52:25 UTC+2: > To address Viktor's last point: Both the original, and the new one, *are > made to be totally agnostic of the client and are not made with leointeg > exclusivity in mind at all.* Any signs of that not being the case >

Re: First draft: documentation for leoservers.py

Hello Edward, Edward K. Ream schrieb am Samstag, 15. Mai 2021 um 17:51:53 UTC+2: > On Sat, May 15, 2021 at 8:06 AM tbp1...@gmail.com > wrote: > >> I'm not necessarily saying that it doesn't do what it's supposed to. I'm >> saying that the draft doc doesn't say what it is supposed to do, at

Re: First draft: documentation for leoservers.py

tbp1...@gmail.com schrieb am Samstag, 15. Mai 2021 um 06:39:53 UTC+2: > Looking at this and thinking about it a bit for the first time, I have the > reaction that an HTTP server should respond to at least GET and POST > requests. The draft docs say nothing about this. The server docs should

Re: First draft: documentation for leoservers.py

Hello Edward, Am Fr., 14. Mai 2021 um 14:54 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > The following is pre-writing for a new Chapter in Leo's documentation. > > All comments, suggestions, additions, and corrections are welcome. > > - > > leoserver.py is a stand-alone web server

  1   2   3   4   5   >