Extension issue

[Cl4xt0r]

Extension issue

[slavek-kucera]

Hello @Cl4xt0r,

could you please describe the actual problem you encountered?

[Cl4xt0r]

Dear Slavek-Kucera Thank the team for fixing the JAVA HOME problem and “Sorry” for the delay in replying.I have been investigating the problem and searching for solutions. I am a returning COBOL programmer after 10yrs in retirement. I have re-badged with IBM and chose VS Code and Git as the base of my workstation, using Ubuntu v.20.04.1, but in the past I have always had a DBA, so it has been a challenging, but an enjoyable journey, all so I can work from home and soon I hope. The problem is a known one, [see: https://code.visualstudio.com/docs/supporting/faq#_resolving-shell-environment-fail ] This has helped me to identify that the main problem is with my Node.js package manager NVM. When launched via a UI gesture, VS Code that starts a small process to run (or "resolve") the shell environment defined in my workstation by .bashrc file, to check which node version to auto-use based on .nvmrc and this is the one that takes most of the time to complete. I have found a solution that proposes skipping that check and adding a default node to the path to replace the autoloaded node version for a faster access. The proposed change is: # Add default node to path export PATH=~/.nvm/versions/node/v16.1/bin:$PATH # Load NVM export NVM_DIR=~/.nvm [[ -s "$NVM_DIR/nvm.sh" ]] && source "$NVM_DIR/nvm.sh" --no-use RC note: my node version path is v16.1 (Not: v12.16.1 as in the guidance.) However: when I attempt to open my shell's startup file in VS Code by typing ~/.bashrc, I get the response “Permission denied” probably for good reason. Any help would be appreciated. Kind regards, Roy

…

________________________________ From: slavek-kucera ***@***.***> Sent: 21 March 2022 08:02 To: eclipse/che-che4z-lsp-for-hlasm ***@***.***> Cc: Cl4xt0r ***@***.***>; Mention ***@***.***> Subject: Re: [eclipse/che-che4z-lsp-for-hlasm] Extension issue (Issue #245) Hello @Cl4xt0r<https://github.com/Cl4xt0r>, could you please describe the actual problem you encountered? — Reply to this email directly, view it on GitHub<#245 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARP633NKI45J3OXJKOIQ2FLVBAULHANCNFSM5REQZ6UQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[slavek-kucera]

This is starting to sound less and less like the problem with the plugin.
By default, we are running the language server in a native process, so node version is really immaterial and we are not using java at all in the hlasm plugin.

I am still not clear on what is the actual problem you are experiencing.

[Cl4xt0r]

Hi. You are right, it is Linux creating the Shell environment that VS Code runs in. I have searched online and edited the program that creates it, to speed it up. Only just finished and the test worked O.K. Thanks for your time. Please close the issue. Roy

…

________________________________ From: slavek-kucera ***@***.***> Sent: 11 April 2022 09:16 To: eclipse/che-che4z-lsp-for-hlasm ***@***.***> Cc: Cl4xt0r ***@***.***>; Mention ***@***.***> Subject: Re: [eclipse/che-che4z-lsp-for-hlasm] Extension issue (Issue #245) This is starting to sound less and less like the problem with the plugin. By default, we are running the language server in a native process, so node version is really immaterial and we are not using java at all in the hlasm plugin. I am still not clear on what is the actual problem you are experiencing. — Reply to this email directly, view it on GitHub<#245 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARP633IHMZVXIINQ5PORR53VEPNXFANCNFSM5REQZ6UQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>