I am wondering if something is wrong with my computer (or myself), because I can't seem to drag & drop a file into Visual Studio Code to open it in the editor. Closing an opened folder first doesn't make a difference. VSCode always shows me the 'stop sign', in every spot I tried (the editor, the opened tab bar, an existing opened file, ...).
Why does VSCode block this ?
(I have experienced this in earlier versions as well. Currently on v1.6 on Windows 7.)
Searching for a solution, I stumbled on this page, where one commenter explains:
I think you are running into the security issue where lower permission processes cannot send messages to higher permission processes. Explorere.exe, running at normal permission levels, cannot send the window message to winword.exe, running elevated.
I am indeed always running VSCode as Administrator, but not my Explorer windows.
When I run VSCode in non-administrator mode (so just my regular user), drag-and-drop works fine.
I feel silly as I lost 15 minutes looking into this. In case it helps:
Make sure you are not trying to open files from a zip file...
Cheers.
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 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.
I've always developed with Sublime Text, but I feel that VS Code is much better, so I want to get started.
I have a problem please (with Sidebar of VS Code):
When I open a sub-folder in my project, and I open a file that is inside, I like to manually close this sub-folder (because I like to see the architecture of the project, etc.) and to continue working on its files which are already open in my editor.
For example (I work with Laravel): if I open a "User.php" file which is in the "App/Modals" folder, then I manually close the "App/Modals" folder, then I will work in another file, then I come back to work in "User.php", the "App/Modals" folder reopens by itself ...
I do not have this behavior with Sublime Text, nor with PHP Storm.
SVP: Is there a regulation to prevent this behavior?
Thank you.
There's an option to make this feature (it's not something that's just happening to you, it's a feature of VSCode) go away. Go to settings (ctrl + , or cmd + , on mac) and search for "explorer.autoReveal". Make sure it's unchecked, or set it to false in your setting's json.
Just by the way, I don't know if you did, or you didn't know what to search, but you should try to solve this kind of problems by googling for an answer. For instance, I didn't know the answer, but a simple 'disable auto opening folder vs code' in google brought me several results. Just a recommendation, so that you can learn how to solve your own problems and be more efficient.
One of the most useful features of Sublime Text for me was that it keep a history of all the files that I opened. How can I get this functionality in VS Code?
The list of previously opened files/editors when I open cmd+p is really small and it doesn't persist across sessions.
Edit: the problem isn't that I lose my previously opened files when I close the session, but that there is no convenient way of accessing a file I opened a week ago, for example.
To see a list of recently opened files (as of v1.42) try this in the command palette:
View: Show All Editors By Most Recently Used
or use this command workbench.action.showAllEditorsByMostRecentlyUsed in a keybinding.
On mac it's ⌘ + P.
I'm using mac monterey
I don't know how I missed this: File | Open Recent | More it's assigned to action workbench.action.openrecent.
The only thing I'd like to know is if there is a way of setting the number of files it remembers (the buffer size).
I am using Visual Studio code and it works fine except that double clicking the file doesn't seem to open the file. Instead the Program just opens with an Untitled.txt screen.
Right click -> Open with code also works.
How do I make it work? I am using Windows 8.
This wasn't the case some versions back, but now it seems, that it actually is the expected behaviour. The developers intentionally do not register VSCode as the default open handler (don't ask me why).
But maybe there is a workaround. Try the following steps:
1. Try to associate the filetype(s) with another app, and then again to VSCode.
2. If setting to other editors and returning to VSCode still opens Untitled-1.txt, then you could
3. try reinstalling VSCode, and then reset it. When resetting, confirm that there is only one VSCode in the choice list.
It also could be, that you'll need to reboot your machine. Finally, you'll possibly also want to take a look at this issue on GitHub.
Hope you can solve it this way.