Re: Data-Forge Notebook 1.0 release may be of interest

As soon as I saw "edit in external editor" I had to export and load in Leo. Joplin uses sentinels to keep track of all the snippets of md. id: 00e76bec2ebd416fb31e10a9921e0945 parent_id: abbb63233c614a8ba6262ae0eed79bd6 created_time: 2019-06-13T01:04:20.807Z updated_time:

Re: Retire @bool recent_files_group_always?

Yes, makes sense to me. Seems to work as expected now. Thanks for the fix! Rob... > > > At last I understand. If I understand correctly, this means that #1188 > can be closed. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: Data-Forge Notebook 1.0 release may be of interest

Responding to "{thing} may be of interest" part of the topic, here's one that's caught my eye recently: *Joplin* (https://joplinapp.org/). *"a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. The notes are searchable, can

Rev 2dd87c in devel: plugins use Qt docks when possible

This completes #1154 . Please report any problems. Only a straightforward change to LeoQtLog.createTab was needed. Initially, quicksearch.py (The Nav pane) crashed. The fix was to disable a legacy binding when g.app.dock is True. Edward

Re: Bookmarks plugin for docks

On Wed, Jun 12, 2019 at 4:29 PM Edward K. Ream wrote: Thanks for this. I'll add it to the list. > Heh. bookmarks.py does not create any tab in the Log pane, so nothing needs to be done. > plugins probably use common code to add themselves to the (legacy) Log > pane. I'll just adapt that

Re: Bookmarks plugin for docks

On Wed, Jun 12, 2019 at 1:38 PM Terry Brown wrote: > Bookmarks isn't particularly entangled in the old UI, I had it working in > my attempt at a docks based UI. > > I don't really see it as different from the other plugins listed in #1154 > ,

Re: Retire @bool recent_files_group_always?

On Wed, Jun 12, 2019 at 3:02 PM Rob wrote: > I use the setting because I have a number of .leo files withe the same > name, but different file paths. By grouping them, it reduces clutter and > makes it easier to see which path version I'm opening. > At last I understand. If I understand

Re: Retire @bool recent_files_group_always?

I use the setting because I have a number of .leo files withe the same name, but different file paths. By grouping them, it reduces clutter and makes it easier to see which path version I'm opening. HTH It won't be the 'end of the world' to deprecate the option, but it is useful. Perhaps I'm

Re: Bookmarks plugin for docks

Bookmarks isn't particularly entangled in the old UI, I had it working in my attempt at a docks based UI. I don't really see it as different from the other plugins listed in #1154 , it has state persistence, but I don't think that's a GUI tied

Re: Leo 6.0b1 coming Friday, June 14

On Monday, June 10, 2019 at 11:36:56 AM UTC-5, Edward K. Ream wrote: > The remaining issues scheduled for 6.0 need not delay 6.0b1. I may delay b1 for a few days. There is no need to rush.

Re: Retire @bool recent_files_group_always?

On Wednesday, June 12, 2019 at 5:23:35 AM UTC-5, Edward K. Ream wrote: However, I don't see the purpose of setting @bool recent_files_group_always > to True. It seems mostly to clutter the recent files menu. Can anyone > explain why this setting is useful? > I have a half memory that this

Re: Bookmarks plugin for docks

On Wed, Jun 12, 2019 at 8:31 AM lewis wrote: I have found Leo's Bookmarks plugin a very useful tool. With the > introduction of docks it is no longer available unless you use the > --no-dock option, but then you lose dock features. > Is there any prospect of there being a compatible plugin

Re: ENB: another playful prototye

On Wed, Jun 12, 2019 at 10:49 AM Edward K. Ream wrote: > On Wed, Jun 12, 2019 at 6:59 AM vitalije wrote: > On my machine in my version of LeoPy.leo this script finds about 3737 missing docstrings in 122.28ms. Please feel free to add this script to scripts.leo. Presumably you would disable the

Re: ENB: another playful prototye

On Wed, Jun 12, 2019 at 6:59 AM vitalije wrote: > I am not sure what were your intentions for find-missing-docstrings > command. > It was mostly to play with live objects. Pylint's "missing-docstring" test creates clickable links, so for actually adding docstrings pylint is the best tool.

Re: ignoring a node without using sentinels

On Wed, Jun 12, 2019 at 10:00 AM Josef wrote: > I mostly work with @clean these days, as that gives me the least grief > when working with others, who do not use Leo. > I often would like to ignore or at least comment out node including the > subtree underneath, ideally by marking the node

ignoring a node without using sentinels

I mostly work with @clean these days, as that gives me the least grief when working with others, who do not use Leo. I often would like to ignore or at least comment out node including the subtree underneath, ideally by marking the node headline. So far I only found a way by commenting out the

Bookmarks plugin for docks

I have found Leo's Bookmarks plugin a very useful tool. With the introduction of docks it is no longer available unless you use the --no-dock option, but then you lose dock features. Is there any prospect of there being a compatible plugin enabling a Bookmark panel to be inserted or merged into

Re: ENB: another playful prototye

I am not sure what were your intentions for find-missing-docstrings command. I assume you found out that it is impossible to use live objects in general, but useful for searching in Leo's own code. Here is my script that searches Leo outline for methods and classes with missing docstrings:

Re: Data-Forge Notebook 1.0 release may be of interest

On Tue, Jun 11, 2019 at 5:49 PM Paul wrote: > Data-Forge Notebook version 1.0 has been released > http://www.data-forge-notebook.com/ > Thanks for this link. I've bookmarked it. Let us know what you discover. Edward -- You received this message because you are subscribed to the Google Groups

Retire @bool recent_files_group_always?

Rev 3afff37 fixes #1188 by undoing a change related to #1121 : unicode characters in command names. This new fix is unlikely to cause problems. However, I don't see the purpose of