Re: SQL Syntax / Custom Syntaxes
Yes, I believe it would :-) There still might be an issue with name collisions since @sql isn't directly a mode (i.e. tsql) and creating a directive for every mode obviously wouldn't be ideal either - but maybe a shorthand/mapping could be defined in the document Startup section? i.e. to map a local directive @sql (arbitrary) to a specific mode assignment, like tsql. I could also deal with buttons to assign/remove attributes but I'd need to be able to view them. The attributes plugin has still been on my list to try but haven't had time to dive into it yet. I understand these could also impact things like VR3 so I'm not quite sure how that would factor in. As it is, I already have to define in a comment, `-- language=sql`, for pycharm to nest syntaxes, so aligning with this could work too. On Thu, 2020-09-24 at 08:47 -0500, Edward K. Ream wrote: > On Thu, Sep 24, 2020 at 8:32 AM wrote: > > > I've attached an example of how I'm wrapping the (t)sql nodes. > > > > Interesting! > > I can deal with this, but it would be a lot cleaner if I could > > assign the language directive either in just a sql comment (i.e. -- > > @language sql ) > > or using a uA/attribute or maybe something in the headline. > > > > Would marking nodes with @sql help? > > Edward > -- > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/pU1HOGQ6jXU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS1WTzdoWhuzRWs3%3DCaw4ViB3s8Hxx-s1kvqkbOtbHEoKg%40mail.gmail.com > . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c50f1d18dd1b40a74737cc978af61d58e4fa8792.camel%40gmail.com.
Re: SQL Syntax / Custom Syntaxes
Ah, ok, I found those modes, thanks! I've attached an example of how I'm wrapping the (t)sql nodes. I can deal with this, but it would definitely be a lot cleaner if I could assign the language directive either in just a sql comment (i.e. -- @language sql ) or using a uA/attribute or maybe something in the headline. As it is the hierarchy is quite clunky to navigate with this double nesting and I'd prefer for the body to be pure valid sql so I can copy/paste and users linters and things because I have to switch between editors quite frequently. There are *thousands* of these statements I'd need to convert, so I thought I'd throw it out there to see if there might be a cleaner way to do this before I start digging in. Much appreciated. Kevin On Thu, 2020-09-24 at 06:43 -0500, Edward K. Ream wrote: > On Tue, Sep 22, 2020 at 12:20 PM k-hen > wrote: > > > OK, I've looked around, but can't seem to find anything on the docs > > on defining custom syntaxes. > > > > Controlling Syntax Coloring tells everything you need to know. Feel > free to ask questions. > > > i.e. I can't seem to find and @language sql > > > > There is no such language because there is no leo/modes/sql.py file. > > > > > Can I do this myself (realistically)? > > > > Yes you can. If jEdit has a sql colorer, you can use the @button > jEdit2Py button in scripts.leo to convert the jEdit language > description file to a modes/sql.py. > > Edward > -- > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/pU1HOGQ6jXU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS2C2ZX-LjSzUDyGDE-tSbt60_ctPMDuRCnYHGqr11E-%2Bg%40mail.gmail.com > . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/0e256bcc0d749589e1f4b42a12a57345013dfceb.camel%40gmail.com. sql_wrapper_example.leo Description: XML document
Re: SQL Syntax / Custom Syntaxes
Ok, well, I really appreciate the reply gar, thank you. Should be an interesting project once I've got the time to look into it :-) On Thu, 2020-09-24 at 10:07 +0300, gar wrote: > I think that if you are quite familiar with sql and python - it'll > take a 3-4 of days for you > first two you'll spend trying to understand what's going on around > > вт, 22 сент. 2020 г. в 20:20, k-hen : > > OK, I've looked around, but can't seem to find anything on the docs > > on defining custom syntaxes. i.e. I can't seem to find and > > @language sql > > > > Can I do this myself (realistically)? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/91bedf5f3adff3d771b658f887e7a933e166b7a9.camel%40gmail.com.
Re: Leo Node Move Error
For the record, unfortunately this script didn't fix the issue - it still wasn't happy.I had to convert to .leo xml and then back to .db. I think there's still a lot of value in fixing the DB format, but hopefully in a way that won't limit it's potential performance. On Fri, 2020-09-04 at 02:52 -0700, vitalije wrote: > > My tentative conclusion is that there may be a bug in > > fc.retrieveVnodesFromDb. However, there are no special cases in > > this code, so what the bug could possibly be is a big mystery. > > Iirc, Vitalije wrote this code. Any insights would be appreciated. > > > > I am almost 100% sure that the fc.retrieveVnodesFromDb works > correctly. It just restores outline from the rows retrieved from db. > Saving and loading from db work in tandem. If the outline being saved > has broken links, then the outline loaded afterwards will have broken > links too. > > Most likely outline got broken links during some modification and > later was saved as such. > > Here is a script that can fix broken links: > from collections import defaultdict > def relink_outline(c): > '''Normalizes outline fixing broken links''' > parDict = defaultdict(list) > for p in c.all_positions(): > parDict[p.gnx].append(p._parentVnode()) > gnx2v = c.fileCommands.gnxDict > for gnx, parents in parDict.items(): > v = gnx2v[gnx] > v.parents = parents > c.checkOutline() > relink_outline(c) > > When saving to xml information about parent links is omitted. When > loading from xml file, correct parent links are infered again. > Perhaps I can change writing to db to omitt parent links and just > infer them when loading from db. > > It is still a mistery how k-hen got his outline to this invalid > state. My guess is that it was caused during the updating clones in > both @file files and @nosent files. That would explain why we haven't > noticed this bug before. It is not very common to have shared clones > in both @nosent and @file files. > > Vitalije > > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/sANduRjZDVI/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/56aa7952-a09d-4da5-b176-206916448e26o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/8b75432c2bbc5e959d821b7a3244813cc5672431.camel%40gmail.com.
Re: Leo Node Move Error
Thank you for this :-) I realize that @nosent is nontraditional. I'd be happy to use @adoc or @md but I currently don't know of a way to identify nodes that aren't section headlines.Once the outline is too deep then the doc fails :-/ Nosent doesn't write the headlines so it makes this possible but I agree that it's not very elegant. On Fri, 2020-09-04 at 02:52 -0700, vitalije wrote: > > My tentative conclusion is that there may be a bug in > > fc.retrieveVnodesFromDb. However, there are no special cases in > > this code, so what the bug could possibly be is a big mystery. > > Iirc, Vitalije wrote this code. Any insights would be appreciated. > > > > I am almost 100% sure that the fc.retrieveVnodesFromDb works > correctly. It just restores outline from the rows retrieved from db. > Saving and loading from db work in tandem. If the outline being saved > has broken links, then the outline loaded afterwards will have broken > links too. > > Most likely outline got broken links during some modification and > later was saved as such. > > Here is a script that can fix broken links: > from collections import defaultdict > def relink_outline(c): > '''Normalizes outline fixing broken links''' > parDict = defaultdict(list) > for p in c.all_positions(): > parDict[p.gnx].append(p._parentVnode()) > gnx2v = c.fileCommands.gnxDict > for gnx, parents in parDict.items(): > v = gnx2v[gnx] > v.parents = parents > c.checkOutline() > relink_outline(c) > > When saving to xml information about parent links is omitted. When > loading from xml file, correct parent links are infered again. > Perhaps I can change writing to db to omitt parent links and just > infer them when loading from db. > > It is still a mistery how k-hen got his outline to this invalid > state. My guess is that it was caused during the updating clones in > both @file files and @nosent files. That would explain why we haven't > noticed this bug before. It is not very common to have shared clones > in both @nosent and @file files. > > Vitalije > > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/sANduRjZDVI/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/56aa7952-a09d-4da5-b176-206916448e26o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/493fbb4b8cbce30123b45166e2a2a63a8103b3dd.camel%40gmail.com.
Re: Leo Node Move Error
Hmm ... well at least it seems reproduceable. I did run across at least one set of nodse after filing this that were behaving as clones but not flagged as clones, and it's probably the same ones. Not sure if it matters but the box icon was grey instead of black, I thought that was unusual as well, but not sure what that indicates I'm using the sqlite version because I assumed it could offer better performance for very large outlines (e.g. potentially 50K+ nodes). Also, because I like SQL and can connect to it with DBVisualizer/alternate tools and write queries (read only ones for now) and/or use ETL workflows with it. One thing that _might_ be happening is that I have a 'code' top-level tree that syncs with other developers using Git.It's using @file's and so there are now comments scattered throughout the code base. Then subnodes within this tree are cloned into @nosent 'documentation' trees which contains other notes/commentary outputs.This is mostly doing what I want, but importing the nodes sometimes results in errors/broken outlines/etc, which I have to repair.I close Leo, do the pull, then open Leo again and let it import. Then I fix any issues (mostly nodes losing their parents and appearing at the root).I also keep an eye on Git to ensure that I'm not making any unwanted changes after doing this and can revert if necessary.It's possible that other developers are copying/moving blocks of code that include the Leo comments (I've asked them not to do this).We're making a lot of structural changes now too as we're refactoring so this should settle down later. For now, perhaps I can save as .leo and then save back as .leo.db to potentially repair any issues. Is it perhaps possible to detect and/or repair these broken clones using a script? Thanks so much for all your help. Kevin On Thu, 2020-09-03 at 11:52 -0700, Edward K. Ream wrote: > On Wednesday, September 2, 2020 at 3:24:45 PM UTC-5, k-hen wrote: > > > Ok, got it, will need a bit of time, but will get back to you soon. > > Something strange is going on. Here is what I think I know: > > The unpacked original file is leo_error_test_01 - cleared - Copy.db. > It is about 28.1 MB in size. > > Opening the file with Leo does work, but the two "node 5660" are not > shown as clones of each other. Yet they have the same gnx and id(v) > is the same for each. Imo, this is likely the ultimate cause of the > crash. > > Saving this .db as a .leo file creates a valid .leo file in which the > two "node 5660" are indeed true clones. The bug never appears in the > .leo file. > > Saving the .leo file as a .leo.db file creates a much smaller file, > about 1.2 MB. However, in all other respects it appears to be > identical to the original .db file. The two "node 5660" are not shown > as clones of each other, and the bug does manifest itself. > > My tentative conclusion is that there may be a bug in > fc.retrieveVnodesFromDb. However, there are no special cases in this > code, so what the bug could possibly be is a big mystery. Iirc, > Vitalije wrote this code. Any insights would be appreciated. > > Finally, I note that the .leo files are smaller than the > corresponding .db files, so one workaround would be to use the .leo > files instead. Presumably, however, there are reasons for using the > .db files. > > Edward > > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/sANduRjZDVI/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/9afd5fe4-7fd3-4e68-91d7-283f02367601o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/2c4906311bc48e909c60b3d7bb4fc0446b87bb78.camel%40gmail.com.
Re: New Version of Viewrendered3 Updates Asciidoc Handling.
Nice! On Wed, 2020-09-02 at 12:37 -0700, Thomas Passin wrote: > > > On Tuesday, September 1, 2020 at 11:16:24 AM UTC-4, Thomas Passin > wrote: > > I've issued a PR for VR3, and otherwise it is available from my Git > > repo on the vr3-asciidoc branch - > > > > https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo > > > > I have found that Asciidoc processing is much slower than for RsT > > and Md. For example, 15k of Rst takes much less than a second to > > process but 20k of Asciidoc text takes about 10 seconds on my > > computer, which is pretty fast. So I can't recommend rendering > > entire subtrees if they are long. It is likely that using the Ruby > > version of asciidoc would be much faster (they claim a factor of > > 100), but I have not tested this. > > I just installed Ruby and the asciidoctor gem that it runs. It did > convert that 20k asciidoc file in a twinkling. I will get VR3 to use > it too, and see how that works out. > > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/EJxEEFWSkRM/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/eba583db-6dfe-4d10-9084-9d6869b8fdd0o%40googlegroups.com > . > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ead153d32c138ff056e1ccb91c6902df0e90cc56.camel%40gmail.com.
Re: Leo Node Move Error
Ok, got it, will need a bit of time, but will get back to you soon.
Thanks! :-)
Kevin
On Wed, 2020-09-02 at 07:20 -0700, Edward K. Ream wrote:
> On Wednesday, September 2, 2020 at 9:04:18 AM UTC-5, Edward K. Ream
> wrote:
> > It would help if you would run a script to remove all body text (it
> doesn't matter) and replace all headlines with something innocuous.
> That way you can send me the problematic outline without compromising
> privacy.
>
> Here is the tested script:
>
> """Remove all sensitive material in this outline, except for this
> node."""
> # Warning: This script is dangerous! Use on a copy of your outline.
> n = 1
> v0 = c.p.v
> for p in c.all_unique_positions():
> if p.v != v0:
> p.h = f"node {n}"
> p.b = ''
> n += 1
> c.redraw()
> Please run this script inside a copy of you file, and send the result
> to me.
>
> Edward
>
>
>
> --
>
> You received this message because you are subscribed to a topic in
> the Google Groups "leo-editor" group.
>
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/leo-editor/sANduRjZDVI/unsubscribe.
>
> To unsubscribe from this group and all its topics, send an email to
> leo-editor+unsubscr...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/3d6a2dc6-d63f-493f-9554-e70eb1223124o%40googlegroups.com
> .
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/85bbc0226b6035bf2c0e061e20c0ba6473b16c22.camel%40gmail.com.
Re: Leo Node Move Error
To be clear, these are just the top level nodes and everything is collapsed. Y is a new top-level node created right above X, then X is indented right under its parent.I think we're saying the same thing. On Wed, 2020-09-02 at 06:35 -0700, Thomas Passin wrote: > I would have moved it by collapsing the node, then until it > was under the intended parent, then to make it a child of > the target. I'm not saying you did it "wrong", just that this is the > sequence that seems simplest and has always worked well for me. > > On Wednesday, September 2, 2020 at 9:14:14 AM UTC-4, k-hen wrote: > > I had root nodes like the following, I selected node B and inserted > > a new node below, i.e. using insert-node Y. Then I attempted to > > move X under Y. Note that I repeated this and also tried to move > > deep nodes within X at lower levels which also resulted in the > > error.Node X currently has ~6,700 descendant nodes. > > ABXD > > Kevin(I'll also add this to the Git ticket) > > > > > > On Wed, 2020-09-02 at 08:08 -0500, Edward K. Ream wrote: > > > On Wed, Sep 2, 2020 at 7:38 AM k-hen > > > wrote: > > > > > > > > > > I'm getting an error moving a node in Leo. It's a very > > > > large/deep node if that matters. > > > > > > Thanks for this report. I have just created #1639 for this issue. > > > > > > > This large node, X, is/was a root. I added a new root node, Y, > > > > then tried to move X under Y which resulted in the attached > > > > error. > > > > > > > > > > How exactly did you add Y? Did you use insert-node-before? > > > > > > Usually, adding Y (say with Ctrl-I) would not create a new root. > > > After creating Y, you would then have to move Y to the root, > > > which in this case would likely init Leo's data structures > > > properly. > > > > > > Edward > > > > > > > > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/137220b5264021c83acff6db7553b7ecc8d5d802.camel%40gmail.com.
Re: Leo Node Move Error
Thanks re: the clarification, yes they are 'top-level' then. Unfortunately I'm unable to send this _particular_ outline due to client confidentiality, but am happy to run whatever code or tests that you'd like me too. On Wed, 2020-09-02 at 08:19 -0500, Edward K. Ream wrote: > On Wed, Sep 2, 2020 at 8:14 AM wrote: > > > > I had root nodes like the following, I selected node B and inserted > > a new node below, i.e. using insert-node Y. > > Then I attempted to move X under Y. Note that I repeated this and > > also tried to move deep nodes within X at lower levels which also > > resulted in the error. > > Node X currently has ~6,700 descendant nodes. > > Thanks for the clarification. A note of terminology. The "root" node > is the first top-level node. I think you mean "top-level" node > instead of root node. > > If you can, please send me the smallest node X that demonstrates the > bug. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/sANduRjZDVI/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS3MiyXu6xx3nvaU3gzfYRRoK2WhyV6tO3ni85NPCSUK-w%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/99cdbe38f4e0383101c925d6d8656364db75f48c.camel%40gmail.com.
Re: Leo Node Move Error
I had root nodes like the following, I selected node B and inserted a new node below, i.e. using insert-node Y. Then I attempted to move X under Y. Note that I repeated this and also tried to move deep nodes within X at lower levels which also resulted in the error.Node X currently has ~6,700 descendant nodes. ABXD Kevin(I'll also add this to the Git ticket) On Wed, 2020-09-02 at 08:08 -0500, Edward K. Ream wrote: > On Wed, Sep 2, 2020 at 7:38 AM k-hen > wrote: > > > > I'm getting an error moving a node in Leo. It's a very large/deep > > node if that matters. > > Thanks for this report. I have just created #1639 for this issue. > > > This large node, X, is/was a root. I added a new root node, Y, then > > tried to move X under Y which resulted in the attached error. > > > > How exactly did you add Y? Did you use insert-node-before? > > Usually, adding Y (say with Ctrl-I) would not create a new root. > After creating Y, you would then have to move Y to the root, which in > this case would likely init Leo's data structures properly. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/sANduRjZDVI/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS1j42g_U6rs5b0sUO9kAaVG7ys998R-uN1yma%3D6t4tejg%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/8994f89c2e127402d66ad56b72b5fe5a4a76a430.camel%40gmail.com.
Re: Defining Attributes
Yes, this is accurate. I think that XML has been somewhat supplanted by JSON, but there are some json libraries which attempt to do similar things as xslt: like https://github.com/tidwall/gjson and https://github.com/qntfy/kazaam fo r example. Note that while these essentially operate on the *document* level, using a graph-db with GraphQL for example would work on a *system* level and be *much* more powerful to do those transforms. I think we're on the same page here :-) https://graphql.org/ I'm also ok with perhaps having more of a data structure-type outline as H1 which the commentary interwoven, given we could represent the simple JSON structures of a dictionary and a list somehow. This could then be pieced together in the H3 markdown/output section. Regarding the DDL, I'd be linking those code snippets into the H2 hierarchy and embedding into python documents that use the python alembic library to do the setup.I'd probably continue to use PyCharm and/or DBVisualizer for some of this, but it's great to know I script queries in Leo too. The question remains though what the techniques are for representing something like this using Leo. Of course I'll keep plugging and can development something on my own, just thought you guys might know better and/or have some ideas kicking around :-) 1: Define & Document the "Model" (Types + Content)2: Transform/Link the Model to Code (files)3: Transform the Model to Presentation Docs (files) Kevin On Tue, 2020-08-25 at 09:49 -0700, Thomas Passin wrote: > So let me see if I am getting some kind of a handle on this. The > following will not be complete; it's just responding to some of the > elements. > 1. You need to produce documentation to fit some template not of your > choosing, probably in markdown or similar. The template is not > the way you want to write your in-Leo information, and you also want > to be able to have commentary, preliminary thoughts, etc., which > should not be included into any output document. So some kind of > selection and transformation mechanism will be needed. The simplest > thing would be to write your own outlines with markdown using that > format so that individual nodes can be cloned as is into the output > documentation tree. But that may not suit what you want to do. > Selection based on some definite characteristic, such as special > markers, would be promising. In the old days, I would have > considered writing XML, because XSLT is so good for transforms. But > I'm sure you don't want to do that here. You want something that is > much easier to write and read. > > 2. You want to use data in nodes to create database tables and run > other database DDL.Here I'm just sticking with the particular > example you gave; I know there are other, non-db things you will > probably want to do.A Leo script sounds like it would be > practical, and not to hard, as long as you will be able to run it > from Leo. But if this is serious work, it would be hard and maybe > fragile to have your Leo script do all the error checking and > recovery you need, and perhaps Leo would be even be able to access > the database (e.g., you might not be allowed to have Leo on the > target system, or to have Leo connect to it. So probably you would > want a Leo script that would produce external .sql files. > That should be very practical. > Please do not use the "@" character. Leo (and VR3) uses it > already for special purposes. Pick something different. > 3. > > On Tuesday, August 25, 2020 at 9:03:10 AM UTC-4, k-hen wrote: > > I keep flipping on how to sanely handle attributes. > > > > My mind is more comfortable when I label nodes in meaningful > > *phrases* but that's not how I want to represent them from a file > > output or coding perspective. > > > > I've been experimenting with jamming lots of information into the > > headline using naming conventions but while efficient, it makes > > things much more confusing, which I what I'm using Leo to avoid :- > > ) e.g. things like '5:table>my_table' - where 5 indicates the > > markdown/asciidoc heading style, table is the type/class for > > decorating, and my_table is the leaf thing. Then regex's could be > > used to parse out the different components, but I'm not really > > liking this. > > > > In a perfect world I'd maybe make an attributes plugin in the tabs > > pane similar to tags, but is it reasonable/possible to define tags > > as directives within the body? (not sure if I'm saying that > > right). e.g. 'My Table' with @class Table, @name my_table lines > > within the body? These could then be saved within the user > > attributes. > > > > I would have a script then iterate over these 'model' nodes and > > output this information into markdown/asciidoc tables for > > presentation. > > > > Any pointers or advice? > > > > Thanks again for all your patience and support, very much > > appreciated. > > > > Kevin > > > > > > > > > > > > > > > > >
Re: Contract Node and Descendants
Success! :-) On Mon, 2020-08-24 at 17:45 -0500, Edward K. Ream wrote: > > > > On Mon, Aug 24, 2020 at 5:41 PM wrote: > > I did actually see that under the tree options in leoSettings but > > it appears to be set to true by default, > > might there be something else that could be unsetting it? > > > > How might I go about checking its currently assigned value? > > show-settings. In any case, see my second reply. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/3w_vfg39w8Q/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS3Q-CnR1H2JkZUR4Z7xGNa3eCG3w-3ekUQVxjE%2BsXSyuA%40mail.gmail.com > . > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/d7956d99975a2d036e7087e6c4d8b64f5a2ac89f.camel%40gmail.com.
Re: Contract Node and Descendants
I did actually see that under the tree options in leoSettings but it appears to be set to true by default,might there be something else that could be unsetting it? How might I go about checking its currently assigned value? On Mon, 2020-08-24 at 17:34 -0500, Edward K. Ream wrote: > > On Mon, Aug 24, 2020 at 4:18 PM wrote: > > So, what i'd ultimately like is for the left arrow key to first > > 'collapse-all-subheads' and then 'contract-or-go-left', maybe > > called 'collapse-or-go-left'. > > This is almost what the default action of @bool collapse-on-lt-arrow > is. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/3w_vfg39w8Q/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS0NqtS%3Dov9YVJV_p8h42wJCagMfjVhT9aDvXHJwXQMg9w%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ee976f2bce20f89c8d2d08d13f369c53b4c5cfd3.camel%40gmail.com.
Re: Contract Node and Descendants
So, what i'd ultimately like is for the left arrow key to first 'collapse-all-subheads' and then 'contract-or-go-left', maybe called 'collapse-or-go-left'.I'm quite sure that I could accomplish this by creating a custom command in my myLeoSettings file and then binding that to hotkey.I can't seem to find anything on how @command (within settings/commands) should work though.I do see the 'prompting for command arguments' in the cheatsheet, but I'm not quite sure how that relates. If someone could maybe help point me in the right direction for this I'd appreciate it :-) On Mon, 2020-08-24 at 15:44 -0500, Edward K. Ream wrote: > > On Mon, Aug 24, 2020 at 2:19 PM wrote: > > Wow, that was fast - thank you so much! > > You're welcome. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/3w_vfg39w8Q/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS1A5mgoz8T2mSZRNXebkNY0BDBd09Fuo-COn4Hs16qbSQ%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b64cf13fa665cfee713dd0072a4ab60768cba328.camel%40gmail.com.
Re: Contract Node and Descendants
Wow, that was fast - thank you so much! On Mon, 2020-08-24 at 11:32 -0700, Edward K. Ream wrote: > On Monday, August 24, 2020 at 1:07:10 PM UTC-5, Edward K. Ream wrote: > > > Leo does have an expand-all-subheads command. It should have the > > corresponding contract-all-subheads command. I've just created > > #1632 for this. Expect it later today. > > Done at rev 52610e6f in devel. There are some minor issues. See PR > 1632 for details. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/3w_vfg39w8Q/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/497d6f6a-f233-4f78-9dd5-265966e74f85o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/a1cbb0d29f5387e150b954b377641c0fe4a75556.camel%40gmail.com.
Re: Unbinding Keys
I use and am big fan of these :-) https://www.microsoft.com/accessories/en-ca/products/keyboards/sculpt-ergonomic-desktop/l5v-2 I've managed to get the keys working now, that's a good trick using the minibuffer & completions window for that,it beats using the show- bindings & copy/pasting into another window - thank you :-) On Sat, 2020-08-22 at 08:30 -0700, Edward K. Ream wrote: > On Saturday, August 22, 2020 at 7:51:57 AM UTC-5, k-hen wrote: > > > To confirm, I just tried these (Ctrl+Shift+C & Ctrl+Shift+V) in > > another app and they work fine, > > so it would seem to be something with Leo. > > I just took a look at your copy of myLeoSettings.leo. All bindings > and unbindings work as specified, including shift-ctrl-c and shift- > ctrl-v. > > To verify that unbindings took effect, I used the minibuffer. For > example, toggle-ac shows just `toggle-active-pane`, > without any key bindings. > > Did you say what keyboard you use? > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/vA5k0hVdXvQ/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/2d3c421c-3f87-4576-93dd-bbbcb26f90f4o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/899d0f5f2ee16f5913f4469f3b22e462863a5334.camel%40gmail.com.
Re: Documented Database Use Case
Yes, that's true, and just to be clear, that's not what I'm suggesting or expecting :-) What I want is to use Leo to build the *code* that constructs/populates/queries a separate 'proper' database. One option is just to have Leo remain in Sqlite (and allow some basic querying that way), but *also* to define a connection in which to run various updates and queries through a global variable or something. For this I want Leo to supplement/replace a query studio. Another option is to use agnostic ansi sql or a wrapper library (sqlalchemy has some support for this) to store the Leo node tables inside of another target db, thereby allowing joins and things between the Leo nodes and their non-Leo counterparts. I can think of arguments for both based on different circumstances, but initially at least, my preference would probably be the former. On Fri, 2020-08-21 at 08:21 -0700, Thomas Passin wrote: > I'm doubtful about Leo-as-a-database as a replacement for a > conventional rdbms, because of the need for atomic transactions. > That has always take a lot of care in design and implementation of > the code. Of course, we don't know what Speed has done, and maybe > you don't need such capabilities anyway... > > On Friday, August 21, 2020 at 10:59:07 AM UTC-4, k-hen wrote: > > Is there *anything* I can do to help entice him? > > > > Please Speed, please - if you're reading this, I'd *love* to see > > what you've done, > > it sounds incredible to me and it could really make a big > > difference to me to be able to use and build on your amazing work. > > > > I do a lot of database development and this could really, really > > help me out a whole lot. > > I'll take scraps/hello worlds/anything, I don't mind trying to pick > > through it, it doesn't need to be a fancy write-up or anything > > either. > > I could see myself using and building and growing it every single > > day :-) > > > > Thanks so much for considering, hope all is well. > > > > Yours Sincerely, > > Kevin > > > > :-) > > > > > > > > On Friday, August 14, 2020 at 11:03:25 AM UTC-4 k-hen wrote: > > > I'd be *very* interested in that, thank you! :-D > > > > > > > > > On Fri, 2020-08-14 at 06:55 -0500, Edward K. Ream wrote: > > > > On Thu, Aug 13, 2020 at 9:37 AM k-hen > > > > wrote: > > > > > > > > > Is there a concept of Leo-as-database? > > > > > > > > Yes, and probably in several forms. > > > > > > > > My brother Speed has created something he calls Leopard: Leo > > > > (something) response demon. Don't know exactly how it works. > > > > For years I've been asking him to describe it here, but he > > > > seems to have other priorities. As he describes it, the Leo > > > > outline is the db, including queries. > > > > > > > > I'll ask him again to tell us more. > > > > > > > > Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/eac181c4d302feafd68beca2a8727f406a7137d3.camel%40gmail.com.
Re: Leo Write-Only Mode
My sincerest apologies if I came off too alarmist with this message, this is an awesome community and Leo is a truly amazing tool and ecosystem. Rest assured I'm certain the problems are with *me* and not the software :-) I still believe there would be a huge amount of value in a file type that is write-only and not synchronized with the filesystem. In fact I want to pick up changes with many small @auto nodes and then clone the content of those nodes and embed them into *multiple* separate @write nodes and thus avoid the 'clone wars' (among other things). I think the @rst directive maybe does this and perhaps the @adoc one can do that too, but it wouldn't really solve the whole issue since some of the output files would include additional file formats. I'll try to put together a simple walk through and use case. Thanks again for your patience. Kevin On Thu, 2020-08-20 at 13:13 -0700, Félix wrote: > If I may suggest : A quick [Alt+PrintScreen], on any OS, will capture > the currently focused program window as a picture. > > Under windows, its in your clipboard so you can just CTRL+V to paste > right in here while you type. Like this: > > (In linux its put into your home/picture folder. ) > > So I would recommend you paste one before, and at each step of the > behavior/actions your trying to illustrate with your textual > description. This will allow experienced users to spot instantly some > details that explains the behavior you're experiencing while using > Leo. > -- > Félix > > > > On Thursday, August 20, 2020 at 3:31:18 PM UTC-4, Thomas Passin > wrote: > > Please describe exactly what you are doing. See if you can come up > > with a very condensed example (a small file with only a few nodes, > > for example). What do you want to achieve, what did you expect, > > and what actually happened? > > > > Bear in mind the the entire Leo code base is contained in a few Leo > > outlines, many people every day open those outlines that contain > > thousands of @file files, and don't have these kind of troubles. > > Of course, that's not importing. But - ask Edward - entire trees > > of code get imported into Leo all the time, too. > > > > So it's probably just that you have something amiss in your picture > > of how things work. Let's help you get that straightened out. > > Gotta start simple! > > > > On Thursday, August 20, 2020 at 2:20:30 PM UTC-4, k-hen wrote: > > > Is it possible to configure a non-sentinel file to be write-only? > > > > > > The file sync is making me very nervous because (and I'm sure I > > > did something wrong) the file didn't import correctly and blew > > > away my changes. Fortunately I had a backup but this just isn't > > > acceptable for me :-/ > > > > > > What I think is happening is that the file can't write or writes > > > partially, then I have to kill Leo for one reason or another, > > > then it's importing that incorrect file and wiping out my > > > changes. > > > > > > If I can't figure out a way around this, it's a deal breaker for > > > me unfortunately :-( > > > > > > > > > > > > > > -- > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/yo1p0tkOCDg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/292fb4c0-aea6-48d8-9062-df042d4d2c00o%40googlegroups.com > . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ec686cf12ff8ae7b93034daede2c71ebecde8143.camel%40gmail.com.
Re: Sentinel Naming Convention
True, but maybe *someday* a GUID/UUID or a Hash of that gnx - something like: http://cyan4973.github.io/xxHash/ or https://github.com/google/fa rmhash They also have Python libraries, e.g. https://pypi.org/project/xxhash/ & https://pypi.org/project/pyfarmhash/ On Mon, 2020-08-17 at 07:05 -0700, Thomas Passin wrote: > You could, however, use a new meaningless user name in Leo. That > should have the effect you want. It will still have the date, but > the name wouldn't disclose anything. > > On Monday, August 17, 2020 at 9:59:56 AM UTC-4, Edward K. Ream wrote: > > > > On Mon, Aug 17, 2020 at 7:40 AM k-hen > > wrote: > > > Hi All, > > > This is low priority, just thought I'd ask if perhaps there's a > > > way to configure the sentinel naming system. I'll probably keep > > > using @clean, but I'd be much more likely to use @file & > > > sentinels if they were a *hash* or custom specified instead of my > > > name/date. > > > > > > > This is unlikely ever to happen. The name/date is actually a gnx > > (global node index), which must be unique and invariant. gnx's make > > Leo's clones possible, and reliable. > > > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/g-Dl-g4S13s/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/948b2edf-ea56-4ec4-9376-ab45c2589127o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ba27ce2c4ac3ab854cd72ebf0acc688d677d36e3.camel%40gmail.com.
Re: @clean orphan node error
... Ohhh Thank you Thomas, that explains it (feeling rather foolish). And thank you too Edward, you stated it quite clearly in your message, I was just too thick-headed to pick up on it :-( I knew the @others directive was an *option* (like the others), just didn't seem like it was a *requirement*. But 20/20 hindsight. FWIW, I don't mind plowing through words, I've been reading this one extensively: https://leoeditor.com/directives.html (and I'm using the LeoDocs.leo file for this). But it wasn't clear to me from reading this (many times) that it was necessary, and that it was working without them (for good reasons) for @auto files was adding to my confusion. I saw there was a tutorial on "Creating Documents from Outlines" but it seems specific to @rst which isn't my objective. I haven't located any other tutorials re: documents, but perhaps I'm blind. It's maybe worth a quick note or column in the @file kind comparison table to say if it requires these or not. I'd definitely be interested in simple walk-through tutorials for how to do these basic tasks, I hope to become proficient enough to contribute to these as well :-) Thanks again, I really appreciate it, Kevin On Sun, 2020-08-16 at 09:13 -0700, Thomas Passin wrote: > It's what we were saying the other day. If you want to have child > nodes, you need to put a line > @others > in the parent where you want the "others" - that is, the child > subtree - to show up in the external file. And, most useful for > Python programming, if the "@others" is indented, then the lines from > the child nodes will be indented that amount when inserted into the > external file. > For example, if you wanted to have an html file, it might go like > this - > @file example.html- HEAD- BODY > Then the top node could contain: > @others > The HEAD node could contain: > Example File > The BODY node could contain:This is a test > Or the BODY node could contain: > This is a test > @others > > > There would be another subtree as a child of the BODY node. > > I've attached a Leo outline that illustrates. > > > On Friday, August 14, 2020 at 12:48:58 PM UTC-4, k-hen wrote: > > Hi guys, > > I'm trying to change and @auto node to an @clean node, but I'm > > getting and error writing the file. When I use the @auto then the > > file writes fine so it's not the path or anything. > > > > I'm sorry to keep bothering you, but I really want this to work. > > > > errors writing: test.txt > > Orphan node: does this work > > parent node: @clean test.txt > > Orphan node: @clean test.txt > > parent node: FileTest > > not written: test.txt > > finished > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/aLLyvf7PWWA/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/775f00e3-0ac2-4641-b48a-a9c4eb355315o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/88a4d0c2d200c7c7f456a89b37b1ea1d3b6ab4bb.camel%40gmail.com.
Re: Losing Clones after restart
Interesting, that's a good point, thanks for the info. On Fri, 2020-08-14 at 07:49 -0700, Thomas Passin wrote: > > > On Friday, August 14, 2020 at 10:17:20 AM UTC-4, k-hen wrote: > > Thank you kindly for your reply. I've enabled this feature and it > > seems very promising, but I think I might need a slightly different > > behaviour.I'll take a minute to explain the use case. > > > [snip] > > This is likely the desired behaviour for _code_ because it would be > > at the function/method level, > > > [snip] > > I know this is not the main thrust of your message, but I just want > to point out something here that bears on using Leo; in fact it's > one of the great things about Leo when compared to other editors that > have a tree-view pane. You are not limited to having a function or > method in a single node. I often split parts of a function or method > across several child nodes, and Leo's code base does the same. This > lets you keep a useful block of code on one screen. The common (non- > Leo) advice is to split a function up into smaller function calls if > it's too long, but that can be annoying and even confusing because > you have to keep too many functions and their parameters in mind at > once. Leo lets you break out from that rigid mold, though of course > you can still do so if you want. > > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/oKGhRhUVTXA/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/393409e5-1fc8-4a8e-ab43-05e46d5e36cbo%40googlegroups.com > . > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f5cc009dff17babe524ecc964c6fe8196c405c17.camel%40gmail.com.
Re: Documented Database Use Case
I'd be *very* interested in that, thank you! :-D On Fri, 2020-08-14 at 06:55 -0500, Edward K. Ream wrote: > On Thu, Aug 13, 2020 at 9:37 AM k-hen > wrote: > > > Is there a concept of Leo-as-database? > > Yes, and probably in several forms. > > My brother Speed has created something he calls Leopard: Leo > (something) response demon. Don't know exactly how it works. For > years I've been asking him to describe it here, but he seems to have > other priorities. As he describes it, the Leo outline is the db, > including queries. > > I'll ask him again to tell us more. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/rPA65N-Ujhc/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS0OoBRm2CrLe7K%2Bo0AhsLD1YkkH5f9v4DJEcRuo%2Bs-ABw%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3689546dc8149b3497a15f013aa90c98c1a38f1d.camel%40gmail.com.
Re: view-rendered plugin and mermaid.js
Ok, so this helped, thank you - but I still wasn't able to undock it from an existing window, but in other docs I was able to move it around.I was able to reset the local cache (db folder) and IT'S WORKING!! :-D Thanks so much for your help guys. - Kevin On Thu, 2020-08-13 at 18:13 -0700, lewis wrote: > There is a setting in LeoSettings :@bool use-vr-dock = False > True: The VR dock is (can be) moved. > False: (Recommended) The VR dock splits the body dock. > > > *Warning*: You may have to clear caches if you change this setting. > > Add that setting to your myLeoSettings file, set to True. You will > then be able to drag and detach the VR3 pane. > > Regards > Lewis > > > On Friday, August 14, 2020 at 9:01:56 AM UTC+10, k-hen wrote: > > This worked! I was able to get it for a new test file BUT the > > original file has VR3 docked *inside* the body and I can't seem to > > detach it. > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/KpI22_NJCz0/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/f290e3fb-4686-42bf-a5b8-7208a42827e4o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ee1e168204d8e932101089d0d92c8fc03102a405.camel%40gmail.com.
Re: Losing Clones after restart
Thank you kindly for your reply. I've enabled this feature and it seems very promising, but I think I might need a slightly different behaviour.I'll take a minute to explain the use case. In our git project we have a docs directory which is a simple collection of markdown files. This works great for the team because it's so simple and because many, many editors support this easily.MkDocs [https://www.mkdocs.org/] is also an amazing project that with the serve command,will allow you to view and navigate these files easily and convert to many client-friendly formats for basic publication. Obviously when I git pull, I'd like for Leo to refresh the content of those files, then I can edit them in Leo and save the changes back. The markdown docs are *trees* themselves however and the cloning behaviour seems to be occurring at the bottom/leaf level instead of the root.This is likely the desired behaviour for _code_ because it would be at the function/method level, but the commonality with markdown docs is a common *root* node for each document,(although there is the added snag of a possible front-matter section preceding this, but that could be a fixed section as its universal). In a perfect world, I could specify a sync directory in Leo and it would automatically import all of the files in those directories,then I could clone them into my own custom outline which is organized differently and with code and notes and statuses and such that don't belong in the docs. Does this seem feasible somehow (within reason)? :-) On Fri, 2020-08-14 at 07:10 -0500, Edward K. Ream wrote: > > On Thu, Aug 13, 2020 at 10:29 PM Thomas Passin > wrote: > > On Thursday, August 13, 2020 at 7:31:02 PM UTC-4, k-hen wrote: > > > [snip] > > > > > > > Would you file a bug issue on this? The issue URL is > > > > https://github.com/leo-editor/leo-editor/issues > > My apologies for not jumping in yesterday. > > > This is not a bug. Leo has substantial machinery for recreating > clones in all kinds of @auto nodes. To activate this machinery put > the following underneath your @settings tree in myLeoSettings.leo: > > @bool create-at-persistence-nodes-automatically = True > > Here is the comment in the body text of this node: > > With @clean and @file, Leo can store persistent data in nodes. This > information consists of the node’s gnx (Global Node Index) and the > node’s > uA, (User Attributes). > > The gnx gives each node a unique, immutable identity. Gnx’s make > clones > possible. The uA allows scripts and plugins to associate arbitrarily > much > additional data with each node. > > By default, Leo’s importers preserve neither gnx’s nor uA’s. This > makes > imported @auto trees second class citizens. To remedy this, if an > outline > contains an @persistence node, Leo will save data in the @persistence > tree > that allows Leo to recover gnx’s and uA’s when re-reading @auto files > later. This allows clone links and uA’s to persist. > > This is an optional feature. The stored data is akin to bookmarks. > The data > can “break” (become inaccessible) if the structure (including > class/method/function names) changes. > > HTH. > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/oKGhRhUVTXA/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS0NRj8qMAdwjVoBwv9X5PZFrCXE2RiVSr9ate_mPkpjpw%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/9be0f302a76fbc1cc63444aa501d9c058a4a9173.camel%40gmail.com.
Re: Losing Clones after restart
Well, Glad I'm in good company :-) I'm thinking the workaround is to use a the full path for every @auto headline, rather than nesting @path nodes?.Is there perhaps a way to do expansion on the filename within a headline or something so I don't need to repeat it all? It doesn't seem wise to clone the @auto-md, but maybe that works. If there's a directive or expansion or something I can put in the @auto node body then that could make it a lot cleaner.Note that there are hundreds if not thousands of files and the paths are subject to change. What I'd like to have: * MyOutline** MyFolder*** Thing1 Thing1 Docs* @auto-md Thing1 .md Thing1 Code Thing1 Notes** Files*** Docs @path ..\docs* @path things** @auto-md Thing1.md (clone) Workaround? * MyOutline ** MyFolder *** Thing1 Thing1 Docs * @auto-md ..\docs\things\Thing1 .md Thing1 Code Thing1 Notes On Thu, 2020-08-13 at 15:38 -0700, Thomas Passin wrote: > Aha! I duplicated this behavior. I got the same loss of clone-hood > in an @auto-md tree. I did not get it in an @file tree. When I > cloned a node in an @auto-md tree and dragged it out of the tree, it > still lost its clone status whe I closed and reloaded the file. > > On Thursday, August 13, 2020 at 6:28:00 PM UTC-4, Thomas Passin > wrote: > > Is it correct that you only are seeing this behavior on (a?) auto- > > md file? > > > > On Thursday, August 13, 2020 at 5:46:36 PM UTC-4, k-hen wrote: > > > Hi Felix,I am also perplexed. Note that the clones which are not > > > a descendant of the file don't have this behaviour either. > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/oKGhRhUVTXA/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/acbc9659-bba6-4b92-b870-0048a578b682o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/7f09a9b5acdd5ed20f544393a3f2264f0638b47b.camel%40gmail.com.
Re: view-rendered plugin and mermaid.js
This worked! I was able to get it for a new test file BUT the original file has VR3 docked *inside* the body and I can't seem to detach it.It seems these settings are on a per-file basis, but there's nothing I can see saved within the document on positioning. Is there a way I can reset the positioning? On Thu, 2020-08-13 at 15:42 -0700, Thomas Passin wrote: > On Thursday, August 13, 2020 at 6:22:54 PM UTC-4, k-hen wrote: > > Ok, thanks! I've got this going, the docks feature is interesting. > > Strangely I can move the body and the tabs, but not the VR3 > > panel... > > I've tried restarting & redragging it a few times but still no luck > > :-/ > > Add a node with this headline to your MyLeoSettings tree, then > restart Leo: > > @string central-dock-widget = body > > I had to add this to get what I considered desirable positioning. I > like to place the outline pane n the upper left, the Tabs pane in the > lower left, the body pane in the middle, and have the VR3 pane open > in the right hand side. > > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/KpI22_NJCz0/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/2f338703-f6cf-4620-a81d-a000626fda26o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/6a1f27b50d203bc7fbcac1ee6646e6212a22e278.camel%40gmail.com.
Re: Losing Clones after restart
I've been thinking about this a bit more, and I'm thinking this is probably expected and I just wasn't thinking about it properly.Since this is an *auto* node, perhaps it's clearing & reloading the descdendant nodes of my file on the load of Leo.So the clone is there originally, then it deletes the file child node to re-import (making the non-file node a non-clone), then recreates a new child node with the same name as a copy. This at least makes sense to me now, I suppose I'll just have to restructure my outline because I still want to be able to sync with other users using pure markdown and not using Leo. Kevin On Thu, 2020-08-13 at 14:46 -0700, k-hen wrote: > Hi Felix,I am also perplexed. Note that the clones which are not a > descendant of the file don't have this behaviour either. > I first encountered this in my large document using the pip version > (6.2). > I was able to reproduce this however using both a new/fresh/extremely > small .leo file, > I was also encountered this after installing/using the git version > (6.3-devel). > > I don't have any custom scripts or plugins, only the defaults. > > Kevin > > > > > On Thursday, August 13, 2020 at 4:59:08 PM UTC-4 Félix wrote: > > That's weird, > > > > For a leo file to change between having 2 positions be clone of > > each other, to being two distinct nodes, happening to have the same > > headline and content, requires a non-trivial change... > > Would be curious to see if you dont have scripts or plugins enabled > > that would make changes to your document while its saving it. > > > > Do you have the bug in a completely new file with only two simple > > nodes (clones), saving the file, closing the file, then re-opening > > it? > > > > Or do you have this bug only in a particular Leo file ? > > -- > > Félix > > > > > > On Thursday, August 13, 2020 at 1:59:51 PM UTC-4, k-hen wrote: > > > I saw another post from today about cloning, so I've checked out > > > the current devel branch - and unfortunately it's happening there > > > for me also :-( > > > The post says something about 'clones' branch, but I don't see > > > one of those. > > > > > > > > > On Thursday, August 13, 2020 at 1:46:13 PM UTC-4 k-hen wrote: > > > > OK, so I've been able to repeat the behaviour at least. > > > > I created a new outline and cloned a node and it worked fine. > > > > > > > > Then for my use case I have an @auto-md clone_test.md with a > > > > child node that is being cloned and moved out, and that one is > > > > also dropping the clone after restarting leo :-/ > > > > > > > > > > > > > > > > > > > > On Thursday, August 13, 2020 at 1:38:53 PM UTC-4 > > > > tbp1...@gmail.com wrote: > > > > > You aren't doing anything wrong, but it shouldn't be > > > > > happening. I don't lose my clones that way. I happen to be > > > > > on the devel branch but I don't think that's a factor here: > > > > > > > > > > Leo 6.3-devel, devel branch, build 6a92120f1a > > > > > 2020-06-23 09:38:53 -0500 > > > > > Python 3.8.2, PyQt version 5.14.2 > > > > > Windows 10 AMD64 (build 10.0.18362) SP0 > > > > > > > > > > Maybe Edward could shed some light here. > > > > > > > > > > > > > > > On Thursday, August 13, 2020 at 1:24:19 PM UTC-4, k-hen > > > > > wrote: > > > > > > Hi, > > > > > > I'm not sure if this is a bug or if I'm doing something > > > > > > wrong. I've created some cloned nodes, and the icon is > > > > > > correct and they work as I expect, but as soon as I close & > > > > > > reopen leo they become non-cloned (copied) nodes. > > > > > > > > > > > > I first tried using an in-place clone (ctrl+`) then > > > > > > dragging the clone out, and also tried copy/paste-as-clone > > > > > > but got the same behaviour both times. > > > > > > > > > > > > Am I missing something? > > > > > > > > > > > > I'm using Leo installed via pip, > > > > > > Leo 6.2.1 final > > > > > > Python 3.6.3, PyQt version 5.14.2 > > > > > > Windows 10 AMD64 (build 10.0.14393) SP0 > > > > > > > > > > > > Thanks, > > > > > > Kevin > > > > > > > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/oKGhRhUVTXA/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/f5e36dce-6a7a-407c-b356-1fe40c7f3e91n%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/8238f67726e35646df58ad61cd88328690d718b6.camel%40gmail.com.
Re: view-rendered plugin and mermaid.js
Ok, thanks! I've got this going, the docks feature is interesting.Strangely I can move the body and the tabs, but not the VR3 panel...I've tried restarting & redragging it a few times but still no luck :-/ On Thu, 2020-08-13 at 11:24 -0700, Thomas Passin wrote: > On Thursday, August 13, 2020 at 1:39:17 PM UTC-4, k-hen wrote: > > I don't mind refreshing at all. Pardon the naive question, but how > > would I go about trying VR3? > > You edit the MyLeoSettings.leo file, which you can open from Leo's > Settings menu. Find a node titled @enabled plugins. Comment out > viewrendered.py and add or uncomment viewrendered3.py. Then restart > Leo. Actually, you could run both plugins, but it's less confusing > and a better use of screen real estate not to. > > I don't recall if the version of the plugin in Leo 6.2.x final is the > same as its current version. If you want to run the devel branch > from GitHub, you will certainly get the current version. The way I > run Leo with the devel branch is to clone Leo's GitHub repository and > switch to the clone's devel branch. Then open a console window and > set the environmental variable > set PYTHONPATH=path\to\github-leo > Then run Leo from that console. I usually launch it this way - > python -m leo.core.runLeo --use-docks > If your outline and tab panes start out in strange locations, drag > them around and then restart Leo. You may need to do this a fe times > before the positions settle down. I don't know why that happens. > Edward says it is a quirk of the QT5 system that we can't do anything > about. > Open and close the plugin using . > > > > On Thursday, August 13, 2020 at 1:32:49 PM UTC-4 tbp1...@gmail.com > > wrote: > > > The VR3 plugin can display the diagram outputs. It wouldn't > > > update automatically when you made a change - you would have to > > > refresh the plugin view to see that changed image. > > > > > > It *may* be possible to get mermaid to run in a panel inside > > > Leo. It could be launched using graal, and Leo can be made to > > > display what is basically a Chrome browser in a panel or a free > > > floating frame - see > > > > > > https://groups.google.com/forum/#!topic/leo-editor/hweJvjeYiEM. > > > > > > The development might take some time, and just viewing the output > > > images in VR3 might be all you really need. > > > > > > > > > On Thursday, August 13, 2020 at 9:44:38 AM UTC-4, Edward K. Ream > > > wrote: > > > > On Thu, Aug 13, 2020 at 8:21 AM k-hen > > > > wrote: > > > > > > > > > > > > > I was wondering if it's possible to get mermaid.js [ > > > > > https://mermaid-js.github.io/] working via the view-rendered > > > > > plugin. > > > > > > > > Thanks for the link to mermaid! > > > > > > > > Leo doesn't do js directly, so I don't think the vr plugin is > > > > likely ever going to support mermaid. > > > > > > > > When you think js, remember vs code :-) There are several > > > > mermaid extensions in vs code. > > > > > > > > Félix is working on leoInteg as we speak. I am excited about > > > > the partnership of leoInteg and "traditional" Leo, leo on the > > > > desktop. > > > > > > > > Edward > > > > -- > > You received this message because you are subscribed to a topic in > the Google Groups "leo-editor" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/KpI22_NJCz0/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > leo-editor+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/c5ad72ed-4c9e-49d9-a666-63e9099a8661o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/09ef52a85bea7e62d79df80b183ad77c0f70113d.camel%40gmail.com.
