Re: Updates to LeoVue

> >- clicking on "Feature Introduction" and "Chunking" items in ToC >starts a download of the .md file for that node. The other items seem to > be >okay > > That's weird, does it on FF in Mac too. But the page does display after you get rid of the download dialog. I'll look into

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?

Heads up: I've just had this weird situation where I noticed the @file contents were definitely NOT the most recent version of the file. There were several sections of old content in nodes I know I'd changed over the last few days. I used "refresh from disk", after which the I saw the new

Re: Scoop, a new way to install?

> > I am going to stick with conda install and pip install. That way I use > the more typical installation methods. > > Perhaps Matt will be interested in scoop for his work. > Thanks! I will check it out. So far I've investigated Chocolatey, Just-install.it, Ninite, and a number of others

Re: Updates to LeoVue

> > Facelift for LeoVue and some new features. More screenshots so should > better convey the advantages. Yay! Quick comments (I'm using firefox on windows): - clicking on "Feature Introduction" and "Chunking" items in ToC starts a download of the .md file for that node. The other

Re: FYI: I'll be removing leo/external/rope

> Rev ea79240bb changes leoRope.py so that it fails gracefully if rope does > not exist. Rev f5a3ef694 deletes the rope folder. All tests pass. > But somehow this breaks TravisCI. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: Supporting pytest

On Sunday, October 14, 2018 at 5:52:08 AM UTC-5, Edward K. Ream wrote: #994 suggests running > pytest from unitTest.leo. > Rev 3dab6d161 is a good start. It defines `@test run pytests` in unitTest.py. This script runs a new file,

Re: Supporting pytest

On Sunday, October 14, 2018 at 6:27:16 AM UTC-5, Edward K. Ream wrote: I'll be searching the docs for guidance. > Found it here . There could still be complications. We'll see. *Important*: not all the unit tests

Re: Supporting pytest

On Sunday, October 14, 2018 at 5:52:08 AM UTC-5, Edward K. Ream wrote: > > #994 suggests > running pytest from unitTest.leo. > > Running pytest from the command line (from the leo-editor folder) "just > works". So the major remaining task is

Re: FYI: I'll be removing leo/external/rope

On Sunday, October 14, 2018 at 5:55:35 AM UTC-5, Edward K. Ream wrote: Unless I hear howls of protest, tomorrow I'll remove the entire > leo/external/rope folder, and all its sub-folders. > On second thought, I'm not going to wait for protests. rope exists in the Anaconda distro, so

FYI: I'll be removing leo/external/rope

Unless I hear howls of protest, tomorrow I'll remove the entire leo/external/rope folder, and all its sub-folders. leoRope.py uses rope, but it should not default to ancient rope code. Instead, it should fail gracefully if rope can not be imported. Edward -- You received this message

Supporting pytest

#994 suggests running pytest from unitTest.leo. Running pytest from the command line (from the leo-editor folder) "just works". So the major remaining task is to run pytest from inside unitTest.leo. That should be straightforward,

Re: Scoop, a new way to install?

On Sat, Oct 13, 2018 at 7:51 PM 'tfer' via leo-editor < leo-editor@googlegroups.com> wrote: > 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. > I am

Re: Progress report: embedding neovim in Leo

On Sat, Oct 13, 2018 at 9:58 PM 'tfer' via leo-editor < leo-editor@googlegroups.com> wrote: 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