Re: What's next, continued

On Tuesday, March 24, 2020 at 2:12:39 AM UTC-4, Edward K. Ream wrote: > > On Mon, Mar 23, 2020 at 7:56 PM Thomas Passin > wrote: > > > Here's a simple Bokeh program that VR3 executes: [snip] > > Thanks for this. Looks like holoviews/bokeh are just what we need. > I've been looking at them a

Re: Dark theme

On Fri, Mar 20, 2020 at 1:26 PM Ville M. Vainio wrote: > I have forgotten how to enable dark theme in Leo :). > > Googling brings up the FAQ: > https://leoeditor.com/FAQ.html#how-can-i-use-a-dark-theme-in-leo > > ...but it's horribly technical. Time to improve the FAQ or the enabling > process?

Re: ENB: Improving popup menus

On Tuesday, March 24, 2020 at 10:11:30 AM UTC-5, Edward K. Ream wrote: The configuredcommands_rclick function in contextmenu.py does not work as > is with cut/copy/paste-text. These commands require an event arg which the > callback must create. The necessary change should be safe enough, but

Re: ENB: Improving popup menus

Deleting the two lines in leo/plugins/qt_text.py in the LeoQTextBrowser.__init__ method: self.setContextMenuPolicy(QtCore.Qt.CustomContextMenu) self.customContextMenuRequested.connect(self.onContextMenu) Will revert to the old style. Context menu in the body would have standard commands like

Re: ENB: Improving popup menus

On Tuesday, March 24, 2020 at 8:14:37 AM UTC-5, Edward K. Ream wrote: For 6.2, I *will *add items to @data contextmenu-commands in > leoSettings.leo. These items will create cut/copy/paste/select-all *text* > items popup menus. These items will be added in the 6.2 branch, and merged > into

ENB: Improving popup menus

This is #1531 , which arises from a less-than-perfect fix for #1286 . This post describes the details and choices. But first, a summary of my plans... *Plans* It's too late to complete

Re: Dark theme

> Thanks for the wishes, we are doing fine. Schools in .fi are closed so > "home schooling" my sons, and working from home > Yep, same here. FWIW, I found this podcast on remote work from CBC Spark especially apropos

Re: On packaging Leo plugins

> > > Does anyone have thoughts on the topic? > > Imo, there is no need to make plugins separate projects. That would be > lots of work for you, and others, and imo would offer no benefits to > anyone. It usually makes no sense to have a Leo plugin packaged separately. > Thanks for your

Re: A better way to send code to language processors

Well, yes, in my response I avoided more complicated possibilities. And I wrote about Viewrendered3 because I recently completed this plugin (really a beta version). VR3, an extension of the Viewrendered plugin, aims to render various node types, such as Markdown and Restructured Text. As a

Re: A better way to send code to language processors

Am Dienstag, 24. März 2020 01:32:29 UTC+1 schrieb Thomas Passin: I often use mixtures of code and non-code blocks. If there are different > kinds of code blocks, though, there can be problems if you want to execute > them. If you execute each code block with a different language processor,

Re: What's next, continued

On Mon, Mar 23, 2020 at 7:56 PM Thomas Passin wrote: > Here's a simple Bokeh program that VR3 executes: [snip] Thanks for this. Looks like holoviews/bokeh are just what we need. I'll be studying them both. Edward -- You received this message because you are subscribed to the Google Groups