When I save file in Visual Studio Code with Control+S it creates something like try_django\views.py.b2ea9afa731de4b4d202b20f80c4a769.tmp first, then delete it and then saves file... but that thing can take like up to 5 seconds so I gets annoyed with it. Some time ago it wasn't like that... The question is how to make VS Code saves file quicker, like it was before?
UPD: that was because of anaconda, but can I leave it and make python files save like faster?..
Related
Folks,
Sorry for such a basic question, but I'd like to know how to save changes to JSON files edited in Visual Studio Code that was launched from inside Azure Cloud Shell. I've made changes to a JSON file using the editor, but can't find a way of saying those changes unless I navigate away to another file and then I'm prompted to save my changes. Does anyone have a cheat sheet of useful keystrokes or something?
Lisa.
I'm working with a new student who's getting started with Python programming in Visual Studio Code. She's exploring and getting to know programming by feel and using VS Code and kitao/pyxel to learn the ropes. In that project, one creates .pyres files (that are binary/zip files). When that file appeared in the editor, the user clicked on the file, acknowledged the "view this file as text even though it's binary" warning, and then saved it, thereby corrupting the file. And since VS Code and Windows are uncompromising on these sorts of mistakes, all of the work in generating the assets appears to be lost.
Is there any way given a binary file that was opened and re-saved unchanged in VS Code to reverse the changes that VS Code makes to that file? Any insight into what changes VS Code makes to a binary file when opened as text and saved?
I'm trying to understand how a specific javascript app works reading the source code.
I know there is a file that, at some point, gets executed, but the file has no exports so I am thinking that, in some other point in the code, there is an import 'foo/bar' statement causing the file to be run, but I don't know how to find where from.
Visual Studio Code has a feature that lets me see where a function has been defined or where is it used, is there a similar feature for tracking imports of a file?
Hi my visual studio code does this weird single line paste whenever I copy a code from a pdf or any other sources.
this picture below is what I copied from
this is what happens when I paste my code
Not really sure what made it this way but I have tried reinstalling, deleting the cache, all the files related to visual studio code but it doesn't work.
The reason why I am asking this because it used to work and my friends that use vscode doesn't have this problem.
Your help is very much appreciated.
I've just started with Visual Studio Code.
One thing I find really strange is, if my code compiles to an *.exe, and I select it in the explorer, VS Code tries to "open" it, as if it was a text file, and then complains it's a binary file.
Ideally, it should do nothing when I select it, and I should have to easy way of running it if I want, like "double-click" or some option in context menu. I don't want to hide the .exe, I just want VSCode to know it cannot edit it, so it shouldn't try.
[EDIT] In case someone wonders why I'd single-left-click on something where that click "makes no sense", it's because I've spent the last 15 years using an IDE where that does nothing except select the file in the explorer, and so I got into the habit of click on things while I'm "thinking about it", for example when I'm talking about this file to someone else. That's a hard habit to get rid of, in particular since I'm still using that IDE in my "day job".
As far as I know, this is not possible. There aren't any settings to control this and extensions can't block an editor from opening.
An extension COULD automatically close any tabs that were opened for a .exe file. So if you clicked on it and a tab opened, the extension could close it. I don't know if such an extension exists.
Otherwise you can create a feature request on github: https://www.github.com/microsoft/vscode/issues/new