I used Python with VSCode for the first time in a while. When I went to debug the script I'd written, I couldn't see any variables in the debug panel. It's not just that none are showing up - there's not even a section where they would be appearing - please see the screenshots below.
When I right click on the three dots at the top of the debug panel, I can see "Watch", "Call Stack", and "Breakpoints", with ticks next to them, but no "Variables" option.
I swear I used to be able to see variables, and everything I'm seeing online is saying that I should be able to, but they just don't seem to be there. At first I thought it was just Python, but I've just tried to debug a simple C program and the same thing happens.
Besides this issue, the debugger seems to work just fine.
What I'm seeing:
What I'm supposed to be seeing, and what I used to be able to see:
Any information would be really helpful, it must be something daft I'm missing.
To clarify, I've tried a fresh VSCode install, which did not fix the issue.
Solution moved from #DCoxshall's question post.
Just did [a reinstall] and the issue disappeared. If anyone knows what caused it I'd still be interested in information, although the problem is now gone.
Related
I have a Theia IDE built in a docker.
Every time I launch a new docker and open a python file for the first time, I got some annoying pop-up:
A new tab: Python - Get Started
A pop up: Linter pylint not installed
Both have a Do not show again option. However, it does not work in my use case because every time a user connects, he will get a new Docker.
I tried to look in the settings and preferences but could not find where to disable these pop-ups.
I also tried to look at the settings files (launch.json for example) after having clicked the Do not show again button but nothing change.
The perfect solution for me would be to add a line in the launch.json file to tell Theia to never display those pop-up in the first place but I am not sure it is possible.
If you know a way to do it (in the launch.json or another way) I would be pleased to hear it!
If you know how to do it in VS code I would also be pleased to hear about it as Theia took a lot from VS code
Thanks!
I finally found the answer by observing which files were changed last on the docker.
I found out that you have to write "python.showStartPage": false in /home/theia/.theia/settings.json
However, it was not enough, I also had to add some lines in /home/theia/.theia/plugin-storage/global-state.json.
I don't know which lines exactly as I just copied-pasted the full file from a previous execution. But I would guess that it is one of the lines beginning with gettingStarted.overrideCategory
I have the weirdest bug. If I edit anything in the 'Script Execution Order' list in Project Settings, and click 'Apply', it just reverts back to how it was before immediately. This includes any type of change: removal of entries, adding entries, or changing the number of the entry. Everything just plops right back to the previous state on clicking Apply - no error messages whatsoever.
Visually, it's exactly the same result as clicking the 'Revert' button instead of 'Apply' - except that the editor actually starts doing its refresh thing afterwards (I thought for a moment maybe the Apply button was broken, but this kinda rules that out).
After hours of trying stuff I figured out that it works if I remove the 'Unity UI' package, so I guess the problem may have to do something with that. However, another project that includes this package does not have the same problem.. so it's still project-related, somehow. I tried uninstalling and reinstalling all packages 10 times, no luck..
I had submitted this as a bug to Unity support, who have just responded.
After some investigation, I've concluded that this is currently by
design. You're trying to make changes to scripts from Packages,
currently, you can't do that. If you would add your own script and try
to change the execution order, you'd notice that everything works
correctly. (Matas, Customer QA Team)
He is correct, and indeed, changing/adding entries from your own code DOES work. In hindsight, this makes sense, even if it's a bit rigid. Problem 'solved', as in, I can live with packages' entries being readonly.
I need to figure out how to turn off emphasized items in Visual Studio Code
This might sound like a strange requirement, but in my workflow vscode functions as less an IDE than a cross-platform ViM-esque frontend with lots of remote development tools built-in.
Due to this use case, I don't need or want the linting features to show up in the file browser. How might I accomplish this?
Attempts to solve the problem
I've run out of search terms here and cannot find an answer.
Searches including terms in this question's title yielded little
SO-specific search queries also yielded little
This seems to be somewhat related, at least as a representation of the "feature" I'm referencing: VS code containes emphasized items but no error
VSCode "preferences" do not appear to show what I'm looking for, likely an issue with me not searching for the right variable name.
In my experience with VSCode it has been wonderfully customize-able, so I'm guessing there's a setting somewhere ready to be modified to accomplish this. Any help much appreciated, thanks!
My use case was a bit different: after viewing some files in a git submodule those files became linted, and errors and warnings cluttered up my VS Code Explorer file browser window on files I had no intention of ever handling. I basically wanted a way to clear out those lint warnings, and found it here. The solution is to reload the window:
CtrlShiftP on Windows/Linux, ⌘ShiftP on Mac -- then select "Developer: Reload Window"
One by-product of reloading the window is that it clears out those unwanted warnings (at least until the next time I visit the file). It also has the effect of clearing out warnings on files that I would normally want to see, of course, but chances are I'll be visiting those files again soon, so it's fine. Not a perfect solution, but it works for me and my use-case; hopefully it can help others.
I don't know how to turn it off, but I had this on multiple folders and I fixed it by renaming the folder to a random name, then naming it back to the name it was before and the error would go away.
If you have this issuse then uninstall extention then CtrlShiftP on Windows/Linux, ⌘ShiftP on Mac -- then select "Developer: Reload Window" then type developer: relode page this issuse automatically resovle
i have this issuse then i uninstall extension then this issuse resolve.
I was able to permanently prevent this by adding the files to the .gitignore file. It seems that this happens in a cloned repository when you add new files.
im not sure what i did.. but i am working through some tutorials to get up to speed on python, and i started getting this error message... any ideas on how to fix this? from the error, i looked up the message, and it looks like wham i press the run button it is looking for a file that is no longer there.... but I'm not even working on that file anymore... I'm trying to run something different that does not refer to the previous file.
what does work is if i do run as.. but id rather not do that every time. I'm sure there is a setting I'm just not aware of that i messed up.
Well, not sure how exactly you're getting to that point from your explanation, but please take a look at: http://pydev.org/manual_101_run.html to see how to properly run a module inside PyDev.
I'm using the "SPIDER" IDE for SICSTUS Prolog development, as instructed by the SICSTUS Manual and the documentation on the SPIDER IDE itself. When debugging, under the 'SICSTUS Debugging' perspective, the variables do not show on the Variables window, as can be seen in the top right in the image shown here (it's the first thing in the Spider page)
I set up everything according to this guide and this is, as far as I can tell, the only thing not working. Are there any additional steps to get the variable bindings while debugging?
Thanks in advance,
edit: I've recently reinstalled everything in the same system after formatting a drive, and it now works perfectly. I have no idea what, but I assume I did something wrong the first time.
Variable bindings should work by default. However, some variables may be omitted depending on compiler optimizations and other factors. Try it with the example program shown in the SPIDER image.