Also, it just occurred to me that maybe the 'environment' dialog is just
the other instance of vscode, with leointeg running, that happened to be
opened in a workspace that contains some javascript or typescript files,
and its just vscode reacting to the languages of the files happening to be
in the workspace its oppened into. (some thing that would have happened if
you would have opened that folder with vscode anyhow)
That happened to some people before, although it might not be whats
happening here.... it might help some other people who are new to vscode
itself to take note that:
It is very proactive in detecting what opened folder the explorer view is
in, and will suggest interpreters environments, and extensions to install,
or pop up dialogs to ask for environments if it detects more than one
interpreters available on your machine for a given language, etc. and so
on... (those generaly dont come back) those might be mistaken with leointeg
or something going wrong,
just cancel/close those and try to see if the new vscode debug-instance is
running and has the leo icon is in the main activity bar - generaly on the
left, and try to do what i do in the first animated gif of the readme. if
possible.
Thanks for reporting any details about this! It will be concatenated and /
or be used to facilitate the installation and running by giving explicit
steps to run without those problems in the readme file.
I think I'll just uninstall vscode completely on my windows box and try to
install vscode and leointeg in 4 or 5 steps with screen captures to
acompany the text in my readme... or maybe another animated gif? hehe, i
like animated gifs... but its late and i'm laughing at my own jokes so i'm
going to bed now i'll do this tomorrow.
Thanks again!
Félix
On Monday, June 1, 2020 at 1:02:08 AM UTC-4, Félix wrote:
>
> Thanks for trying it out and sharing your experience!
>
> 1- npm install logs gives exact same warnings for those dependencies for
> me too. that's normal.
>
> 2- I'm not familiar with sitecustomize.py but I just googled it and found
> out its about customizing python environments for different projects on a
> machine. I will at some point have to give more friendly details of
> installation for people using that, and/or anaconda. But everything related
> to the python side of things can be tested independently of vscode and
> leointeg, by simply starting the leobridgeserver.py script manually
> yourself in any way you choose... (terminal, or some shell...)
>
> 3- Hmmm ... I've never encountered this dialog asking for an 'environment'
> nor dialog saying '${file}' can not be resolved... I'll switch to my
> windows machine and will come back here to report about the current node.js
> version that is installed on my machine, along with version of any other
> thing that might not have been taken care of by the 'npm install' step.
>
> In the meantime, (if you're ok with this), could you please click on the
> help/about button in vscode's menu? it's got a handy 'copy' button which
> you could use to then paste the results in here. That would give general
> info that might be useful. For instance on my linux machine I get this
> report:
>
> Version: 1.45.1
> Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
> Date: 2020-05-14T08:27:22.494Z
> Electron: 7.2.4
> Chrome: 78.0.3904.130
> Node.js: 12.8.1
> V8: 7.8.279.23-electron.0
> OS: Linux x64 5.5.5-050505-generic
>
> (back to edit this message from windos) and here is the same on my windows
> machine :
>
> Version: 1.45.1 (user setup)
> Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
> Date: 2020-05-14T08:27:35.169Z
> Electron: 7.2.4
> Chrome: 78.0.3904.130
> Node.js: 12.8.1
> V8: 7.8.279.23-electron.0
> OS: Windows_NT x64 10.0.17763
>
> Félix
>
> On Sunday, May 31, 2020 at 6:39:48 PM UTC-4, Edward K. Ream wrote:
>>
>> On Friday, May 29, 2020 at 10:44:13 PM UTC-5, Félix wrote:
>>
>> > I just pushed a new version on the master branch of LeoInteg. ...I made
>> sure it runs well under Windows this time! ;)
>>
>> Here are my experiences.
>>
>> 1. npm install reported the following:
>>
>> found 310 vulnerabilities (298 low, 12 high)
>> run `npm audit fix` to fix them, or `npm audit` for details
>>
>> I didn't run npm audit fix, to keep things as they were.
>>
>> 2. Adding the path to the leo-editor folder did not work. Adding this to
>> my sitecustomize.py did work:
>>
>> import sys
>> leo_path = r'C:\leo.repo\leo-editor'
>> if leo_path not in sys.path:
>> sys.path.append(leo_path)
>>
>> Finally, running F5 in vs code gave an error previously. Now it asks me
>> for an environment. When I select node.js I get a dialog saying '${file}'
>> can not be resolved. Please open an editor.
>>
>> What do I do now?
>>
>> 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/25712f10-e51b-49ed-a05e-a3c69008a041%40googlegroups.com.
