There are many articles on how to customize with VScode, but there is no page that can be finished in one shot (it is natural because the usage differs depending on the person), so I decided to summarize my customization.
First of all, I will write about how I use VScode and what I want to use.
The most common is to write python code. This is because I mainly use machine learning in my research, so I want to make it easier to write here. There is also the option of jupyter, but I don't want to use it too much due to customizability issues. (Completely likes and dislikes)
Also, I think it's okay to leave everything to me, but I also want to write a web application using Flask, which I make as a hobby, using VScode.
I also want to manage the version on GitHub, so I want to make it easier.
Finally, I want to be able to use key bindings so that I can write code without moving my hand with the mouse.
This is a desire, but I will study to master the previously frustrated vim keybindings.
This is the application that I am currently thinking about.
As you can see, it's like a self-introduction with a feeling of a fledgling programmer, but I will customize VScode to realize the above. (I will write a memorandum about what I have already introduced)
I will write the miscellaneous feelings myself, but I will link to the introduction.
Introduction method https://qiita.com/nanamesincos/items/5c48ff88a4eeef0a8631
This is Miso in the foreground, but first of all, it is an article about my own Japanese localization.
I personally think that Japaneseization should not be done (because it may not be possible to obtain secondary information or information in the first place because it is not possible to obtain information overseas).
However, I have translated it into Japanese because it may interfere with the use of VS code due to my English ability.
I would like to refer to something like VScode best practices in English-speaking countries.
Introduction method https://qiita.com/blue0513/items/2634fcb3757629124c87
I have an impression that this is a good idea. Maybe it's just not coded enough to realize the awesomeness of AI.
Normally, it is enough to put VScode's python extension function normally.
It's just cool, so it feels like I'm putting it in.
Python Extension Pack
Installation link (You should click Install from here, or you will be told to open the .py file with VScode) https://marketplace.visualstudio.com/items?itemName=donjayamanne.python-extension-pack
A loved one who automatically installs various useful extensions for python.
For the time being, if you put this in, you can start writing python code. Let's put this in.
Complementary features for various languages included in the Python Extension Pack.
Very amazing ().
Seriously the most useful. Because it can be complemented to the integrated development environment (although it is derived from the integrated development environment because it is a complementary function of Visual Studio in the first place) I even feel like I can't write code without it.
(Maybe it was derived from AI all the time. Then maybe this is all that is needed?)
Not an extension, but how to install https://qiita.com/_meki/items/5b4f06318f1a0986c55c
Since I often write python code for machine learning, I use Anaconda to put in all the computing libraries.
In addition to that, since Anaconda functions are used for creating virtual environments, whether or not Anaconda Prompt can be used on the VS code terminal has a strong effect on comfort.
A virtual environment is indispensable because we end up using the python2 system for various reasons.
However, I introduced it because I can only use Powershell or Command Prompt without changing the settings.
It's comfortable because you don't have to open Anaconda Prompt in a separate window.
I have to study setting.json.
Introduction method https://qiita.com/firedfly/items/00c34018581c6cec9b84
Introduced because I thought that the code became bright red in VScode and the syntax error was hard to see As a result, the code that follows the rules is automatically generated to improve readability, and errors are easier to see, so I'm very old.
For the time being, this is the one I am currently using.
It is also a memorandum, so I would like to update it from time to time.