How can I get made code files running at the same time in VS code app?
When I run say my_pomodoro_app.py which comes with a Tkinter window, I am unable to run any other code file unless I close my pomodoro app. This does not happen in Pycharm.
Is that how VS code works? Or I have to do some settings to enable running mmany programs?
I search on the internet but coudn't get the solution
Related
When trying to run a file or just open the terminal in VS Code, the terminal opens for a half second and then promptly closes without error messages.
I've tried updating VS Code, and external libraries/environments. I'm thinking I might need to fully uninstall and reinstall, but hoping there is a easier fix.
When I open the terminal in VS Code, the terminal opens for about half a second, crashes, and outputs this message:
The terminal process "/bin/zsh '-l, '" terminated with exit code: 1.
What could possibly be the cause of this problem. and how do I fix it? I'm using a Mac.
You would want to check your user settings first. Review terminal.integrated settings that could affect the launch.
You're using a Mac, so on macOS, go to Code > Preferences > Settings. In the settings, you may want to search for this:
Just in case you modified settings.json without knowing, you could by typing in #modified or accessing it by Filter Settings (top right) > Modified.
If you did not modified anything, then it may be due to these:
Test your shell directly. Try running your designated integrated terminal shell outside VS Code from an external terminal or command prompt. Some terminal launch failures may be due to your shell installation and are not specific to VS Code. The exit codes displayed come from the shell and you may be able to diagnose shell issues by searching on the internet for the specific shell and exit code.
Use the most recent version of VS Code. Each VS Code monthly release has many updates and fixes and may include integrated terminal improvements. You can check your VS Code version via Help > About (on macOS Code > About Visual Studio Code). To find the latest version of VS Code, go to the VS Code release notes. You may also want to check that you have installed the latest version of your shell.
Use the most recent version of your shell. If your shell is installed separate from your platform, try installing the latest available version of the shell. The same advice applies if you are on an older build of your operating system. For example, some older versions of Windows 10 did not work well with the VS Code terminal.
Enable trace logging. You can enable trace logging and capture a log when launching the terminal. Logging often reveals what is wrong as all arguments used to create the terminal process/pty are recorded. Bad shell names, arguments, or environment variables can cause the terminal to not launch. Keep this log for later if your problem isn't solved.
Exit codes and shells
Search for the specific shells or exit codes in Google (if provided), maybe it would help.
If these still did not help, you may consider searching it in Google (mainly Stackoverflow or github).
Reference link: https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch
I'm developing an office-js taskpane add-in for Excel.
I am using VS code as the IDE and debugging environment.
After running a debug, more often than not I cannot run a second debugging session because VS code does not launch WebPack.
I end each debugging session simply by closing Excel. That also ends the session according to the VS code terminal. But if I hit F5 again, Excel starts immediately and webpack does not. I have to reboot the machine to get it working again.
Does anyone here know how I might fix this extremely annoying issue?
Here are a few links you may find helpful in debugging Office Add-ins:
Debug Office Add-ins
Attach a debugger from the task pane
Sideloading and Debugging Outlook Add-ins
I am working on two projects, one is a library, the other is a program that uses that library. When I make changes to the library the other window (the program) doesn't see these changes, so I do not get updated IntelliSense. Closing the program that uses the library and reopening it does force an update but I really prefer not having to go that far.
Answering the title directly and not the root issue...
You can reset IntelliSense and all Rust code features by running the "Rust: Restart the Rust server" command from the command palette (Ctrl+Shift+P).
Progress will be indicated in the status bar.
Still a blunt tool but it will ensure you're in a fresh state without having to restart VS Code entirely.
I've noticed that, despite always closing it before I quit, despite opening other files as well, Visual Studio Code will always re-open a particular file when I launch the app. This is still the case after upgrading to the latest version - 0.7.0 at the time of writing.
Is there a setting I'm missing, or something that needs to be cleared out / blown away?
I'm running on Windows Server 2012 R2.
This issue has been fixed for the next release and only shows up when you work in file mode and not folder mode (that is when you are not actually opening a full folder inside VS Code).
To workaround this, use the -n option when you run VS Code. -n will force to open VS Code empty without any file or folder opened.