Do you know the .vscode/tasks.json file? You can add it to your project, and @vscode will run your configured commands automatically when you open the project ✨
I use this for the Inertia Table so it starts the web server and Vite without me having to open terminals for them 👌
Here is how you can add a simple action to open a folder in VSCodium within Nemo file manager.
Create a new file in ~/.local/share/nemo/actions/ and name the file vscodium.nemo_action
Open the file in a text editor
Copy the code below into the file
[Nemo Action]
Name=Open in VSCodium
Comment=Open VSCodium in the selected folder
Exec=codium %F
Icon-Name=vscodium
Selection=Any
Extensions=dir;
Save the changes made to the file
Now when you right click inside a folder in Nemo, it will show an option "Open in VSCodium" and when you click this option, it will launch VSCodium using the currently directory as the workspace.
This can be modified to work with Visual Studio Code (Which is closed source unlike VSCodium) by editing codium %F to code %F
I need to be able to see the difference between the current working file and the previous commit as I am editing the file. The only history plugins I can find either use pop-ups (which disappear when I start typing) or a dedicated diff-view which takes up too much space on my small monitor.
I am an intermediate VSC user, and have a problem with commands that are too close to each other in the right-click context menu for the SFTP. I constantly click something other than the top one marked here. It causes a mess that's easy enough to clean up but it's annoying. Any suggestions here?