I might want to add that I'm not primarily a python coder, (I'm quite the 
newbie when it comes to python), so my choice of extensions and settings 
might look silly for an experienced python coder who is also experienced 
with vscode.

On Sunday, June 21, 2020 at 1:36:10 PM UTC-4, Félix wrote:
>
> Hi Edward, 
>
> *launch.json* is also what defines the choices you have when you unfold 
> the dropdown beside the green triangle in the run/debug panel. Subsequent 
> F5 will repeat the startup of the chosen entry's 'launch configuration'.
>
> I wish I could help you more effectively given the details you provided but* 
> I'm still pretty new to vscode debug panel and how to use it effectively.* I 
> just set it up as per recommended configurations for launching an 
> extension, a basic python program for the second one, and a compoud of the 
> two for the third. 
>
> Here are a few things that I though might help. Of course there also the 
> option of removing vscode and its related settings, and re-install but that 
> should be last resort! 
>
> For comparison, here is what I have without the comments (as you can see 
> the third one is a compound of the first two): 
> {
> "version": "0.2.0",
> "configurations": [
> {
> "name": "Run Extension",
> "type": "extensionHost",
> "request": "launch",
> "runtimeExecutable": "${execPath}",
> "args": [
> "--extensionDevelopmentPath=${workspaceFolder}"
> ],
> "outFiles": [
> "${workspaceFolder}/dist/**/*.js"
> ],
> "preLaunchTask": "npm: webpack"
> },
> {
> "name": "Python: leoBridge Server",
> "type": "python",
> "request": "launch",
> "program": "${workspaceFolder}/leobridgeserver.py",
> "console": "integratedTerminal"
> }
> ],
> "compounds": [
> {
> "name": "Server and Extension",
> "configurations": [
> "Run Extension",
> "Python: leoBridge Server"
> ]
> }
> ]
> }
>
> This file is also 'gitted' along with the leoInteg project so you can 
> easily get it back to if you need to. 
>
> I'm afraid I dont know much about this whole setup and what might be 
> preventing compiling and running with it. As you said, maybe an extension 
> broke something. (they can be disabled temporarily through the CTRL+X 
> (extensions) panel and a reload of vscode, to see if behavior changes)
>
> I always try to add new extensions one at a time, (and see if it doesn't 
> break anything), and that I really like it by using it for an hour or so. 
> (i.e. do I feel like I could not go back to not having it?) otherwise I 
> remove it before trying another one.
>
> For comparison, here are my (*badly commented*) settings : 
> https://gist.github.com/boltex/57ab6c814253dc538a55e81ad2c7a72a (access 
> rapidly with CTRL+',' (comma) and click on text view in top right corner to 
> compare) and for ideas of extensions/themes to try out, here's a 
> screenshot of the extensions I have enabled (I needed the 
> "python.languageServer": "Microsoft" part for debugging python smoothly). 
> (didnt bother to find out how to export it textually - also as a graphic 
> designer I care about people who designed graphical icons and such that are 
> nice to look at, and helps make sure you've got the right extension and not 
> an homonym)
>
>
>
> Feel free to ask for more about that kinds of stuff, Sometimes something 
> 'clicks' and it was merely a detail that prevented things to run smoothly!
> --
> Félix
>
>
> On Sunday, June 21, 2020 at 7:07:41 AM UTC-4, Edward K. Ream wrote:
>>
>> Hi Félix.  I am learning more about vs-code. I think I enabled a plugin. 
>> After that F5 stopped working.
>>
>> To fix this, I removed launch.json from the leo/.vscode folder. Not sure 
>> how I as lead to that folder. Perhaps git reported that it had changed.
>>
>> After a restart, F5 worked again. launch.json contains:
>>
>> {
>>     // Use IntelliSense to learn about possible attributes.
>>     // Hover to view descriptions of existing attributes.
>>     // For more information, visit: 
>> https://go.microsoft.com/fwlink/?linkid=830387
>>     "version": "0.2.0",
>>     "configurations": [
>>         {
>>             "type": "pwa-node",
>>             "request": "launch",
>>             "name": "Launch Program",
>>             "skipFiles": [
>>                 "<node_internals>/**"
>>             ],
>>             "program": "${file}"
>>         }
>>     ]
>> }
>>
>> Any idea what the problem is?  Does leoInteg need an entry in launch.json?
>>
>> 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/fefede3d-0678-47da-819c-096856708601o%40googlegroups.com.

Reply via email to