Re: Discuss: remove ctext importer and writer?

On Wed, Sep 13, 2023 at 10:58 AM Edward K. Ream wrote: Does anyone know anything about the ctext file format? Googling ctext > yields no relevant hits. > Hmm. The docstring for the ctext importer class is: QQQ Read/Write simple text files with hierarchy embedded in headlines:: L

Discuss: remove ctext importer and writer?

Does anyone know anything about the ctext file format? Googling ctext yields no relevant hits. The ctext importer came to my attention today because of #3558 , which lists various importer-related "quirps". The most serious concerns ctext,

Re: Read the history of Leo

On Sat, Sep 9, 2023 at 6:50 PM HaveF HaveF wrote: I have kept the new entries *brief* and have removed some extraneous >> details (logs) :-) >> > Thanks for the update, Edward. > You're welcome. History is not history only, it is also a clue for what's important > commands which readers can't

Re: Expect Leo 6.7.5 on Friday, September 16

On Sat, Sep 9, 2023 at 4:22 PM Edward K. Ream wrote: Félix and I have agreed to delay 6.7.5 until he has nearly completed leoJS. > The unofficial release date for Leo is now Friday, September 29. That may > change. I should emphasize that (except for fixing quirps) I shall make no f

Re: Expect Leo 6.7.5 on Friday, September 16

On Sunday, September 3, 2023 at 6:23:44 AM UTC-5 Edward K. Ream wrote: Leo 6.7.5 contains significant improvements to Leo's python importers. It also adds several new commands. I'll save any further bright ideas for enhancements for Leo 6.7.6 :-) This release will be the last before the first

Re: Read the history of Leo

On Wednesday, September 6, 2023 at 11:33:52 PM UTC-5 iamap...@gmail.com wrote: https://leo-editor.github.io/leo-editor/history.html Leo's history is intriguing. I thoroughly enjoyed reading everything except the change log section. I have revised this history to include events following

Re: Read the history of Leo

On Wed, Sep 6, 2023 at 11:33 PM HaveF HaveF wrote: > https://leo-editor.github.io/leo-editor/history.html > > Leo's history is intriguing. I thoroughly enjoyed reading everything > except the change log section. Leo's history goes beyond the mere > development of LEO; it encompasses a journey of

Re: When scripting with Leo, how to call a command by name?

On Monday, September 4, 2023 at 5:01:51 AM UTC-5 Edward K. Ream wrote: On Sun, Sep 3, 2023 at 7:41 PM Félix wrote: The *c.doCommandByName* method exists, but it insists on having an event as a second parameter. ... I discovered that I can make it work by passing a fake event such as : {&q

Re: Quick Survey: When running script in leojs, where should the 'vscode' object be accessible?

On Sun, Sep 3, 2023 at 8:33 PM Félix wrote: I thought I'd share this :) > > Just a small example script that is possible to run in leojs, (with also > having the vscode API available in g.app.vscode) > > Incredibly, when executing the script, the global objects you'd expect to > see in

Re: When scripting with Leo, how to call a command by name?

On Sun, Sep 3, 2023 at 7:41 PM Félix wrote: The *c.doCommandByName* method exists, but it insists on having an event as > a second parameter. Hah. I had completely forgotten about c.doCommandByName. Furthermore, I had completely mis-remembered the complexity of k.simulateCommand. Maybe

Re: ENB: info re unit tests

On Sun, Sep 3, 2023 at 6:54 AM Edward K. Ream wrote: > This Engineering Notebook post discusses conventions for unit testing. It > continues a discussion in PR #3532 > <https://github.com/leo-editor/leo-editor/pull/3532>. This post will be > pre-writing for an info item. &

ENB: info re unit tests

This Engineering Notebook post discusses conventions for unit testing. It continues a discussion in PR #3532 . This post will be pre-writing for an info item. Félix asked about the difference between assert and self.assertX

Expect Leo 6.7.5 on Friday, September 16

Leo 6.7.5 contains significant improvements to Leo's python importers. It also adds several new commands. I'll save any further bright ideas for enhancements for Leo 6.7.6 :-) This release will be the last before the first official release of leoJS. Félix continues to suggest small changes.

Re: Quick Survey: When running script in leojs, where should the 'vscode' object be accessible?

On Sat, Sep 2, 2023 at 8:49 PM Félix wrote: > Not sure what to decide for this so I thought of doing this quick survey! > :) > > When running scripts, (CTRL+B) Leo offers the g, c and p variables. I > obviously want to expose the vscode API from it's base object "vscode". > > Should it be

Re: Help needed with understanding @others vs @all directives

On Sat, Sep 2, 2023 at 6:15 PM Félix wrote: I've never used the @all directive and I'd like to test it properly with > both Leo and LeoJS. In leoPy.leo (LeoPyRef.leo) the node @file ../doc/leoAttic.txt contains the only @all directive that Leo uses. A recent PR cleared most of the attic, but

Re: Leointeg - A beginner fumbles!

On Thu, Aug 31, 2023 at 9:11 PM Félix wrote: I have no problem with a release of 6.7.5 in the time frame that you > suggested. Excellent. I've the moved four "waiting" items to 6.7.6, still due in November. I'll fix the new quirps you just reported for 6.7.5 soon. Keep them coming :-)

Re: Leointeg - A beginner fumbles!

On Wednesday, August 30, 2023 at 8:29:06 PM UTC-5 Félix wrote: But hold on to your hats, LeoInteg is insignificant compared to LeoJS! (Coming soon!) That's great news! Do you want to include the completed 6.7.5 items

New python importer merged into devel

PR #3518 contains, by far, Leo's best python importer. I have tested the importer on mypy sources. The leo-editor-contrib repo contains a new version of mypy.leo. See the StudyOutlines

Re: ENB: Improving the python importer

On Sunday, August 27, 2023 at 5:44:23 AM UTC-5 Edward K. Ream wrote: PR #3515 <https://github.com/leo-editor/leo-editor/pull/3515> contains preliminary work improving Leo's python importer. This PR has now been merged into devel. *Packaging* Moving the RIC postposs into the base Im

Re: @auto-md: multiple vnodes with gnx

On Tue, Aug 29, 2023 at 8:03 AM Thomas Passin wrote: > You can also export the Markdown to your external text editor using the > viewrendered3 plugin. The drawback is that you would need to save it to > the desired location yourself. Imo, after a certain point of complexity it will be simpler

Re: @auto-md: multiple vnodes with gnx

On Mon, Aug 28, 2023 at 3:56 AM p.os...@datec.at wrote: Yes, that's the point. It simply should work as the RST-plugin does. > LeoDocs.leo contains a disabled button: make-md-toc. Please take a look. Funny, there is a tip about this script. Edward -- You received this message because you

Re: ENB: Improving the python importer

On Mon, Aug 28, 2023 at 3:30 AM Edward K. Ream wrote: > *os.path.relpath *works in all common situations. > I'm not sure recursive imports should allow such "distant" @path directives. Recent revs avoid os.path.relpath entirely. Instead, the path to each imported

Re: ENB: Improving the python importer

On Sunday, August 27, 2023 at 5:44:23 AM UTC-5 Edward K. Ream wrote: > Oops: The generated @path directives will be *wrong* unless dir_ is either the outline directory or a subdirectory. Let's call this the *directory constraint*. *os.path.relpath *works in all common situations. The out

ENB: Improving the python importer

PR #3515 contains preliminary work improving Leo's python importer. This work has uncovered several related issues. This Engineering Notebook discusses the way forward. *Background* The files in leo/plugins/importers contain all of

Re: @auto-md: multiple vnodes with gnx

On Thu, Aug 24, 2023 at 8:09 PM HaveF HaveF wrote: > > Imo, `@clean` is a better option for most people than `@auto`. >> > > I see. But like @auto-md can generate section heading of the appropriate > level, this feature is indeed more convenient. > If I use @clean, I have to generate my own

Re: @auto-md: multiple vnodes with gnx

On Wed, Aug 23, 2023 at 11:29 PM HaveF HaveF wrote: > > @bool create-at-persistence-nodes-automatically > > Everything works for me if this setting is True. (The default in > leoSettings.leo is False). > > > How about set the setting to True as default? > Creating `@persistence` nodes by

Re: @auto-md: multiple vnodes with gnx

On Wednesday, August 23, 2023 at 7:18:26 AM UTC-5 p.os...wrote: It becomes more and more annoying, that when I want to clone a node below a @auto-md file into another @auto-md I get this error: What is the value of this setting in your file? (show-settings will list all settings.) @bool

Re: @auto-md: multiple vnodes with gnx

On Wed, Aug 23, 2023 at 7:18 AM p.os...@datec.at wrote: > when I want to clone a node below a @auto-md file into another @auto-md I get this error: Thanks for this report. I have just created #3512 for it. I'll investigate immediately.

ENB: An assessment of json-based cut/copy/paste-node commands

This Engineering Notebook post summarizes PR #3473 : use flat json for cut/copy/paste nodes. This PR is full of unexpected complications and edge cases. *I plan to delay this PR until after Félix releases leoJS*. I don't want to distract

Re: Option key Mac

On Tue, Aug 22, 2023 at 4:13 AM kilivor wrote: > Solved, thanks! > Glad to hear it. Good work :-) 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

Re: LeoInteg 1.0.14 released

On Mon, Aug 21, 2023 at 6:28 AM Thomas Passin wrote: I had the same situation. I found I had to update vsc, then restart vsc. > I had automatic updates for extensions enabled, and after the restart, > Leointeg's version had been updated to 1.0.14. > Thanks Thomas. That worked for me too.

Re: LeoInteg 1.0.14 released

On Saturday, August 19, 2023 at 9:06:17 PM UTC-5 Félix wrote: > Announcing the release of LeoInteg 1.0.14 > Available to all leonistas via automatic update, or on the vscode marketplace

Re: LeoInteg 1.0.14 released

On Sat, Aug 19, 2023 at 9:06 PM Félix wrote:  *Announcing the release of LeoInteg 1.0.14 > * > Many thanks for all your good work! LeoInteg (and soon, leoJS) are the cutting edge of the Leonine world. Edward -- You received this message

Re: Leo 6.7.4 released

> *AFAICT its (always?) related to the two variants of how Leo is > distributed !* > Thanks for your persistence. I am convinced. I have just reopened #3497 . Edward -- You received this message because you are subscribed to the Google

Re: Leo 6.7.4 released

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

Re: Leo 6.7.4 released

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

Re: Leo 6.7.4 released

On Friday, August 18, 2023 at 6:11:03 AM UTC-5 Edward K. Ream wrote: > Thanks for this report. See #3497 <https://github.com/leo-editor/leo-editor/issues/3497>. PR #3498 <https://github.com/leo-editor/leo-editor/pull/3498> contains suppresses some unit tests in certain situ

Re: ENB: Bugs in Leo's outline-paste commands

On Thursday, August 17, 2023 at 6:53:00 AM UTC-5 Edward K. Ream wrote: > This Engineering Notebook post discusses subtle problems with Leo's paste-outline commands: paste-node, paste-retaining-clones, and paste-as-template. A new unit test (in PR #3473 <https://github.com/leo-editor/leo-

Re: Leo 6.7.4 released

On Fri, Aug 18, 2023 at 12:04 AM Viktor Ransmayr wrote: > [unit test failures] Thanks for this report. See #3497 . Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

Re: Leo 6.7.4 released

On Thu, Aug 17, 2023 at 3:55 PM Viktor Ransmayr wrote: > I installed Leo 6.7.4 from PyPI into a Fedora 38 VM. - When I run the unittests I receive errors. > I installed the current development branch from Leo into this Fedora 38 VM as well - and - did NOT receive any unittest errors. Thanks for

Re: Leo 6.7.4 released

On Thu, Aug 17, 2023 at 5:11 PM Thomas Passin wrote: I upgraded my Windows 6.7.3 installation to 6.7.4 using pip: > > py -m pip install --user --upgrade leo > > It installed correctly but I got this deprecation warning: > > C:\Users\tom>py -m pip install --upgrade --user leo > DEPRECATION:

Re: Leo 6.7.4 released

On Thu, Aug 17, 2023 at 2:42 PM Félix wrote: >  拾 Hurray!!   > :-) 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

Re: Leo 6.7.4 released

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 <https://github.com/leo-editor/leo-editor/releases> and pypi > <https://pypi.org/project/leo/>. > I'll delay more public announceme

Leo 6.7.4 released

Leo https://leo-editor.github.io/leo-editor/ 6.7.4 is now available on GitHub and pypi . Many thanks to all who have contributed. Leo is an IDE, outliner and PIM

ENB: Bugs in Leo's outline-paste commands

This Engineering Notebook post discusses subtle problems with Leo's paste-outline commands: paste-node, paste-retaining-clones, and paste-as-template. A new unit test (in PR #3473 ) revealed these problems. They may be ancient. This post

Re: Option key Mac

On Fri, Aug 11, 2023 at 12:03 PM kilivor wrote: I am using macOs Ventura with Spanish keyboard layout. The key Option+2, > instead of @, shows 'call tips On' / 'Off'. Is there anything I should > configure? In leoSettings.leo, the binding for toggle-calltips is Alt-2, which I suppose is the

ENB: Using alt generators properly

Yesterday I made an instructive mistake. In PR #3473 , I attempted to fix a hang in Leo's paste-node command using alt generators. Instead, I should have looked for the actual cause of the hang. *c.recompute_all_parents* must use a

Discuss: Remove read-outline-only command?

#3492 suggests fixing an interface problem with Leo's read-outline-only command. Instead, I propose removing this command entirely: - It has no apparent use. - Saving the resulting outline might corrupt external files. Does anyone use this

Re: ENB: Ahas re paste-retaining-clones

On Monday, August 14, 2023 at 7:29:47 AM UTC-5 Edward K. Ream wrote: > Here is c. alt_all_unique_nodes: The PR now contains an improved version that doesn't visit children redundantly. The unit tests prove that the redundancy didn't affect the results. Edward -- You received this mess

Re: ENB: Ahas re paste-retaining-clones

On Sun, Aug 13, 2023 at 8:28 PM HaveF HaveF wrote: > I'm a person who is not good at expression, but I hired GPT4 to express my meaning. Bwahahahaha. Thanks for this. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

Re: ENB: Ahas re paste-retaining-clones

On Mon, Aug 14, 2023 at 7:22 AM Edward K. Ream wrote: > PR #3473 <https://github.com/leo-editor/leo-editor/pull/3473> now contains working code. See *c.recompute_all_parents* and *c.alt_all_unique_nodes*, both covered with unit tests. Here is c. alt_all_unique_nodes: def alt_all_uni

Re: ENB: Ahas re paste-retaining-clones

On Mon, Aug 14, 2023 at 12:48 AM vitalije wrote: >> We can't use VNode generators because they don't yield VNodes in outline order. > I really don't know where did you get this idea from? You're quite right. There were some brain spikes in my comments. PR #3473

Re: ENB: Ahas re paste-retaining-clones

On Sunday, August 13, 2023 at 2:17:56 PM UTC-5 Viktor wrote: Another one joining late - but - still in time ;-) There's no rush, hehe. Enjoy your birthday exactly the way you prefer to ! I'm having way too much fun. Time to rejoin my family :-) Edward -- You received this message because

Re: ENB: Ahas re paste-retaining-clones

On Sun, Aug 13, 2023 at 12:10 PM Edward K. Ream wrote: > c.*alt*_all_positions must use a stack just like Position.stack. True, but c.alt_all_positions is simpler than I dared hope: def alt_all_positions(self) -> Generator: """An alternative implementation of c.al

Re: ENB: Ahas re paste-retaining-clones

On Sunday, August 13, 2023 at 2:06:19 PM UTC-5 Félix wrote: Edward, I also want to join my voice to the group in wishing you a happy birthday! :D So Happy Birthday, Edward! Another year older, but your programming prowess keeps getting younger! Cheers to you and the adventures your code will

Re: ENB: Ahas re paste-retaining-clones

On Sun, Aug 13, 2023 at 1:10 PM Thomas Passin wrote: > Best wishes on your birthday from this quarter, too! > :-) 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

Re: ENB: Ahas re paste-retaining-clones

On Sunday, August 13, 2023 at 12:00:43 PM UTC-5 David Szent-Györgyi wrote: > Thank you for working on your birthday and giving a gift to us all. You're welcome. It's been my pleasure. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: ENB: Ahas re paste-retaining-clones

On Sun, Aug 13, 2023, Edward K. Ream wrote: >> Is it possible to write [*c.all_vnode_positions*]? > You bet: [snip] > This generator passes the following consistency test: vnodes1 = [c.hiddenRootNode] + [z.v for z in c.all_positions()] vnodes2 = list(c.all_vnode_positions()) as

Re: ENB: Ahas re paste-retaining-clones

On Sun, Aug 13 Edward K. Ream wrote: > Is it possible to write [*c.all_vnode_positions*]? You bet: def all_vnode_positions(self) -> Generator: c = self to_be_visited: list[VNode] = [c.hiddenRootNode] while to_be_visited: v = to_be_visited.pop() y

Re: ENB: Ahas re paste-retaining-clones

On Sun, Aug 13, 2023 at 4:50 AM jkn wrote: > Well, Happy Birthday Edward! ;-) > Thanks :-) 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

ENB: Ahas re paste-retaining-clones

Today is my 74th birthday. This Engineering Notebook post is my birthday present to myself. For the last week, I have been trying to make paste-retaining-clones work. Unit tests show this command improperly computes v.parents arrays in the pasted outline. This morning I saw the way

Re: ENB: Positions vs VNodes

On Thursday, August 10, 2023 at 1:14:05 PM UTC-5 Edward K. Ream wrote: The timeit script below shows that c.all_unique_nodes is about three times faster than c.all_unique_positions. On my machine the output is something like this: positions 0.012876 vnodes 0.004999 *Note: *I ran

Re: ENB: Positions vs VNodes

On Wednesday, August 9, 2023 at 8:49:51 AM UTC-5 Edward K. Ream wrote: > When writing a .leo file, Leo must scan *all* nodes to find dirty @ nodes. > Using *c.all_unique_nodes* will be *slightly* more efficient than *c.all_unique_positions*. But not enough to matter. The timeit script

Re: Leo 6.7.4 due Friday, August 18

On Wednesday, August 9, 2023 at 6:30:57 PM UTC-5 Félix wrote: The previous behavior [of paste-retaining-clones] was not 'buggy' per say, just that the nodes in the outline have priority over pasted nodes when their gnx matches, when 'retaining' clones, where the opposite would be preferred.

Leo 6.7.4 due Friday, August 18

I have pushed back the release date for Leo 6.7.4 yet again to allow more time for testing. PR #3484 (merged into devel) restores the paste-retaining-clones command to its previous (buggy) state. A complete fix must wait until 6.7.5. Expect

ENB: Positions vs VNodes

This Engineering Notebook post discusses when to use Positions and when to use VNodes. The general rules: 1. Prefer VNodes to Positions if possible, but 2. Most outline operations *must* use Positions. *Examples* Outline commands such as insert-node, delete-node, and paste-node must use

Re: v.self_and_subtree, a true vnode generator

On Tuesday, August 8, 2023 Edward K. Ream wrote: > PR #3473 <https://github.com/leo-editor/leo-editor/pull/3473> defines Leo's first VNode generator, v.self_and_subtree. And now this PR defines *v.self_and_all_parents*, a generator similar to v.self_an

Re: v.self_and_subtree, a true vnode generator

On Tue, Aug 8, 2023 at 1:56 PM, vitalije wrote: >> c.all_positions_for_v shows how to generate all *positions* p such that p.v == v. > Maybe it is just mildly interesting to you, but it is orders of magnitude faster than what you propose as a "straightforward" solution. Thanks for your

Re: v.self_and_subtree, a true vnode generator

On Tuesday, August 8, 2023 at 10:27:14 AM UTC-5 Edward K. Ream wrote: > - c.all_unique_roots contains code equivalent to c.hiddenRootNode.self_and_subtree(). My mistake. c.all_unique_roots should stay as it is. Edward -- You received this message because you are subscribed to the Goo

Re: v.self_and_subtree, a true vnode generator

On Tuesday, August 8, 2023 at 10:27:14 AM UTC-5 Edward K. Ream wrote: > c.all_positions_for_v shows how to generate all *positions* p such that p.v == v. This method "reconstitutes" positions using only VNode operations. But this trick is only mildly interesting. Instead,

Re: v.self_and_subtree, a true vnode generator

On Tuesday, August 8, 2023, Edward K. Ream wrote: > PR #3473 <https://github.com/leo-editor/leo-editor/pull/3473> defines Leo's first VNode generator, v.self_and_subtree. Here are some ENB-like notes. Feel free to ignore this post. - v.self_and_subtree contains no recursion and

Re: v.self_and_subtree, a true vnode generator

On Tue, Aug 8, 2023 at 6:51 AM Edward K. Ream wrote: > Here is the code: The PR <https://github.com/leo-editor/leo-editor/pull/3473> now contains an improved version of v.self_and_subtree Edward -- You received this message because you are subscribed to the Google Groups "leo

Re: a question about section reference

On Tue, Aug 8, 2023 at 6:54 AM HaveF HaveF wrote: > Can you give me a general idea about the scripts? The script could create or update an @file tree, creating section references from some input data. I would write such a script only if it saved *lots* of work. Otoh, writing such scripts can

v.self_and_subtree, a true vnode generator

PR #3473 defines Leo's first VNode generator, v.self_and_subtree generator. This generator is more than a curiosity. It shows that for *some* purposes VNodes can supplant positions. Here is the code: def self_and_subtree(self) ->

Re: a question about section reference

On Mon, Aug 7, 2023 at 8:39 PM HaveF HaveF wrote: > I find section reference useful when organizing profiles, as it logically divides profiles into section > But in some cases I find it a bit troublesome. There have been several proposals to generalize Leo's section references. However Leo's

Re: ENB: A new file format and a new uA policy

On Wednesday, August 2, 2023, Edward K. Ream wrote: > Leo's old, ugly, inscrutable, legacy file code must remain even in Leo 6.7.5. PR #3473 <https://github.com/leo-editor/leo-editor/pull/3473> shows that I must change my mind. Leo 6.7.5 will likely use json for uAs, copy-node, and p

Leo 6.7.4 coming this Friday, August 11

Once again, Leo 6.7.4 is code complete :-) The last remaining PRs scheduled for Leo 6.7.4 have been merged into the devel and 6.7.4 branches. These issues should have little effect on Leo. Please continue testing the devel or 6.7.4 branches. Leo will go out the door this coming Friday, August

Re: ENB: How to mimic Python's overriding of the dunder methods in typescript.

On Fri, Aug 4, 2023 at 8:53 PM Félix wrote: Dunder methods being (unexhaustive list) : *__contains__, __delitem__, > __getitem__, __setitem__, __iter__ and __repr__* in my case. > Thanks for this. Your post shows how much behind-the-scenes work you have done with leoJS. Edward -- You

Re: ENB: What to do about show-file-line?

On Saturday, August 5, 2023 at 5:46:11 AM UTC-5 Edward K. Ream wrote: This Engineering Notebook post considers what to do about Leo's show-file-line command, the evil twin of goto-global-line. I forgot to mention the history of show-file-line. Years ago, someone suggested showing the *file's

ENB: What to do about show-file-line?

This Engineering Notebook post considers what to do about Leo's show-file-line command, the evil twin of goto-global-line. The goto-global-line command is solid, frequently used, and essential. Leo uses its code whenever you click an error link. In contrast, show-file-line is buggy and

Re: ENB: A new file format and a new uA policy

On Wed, Aug 2, 2023 at 9:04 AM Edward K. Ream wrote: > On Wednesday, August 2, 2023 at 5:21:54 AM UTC-5 Edward K. Ream wrote: > > This Engineering Notebook post explains why #3474 > <https://github.com/leo-editor/leo-editor/issues/3474> (reforming uAs) > must

Re: ENB: A new file format and a new uA policy

On Wednesday, August 2, 2023 at 5:21:54 AM UTC-5 Edward K. Ream wrote: This Engineering Notebook post explains why #3474 <https://github.com/leo-editor/leo-editor/issues/3474> (reforming uAs) must wait until Leo 6.7.5. The present code that handles uAs is too complex to understand or

ENB: A new file format and a new uA policy

This Engineering Notebook post explains why #3474 (reforming uAs) must wait until Leo 6.7.5. The present code that handles uAs is too complex to understand or change. New unit tests won't change this situation. Instead, #3472

Re: leojs status report

On Tue, Aug 1, 2023 at 10:02 PM Félix wrote > Just a quick post to say 'hi!' while I'm coding leojs, and to mention that > I was overjoyed that I've got sqlite working on both the desktop -and- web > version of vscode! (with web-assembly!) > > So .db file support will soon be available! *along

Re: ENB: Momentous Ahas re vnodes

On Sunday, July 30, 2023 at 6:37:16 AM UTC-5 Edward K. Ream wrote: > Define *p.archive* (yes, p) something like this. PR #3473 <https://github.com/leo-editor/leo-editor/pull/3473> contains the latest code. I'll say no more here. Edward -- You received this message be

Re: PR #3468 merged into devel

On Mon, Jul 31, 2023 at 3:01 PM Viktor Ransmayr wrote: 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 ... > Many thanks, Viktor, for your continued testing. Edward -- You received this message because you

ENB: Two passes will simplify all reads and pastes

This Engineering Notebook post suggests improvements to the code that reads outlines and pastes nodes. These changes must wait until Leo 6.7.5. Recent changes automatically correct link errors in paste-retaining-clones. These changes suffice for Leo 6.7.4. I propose the following

PR #3468 merged into devel

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! Edward -- You received this message because you are subscribed to

Re: ENB: Momentous Ahas re vnodes

On Fri, Jul 28, 2023 at 7:18 AM Edward K. Ream wrote: > This Engineering Notebook post announces several momentous Ahas all directly related to VNodes. ... > Define *p.archive* (yes, p) something like this (untested, but the code passes mypy): def archive(self) -> dict[str, Any]:

Re: Leo 6.7.4 now scheduled for Friday, August 11

On Saturday, July 29, 2023 at 11:23:45 AM UTC-5 Edward K. Ream wrote: PR #3468 <https://github.com/leo-editor/leo-editor/pull/3468> should fix the last release blocker. I forgot to mention that #3452 <https://github.com/leo-editor/leo-editor/issues/3452> (archive & undo/redo

Leo 6.7.4 now scheduled for Friday, August 11

PR #3468 should fix the last release blocker. I think it wise to give us plenty of time for testing. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

Re: ENB: paste-retaining-clones has always beeen broken & my plans to fix it

On Sat, Jul 29, 2023 at 4:08 AM Edward K. Ream wrote: > PR #3467 <https://github.com/leo-editor/leo-editor/pull/3467> will attempt a complete fix for paste-retaining-clones. Great news. The "Emergency" PR (PR #3468 <https://github.com/leo-editor/leo-editor/pull/34

Re: ENB: paste-retaining-clones has always beeen broken & my plans to fix it

On Saturday, July 29, 2023 at 4:01:18 AM UTC-5 Edward K. Ream wrote: > PR #3467 <https://github.com/leo-editor/leo-editor/pull/3467> will attempt a complete fix for paste-retaining-clones. This work is experimental and is likely to delay Leo 6.7.4. Félix suggests we wait until

ENB: paste-retaining-clones has always beeen broken & my plans to fix it

*Warning:* Please consider paste-retaining-clones unreliable until further notice. Leo's new structure tests have shown that paste-retaining-clones has *always* been buggy! This Engineering Notebook discusses the bug and my plans for fixing it. *Problems with paste-retaining-clones*

Re: ENB: Momentous Ahas re vnodes

On Fri, Jul 28, 2023 at 8:30 PM HaveF HaveF wrote: > Maybe this file should not be in repo? leo/core/fail-leoPy.leo is a temporary measure. For now, it is essential for testing. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: ENB: Momentous Ahas re vnodes

On Friday, July 28, 2023 at 9:27:28 AM UTC-5 Edward K. Ream wrote: > I have just merged the unified PR into devel. This merge will require some cleanups. Done at rev d5d3a2 <https://github.com/leo-editor/leo-editor/commit/d5d3a28a453f5250d475ff717c8c76283fbf1c85> in devel.

Re: ENB: Momentous Ahas re vnodes

On Friday, July 28, 2023 at 9:27:28 AM UTC-5 Edward K. Ream wrote: > Hurray! Leo has just reported link errors after I switched branches. For the record, here is the report, slightly cleaned up: Mismatch between parent.children and child.parents parent: u.Externally visible entries co

Re: ENB: Momentous Ahas re vnodes

On Fri, Jul 28, 2023 at 7:18 AM Edward K. Ream wrote: > This Engineering Notebook post announces several momentous Ahas, all directly related to VNodes and our attitude towards them. Several notes: 1. I have just merged the unified PR into devel. This merge will require some cleanups. I

Re: ENB: Momentous Ahas re vnodes

On Friday, July 28, 2023 at 7:18:01 AM UTC-5 Edward K. Ream wrote: *> Acknowledgements*: These Ahas would not have happened *without *the recent discussions with Félix and Vitalije. Edward -- You received this message because you are subscribed to the Google Groups "leo-edito

ENB: Momentous Ahas re vnodes

This Engineering Notebook post announces several momentous Ahas, all directly related to VNodes and our attitude towards them. These Ahas resolve long-standing questions and suggest new ways of simplifying Leo's most fundamental code. *Acknowledgements*: These Ahas would not have happened

<    1   2   3   4   5   6   7   8   9   10   >