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 tho

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 to be

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

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, Vik

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 vie

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 complet

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 r

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 t

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 D

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 the

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 rec

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 continue

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

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 'test-

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 * https://github.com/leo-editor/leo-editor/issues/15

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

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 `python

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 outp

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 server

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 ca

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 Vikt

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 h

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 is

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

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, tha

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 F

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 pl

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 y

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 t

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

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 > C:/Users/tom/AppData/R

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 p

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 0.1.1

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' release

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 Grou

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 is

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/le

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' s

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 win

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 ini

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 c

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 launchleo.py,

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 * https://github.com/l

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

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 le

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 tha

Re: Please test the ekr-qt branch (Qt6) *regardless* of your qt version

Hello Edward, Edward K. Ream schrieb am Samstag, 10. April 2021 um 22:25:29 UTC+2: > The ekr-qt branch (PR #1881 > for issue #1846 > ) is ready for > testing. > As part of my light tests

Re: Please test the ekr-qt branch (Qt6) *regardless* of your qt version

Hello Edward, On Saturday, April 10, 2021 at 3:25:29 PM UTC-5 Edward K. Ream wrote: > > > The ekr-qt branch (PR #1881 > for issue #1846 > ) is ready for > testing. > ... > > I would like

Re: Change to ekr-abbrev branch

Hello Edward, Edward K. Ream schrieb am Dienstag, 13. April 2021 um 17:28:33 UTC+2: > On Monday, April 12, 2021 at 11:44:16 AM UTC-5 Edward K. Ream wrote: > > I plan to merge [the ekr-abbrev] branch into devel later today. > > > Done. Please report any problems immediately. > Not a problem repor

Re: The new rst3 command is now in devel

Hello Edward, Edward K. Ream schrieb am Freitag, 9. April 2021 um 19:03:13 UTC+2: > > @ @rst-options >> default_path=./TL/2021/01/CWxx/ >> @c >> >> in the @path body. - Did you consider removing the now 'useless' >> default_path' statement - or - the @rst-options section in general? >> > > I d

Re: The new rst3 command is now in devel

Hello Edward, Edward K. Ream schrieb am Montag, 5. April 2021 um 07:51:32 UTC+2: > On Sun, Apr 4, 2021 at 1:27 PM Viktor Ransmayr > wrote: > ... > >> I'm not (yet?) confident / really happy about the removal of the >> "@rst-preformat" option. >&

Re: The new rst3 command is now in devel

Hello Edward, Edward K. Ream schrieb am Sonntag, 4. April 2021 um 14:10:33 UTC+2: > On Sun, Apr 4, 2021 at 4:44 AM Viktor Ransmayr > wrote: > > I used the new command successfully on one outline. - It did convert >> everything properly ... >> > > Glad to he

Re: The new rst3 command is now in devel

Hello Edward, Edward K. Ream schrieb am Samstag, 3. April 2021 um 23:00:52 UTC+2: > On Saturday, April 3, 2021 at 7:40:12 AM UTC-5 viktor@gmail.com wrote: > > > Let me know, when this new command is available in the 'devel' branch & > I'll give it a try on some of my outlines. > > The rst-co

Re: The new rst3 command is now in devel

Hello Edward, Am Sa., 3. Apr. 2021 um 13:44 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > On Sat, Apr 3, 2021 at 4:53 AM Viktor Ransmayr > wrote: > > * The directory structure I've been using is "./ >> ///". >> >> As far as I know,

Re: The new rst3 command is now in devel

Hello Edward, Edward K. Ream schrieb am Freitag, 2. April 2021 um 23:31:30 UTC+2: > > On Fri, Apr 2, 2021 at 2:31 PM Viktor Ransmayr > wrote: > > In the example file you sent, you could set: > > @string rst3-default-path = ./TL/2021/01/CWxx/ > > in the .leo file&#

Re: The new rst3 command is now in devel

Hello Edward, Edward K. Ream schrieb am Samstag, 3. April 2021 um 00:09:31 UTC+2: > On Fri, Apr 2, 2021 at 4:36 PM Edward K. Ream wrote: > > > I have just created #1876: Honor @rst-preformat. It should be easy to > fix. > > The ekr-rst-preformat branch contains the proposed fix. See PR #1877 >

Re: The new rst3 command is now in devel

Hello Edward, I started 'playing' with this commit & have to report the following ... Am Fr., 2. Apr. 2021 um 18:04 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > On Friday, April 2, 2021 at 7:25:01 AM UTC-5 Edward K. Ream wrote: > > Devel now contains the completed #1867 >>

Re: The new rst3 command is now in devel

Hello Edward, Edward K. Ream schrieb am Freitag, 2. April 2021 um 18:04:01 UTC+2: > On Friday, April 2, 2021 at 7:25:01 AM UTC-5 Edward K. Ream wrote: > > Devel now contains the completed #1867 >> : radically >> simplify the rst3 command. >>

Rst3 vs. rst4?

Hello Edward, When I was reading your latest post on "Discuss: Radically simplify the rst3 command?", one additional un-related question came to my mind: *Can you explain what measures you use to decide, when you rework an available command / extension & accept (the possibility of) breaking

Re: Leo on Debian?

ng me of that option. On Saturday, March 13, 2021 at 3:15:57 PM UTC-5 viktor@gmail.com wrote: > >> Viktor Ransmayr schrieb am Samstag, 13. März 2021 um 20:19:02 UTC+1: >> >>> >>> stevelitt schrieb am Samstag, 13. März 2021 um 19:54:46 UTC+1: >>> >>

Re: Leo on Debian?

Viktor Ransmayr schrieb am Samstag, 13. März 2021 um 20:19:02 UTC+1: > > stevelitt schrieb am Samstag, 13. März 2021 um 19:54:46 UTC+1: > >> >> This isn't responsive to your question, but it's some information... >> >> I have an extremely low

Re: Leo on Debian?

Hello Steve stevelitt schrieb am Samstag, 13. März 2021 um 19:54:46 UTC+1: > > This isn't responsive to your question, but it's some information... > > I have an extremely low opinion of Debian. I'm not a big fan of pip > either. Why not follow the instructions for git clone to install? I've >

Re: Leo on Debian ?

tbp1...@gmail.com schrieb am Freitag, 12. März 2021 um 22:38:31 UTC+1: > I tried downgrading Leo to 6.0, but it still failed with the same error. > Then I downgraded PyQt5 to 5.15.1. I then downgraded PyQtWebEngine - but > spelled all lowercase - also to 5.15.1 and then Leo 6.0 worked. Then

Re: Leo on Debian ?

Viktor Ransmayr schrieb am Freitag, 12. März 2021 um 22:09:20 UTC+1: > Am Fr., 12. März 2021 um 19:19 Uhr schrieb tbp1...@gmail.com < > tbp1...@gmail.com>: > >> I just installed a Debian VM. After installing Leo with pip I got >> exactly the same error message as yo

Re: Leo on Debian ?

Am Fr., 12. März 2021 um 19:19 Uhr schrieb tbp1...@gmail.com < tbp100...@gmail.com>: > I just installed a Debian VM. After installing Leo with pip I got exactly > the same error message as you. I don't know what to do with it, though. > > On Friday, March 12, 2021 at 12:29:34 PM UTC-5 viktor

Re: Leo on Debian ?

tbp1...@gmail.com schrieb am Freitag, 12. März 2021 um 15:44:31 UTC+1: > I can't help directly with Debian, but Leo works fine on my VMs running > both Mint and Ubuntu, which are both Debian-based. I would have thought > that they use Debian packages directly, but maybe that's not so. > > ... >

Leo on Debian ?

Hello Leo Community, Does anyone have Leo successfully running on top of Debian? Background of my question: Since more than a year I'm successfully running Leo in various Fedora & Windows VMs on top of Qubes OS. - For some reason I now have to use a Debian VM - and - obviously would like to co

Leo on Debian?

Hello Leo Community, Does anyone have Leo successfully running on top of Debian? Background of my question: Since more than a year I'm successfully running Leo in various Fedora & Windows VMs on top of Qubes OS. - For some reason I now have to use a Debian VM - and - obviously would like to co

Re: abbreviations ended with ";" don't work for me

Hello Edward, Am Mi., 17. Feb. 2021 um 12:53 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > On Wed, Feb 17, 2021 at 3:56 AM Eloi Torrents > wrote: > >> Hi, >> >> I was having trouble setting up an abbreviation like >> >> > date;;={|{import time; x=time.asctime()}|} >> >> I think a cause f

Re: ENB: unit testing for leoserver.py

Edward K. Ream schrieb am Montag, 15. Februar 2021 um 23:05:42 UTC+1: > On Mon, Feb 15, 2021 at 3:30 PM Viktor Ransmayr > wrote: > > > Is there a specific reason, why you make it Windows specific here - and > - don't use the same generic variant, that you use below for

Re: ENB: unit testing for leoserver.py

Hello Edward, Edward K. Ream schrieb am Samstag, 13. Februar 2021 um 13:58:26 UTC+1: > This Engineering Notebook post shows the workflows I use to unit tests for > leoserver.py. I won't say much about the unit tests themselves. If you are > interested in the details, see the TestLeoServer class

Re: Sabbatical status and plans

Hello Edward, Edward K. Ream schrieb am Dienstag, 2. Februar 2021 um 13:08:58 UTC+1: > I'm back from a two-week staycation, eager to work. > Welcome back & thanks a lot! - I learned a new word, that I had not known before. I'm not looking for anything better than python. As I said yesterday,

Re: ENB: Leo as a web app?

tbp1...@gmail.com schrieb am Montag, 1. Februar 2021 um 05:21:52 UTC+1: > On Sunday, January 31, 2021 at 1:46:13 PM UTC-5 viktor@gmail.com > wrote: > >> tbp1...@gmail.com schrieb am Sonntag, 31. Januar 2021 um 17:22:29 UTC+1: >> > [snip] >> > OK, I misunderstood your question then - and - I g

Re: ENB: Leo as a web app?

tbp1...@gmail.com schrieb am Sonntag, 31. Januar 2021 um 17:22:29 UTC+1: > Viktor, those diagrams describe the Jupyter ecosystem, but not a workflow > that uses it. Your workflow is what I'm interested in. For example, if > you are not doing anything very specific to Jupyter, Leo + VR3 provide

Re: ENB: Leo as a web app?

tbp1...@gmail.com schrieb am Sonntag, 31. Januar 2021 um 15:15:13 UTC+1: > Viktor, could you say more about the workflow you are thinking of? For > myself so far, I am happy to keep Leo open in its own app outside a > browser. And I would prefer to avoid running a server on my system to > m

Re: ENB: Leo as a web app?

Hello Edward, Am So., 31. Jan. 2021 um 11:46 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > On Thu, Jan 28, 2021 at 8:24 AM gar wrote: > >> It depends on how rich leo-in-web become. If the same feature-full as a >> console version of UI - then no, thank you. >> If rich enough to use it as

Re: Command 'restart-leo' is not working ...

tbp1...@gmail.com schrieb am Samstag, 9. Januar 2021 um 17:01:53 UTC+1: > I had not even known this command existed. So I tried it, and although > Leo restarted successfully, I noticed a lot of apparently similar error > messages. Here is a partial list: > > can not open > C:/Users/tom/AppDat

Command 'restart-leo' is not working in Leo's devel branch, build 7d98c87f04

Hello Edward, I receive the following traceback, when I execute the 'restart-leo' command: ### (Leo-Repo) [user@fedora-leo-study-vm Leo-Repo]$ leo & [1] 3307 (Leo-Repo) [user@fedora-leo-study-vm Leo-Repo]$ setting leoID from os.getenv('USER'): 'user' Leo 6.4-devel, devel branch, build 7d98c87f

Re: Pls read: The new theme code is in devel

Hello Edward, Edward K. Ream schrieb am Donnerstag, 24. Dezember 2020 um 12:23:25 UTC+1: > On Thu, Dec 24, 2020 at 1:37 AM Viktor Ransmayr > wrote: > >> >> I'm attaching the simplest possible test outline, which in my Fedora 32 >> Linux OS environment: &g

<    1   2   3   4   5   6   >