*> I pulled master and did npm install.*

Please install the real vsix compiled extension file instead.

For testing purposes, I would not recommend using via the git repo with the 
run and debug command from vscode (F5) instead of simply installing the 
plugin with the vsix file. 

Main reason is that there are small differences when launching the server 
internally because a debugging external host is different from a standalone 
instance of vscode. (for when the tk window pops up if you forgot unsaved 
files and other server behavior while being spawned from a 'parent' nodejs 
process.)

On top of that, while having the real extension installed through the vsix 
file, nothing prevents you from developping and running a development 
(cloned git repo) version with F5, If you modified it, it will replace the 
real extension in that debugging extension host while it runs. So there no 
inconvenience in installing and running from the real compiled extension 
file. (btw the vsix file format is just a renamed zip file, so you can 
inspect it and see its exactly the extension form source.)

Also, you don't have to uninstall the 0.1.16 (older) version when 
installing the new beta, it will just replace it automatically. It will 
also replace it automatically when I release a 1.0 through the microsoft 
store.

Thanks again to all beta testers!

(Eager to hear about how the git-diff and rst3 command work from other 
leonistas!)
--
Félix
On Monday, August 16, 2021 at 6:16:22 AM UTC-4 Edward K. Ream wrote:

> On Monday, August 16, 2021 at 5:13:40 AM UTC-5 Edward K. Ream wrote:
>
> I installed leointeg from git as usual. The installation went fine.
>
>
> I pulled master and did npm install.
>
> Edward
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9e6a5aa5-dddc-42bf-87da-3a56e3fbc1a1n%40googlegroups.com.

Reply via email to