Re: Progress report: embedding neovim in Leo

While this may be important towards the physical integration of the Qt pane that will be the gui frontend for the Neovim core, this doesn't need to be finished to start working on the "plumbing" that will need set up between Leo and the neovim core, e.g., nvim.exe. The "plumbing" is msgpack

Re: Scoop, a new way to install?

I should mention that what I have used scoop for so far, is to install ripgrep, and Neovim. As a plus, it looks like scoop will let you known if an app has a newer version available. Tom -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: Updates to LeoVue

On Sat, Oct 13, 2018 at 3:26 PM Joe Orr wrote: > Facelift for LeoVue and some new features. More screenshots so should > better convey the advantages. > > https://kaleguy.github.io/leovue > Many thanks for all this. I've just added a link to LeoVue to Leo's wikipedia page

Re: Request - mode to open Leo files read-only

On Saturday, October 13, 2018 at 12:39:37 PM UTC+1, Edward K. Ream wrote: > > > > On Sat, Oct 13, 2018 at 6:24 AM jkn > > wrote: > > Occasionally I would like to protect myself from changing any files within >> Leo. Would it be possible to have a command-line option for all files to be >>

Updates to LeoVue

Facelift for LeoVue and some new features. More screenshots so should better convey the advantages. https://kaleguy.github.io/leovue * @cover for cover page * Added bootstrap-vue, so bunch of new components, like carousel * Fixes to improve wiki operation * Fixes to improve JSON feed + template

Scoop, a new way to install?

Having to set up a new laptop to work with Leo and follow some of the current lines of development, I came across a new command line installer for Windows, scoop. It is written in Powershell and to install a particular app scoop can run off a json file in the git repo. Currently, I clone

Re: Progress report: embedding neovim in Leo

On Sat, Oct 13, 2018 at 8:40 AM Edward K. Ream wrote: The leo-editor-contrib branch now contains neovim.leo, a study outline for > the python-client code . > The C++ sources for the stand-alone neovim-qt app are here

Progress report: embedding neovim in Leo

The leo-editor-contrib branch now contains neovim.leo, a study outline for the python-client code . This is elegant code, surely the simplest code that could possibly work. The use of functools.partial

Re: Simplifying Leo's undo logic

On Saturday, October 13, 2018 at 7:30:24 AM UTC-5, Edward K. Ream wrote: Vitalije's recent discussions of functional programming has indirectly lead > me to a tentative plan to simplify Leo's undo logic. > I made more than the usual number of typos in the original post. They have been

Re: Dreaming big dreams

On Sat, Oct 13, 2018 at 8:00 AM Terry Brown wrote: > Hmm. This suggests creating unl's linking code to their tests. > > You don't really even need an UNL, if you have a convention a button > can work out whether you're looking at the test or the code, and switch > between them, see >

Re: Dreaming big dreams

On Sat, 13 Oct 2018 06:06:29 -0500 "Edward K. Ream" wrote: > > .../foo/test/test_my_module.py->test_my_func() > > > Thanks for this.  So for every @file x.py, we would create an @file > test/x.py. It's a reasonable solution. > > Leo makes the idea of "near" meaningless, there's plenty of ways

Simplifying Leo's undo logic

Vitalije's recent discussions of functional programming has indirectly lead me to a tentative plan to simplify Leo's undo logic. *A thought experiment* Suppose Leo outlines behaved kinda like Python strings. You never actually change a Python string, you only compose new strings. Of course,

Re: my 2 cents to embedding Leo into other editor or vice versa

On Sat, Oct 13, 2018 at 5:51 AM vitalije wrote: > Heh. I just realized that Vitalije's post was first made in February, not >> yesterday, > > > I was also surprised to see new topic and "me" as author of it. For a > moment I thought it was some bug in google. :-) > Hehe. I thought exactly

Re: Request - mode to open Leo files read-only

On Sat, Oct 13, 2018 at 6:24 AM jkn wrote: Occasionally I would like to protect myself from changing any files within > Leo. Would it be possible to have a command-line option for all files to be > open read-only? > I think so. --read-only would disable the save-* commands. I've just created

Re: Unit Testing Nodes

On Sat, Oct 13, 2018 at 1:49 AM vitalije wrote: > I usually make clone of the whole content of a module being tested as a > first child of a @test node, and put there in the @test node @others > directive at the top of body. After @others I write code that tests some > function from the module.

Request - mode to open Leo files read-only

Hi Edward a small suggestion/request. Occasionally I would like to protect myself from changing any files within Leo. Would it be possible to have a command-line option for all files to be open read-only? Thanks Jon N -- You received this message because you are subscribed to the

Re: Unit Testing Nodes

On Fri, Oct 12, 2018 at 5:23 PM MN wrote: For the examples you gave (and your other comments in the group), it seems > like I cannot put the unit test in its own node (even as a sibling)? > I'm not sure I understand what you mean, but it's not wise to put @test nodes as children of @file, @auto

Re: Dreaming big dreams

On Fri, Oct 12, 2018 at 11:59 PM Matt Wilkie wrote: Newbies only need to know how to search outlines, and which outlines to >> search, especially LeoDocs.leo, leoSettings.leo and CheatSheet.leo. >> Really, how hard is it to scan the top-level nodes in leoSettings.leo? >> > > I think this speaks

Re: Dreaming big dreams

On Thu, Oct 11, 2018 at 4:37 PM MN wrote: How do I know which commands I write are automatically undoable and which >> ones are not? My script to alter commenting behavior seems undoable without >> my putting any effort into making it so. >> > I would have to see your script to know whether, and

Re: Dreaming big dreams

On Thu, Oct 11, 2018 at 2:19 PM Terry Brown wrote: > - Why can't we put unit tests near the code being tested? > > I'd argue (for Python) for using the best in class unit testing > framework's practice. pytest puts tests for > > .../foo/my_module.py->my_func() > > in > >

Re: my 2 cents to embedding Leo into other editor or vice versa

> > Heh. I just realized that Vitalije's post was first made in February, not > yesterday, I was also surprised to see new topic and "me" as author of it. For a moment I thought it was some bug in google. :-) Vitalije -- You received this message because you are subscribed to the Google

Re: Dreaming big dreams

On Thu, Oct 11, 2018 at 1:19 PM Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > I think that converting Leo to other languages makes little sense from a > practical point, but exploring Leo ideas in other environments makes a lot > of sense (and viceversa). > I agree. > What I would

Re: my 2 cents to embedding Leo into other editor or vice versa

On Saturday, October 13, 2018 at 5:17:45 AM UTC-5, Edward K. Ream wrote: > > On Wed, Feb 21, 2018 at 2:42 AM vitalije wrote: > > Last summer I had this idea of using another open source editor and adding >> features unique to Leo. I did considered several editors implemented in >> browser or

Re: my 2 cents to embedding Leo into other editor or vice versa

On Wed, Feb 21, 2018 at 2:42 AM vitalije wrote: Last summer I had this idea of using another open source editor and adding > features unique to Leo. I did considered several editors implemented in > browser or browser-like environment. That includes Atom, but also > LightTable, NightCode, and

Re: Three dimensional graphs

On Fri, Oct 12, 2018 at 11:27 AM Terry Brown wrote: > Funny you should bring up a third dimension, I've been experimenting > with something along these lines, although not within Leo :-/ No > doubt inspired by various discussions on this list (sea of nodes, > colored threads, Kent's mysterious

Re: Unit Testing Nodes

I usually make clone of the whole content of a module being tested as a first child of a @test node, and put there in the @test node @others directive at the top of body. After @others I write code that tests some function from the module. Quite often I start developing a module without