To turn off minimap in VS Code, you can directly implement it by setting items or modifying the JSON configuration file. The specific steps are: 1. Open settings (shortcut key Ctrl, or Cmd,); 2. Search for the keyword "minimap"; 3. Uncheck the "Editor: Minimap" option or add the configuration "editor.minimap.enabled": false. If you want to partially hide, you can adjust the width to display narrowly, turn off the auto-expanded scrollbar or just show the slider. Suitable for users who are tight on screen space or are accustomed to navigation with vertical scroll bars, especially for front-end development, profile editing or note writing scenarios.
If you think the side minimap (code thumbnail) is in the way when using VS Code, and want to turn it off, it is actually very simple. You only need to change a few settings to do it.

How to close minimap in VS Code?
VS Code provides direct settings to control whether the minimap is displayed or not. You can search for keywords in settings and then check the corresponding options.

The steps are as follows:
- Open settings: You can use the shortcut keys
Ctrl ,
(Windows/Linux) orCmd ,
(Mac) - Search for keyword "minimap"
- Find "Editor: Minimap" or modify the JSON configuration file directly and add:
"editor.minimap.enabled": false
This way you can completely hide the minimap.

What if you just want to hide partially?
Sometimes you may not want to turn it off completely, but rather want to adjust its behavior. For example, it only appears when needed, or reduces the width.
You can try the following settings:
- Adjust width:
"editor.minimap.size": "narrow"
- Turn off the auto-expand scrollbar:
"editor.minimap.showSlider": "mouseover"
- Show only the slider without the content:
"editor.minimap.renderCharacters": false
These settings allow you to retain the functionality of minimap but reduce its interference with vision.
Which users are suitable?
If you are a developer with relatively tight screen space, or are used to navigation with vertical scroll bars, minimap may become a redundant existence. Especially when writing front-end, configuration files, or writing notes, closing minimap can make the editing area more abundant.
And for those who like to quickly browse the entire file structure, minimap is helpful.
Basically that's it. You can choose whether to turn off completely according to your habits, or just do some fine-tuning.
The above is the detailed content of How to hide the minimap in vscode settings?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to change the default terminal in VSCode: setting through a graphical interface, editing settings.json file, and temporary switching. First, open the settings interface and search for "terminalintegratedshell" and select the terminal path of the corresponding system; secondly, advanced users can edit settings.json to add "terminal.integrated.shell.windows" or "terminal.integrated.shell.osx" fields and escape the path correctly; finally, you can enter "Terminal:SelectD through the command panel

1. Confirm whether the command is installed 2. Check the terminal shell type 3. Update the PATH environment variable 4. Restart VSCode or terminal. When you enter a command in the VSCode terminal, you should first check whether the command has been installed correctly and can be verified through other terminals of the system; secondly, confirm the shell type used by VSCode and check its configuration file; then make sure that the path where the command is located has been added to the PATH environment variable, and manually add and reload the configuration if necessary; finally close and reopen the terminal or restart VSCode to make the changes take effect.

When the "Timedoutwaitingforthedebuggertoattach" issue occurs, it is usually because the connection is not established correctly in the debugging process. 1. Check whether the launch.json configuration is correct, ensure that the request type is launch or attach and there is no spelling error; 2. Confirm whether the debugger is waiting for the debugger to connect, and add debugpy.wait_for_attach() and other mechanisms; 3. Check whether the port is occupied or firewall restricted, and replace the port or close the occupied process if necessary; 4. Confirm that the port mapping and access permissions are configured correctly in a remote or container environment; 5. Update VSCode, plug-in and debug library versions to solve potential

VSCode workspace is a .code-workspace file that saves project-specific configurations. 1. It supports multi-root directory, debug configuration, shortcut key settings and extension recommendations, and is suitable for managing different needs of multiple projects. 2. The main scenarios include multi-project collaboration, customized development environment and team sharing configuration. 3. The creation method is to save the configuration through the menu File>SaveWorkspaceAs.... 4. Notes include distinguishing between .code-workspace and .vscode/settings.json, using relative paths, and avoiding storing sensitive information.

There are two ways to set environment variables for VSCode terminals on Linux: one is to use the terminal.integrated.env.linux configuration item to define variables that are only used by VSCode; the other is to modify the shell configuration file to take effect globally. 1. In VSCode, add variables such as "MY_VAR":"my_value" by setting the terminal.integrated.env.linux field. This method only affects the VSCode terminal; 2. Modify shell configuration files such as ~/.bashrc or ~/.zshrc and add exportMY

To set debug environment variables in VSCode, you need to use the "environment" array configuration in the launch.json file. The specific steps are as follows: 1. Add "environment" array to the debugging configuration of launch.json, and define variables in key-value pairs, such as API_ENDPOINT and DEBUG_MODE; 2. You can load variables through .env files to improve management efficiency, and use envFile to specify file paths in launch.json; 3. If you need to overwrite the system or terminal variables, you can directly redefine them in launch.json; 4. Note that

To access the settings.json file of VSCode, you can directly open it through the command panel (Ctrl Shift P or Cmd Shift P). The default storage location of the file varies according to the operating system. Windows is in %APPDATA%\Code\User\settings.json, macOS is in $HOME/Library/ApplicationSupport/Code/User/settings.json, Linux is in $HOME/.config/Code/User/

Enable Git automatic pull (autofetch) in VSCode needs to be implemented by configuring Git and VSCode settings. 1. Configure Git to remotely get all branches: execute gitconfig --globalremote.origin.fetch "refs/heads/*:refs/remotes/origin/*". 2. Turn on automatic fetch in VSCode: Set "git.autofetch":true to execute gitfetch regularly. 3. Optional installation extensions such as GitLens or AutoFetchforGit are more powerful
