Re: Missing buttons on Find Tab

Ok, I found a way to use the find-all by using the command. It's a bit convoluted, because the settings (searching head or body) are reset every time. I am quite sure there used to be buttons, which made usage a bit smoother. On Thursday, February 24, 2022 at 6:30:03 PM UTC+1 tbp1...@gmail.com

Re: To Plugin or Not?

Thanks for your thoughts. @jake. This app too will only make sense within the specific outline it's for. I thought it might be interesting to some other folks, otherwise I wouldn't even have considered turning it into a plugin. On Thursday, February 24, 2022 at 1:28:23 PM UTC-5

Re: To Plugin or Not?

I have similar 'apps' that live inside Leo outlines, as scripts but not plugins. At least one of them is well over 3000 lines of code :) I think the main question to ask is whether the 'app' makes any sense outside the context of the outline it lives in. In my case, the ones I've built really

To Plugin or Not?

I am developing an Leo application that displays in a tab in the Log frame. Eventually it will probably use two tabs. The code lives in a new subdirectory in Leo's plugins directory. Currently this code is not a real Leo plugin, because it does not use the plugin machinery. Instead, it

Re: Missing buttons on Find Tab

There haven't been buttons there for a long time, as best I know. I've never seen one for "find-all". The others have keystrokes, shown on the panel. They are all commands that can be dispatched in the minibuffer. On Thursday, February 24, 2022 at 12:04:14 PM UTC-5 Josef wrote: > is it

Missing buttons on Find Tab

is it just me or did the buttons really disappear from the Find tab? There used to be a time when I had buttons for "find-next", "find-prev", "find-all" etc on the find tab, but for some time now (several months at least), I see only text indicating the keystrokes to use, like "F3" for

Re: Leo's python development is nearing its end

Does that mean I will have to learn TypeScript to write little Leo extensions in the future? On Friday, February 18, 2022 at 5:41:36 PM UTC+1 Edward K. Ream wrote: > Leo 6.6 may be the last substantial release in Leo's history. At present, > the 6.6 to-do list >

Re: The joys of coming back to Leo

This is all very interesting. One of the first programming language I worked with (after some Focal, Basic and a bit of PDP-8 asm), a long time ago, was Forth. Forth's commands are all defined in Forth except for a few primitives and the little Forth VM, including conditionals and loops. You

Re: The joys of coming back to Leo

Hi Edward, I don't know abut pylivecoding until now, but I can tell you that  its author was a pretty active member of the Pharo community and made some introductory tutorials to it and projects bridging Pharo, Blender and Python[1], so I can see the traces of a Smalltalk inspired live coding

Re: The joys of coming back to Leo

On Wednesday, February 23, 2022 at 12:42:02 PM UTC-6 Edward K. Ream wrote: >> what would it take to add live coding and better self-referential features to python? > pylivecoding is one answer. I am going to take a look. pylivecoding uses reload, which