STM32 Cube IDE Execute Command in Linux - stm32

I have installed STM32 Cube IDE in wsl.
So I'm trying to run it as a command in the terminal, but I don't know how to do it.
I need some help.
I connected to wsl with a virtual desktop screen and ran stm32cubeide, but it works without any problems.
However, I don't know about running it in terminal.

Related

Vscode running on linux but display on Windows. How to recover sessions?

So I don't use the linux desktop. I ssh into the box and run code there but the display is on my windows box. If something happens to the windows machine (example forced update and reboot) when I log back into the Linux machine, code is still running. How do I retrieve/restore the gui?

Way to run python in VSCODE.dev

is there a way I can run python code in vscode .dev, im looking for a way to do this on a school Chromebook.
You can install the Python extension in VSCODE.dev, and then run the file with a Jupyter Server by right clicking and choosing "Run Current File in Interactive Window." HOWEVER: You must run the Jupyter Server on some computer (if you're chromebook has the Linux Development Environment enabled, you could do it there). You could run it on a remote computer, but that will cost money.

Remote running of python file X11 issue

i'm using remote-ssh VSC extension to run python files from windows on remote Ubuntu VPS
The problem is, i cant run code with tinkter or some commands like xeyes
They seems running, but there is no window displaying the result appearing.
What should i look at Local and server sides to fix this?
Got it. I need to run Xming on local machine in parallel with vscode. This way xming open window with graphic content in it

nvm and gulp found on Visual Code terminal but not on linux terminal

I have Ubuntu LTS 20.04 running on wsl2 in Windows, this way I'm able to compile my JS/React code and run my php server in linux and use windows to code using Visual Studio Code.
This is running great, but a strange thing is happening, I installed nvm and gulp through the Visual Studio Code terminal and if I use them on the terminal it works fine but not if I do it outside the terminal (using Windows terminal), it says not found for both gulp and nvm.
I assume VSCode is adding a few things to the PATH but I don't know what to do for them to be found by the windows terminal (outisde VSCode terminal). Screen below. On the left is the result of running nvm list inside VS Code terminal and on the right on Ubuntu terminal, which can't find.
I'm a bit confused by your question. It sounds like you're installing programs on Windows through the VSCode terminal, and then trying to run them on Windows but it's not working. But then your screenshot shows the WSL Ubuntu prompt failing to find the command. Assuming you want to run these under WSL, log in to WSL Ubuntu and run this:
find / -name nvm
If you actually want to use the Windows terminal to run the program, you'll have to find where it is installed in Windows and make sure that's in your %PATH% but this doesn't seem like it's what you're trying to do.
The correct answer was provided by the comment from MindSwipe.
On VSCODE terminal if I "echo $PATH" it has the nvm directory in it while the $PATH on WSL doesn't, I assume VSCODE alters its own terminal PATH when the tools are installed using it instead of the global WSL path.
I've changed the WSL path and it's now working, how can I present the bounty to MindSwipe ?

VS Code installed in Windows comes up as running under WSL Ubuntu 18.04

I installed VS Code in windows, but it comes up as running under WSL Ubuntu 18.04.
I don't want to run in the linux subsystem, but in windows proper.
Uninstalling and reinstalling does not change this.
Uninstalling and deleting all vscode file and folders in /users does not change this.
Try going to the bottom left of your window and press on the WSL: Ubuntu-18.04 button.
After pressing the button, go to the top center of the window and choose Close Remote Connection.
After that, VS Code should stop auto-connecting to the WSL Ubuntu system every time when you open it (I tested myself and it worked on my computer).