Leo for VSCode: LeoInteg beta 0.1.16 released

[Félix]

Hello to all of you in the Leonine world! 

I'm glad to announce that leointeg (Leo for VSCode) is now at the 'beta' stage, offered as an '.vsix' extension  file, where most features are present -- but in dire need of some user testing to finalize and polish before an 1.0 launch on the official vscode/microsoft store!

No more annoying development version installation fuss!

Way more easy to install and run! Just download the extension here, and in vscode, do the 'install from VSIX' command from the command palette. 

Known Issues

So far, I've noticed that when newly installed and used for the first time, I have to restart vscode for Leo's file-change detection features to work properly. 

Thanks for testing and reporting issues and bugs! 

Please download and tryout leointeg to help bring a real '1.0' version by helping finding bugs, or how to reproduce possible bugs by reporting your thoughts here: https://github.com/boltex/leointeg/issues

Make sure you're somewhat familiar with VSCode first!

Editing and debug a project in your favorite language with vscode first if you're not already familiar with this IDE. Begin by watching a couple of videos here, 

and follow through with your preferred language example tutorial:

- Python

- Javascript/Typescript 

- Java

- C/C++

So again: 

THANK YOU FOR TRYING OUT LEOINTEG !

--

Félix

[Edward K. Ream]

On Sun, Jul 18, 2021 at 6:50 PM Félix <felix...@gmail.com> wrote:

I'm glad to announce that leointeg (Leo for VSCode) is now at the 'beta' stage, offered as an '.vsix' extension  file, where most features are present -- but in dire need of some user testing to finalize and polish before an 1.0 launch on the official vscode/microsoft store!

Congratulations! Just so everyone knows, you have been working on leoInteg for over two years. Imo, leoInteg is a huge opportunity to spread the Leonine word :-)

I'll start testing leoInteg today and will report my experiences here.

Edward

[Félix]

Thanks!

Now that i'm using leointeg instead of 'plain Leo', the only major thing i've noticed (so far) is what i talked about in the post above. (changed file detection sometimes doesn't trigger) but it's not random. It either works all the time or not at all. Also, in the instances where leointeg is started and the opened leo file does not detect file changes, simply going to the leointeg settings and changing them (to anything) fixes it. So that tells me that the settings are simply not applied sometimes upon startup/first file-opening ... and i perhaps just broke the EFC it when i refactored everything from leobridgeserver to leoserver and/or when i converted my SEFC to a subclass of EFC. 

It's probably just that i don't set / start the EFC detection loop to start until after certain conditions. (for example , closing all leo files in leointeg where the EFC worked, and then reopening one, breaks it.)

So I'll revise the startup procedures of leointeg itself when connectiong to a server - and/or when opening /closing files, to make sure that the EFC is started properly when appropriate.

Please do report if you can pinpoint how to reproduce, or just confirm what i vaguely stated above about  how to fix / stop / start the EFC file-change detection. :)

(knowing how to reproduce or precisely trigger a bug is 99% of the solution!)

--

Félix

[Félix]

Another thing I just noticed - Not a bug, just an annoyance - The 'recent files' that get re-opened automatically when starting up a vscode window should be saved PER WORKSPACE, not PER USER/GLOBAL. 

That would be different than Leo's behavior, but would make a lot more sense when opening a 'project' folder in VSCODE and having only the related Leo files automatically open, per specific project-folder. (hope this makes sense for people not used to working with VSCODE on a workspace context when opening a folder/workspace with vscode.)

[Edward K. Ream]

On Sunday, July 18, 2021 at 6:50:50 PM UTC-5 Félix wrote:

leointeg (Leo for VSCode) is now at the 'beta' stage, offered as an '.vsix' extension  file, where most features are present -- but in dire need of some user testing to finalize and polish before an 1.0 launch on the official vscode/microsoft store!

I have filed some leoInteg issues for several nits, but I don't want to focus only on what doesn't work :-)

Almost everything works smoothly!! leoInteg is a superb feat of engineering!!!

Edward

[Robert-Felix]

Thanks!! 

I'll answer / resolve a couple more tomorrow :) I'm quite ecstatic about the rollout which went pretty ok so far! Thanks for your counsel and support!!

The major real bugs feel like they will be manageable and fixable as I seem to be able to reproduce them, and provoke them, (or disable them by setting options in the settings panel,.)

Also, the other 'smaller' bugs and issues are VSCode related! (meaning i've only got to point to precise documentation to answer the question, or, wait 'till microsoft fixes a particular bug that's not caused by leointeg. :) heh!!

In a week or two we'll have an acceptably 'stable' 1.0 version to release to the world!! This feels like a dream! (although I'm on the side-effects of the 2nd shot of the vaccine I got yesterday - which hit me pretty hard today - and I smoked a couple joints... So everything feels like a dream about now) 😛 

--

Félix

--
You received this message because you are subscribed to a topic in the Google Groups "leo-editor" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/leo-editor/zuAKJ3lozFI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to leo-editor+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/092d1a27-0740-426a-82a0-91e9ee93fac6n%40googlegroups.com.

[Edward K. Ream]

On Mon, Jul 19, 2021 at 10:27 PM Robert-Felix <felix...@gmail.com> wrote:

In a week or two we'll have an acceptably 'stable' 1.0 version to release to the world!! This feels like a dream! (although I'm on the side-effects of the 2nd shot of the vaccine I got yesterday - which hit me pretty hard today - and I smoked a couple joints... So everything feels like a dream about now) 😛 

Bwahahaha.

Edward

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Montag, 19. Juli 2021 um 01:50:50 UTC+2:

Hello to all of you in the Leonine world! 

I'm glad to announce that leointeg (Leo for VSCode) is now at the 'beta' stage, offered as an '.vsix' extension  file, where most features are present -- but in dire need of some user testing to finalize and polish before an 1.0 launch on the official vscode/microsoft store!

A quick feedback from my side, that I was able to install 'Leo for VSCode' in a VM running Fedora 33 on top of Qube-OS R4.0 following your instructions w/o any issues.

I need to schedule time now on my side to get more familiar with your extension - as well as - VSCode in general.

Thanks a lot for this great work !

With kind regards,

Viktor

[Alexey Tikhonov]

Hi all!

Great job, Felix!

I installed the VSIX package in VSCode on Windows without problems and it run well except for the 'cffm' command. The log pane says:

server:  ServerError: _do_leo_command: Leo command not found: 'cloneFindAllFlattenedMarked'...

Did somebody get the same error?

Alexey

[Edward K. Ream]

On Wed, Jul 21, 2021 at 1:30 AM Alexey Tikhonov <tickli...@gmail.com> wrote:

I installed the VSIX package in VSCode on Windows without problems and it run well except for the 'cffm' command. The log pane says:

server:  ServerError: _do_leo_command: Leo command not found: 'cloneFindAllFlattenedMarked'...

Thanks for testing! Yes, I see this error.

I have just created Leo issue #2091 for this and assigned it to Félix and myself.

Edward

[Félix]

I just wanna say a special thanks to Thomas, Viktor and  Alexey for reporting their experiences and issues with trying out leointeg!

Things are moving forward with resolving those issues and a "stable" 1.0 version will be a reality in a major part because of you! :) 

--

Félix

[Alexey Tikhonov]

Hello again!

I use Leo to work with Fortran sources. Sometimes, I create an empty node '@clean <path to file>.f90', run 'refresh-from-disk' to make Leo load the file's content and finally, I manually restructure the file content in the Leonine way. In LeoInteg 'refresh-from-disk' seems not to work for this scenario. Could you take a look?

Alexey

[Alexey Tikhonov]

False alert, the refresh works fine. I'm trying to get used to VSCode - before I worked in MS Visual Studio, probably, I did something wrong.

[Edward K. Ream]

On Mon, Jul 26, 2021 at 5:37 AM Alexey Tikhonov <tickli...@gmail.com> wrote:

False alert, the refresh works fine. I'm trying to get used to VSCode - before I worked in MS Visual Studio, probably, I did something wrong.

No problem. Many thanks for your testing.

Edward

[Viktor Ransmayr]

Hello Felix,

I tried this afternoon to use 'Leo for VSCode' to update some of the existing outlines, I use to study certain areas.

Again the initial experience was very good. - However this time I noticed that the 'rst3' command, which I heavily use in my note-taking workflow, does not have any effect.

Is this a known issue - or - shall I open an issue in GitHub?

With kind regards,

Viktor

[Robert-Felix]

Hi Viktor,

This may seem silly, but I dont know anything about rst or what the rst3 command is/does/how it's invoked, ...is it from a plugin ect...?

Can you give me a 10 word sentence refresher about what it is / keybinding/ effect? 

Maybe Edward can chime in and give me (or you) some insight about this... 

On the other hand, I'm working on releasing a new beta version today (or late tonight) with all (or most) bugs fixed - so maybe this bug will be indirectly resolved, and the rst3 command will work through the alt-x (minibuffer) command palette.

Anyways I'll finish this release, and come back to this 'rst3' command that you talk about.

So really:  thanks for the heads up about this and I'll make sure to address it more seriously in a day or two.

--

Félix

--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b74c6f23-2a61-4ddb-a37e-144ac77f5e71n%40googlegroups.com.

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Sonntag, 15. August 2021 um 21:55:45 UTC+2:

Hi Viktor,

This may seem silly, but I dont know anything about rst or what the rst3 command is/does/how it's invoked, ...is it from a plugin ect...?

Can you give me a 10 word sentence refresher about what it is / keybinding/ effect? 

Maybe Edward can chime in and give me (or you) some insight about this... 

On the other hand, I'm working on releasing a new beta version today (or late tonight) with all (or most) bugs fixed - so maybe this bug will be indirectly resolved, and the rst3 command will work through the alt-x (minibuffer) command palette.

Anyways I'll finish this release, and come back to this 'rst3' command that you talk about.

So really:  thanks for the heads up about this and I'll make sure to address it more seriously in a day or two.

Rst3 is a command  in Leo, which transfers a reStructuredText (rST) [1] source document into multiple output formats.

The output format that I'm mostly interested is HTML. - It's quite similar to Markdown.

rST is the base for all / most of Leo's documentation - and - it's also the base for Sphinx [2], which is another documentation generator relying on / using rST

As far as I know rst3 is not a plugin - but - is considered part of Leo's core.

With kind regards,

Viktor

---

[1] https://docutils.sourceforge.io/rst.html

[2] https://www.sphinx-doc.org/

[Félix]

how are you invoking this command in Leo? keybinding, from the menu? or the alt-x minibuffer?

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Sonntag, 15. August 2021 um 22:17:26 UTC+2:

how are you invoking this command in Leo? keybinding, from the menu? or the alt-x minibuffer?

Alt-x minibuffer.

With kind regards,

Viktor

[tbp1...@gmail.com]

I'm just chiming in to support Viktor about making the rst3 command available.  It's quite wonderful for all kinds of documentation.

[Félix]

I started https://github.com/boltex/leointeg/issues/189 for this. :) 

Thanks again for pointing out this issue!

--

Félix

[Félix]

Hi Viktor and Thomas, (and Edward) It's fixed now: https://github.com/leo-editor/leo-editor/pull/2131

And please remember to 'star' leointeg in the upper right corner at https://github.com/boltex/leointeg if you havent already ! 

(it helps getting notoriety when asking for priority in features / fixes with the vscode team, and also my ego)

Thanks again to anyone who tries, and reports his experience with leointeg! It really helps a lot!

--

Félix

[Edward K. Ream]

On Sun, Aug 15, 2021 at 3:12 PM Viktor wrote:

> Rst3 is a command  in Leo, which transfers a reStructuredText (rST) [1] source document into multiple output formats...

> As far as I know rst3 is not a plugin - but - is considered part of Leo's core.

That's correct.  See leo/core/leoRst.py.

Edward

[Edward K. Ream]

On Sun, Aug 15, 2021 at 9:39 PM Félix <felix...@gmail.com> wrote:

And please remember to 'star' leointeg in the upper right corner at https://github.com/boltex/leointeg if you havent already ! 

Done!

Edward