Re: history tracer plugin

On Fri, Feb 28, 2020 at 7:36 PM Matt Wilkie wrote: > Still no joy on Windows. I *may *have a prototype for buttons to > start/stop the server from within Leo though: > Thanks for all this work. I would like to use the history tracer plugin on Windows. Edward -- You received thi

Re: history tracer plugin

ded while figuring out how to install and use Vitalije's History Tracer plugin. Ahhh, in reading history_tracer.py I see reference to port # to put in my settings. Trying that... Ok, that's fixed the urllib connection errors, and I see a .history file in same folder as .leo. However there is st

Re: history tracer plugin

Confirmed working now on Linux (yay!) but still not on Win10. I added some info to the issue. I have to leave now but will resume investigating later today. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: history tracer plugin

Thanks Vitalije! installation went smoothly but the browser doesn't show anything and there are connection errors in the terminal. I opened an issue: https://github.com/leo-editor/leo-editor/issues/1502. cheers, -matt -- You received this message because you are subscribed to the Google

Re: history tracer plugin

, please file the issue on the github, or ask here for further help. For the plugin to work correctly, leo-ver-serv should be running and full path to the outline should be in the list of known files that was given to leo-ver-serv on the start. This means if you create a new outline, or if you open

history tracer plugin

Hi Vitalije, I'd like to try your History Tracer plugin. Has anything significant changed since this thread? https://groups.google.com/d/topic/leo-editor/wM38DuOxvGA/discussion -matt -- You received this message because you are subscribed to the Google Groups "leo-editor&q

Re: HOWTO: Display reStructuredText with stylesheets using the Viewrendered2 plugin

Five years later, I have a suggestion about these stylesheet problems. You can get pygments to generate a stylesheet for you. There are various styles, and I just used the one named "default": pygmentize -S default -f html > pygments.css (pygmentize gets installed with "pip install

Re: Discuss: retire the scripts_menu plugin?

On Saturday, December 21, 2019 at 8:21:17 PM UTC-5, Edward K. Ream wrote: > Unless I hear a convincing reason why the [scripts_menu] plugin should exist, I am going to move it to the attic. I have just created #1461 <https://github.com/leo-editor/leo-editor/issues/1461> for this

Discuss: retire the scripts_menu plugin?

Today I spent several hours rewriting the scripts_menu plugin (in devel). It now appears to work as before, but I have a very bad feeling about this plugin. It seems both useless and a serious security concern. Does anyone use this plugin? If so, does it still work as expected? Unless I hear

Re: the autosave plugin: doc bug? how to enable and configure

On Fri, Dec 6, 2019 at 2:43 PM 'Terrence Brannon' via leo-editor < leo-editor@googlegroups.com> wrote: The autosave plugin says that it saves every 300 seconds by default. But > the .getInt() call in the code does not have a default value. So I doubt > that it really saves every

the autosave plugin: doc bug? how to enable and configure

The autosave plugin says that it saves every 300 seconds by default. But the .getInt() call in the code does not have a default value. So I doubt that it really saves every 300 seconds by default. Next, I'm not sure where to put the settings for this plugin versus where to put the @enabled

Re: Anyone using the pyzo_in_leo plugin?

I'm using pyzo_in_leo only to see how useful it can be. It uses a lot of screen area in Leo; pyzo docks have minimum size, so you can't drag them to very narrow space. At least you can toggle pyzo docks on/off if you like. This is one reason think it's good to retain the python_terminal plugin

Help wanted: #990: neovim plugin

I have just changed the name of #990 to "Two-way communication between Leo and neovim". At present, this issue is scheduled for Leo 6.2, but it might be the work of just a few hours... neovim uses MessagePack

Anyone using the pyzo_in_leo plugin?

I'm curious about how much interest there is. 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

Re: How to import an OPML file into Leo after enabling the leoOPML plugin?

On Fri, Oct 4, 2019 at 12:14 PM The Living Cosmos wrote: I'm not sure how to have Leo open a .opml file and then save it as .leo > > My end goal is to have LeoVue present the file on the web. > Selecting the leoopml entry in the Plugins menu will show you the plugin's docstring. You will see a

How to import an OPML file into Leo after enabling the leoOPML plugin?

I have correctly and successfully edited the myLeoSettings.py file via the Leo Editor GUI. leoOPML.py is now enabled (because I uncommented it in the list of plugins). However I'm not sure how to have Leo open a .opml file and then save it as .leo My end goal is to have LeoVue present the

Re: New plugin history_tracer

On Friday, October 4, 2019 at 1:38:29 PM UTC+2, Edward K. Ream wrote: > > > Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided > (‘https://hangouts.google.com’) does not match the recipient window’s > origin (‘https://mail.google.com’). > > Edward > I don't know what

Re: New plugin history_tracer

On Fri, Oct 4, 2019 at 4:09 AM vitalije wrote: > Things one should know about leo-ver-serv and history_tracer.py. > >1. leo-ver-serv should be running before Leo opens and the port it >listens on should match the one from Leo settings (by default 8087) >2. if leo-ver-serv is running

Re: New plugin history_tracer

when starting leo-ver-serv, initially all files will look empty, until Leo sends its first snapshot for each of these files. 5. history_tracer plugin binds a handler on 'command2' which is executed after any Leo command, and this handler just records the time of the last executed

Re: New plugin history_tracer

Did you actually make a change to your outline? Body edits don't count. Iirc Vitalije's code doesn't send anything unless a command is executed. On Thu, Oct 3, 2019 at 3:35 PM Edward K. Ream wrote: > > > On Thu, Oct 3, 2019 at 10:22 AM vitalije wrote: > >> Try to write leo-ver-server-files.txt

Re: New plugin history_tracer

On Thu, Oct 3, 2019 at 10:22 AM vitalije wrote: > Try to write leo-ver-server-files.txt using unix new lines. Does > leo-ver-serv.exe produces any output in console? > No output in console. Browser view unchanged. Edward -- You received this message because you are subscribed to the Google

Re: New plugin history_tracer

Try to write leo-ver-server-files.txt using unix new lines. Does leo-ver-serv.exe produces any output in console? Vitalije On Thursday, October 3, 2019 at 4:25:35 PM UTC+2, Edward K. Ream wrote: > > > > On Tuesday, October 1, 2019 at 12:13:27 AM UTC-5, vitalije wrote: >> >> >> This morning I've

Re: New plugin history_tracer

On Tuesday, October 1, 2019 at 12:13:27 AM UTC-5, vitalije wrote: > > > This morning I've successfully built it with the `cargo install > leo-ver-serv` command on Windows10 laptop. > Still fails for me, as before. I downloaded leo-ver-serv-v0.1.7.exe and ran it. I run it as follows from a

Re: Discuss: is it time to retire the python_terminal plugin?

On Tuesday, October 1, 2019 at 8:32:09 AM UTC-5, Edward K. Ream wrote: > #1155 <https://github.com/leo-editor/leo-editor/issues/1155> suggests retiring the python_terminal plugin. Upon further review, I am not going to do this, for the following reasons: 1. #1212 <https://github.co

Re: Discuss: is it time to retire the python_terminal plugin?

1. Enable pyzo_in_leo.py plugin. 2. Run Leo using --global-docks on the command line. HTH, Chris On Tue, Oct 1, 2019 at 7:11 AM lewis wrote: > I haven't kept up to date with how pyzo features are available in Leo. > Pyzo is installed and the pyzo_in_leo.py plugin is enabled bu

Re: Discuss: is it time to retire the python_terminal plugin?

I haven't kept up to date with how pyzo features are available in Leo. Pyzo is installed and the pyzo_in_leo.py plugin is enabled but from the Plugins menu no pyzo plugin or information is available. LeoDocs currently has no mention of pyzo plugin. Are there any guides on how to use Pyzo shells

Discuss: is it time to retire the python_terminal plugin?

#1155 <https://github.com/leo-editor/leo-editor/issues/1155> suggests retiring the python_terminal plugin. This plugin is known to cause segfaults. Nobody seems to have any interest in fixing it. Now that the pyzo_in_leo plugin is (partly) functional, using pyzo's "Shells" w

Re: New plugin history_tracer

Here is the Windows10 version: leo-ver-serv-v0.1.7.exe sha1: 0d79fd1864d31f190ed3b33e708778ebc4fd8ee6 This morning I've successfully built it with the `cargo install leo-ver-serv` command on Windows10 laptop. Vitalije --

Re: New plugin history_tracer

, 2019 at 1:22 PM vitalije wrote: >> >>> I finally got around to pack and publish my new plugin history_tracer. >>> >> ... >> >>> If you have cargo installed then installation of leo-ver-serv would be >>> quite easy. >>> cargo install le

Re: New plugin history_tracer

I get back I'll add them to git. Vitalije On Tuesday, October 1, 2019 at 12:06:27 AM UTC+2, Edward K. Ream wrote: > > > > On Sat, Sep 28, 2019 at 1:22 PM vitalije > > wrote: > >> I finally got around to pack and publish my new plugin history_tracer. >> > .

Re: leo_in_pyzo plugin is ready for testing

I'm sure you meant *pyzo_in_leo* plugin :) Regards Lewis -- 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.co

Re: New plugin history_tracer

On Sat, Sep 28, 2019 at 1:22 PM vitalije wrote: > I finally got around to pack and publish my new plugin history_tracer. > ... > If you have cargo installed then installation of leo-ver-serv would be > quite easy. > cargo install leo-ver-serv > On windows I get this:

leo_in_pyzo plugin is ready for testing

The code is in devel. Most of #1093 <https://github.com/leo-editor/leo-editor/issues/1093> is complete. This is a major milestone in the plugin's history. --global-docks must be in effect to use this plugin. *Status* - Leo fully inits pyzo, and creates a Pyzo menu in each opened Leo o

Re: New plugin history_tracer

On Sat, Sep 28, 2019 at 1:22 PM vitalije wrote: > I finally got around to pack and publish my new plugin history_tracer. > Many thanks for this. I have just created #1358 <https://github.com/leo-editor/leo-editor/issues/1358> to memorialize your contribution. This will ensure that

Re: New plugin history_tracer

gt; > contains > the plugin. > > On Saturday, September 28, 2019 at 10:10:03 PM UTC+2, btheado wrote: >> >> Vitalije, >> >> I'm see a blank @file history_tracer.py. Did you forget a 'git add'? >> >> Brian >> >> On Sat, Sep 28, 2019 at 2:22

Re: New plugin history_tracer

Good catch. I forgot to add it. Rev d8fc8bc <https://github.com/leo-editor/leo-editor/commit/d8fc8bc81edb9dae64789a90a07f57c1dfcb6211> contains the plugin. On Saturday, September 28, 2019 at 10:10:03 PM UTC+2, btheado wrote: > > Vitalije, > > I'm see a blank @file history_

Re: New plugin history_tracer

Vitalije, I'm see a blank @file history_tracer.py. Did you forget a 'git add'? Brian On Sat, Sep 28, 2019 at 2:22 PM vitalije wrote: > I finally got around to pack and publish my new plugin history_tracer. > > In order to be useful one must have installed leo-ver-serv utility. I

New plugin history_tracer

I finally got around to pack and publish my new plugin history_tracer. In order to be useful one must have installed leo-ver-serv utility. I'll try to make it available as a binary file for Ubuntu 18.04 and Windows 10. It should be straightforward to install from source if one already has

Re: What's wrong with render plugin?

On Mon, Sep 23, 2019 at 1:18 AM gar wrote: > excuse me. something went wrong in my mind and it seemed to me that this > fix doesnt work for render plugin, only affects code highlighting. > now i checked it out once again and convinced that I was mistaken. > excuse me once agai

Re: What's wrong with render plugin?

excuse me. something went wrong in my mind and it seemed to me that this fix doesnt work for render plugin, only affects code highlighting. now i checked it out once again and convinced that I was mistaken. excuse me once again. пятница, 20 сентября 2019 г., 21:04:17 UTC+3 пользователь Edward K

Re: What's wrong with render plugin?

On Fri, Sep 20, 2019 at 12:11 PM gar wrote: This is still not available in leo-6.1-final. When to expect it? > I have no idea what you mean. We are on 6.1-devel. If you have specific complaints about #1287 please take the time to explain clearly what they are. Edward -- You received this

Re: What's wrong with render plugin?

This is still not available in leo-6.1-final. When to expect it? пятница, 16 августа 2019 г., 17:52:43 UTC+3 пользователь Edward K. Ream написал: > > On Friday, August 16, 2019 at 9:00:07 AM UTC-5, Edward K. Ream wrote: > > > I have just created #1287 >

Re: The leo_in_pyzo plugin is ready for testing!

KDE is based on Qt. There may be some interactions there. I will set-up a virtualbox with vanilla Ubuntu and see what happens. Chris On Fri, Aug 30, 2019 at 6:54 AM Edward K. Ream wrote: > On Wed, Aug 28, 2019 at 5:42 PM Matt Wilkie wrote: > > I think he meant also which linux distribution.

Re: The leo_in_pyzo plugin is ready for testing!

On Wed, Aug 28, 2019 at 5:42 PM Matt Wilkie wrote: I think he meant also which linux distribution. > That would help. I do my testing on ubuntu, and I see no problems. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: The leo_in_pyzo plugin is ready for testing!

On Wed, Aug 28, 2019 at 4:09 PM Chris George wrote: > Further testing shows that the artifacts only exist transiently but do not > persist between sessions. > Thanks for this. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: The leo_in_pyzo plugin is ready for testing!

> > The pyzo_in_leo.py plugin requires --global-docks and the qt gui, which is > Leo's default. It is incompatible with --no-dock. > git checkout devel git pull leo # add pyzo_in_leo.py to @enabled-plugins node in myLeoSettings.leo # save, exit leo --global-docks On load the O

Re: The leo_in_pyzo plugin is ready for testing!

Neon which is the official KDE distro. It is built on Ubuntu 18.04. Chris On Wednesday, August 28, 2019 at 3:42:28 PM UTC-7, Matt Wilkie wrote: > > It helps a lot. Please remind me what platform you are using. >>> >> >> Leo 6.1-devel, devel branch, build 05e1e94daf >> 2019-08-28 02:48:56 -0500

Re: The leo_in_pyzo plugin is ready for testing!

> > It helps a lot. Please remind me what platform you are using. >> > > Leo 6.1-devel, devel branch, build 05e1e94daf > 2019-08-28 02:48:56 -0500 > Python 3.6.8, PyQt version 5.12.3 > linux > I think he meant also which linux distribution. -matt -- You received this message because you are

Re: The leo_in_pyzo plugin is ready for testing!

Oh, I forgot to mention that I deleted the cache before testing and this makes pretty much any operation leave the artifact. Closing and opening Leo seems to make it less prevalent. Chris On Wednesday, August 28, 2019 at 2:09:45 PM UTC-7, Chris George wrote: > > Further testing shows that the

Re: The leo_in_pyzo plugin is ready for testing!

Further testing shows that the artifacts only exist transiently but do not persist between sessions. They seem to be caused by activity that moves, nests, resizes etc. widgets. Closing Leo and reopening makes them go away and they do not reappear until you move, nest or resize a widget. They

Re: The leo_in_pyzo plugin is ready for testing!

On Wed, Aug 28, 2019 at 10:58 AM Chris George wrote: Once a pyzo dock is closed using x or unchecking it, it is gone and cannot > be reopened. The "Editors" and "Shells" docks behave correctly ie. they can > be opened and closed using the right-click pop-up titlebar method. > Restarting Leo

Re: The leo_in_pyzo plugin is ready for testing!

dward K. Ream wrote: > As of rev a0c34f4 in the pyzo branch... > > The pyzo_in_leo.py plugin requires --global-docks and the qt gui, which is > Leo's default. It is incompatible with --no-dock. > > Pretty much everything "just works". The plugin properly loads all pyzo >

The leo_in_pyzo plugin is ready for testing!

As of rev a0c34f4 in the pyzo branch... The pyzo_in_leo.py plugin requires --global-docks and the qt gui, which is Leo's default. It is incompatible with --no-dock. Pretty much everything "just works". The plugin properly loads all pyzo docks in *Leo's* main window only once, at &q

Re: What's wrong with render plugin?

On Friday, August 16, 2019 at 9:00:07 AM UTC-5, Edward K. Ream wrote: > I have just created #1287 for this. Fixed at rev 91ac803 in devel. There are some subtleties involved. See the last comment in #1287. Please reopen if necessary.

Re: What's wrong with render plugin?

On Fri, Aug 16, 2019 at 7:26 AM Rob wrote: > I see the same thing: > >- A node w/ @rst header renders as expected. >- Child nodes of this node do not. >- If a parent node on these have an `@language rest`, then all child >nodes render as expected. > > That was as I had intended.

Re: What's wrong with render plugin?

much in the past; now I do. HTH Rob... On Friday, August 16, 2019 at 12:52:28 AM UTC-4, gar wrote: > > Since I upgraded to leo-6 i encounter the following: > > - render plugin does not treat nodes content as in RST anymore - shows it > as plain text (to highlights or ma

What's wrong with render plugin?

Since I upgraded to leo-6 i encounter the following: - render plugin does not treat nodes content as in RST anymore - shows it as plain text (to highlights or markups - nothing) - specifying @rst for a node forces it to be rendered with markup - but only this node, not it's children

mime plugin query

I am trying to get the @mime plugin working. I have *example.pdf* file located in N:\leo folder. My leo file has a node [no body text]: @mime >@path example.pdf Right-click over the node and observe 2 options: *Create dir C:\Users\lewis\* *OneDrive...\example.pdfOpen C:\Users\lewis\**OneDr

Re: livecode plugin and meta

(pip isn't an option); it just does the never-ending swirly thing and > doesn't finish. > You can probably use some form of conda install or conda pip install. Take a look at the conda docs. Or just disable the plugin ;-) Edward -- You received this message because you are subscribed

livecode plugin and meta

finish. Perhaps I'll simply disable the plugin since I don't know why I would need/want/use it. However, I'm wondering if anyone else has problems installing the `meta` package. Rob... -- You received this message because you are subscribed to the Google Groups "leo-editor&q

Re: Usage of Leo plus mod_http plugin?

Hello Lewis, Am So., 23. Juni 2019 um 11:46 Uhr schrieb lewis : > I use the plugin occasionally as an alternative way to view Leo data from 2 > apps. I wasn't aware it offered anything more than 'Read Only' function. > > I had another serious play with it today and jotted some no

Re: Usage of Leo plus mod_http plugin?

And now that I have read the docstring, it obviously does more than 'read only' :) On Sunday, June 23, 2019 at 7:46:27 PM UTC+10, lewis wrote: > > I wasn't aware it offered anything more than 'Read Only' function. > -- You received this message because you are subscribed to the Google Groups

Re: Usage of Leo plus mod_http plugin?

Hi Viktor, I use the plugin occasionally as an alternative way to view Leo data from 2 apps. I wasn't aware it offered anything more than 'Read Only' function. I had another serious play with it today and jotted some notes: With a page refresh your browser updates without having to save leo

Re: #1211: retiring the codewisecompleter plugin

rate from Leo's other code completion commands! - Leo's core uses codewise for completion if `@bool use-jedi` is False. - The codewisecompleter plugin has now been retired. I probably moved the codewise code into the core, and forgot to remove the codewisecompleter plugin. Yes, this is way

Re: #1211: retiring the codewisecompleter plugin

On Friday, June 21, 2019 at 7:14:21 PM UTC-5, Edward K. Ream wrote: #1211 <https://github.com/leo-editor/leo-editor/issues/1211> is now named: > Fix the ctagscompleter plugin. > > For at least three years now the codewisecompleter and ctagscompleter > plugins have been v

#1211: retiring the codewisecompleter plugin

#1211 <https://github.com/leo-editor/leo-editor/issues/1211> is now named: Fix the ctagscompleter plugin. For at least three years now the codewisecompleter and ctagscompleter plugins have been virtually identical. Both have a mixture of gnx's for ekr and ville. Perhaps they have *

Usage of Leo plus mod_http plugin?

Question to the Leo Community: Are there users who actively use the mod_http plugin to read & write content from/to an outline? Background of my question: I've enabled the plugin in 6.0 beta 1 & viewed the quickstart.leo" outline in the browser. My initial reaction: Th

The python_termainal plugin no longer segfaults

Chris George discovered the cause: importing rlcompleter. This is likely an obscure python bug. rlcompleter handles tab completion, which is hardly an essential feature of this plugin. The fix was a new top-level switch: use_rlcompleter = False # A workaround for #1212: segfaults

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: Bookmarks plugin for docks

idgets to manage. If the new model is for each plugin to understand the GUI and manage itself within it, then there might be more work to be done. Cheers -Terry On Wed, Jun 12, 2019 at 11:06 AM Edward K. Ream wrote: > > > On Wed, Jun 12, 2019 at 8:31 AM lewis wrote: > > I have

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 compatib

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

Re: mod_http plugin

This problem occurred while I had a stalled leoflexx session. See #1103 -- 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

mod_http plugin

Trying to use the mod_http plugin I am getting an 'unable to connect' error at http://localhost:8130/ I've checked myLeoSettings file and it meets all the requirements to run the plugin. *Leo Log WindowLeo 5.8.1-b2 devel, build 20190227233831, Wed Feb 27 23:38:31 PST 2019Git repo info

Re: warning: bug in cached @file and/or Leo Cloud plugin?

> > A nested @file node is an indication that the gnx in the external file > does not match the gnx in the outline. > In a "refresh from disk" circumstance I would expect the external file to "win", ie. assume it's the most correct and discard remembered information. The downloaded workbook

Re: warning: bug in cached @file and/or Leo Cloud plugin?

-- Forwarded message - From: Matt Wilkie Date: Sun, Oct 14, 2018 at 6:21 PM Subject: warning: bug in cached @file and/or Leo Cloud plugin? To: leo-editor Heads up: > I've just had this weird situation where I noticed the @file contents were definitely NOT the most rec

Re: warning: bug in cached @file and/or Leo Cloud plugin?

My workbook.leo attached, post "refresh-from-disk" behaviour talked about last message, and post removing all the other private nodes that were in this file. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

warning: bug in cached @file and/or Leo Cloud plugin?

would have happened though if I'd saved before 'Refresh from disk'. This .leo file is using Terry's leo_cloud.py plugin, so that may be involved or implicated somehow. However it reminds strongly of "@auto re-asserts over @file" (https://github.com/leo-editor/leo-editor/issues/580) als

Re: puzzled by valuespace plugin

On Thu, Mar 22, 2018 at 6:08 AM, Edward K. Ream <edream...@gmail.com> wrote: > > >> The valuespace plugin really really really needs to be split in two. >> > > ​Please create a Leo issue, with implementation details. > ​Never mind. I have just created #839:Spl

Re: Nodetags plugin errors

On Sun, Mar 25, 2018 at 4:40 PM, Largo84 wrote: > I can't located that commit. It doesn't show up in master. > ​That's because it's in the devel branch. ​ > Is this related to issue #526 > ? > ​I don't know. Perhaps

Re: Nodetags plugin errors

I can't locate that commit. It doesn't show up in master. Could this be related to issue #526 ? Rob... On Saturday, March 24, 2018 at 2:35:56 AM UTC-4, Edward K. Ream wrote: > > > > On Fri, Mar 23, 2018 at 2:13 PM, Largo84

Re: Nodetags plugin errors

I can't located that commit. It doesn't show up in master. Is this related to issue #526 ? Rob... On Saturday, March 24, 2018 at 2:35:56 AM UTC-4, Edward K. Ream wrote: > > > > On Fri, Mar 23, 2018 at 2:13 PM, Largo84 >

Re: Nodetags plugin errors

I'm only pulling from the master branch and the last commit was March 3, 6c2eef2. Where is that rev? Rob... On Saturday, March 24, 2018 at 2:35:56 AM UTC-4, Edward K. Ream wrote: > > > > On Fri, Mar 23, 2018 at 2:13 PM, Largo84 > wrote: > >> Now, I'm also getting a slightly

Re: Nodetags plugin errors

On Fri, Mar 23, 2018 at 2:13 PM, Largo84 wrote: > Now, I'm also getting a slightly different error in other files when I > copy/paste nodes. > ​Rev​ 1f40d97 adds a guard. How does that work for you? Edward -- You received this message because you are subscribed to the

Re: Nodetags plugin errors

Now, I'm also getting a slightly different error in other files when I copy/paste nodes. hook failed: command2, >, leo.plugins.nodetags Traceback (most recent call last): File "D:\Synced\github repos\leo\leo\core\leoPlugins.py", line 342, in callTagHandler result = handler(tag,

Re: Nodetags plugin errors

Chris On Friday, March 23, 2018 at 9:31:23 AM UTC-7, Largo84 wrote: > > Getting the following errors when re-opening a file with nodes tagged > using the nodetags plugin: > > > hook failed: after-create-leo-frame, , > leo.plugins.nodetags > Traceback (most recent cal

Nodetags plugin errors

Getting the following errors when re-opening a file with nodes tagged using the nodetags plugin: hook failed: after-create-leo-frame, , leo.plugins.nodetags Traceback (most recent call last): File "D:\Synced\github repos\leo\leo\core\leoPlugins.py", line 342, in callTagHandler

Re: puzzled by valuespace plugin

On Wed, Mar 21, 2018 at 10:01 PM, Terry Brown <terrynbr...@gmail.com> wrote: > The valuespace plugin really really really needs to be split in two. > ​Please create a Leo issue, with implementation details. Edward -- You received this message because you are subscribed to the G

puzzled by valuespace plugin

Today I started Leo to a Leo Tip (I like those!) suggesting use of the valuespace plugin. Ok, I'm game. I load it up, and. I am completely clueless as to what this is good for. I have read the documentation, looked for help in this list, and I just don't get it. I'm assuming that it made

Re: Bookmarks plugin - crashes loading layout

On Thu, Mar 15, 2018 at 6:29 AM, lewis wrote: > Yes, I was able to reload my saved bookmark layouts. Nothing lost. > ​Whew! So glad to hear it. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: Bookmarks plugin - crashes loading layout

On Thu, 15 Mar 2018 01:30:39 -0700 (PDT) "Edward K. Ream" wrote: > Are you able to recover your bookmarks? Selecting the top node of the bookmarks subtree and executing `bookmarks-show` should suffice (possibly opening a second bookmarks pane, but that's a one time thing).

Re: Bookmarks plugin - crashes loading layout

Yes, I was able to reload my saved bookmark layouts. Nothing lost. Thanks Lewis -- 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: Bookmarks plugin - crashes loading layout

On Thursday, March 15, 2018 at 2:36:15 AM UTC-5, Edward K. Ream wrote: > I have just created #812: g.glob_glob may have broken bookmarks/urls/unls on Windows

Re: Bookmarks plugin - crashes loading layout

On Thu, Mar 15, 2018 at 12:25 AM, lewis <lewisn...@operamail.com> wrote: > After a recent commit 8ab89ca6f5a1, my bookmarks failed to display. > ​Drat. This rev replaces glob.glob with g.glob_glob. However, there are no direct calls to glob in the bookmarks plugin. ​ > I rig

Re: New plugin line_numbering

ey have the same function but @nosent > is considered a bit archaic. > Fixed at ccf76ca26c268a0ff > On Sunday, January 28, 2018 at 10:49:43 PM UTC+1, John Hutchinson wrote: >> >> Hi: >> >> I'm running the latest Leo from Git. I just enabled this plugin. With >

Re: New plugin line_numbering

Try `@clean` instead of `@nosent`, they have the same function but @nosent is considered a bit archaic. Fixed at ccf76ca26c268a0ff On Sunday, January 28, 2018 at 10:49:43 PM UTC+1, John Hutchinson wrote: > > Hi: > > I'm running the latest Leo from Git. I just enabled this plugin. Wit

Re: New plugin line_numbering

Hi: I'm running the latest Leo from Git. I just enabled this plugin. With "nosent" files (at least, since that's mostly what I use), there seems to be an "off-by-a-few" error in the displayed numbers. My outline is: @nosent foo.py @others (in body of @nosent node) Imp

Re: d0c4a8e: Simpler way to use the demo.py plugin

On Sunday, January 28, 2018 at 5:37:01 AM UTC-6, Edward K. Ream wrote: *Summary* > > The new pattern is an important simplification for non-interactive > scripts. Such scripts will wait for predetermined times between "slides". > > The old pattern is more flexible for interactive demos. It

d0c4a8e: Simpler way to use the demo.py plugin

In a roundabout way I was inspired by the 3Blue1Brown YouTube channel. It uses the manim library to do animations. But the real reason for the Aha was that I had forgotten how to use demo.py.

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