(yet again) New features on the dev branch!

Hello to all Leonistas of the earth :) Bunch'of new features to try to stress test :) ... frankly just gonna have to name the 0.1.13 release the 'ArJan' release ! - Ar'Jans's suggestion of Leo's style of keyboard navigation when focus is on tree/body is now *DEFAULT* option. it brings full imme

Re: Should devel be the default branch?

On Saturday, July 11, 2020 at 4:40:56 PM UTC-5, Edward K. Ream wrote: > I think the default branch really should be "devel", but I want to check with you all first. Thanks for all your comments. I'll leave things as they are, with "master" being the default branch. Edward -- You received thi

Re: leoInteg: my top two wish-list items

On Sat, Jul 11, 2020 at 5:08 PM Félix wrote: > Funny - I was thinking about asking you, and others, about that subject > of: minimal *important* features list! > Glad my list helped. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To un

Re: Should devel be the default branch?

On Sat, Jul 11, 2020 at 5:01 PM Félix wrote: > Here's how most projects workflow are generally setup: > > My understanding is that people branch from a development 'head', > generally not master, as the master branch is reserved for stable and > verified commits that as a whole make a bundle to b

Re: Should devel be the default branch?

I concur, and to recap, precisely, I gotta say that being on a stable 'master' branch after getting a repo with cloning is the norm. And that having to switch branch to be running a 'development' or "insider's" version is also common - which is also the branch from which to branch again out of,

Re: Should devel be the default branch?

On Saturday, July 11, 2020 at 6:13:03 PM UTC-4, Félix wrote: > > Oh - But of course, when git cloning the project master should be default, > not devel. > I agree - BUT with a caveat. The usual advice is to clone the repo if we want to use the latest development version. To that should be

Re: 23:15 video, "A Tour of Acme (2012)" by Russ Cox

Thanks for this Matt detailed recap (I'm seeing the video right now and mark the paper as pending). Seems pretty interesting, as I have a soft spot for digital artifacts archeology. Pharo/Smalltalk has been making any selected text executable since 70's. Also the idea of maximazed windows/panes in

Re: Should devel be the default branch?

Oh - But of course, when git cloning the project master should be default, not devel. (didnt even answer the question) On Saturday, July 11, 2020 at 6:01:52 PM UTC-4, Félix wrote: > > Here's how most projects workflow are generally setup: > > My understanding is that people branch from a devel

Re: leoInteg: my top two wish-list items

Funny - I was thinking about asking you, and others, about that subject of: minimal *important* features list! I was hoping to get a minimal list of 'killer features' from experienced Leo users, as people don't use the same features and workflow at all, i'm very curious to hear what people see

Re: Should devel be the default branch?

Here's how most projects workflow are generally setup: My understanding is that people branch from a development 'head', generally not master, as the master branch is reserved for stable and verified commits that as a whole make a bundle to be published. Then, they ultimately finish their comm

Should devel be the default branch?

On Saturday, July 11, 2020 at 3:52:46 PM UTC-5, Edward K. Ream wrote: I just received and rejected PR #1615 > . This PR was to be > applied to 6.0-final-rel. That's not how things work. We don't change > official releases for any reason. > Th

leoInteg: my top two wish-list items

leoInteg looks like close to being ready for prime time. I will consider using leoInteg for real work when: 1. Syntax coloring works for python and typescript. Support for multiple @language directives in a single node can wait. 2. leoInteg makes it easy to restart a session. There are at least

Re: learning about @buttons

On Sat, Jul 11, 2020 at 11:33 AM Félix wrote: > Edward, I need more time and better comprehension of Leo's code in order > to answer you question about a vscode gui. The way I see it, nullgui is > perfectly fine. > > Also, on a similar topic, leobridgeserver is meant to be agnostic and > reused b

Re: learning about @buttons

On Saturday, July 11, 2020 at 12:19:12 PM UTC-5, Félix wrote: To shed some light on my implementation, here are the few lines it took on > the leo/python side of things: > > def getButtons(self, p_package): > '''Gets the currently opened file's @buttons list''' > w_buttons = [] > w_dict = self.c

Please don't issue PR's against official releases.

I just received and rejected PR #1615 . This PR was to be applied to 6.0-final-rel. That's not how things work. We don't change official releases for any reason. This PR came out of the blue. It contained 2,581 commits and would have changed

Re: How to type Félix on Windows :-)

On Saturday, July 11, 2020 at 6:22:36 AM UTC-4, Edward K. Ream wrote: > > On Sat, Jul 11, 2020 at 5:06 AM jkn > > wrote: > > QQQ > Hi Edward >Wow ... this goes back to ... Windows 3.0, maybe earlier? It was the > 'only known use' of the Grey Alt key for me back then. > There used to be a ta

Re: learning about @buttons

On Saturday, July 11, 2020 at 2:03:48 AM UTC-4, Félix wrote: > > I'm just learning about those @buttons by reading the mod_scripting > 'readme' and trying to bring'em into leoInteg : > > ... > I'm also reading about the @button having to be in a setting file or a > @setting node ? but that woul

Re: Discuss: compare zettlekasten, bookmarks, google

On Friday, July 10, 2020 at 11:00:51 AM UTC-4, Edward K. Ream wrote: > > On Thu, Jul 9, 2020 at 1:01 PM Thomas Passin > wrote: > > Are any links/categories stable over time? I'm constantly adding/deleting > bookmarks. That doesn't bother me much. > Probably not, and I've put some effort into m

Re: How to type Félix on Windows :-)

On Saturday, July 11, 2020 at 11:22:36 AM UTC+1, Edward K. Ream wrote: > > On Sat, Jul 11, 2020 at 5:06 AM jkn > > wrote: > > QQQ > Hi Edward >Wow ... this goes back to ... Windows 3.0, maybe earlier? It was the > 'only known use' of the Grey Alt key for me back then. > There used to be a t

Re: learning about @buttons

Edward, To shed some light on my implementation, here are the few lines it took on the leo/python side of things: def getButtons(self, p_package): '''Gets the currently opened file's @buttons list''' w_buttons = [] w_dict = self.commander.theScriptingController.buttonsDict for w_key in w_dict:

Re: learning about @buttons

Edward, I need more time and better comprehension of Leo's code in order to answer you question about a vscode gui. The way I see it, nullgui is perfectly fine. Also, on a similar topic, leobridgeserver is meant to be agnostic and reused by anyone who wants to 'talk' to, or control leo via htt

Re: learning about @buttons

On Saturday, July 11, 2020 at 3:01:22 AM UTC-5, Félix wrote: > I Made @buttons a reality, merged it on the 'dev' branch, you guys tell me if it works for you. Yes, it works. gitk shows you did a *lot* of work. How much of leo/plugins/mod_scripting.py did you use? Any of it? If possible, I wou

Re: 23:15 video, "A Tour of Acme (2012)" by Russ Cox

On Saturday, July 11, 2020 at 5:53:18 AM UTC-5, Edward K. Ream wrote: Heh. There is an Acmeish plugin for vs code > , so > perhaps we can say this discussion is moot. > There are also *many *live-coding plugins for vs code: - Live

Re: 23:15 video, "A Tour of Acme (2012)" by Russ Cox

On Saturday, July 11, 2020 at 5:13:17 AM UTC-5, Edward K. Ream wrote: vs code shows the power of *millions* of people contributing to a > customizable code base. Imo, we can assume that any useful trick found in > acme will already have found its way into vs code. > Heh. There is an Acmeish plu

Re: learning about @buttons

On Sat, Jul 11, 2020 at 1:03 AM Félix wrote: > if I understand correctly, you cannot just name any random node anywhere in an outline "@button hello" and expect to see a "hello" button appear in the top button bar upon saving, like you would expect a file to be generated, were you to name any nod

Re: How to type Félix on Windows :-)

On Sat, Jul 11, 2020 at 5:06 AM jkn wrote: QQQ Hi Edward Wow ... this goes back to ... Windows 3.0, maybe earlier? It was the 'only known use' of the Grey Alt key for me back then. There used to be a table in the original IBM PC manual (small hardback ring binder affair with clip in pages) wit

Re: 23:15 video, "A Tour of Acme (2012)" by Russ Cox

On Friday, July 10, 2020 at 9:56:33 AM UTC-5, Edward K. Ream wrote: >> https://research.swtch.com/acme > I may have missed something truly interesting in this video. If so, please tell me exactly what it is. To answer my own question, there is a lot *less *to acme than meets the eye, as I shal

Re: How to type Félix on Windows :-)

On Saturday, July 11, 2020 at 10:38:30 AM UTC+1, Edward K. Ream wrote: > > I finally though to google "windows how to type accent character". > Explained here : > > - Ensure Num lock is on. > - Hold down Alt key. > - Type 0233 in numeric keypad

How to type Félix on Windows :-)

I finally though to google "windows how to type accent character". Explained here : - Ensure Num lock is on. - Hold down Alt key. - Type 0233 in numeric keypad. é will appear when you release the Alt key. Who knew :-) This is way faster than u

Re: Install and use Leointeg with Anaconda python

> > Leointeg's Python Command configuration set to python and Running the > extension with the Server and Extension option are mutually exclusive: I > have not explained those concepts clearly - and as I wanted to give more > options for tester than less, it seems people are mix and matching th

Re: learning about @buttons

f*ck it, :) didnt wait for an anwser hehe: I Made @buttons a reality, merged it on the 'dev' branch, you guys tell me if it works for you. (log pane has a small delay in its refresh its normal) G'night ! -- Félix p.s. I may add more icons/eye candy to the buttons later when cleaning up for a