Mdn reference как отключить в vs code

Good evening I would like to know how disabling the documentation popup is somewhat tedious

#Edit in vscode go to preference mdn

Comments (2)

Sadly, even after setting:

Seems to be bug. Maybe this should be reopened.

jasonwilliams commented on February 6, 2022

The Deno typescript plugin is able to get access to the editor config so it must be possible:
https://github.com/denoland/vscode_deno/blob/main/typescript-deno-plugin/src/index.ts#L24-L26

Hopefully someone has time to work a similar solution into the typescript styled plugin

Related Issues (20)

Enable autocomplete in styled function after installing `typescript-styled-plugin` HOT 2
autocomplete is not working in tsx file HOT 12
Complete property with semicolon when typing jsx style properites HOT 2
No syntax highlighting for `padding-inline` / `padding-block` HOT 3
Broken styles highlighting without interpolated variables
IntelliSense not working after updating vscode to 1.64 HOT 30
Intellisense not working on 1.7.2 HOT 1
Intellisense not working = a solution that worked for me, maybe it will work for you HOT 1
Intellisense on this extension not working HOT 5
Broken highlight when using a multiline prop typing in Typescript HOT 1
Smart tips not working after updating VSCode
Incorrect cursor position after css autocomplete HOT 11
Color picker does not register for color strings in .tsx files HOT 5
No color highlighting when using function that returns code HOT 4
vscode-styled-components doesn’t work when i use it with ‘ES7+ React/Redux/React-Native snippets’ extension HOT 4
wrong cursor position HOT 5
Add JSX highlight to styled components HOT 1
Publish ` vscode-styled-components` to Open VSX
Media query string interpolation error, «( expectedts-styled-plugin(9999)» HOT 3
When the prompt pops up and the prompt is selected with a carriage return, the mouse cursor automatically moves to the front of the colon HOT 5

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

Laravel

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML.

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

VSCode Power User

Ahmad Awais

Award-winning GitHub Star Open Sourcerer Google Devs Expert Dir. DevRel Mars Ingenuity Helicopter code contributor Node.js Foundation Community Committee Outreach Lead, Member Linux Foundation, OpenAPI BGB, DigitalOcean Navigator alt=»» width=»24″ height=»24″ />Author of various open-source dev-tools and software libraries used by millions of developers worldwide (including engineers at Google, Netflix, Amazon, Microsoft, Intel). alt=»» width=»24″ height=»24″ />TEDx Speaker (NodeConf, React Live, Next.js Conf). Awais has been listed as #1 JavaScript Trending Developer worldwide by GitHub. He’s the Sr. Director of Developer Relations @RapidAPI. He also created one of the top VSCode themes called Shades of Purple (used by millions of developers). Install SOP theme. Check out his work on corona-cli, Shades of Purple theme, wp-continuous-deployment, cgb, Emoji Log, and many more open-source projects on GitHub. alt=»» width=»24″ height=»24″ />Satya Nadella CEO of Microsoft, said Awais is an awesome example for developers alt=»» width=»24″ height=»24″ />Regular WordPress Core Developer alt=»✍️» width=»24″ height=»24″ />Member of SmashingMagazine Experts Panel, Featured/published author at CSS-Tricks, Tuts+, Scotch.io, TorqueMag, SitePoint. Connect with Awais on twitter @MrAhmadAwais.

Take Their Word for It

Shit, I didn’t know that. This tip is life changing to me!!

Zouhir ⚡Edge Microsoft | Google Dev Expert

Wow; the quality of the courses is outstanding. Really great work Awais Awesome work!

Alberto MedinaGoogle Developer Advocate | Ph.D CS

Suuuuper stoked for this. I just picked up my copy of NodeCLI course! I can’t wait to take my CLI skills to the next level. Keep up the great work @MrAhmadAwais

Alexander RomanoAssociate App Developer | SKF

Get Started Now!

Masterclass

All Nine Modules & Everything. This is the package you should buy to become a VSCode Power User.

alt=»» width=»24″ height=»24″ />21359 + ALREADY SOLD

Price excludes tax VAT/GST

RECOMMENDED!

EVERYTHING : Nine Modules

VIDEOS : All 65 VSCode Videos

EXPIRY : Single One Time Payment

UPDATES : Lifetime Free Course Updates

EXAMPLES : Over 200 VSCode Tips & Tricks

COMMUNITY : VSCODEpro Slack Free Access

EVERYTHING : Including all lessons & modules

VALUE FOR MONEY : 14 days refund (no Q/A)

alt=»» width=»24″ height=»24″ />21359 + ALREADY SOLD

Price excludes tax VAT/GST

Take Their Word for It

Shit, I didn’t know that. This tip is life changing to me!!

Zouhir ⚡Edge Microsoft | Google Dev Expert

Wow; the quality of the courses is outstanding. Really great work Awais Awesome work!

Alberto MedinaGoogle Developer Advocate | Ph.D CS

Suuuuper stoked for this. I just picked up my copy of NodeCLI course! I can’t wait to take my CLI skills to the next level. Keep up the great work @MrAhmadAwais

Alexander RomanoAssociate App Developer | SKF

Today for #devAdvent: the very hardworking @MrAhmadAwais! Awais is a WordPress Core member and TEDx speaker and he recently created a course to help people become VS Code Power Users. If you’re using VSCode as your editor, VSCode.pro is a fun/cool resource!

Sarah DrasnerJS Microsoft & Vuejs Core Team

Open Source work: «It’s very impressive«. — Won Automattic Design Award Trophy. The create-guten-block project is an awesome awesome contribution to the community — at AWP Gutenberg series.

Matt MullenwegCo-Founder of WordPress

I also just made the decision to move away from PHPStorm to VSCode. I mean, just one year in license fees pays for the VSCode.pro master package and I’ll learn from one of the best Just by going through the UI improvements videos, I can already see how the course will help me become #VSCODEpro

Jan KochMentor at WPMastery

«OMG awesome. How do you find those class names?» — Said in response to a VSCode tip shared by Awais on Twitter.

Dan AbramovCore Dev ReactJS at Facebook

It’s a 5 hour course that teaches you a huge amount of knowledge and after going through it myself, I can state that even as a fairly advanced user of VS Code, Awais taught me some neat tricks that I immediately am integrating into my workflow now.

Benjamin LannonVSCode Extensions Developer in NY

I’ve been using VSCode for a few months and I’m not a power user at all. Thanks to @MrAhmadAwais for creating an amazing course to help me bridge that gap in a short time. I highly recommend his course if you’re looking to level up your VSCode game.

Haris ZulfiqarFounder Avada | Engineer at WDS

If you’re looking to expand your VSCode knowledge, I have no doubt this course will be extremely useful. @MrAhmadAwais does great work.

Jeremy EnglertCore Contributor ZURB Foundation

Just grabbed @MrAhmadAwais’s #VSCODEpro course masterclass. If you use any code editor, make the move. Support Awais 🙂 he’s a top guy — does great work. → VSCcode.pro

Mike StottCore Contributor ZURB Foundation

I love this theme! Themes with more unique colors like purple are relatively rare, so it’s great to see purple represented here. It’s a fun theme, and it’s easy to read!

Ali SpittelTech Director WomenWhoCode

Kudos to the teacher @MrAhmadAwais for making the #VSCODEpro learning a breeze. I am on the 14th chapter and this is getting as exciting as a binge learning. Awais, your hard work is making a student’s life easy. You deserve great respect

Raghu VamsiSCRUM Master + Front End Dev

I always find him to be an excellent communicator, highly skilled, considerate, and extremely generous. He’s a pleasure to collaborate with and he’s produced some very impressive public and FREE #OpenSource work for developers to learn and benefit from. In my book, those are some of the best characteristics to have in a person. Awais is highly recommended.

Matt CromwellPartner/Head Community Impress.org

I’ve never known someone to create such useful things on a regular basis. Truly impressive sir. I mean it. You just pump stuff out. It’s incredible.

Lee PetersonCreative Lead at Rusty Dog Design

I’ve read over Awais’s tutorial a few times and implemented most of it. He’s the bee’s knees for this kind of stuff. — In ref to the WordPress & Gulp implementation via WPGulp.

Alex ColemanWeb Designer at LeftSideDesign

This is a gorgeous, high contrast theme that stands out without getting in the way. Especially great for doing developer talks and screencasts and maintained by a supremely dedicated expert in all the VSCode pro tips. The documentation itself is a thing of beauty, too. 5 Stars!

Shawn Swyx WangDev Experience @Netlify | Reactjs

Yes, Awais writes great WordPress tutorials and makes great looking themes and websites, but that’s not the only reason I endorse Awais. He is a great community member, he is a core contributor to WordPress and always helpful to other WordPress users. Also, he is a really nice guy, which is important.

Josh PollockLead Dev & Founder CalderaWP

Ahmad has written tutorials for me to publish at Tuts+ on a number of occasions, and I always appreciate his level of expertise both in the subject matter…, and in helping to educate others. I would hire Awais again for… training or consultancy in a heartbeat.

Japheth ThomsonDirector of Hosting at Human Made

I know Awais from his contributions to world wide web. His expertise in web & software technologies and his contributions to various open-source projects make it stand out of the crowd. I highly recommend Awais.

Jabran RafiqueTech Lead at Rated People

I’m really impressed with how much you are participating in the WordPress community! It’s pretty insane. You’re probably one of the most engaged people I have seen, ever.

Stanislav KhromovDev at Schibsted Media Group

It is extremely rare that you come across highly skilled talent like Awais! We worked together on several occasions over the years and his efficiency is beyond superior.

Emil UzelacWordPress Quality Control Specialist

Awais regularly contributes to WordPress core for code and UX improvements. He is one of the most passionate developers I have ever met with an insatiable desire to streamline the workflow of the process of everything he works on. He dives in head first to any new challenges and conquers them with his tenacity and intelligence which make Awais an invaluable asset to any project.

Mike AndreasenWordPress Expert at Codeable

Awais is a very thorough writer and he is extremely knowledgeable of the WordPress industry. He knows exactly what is going on in the WordPress community and his outreach is an addition to any blog. I would recommend him.

Daan TollOwner of WPLift

I switch syntax themes so often, but I haven’t felt the need to switch since using Shades of Purple for the past 6 months, it’s my new default — keep up the good work man!

Adam HollisterLead Developer at The British & Irish Modern Music Institute

Amazing job with balancing out the colors to ensure it’s not overloading the eyes. The comments, and markdown syntax semi-hidden state styling is also a good idea! If it’s not critical to always see this information then it makes sense to reduce it’s visibility. Nice job mate.

B . SOP Review

I jumped ship from Cobalt 2 by Wes to Shades of Purple theme by Ahmad Awais and I’m not looking back, beautiful shades of purple lighten up my code in a way that no other theme can, great job Awais!

IgnacioaalRails Hacker

At go6.media we always use Shades of Purple for all our PHP/HTML/JS/CSS and other languages. It’s so beautiful and easy to read, we also added some slight tweaks to make it even better and we could not be happier that we found it. Thank you!

WayneDevs at Go6 Media

Awais takes his extension seriously and fixed a bug for me overnight. A fantastic theme that is both attractive but more importantly, effective in bring your attention to the import parts of your code.

Mark PorterDev at PorterPeople

I started loving the Shades of Purple theme from its name 😉 After seeing images of the themes, I saw there was more and to get to know about the ‘more’, an installation will have to occur which did occur. After installation, I got to find out that the theme is super duper awesome than I thought… Welldone Ahmad Awais

Uche JudeSoftware Developer Andela

Just installed Shades of Purple and absolutely love it! Thank you for creating it! I love these colors! I also switched from Cobalt2. And just beginning a new job as a React.js dev, with it 🙂

Alexandra SpalatoJavascript & WordPress Developer

I started using SOP during the better release and ever since it has being a perfect choice for me. Love to see my IDE always with the shades of purple splash. It improved my overall workflow. Thanks @AhamadAwais for such work.

Ojo OluwasetemiJavaScript Dev & Teacher

Have been using Shades of Purple theme for the last couple of weeks and in love with it. Its fun writing code with those shades of purple Ajit BohraEngineer & Speaker @lubusIN

User and Workspace Settings

You can configure Visual Studio Code to your liking through its various settings. Nearly every part of VS Code’s editor, user interface, and functional behavior has options you can modify.

VS Code provides several different scopes for settings. When you open a workspace, you will see at least the following two scopes:

User Settings — Settings that apply globally to any instance of VS Code you open.
Workspace Settings — Settings stored inside your workspace and only apply when the workspace is opened.

In this article, we’ll first describe user settings as these are your personal settings for customizing VS Code. Later we’ll cover Workspace settings, which will be specific to the project you’re working on.

Settings editor

To modify user settings, you’ll use the Settings editor to review and change VS Code settings.

To open the Settings editor, use the following VS Code menu command:

On Windows/Linux — File > Preferences > Settings
On macOS — Code > Preferences > Settings

You can also open the Settings editor from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) with Preferences: Open Settings or use the keyboard shortcut ( ⌘, (Windows, Linux Ctrl+, ) ).

When you open the Settings editor, you can search and discover the settings you are looking for. When you search using the Search bar, it will not only show and highlight the settings matching your criteria, but also filter out those which are not matching. This makes finding settings quick and easy.

In the example below, the Side Bar location and file icon theme have been changed.

Modified settings in the Settings editor showing blue vertical bars to the left of them

Changes to settings are applied by VS Code as you change them. Modified settings are indicated with a blue line similar to modified lines in the editor.

The gear icon (More Actions. ⇧F9 (Windows, Linux Shift+F9 ) ) opens a context menu with options to reset the setting to its default value as well as copy the setting ID or JSON name-value pair.

Edit settings

Each setting can be edited by either a checkbox, an input or a dropdown. Edit the text or select the option you want to change to the desired settings.

An example setting with a dropdown

Settings groups

Settings are represented in groups so that you can navigate them easily. There is a Commonly Used group at the top, which shows popular customizations.

Below, the Source Control settings are focused by selecting Source Control in the tree view.

Settings editor with the Source Control section of the table of contents selected

Note: VS Code extensions can also add their own custom settings, and those settings will be visible under an Extensions section.

Changing a setting

As an example, let’s hide the Activity Bar from VS Code. The Activity Bar is the wide border on the left with various icons for different views such as the File Explorer, Search, Source Control, and Extensions. You might want to hide the Activity Bar to give the editor a little more room, or if you prefer to open views via the View menu or Command Palette.

Activity Bar display on the left of the editor

Open the Settings Editor ( kb((workbench.action.openSettings) ) and type «activity» in the Search bar. You should see at least five settings.

You can further limit the scope to just those settings under the Appearance group in the table of contents on the left. There should now be just three settings.

You can now check and uncheck the Workbench > Activity Bar: Visible setting to hide and unhide the Activity Bar. Notice that when you have changed the setting value to be different than the default value, you see a blue line to the left.

Activity Bar: Visible unchecked and Activity Bar is hidden

You can always reset a setting to the default value by hovering over a setting to show the gear icon, clicking on the gear icon, and then selecting the Reset Setting action.

Settings editor filters

The Settings editor Search bar has several filters to make it easier to manage your settings. To the right of the Search bar is a filter button with a funnel icon that provides some options to easily add a filter to the Search bar.

Modified settings

To check which settings you have configured, there is a @modified filter in the Search bar. A setting shows up under this filter if its value differs from the default value, or if its value is explicitly set in the respective settings JSON file. This filter can be useful if you have forgotten whether you configured a setting, or if the editor is not behaving as you expect because you accidentally configured a setting.

Settings editor with @modified filter showing changed settings

Other filters

There are several other handy filters to help with searching through settings.

Setting editor @ tag filter dropdown

Here are some of the filters available:

@ext — Settings specific to an extension. You provide the extension ID such as @ext:ms-python.python .
@feature — Settings specific to a Features subgroup. For example, @feature:explorer shows settings of the File Explorer.
@id — Find a setting based on the setting ID. For example, @id:workbench.activityBar.visible .
@lang — Apply a language filter based on a language ID. For example, @lang:typescript . See Language-specific editor settings for more details.
@tag — Settings specific to a system of VS Code. For example, @tag:workspaceTrust for settings related to Workspace Trust

The Search bar remembers your settings search queries and supports Undo/Redo ( ⌘Z (Windows, Linux Ctrl+Z ) / ⇧⌘Z (Windows, Linux Ctrl+Y ) ). You can quickly clear a search term or filter with the Clear Settings Search Input button at the right of the Search bar.

Extension settings

Installed VS Code extensions can also contribute their own settings, which you can review under the Extensions section of the Settings editor.

C++ extension settings in the Settings editor

You can also review an extension’s settings from the Extensions view ( ⇧⌘X (Windows, Linux Ctrl+Shift+X ) ) by selecting the extension and reviewing the Feature Contributions tab.

Python extension Settings list under Feature Contributions tab

Extension authors can learn more about adding custom settings in the configuration contribution point documentation.

settings.json

The Settings editor is the UI that lets you review and modify setting values that are stored in a settings.json file. You can review and edit this file directly by opening it in the editor with the Preferences: Open Settings (JSON) command. Settings are written as JSON by specifying the setting ID and value.

User settings.json open in the editor

The settings.json file has full IntelliSense with smart completions for settings and values and description hovers. Errors due to incorrect setting names or JSON formatting are also highlighted.

IntelliSense for settings.json open in the editor

Some settings can only be edited in settings.json such as Workbench: Color Customizations and show a Edit in settings.json link in the Settings editor.

Workbench: Color Customizations setting with Edit in settings.json link

Changing settings.json

As an example, lets change the editor line number color. Click the Edit in settings.json link and add the following JSON:

Here the line numbers in the editor for the settings.json file are now green.

settings.json editor with green line numbers

Remove the workbench.colorCustomizations setting code block to return the line number color to the default.

Note: The example above changes the editor line number for all Color Themes, but you can tune colors per specific Color Theme or even create your own Color Theme extension.

If you prefer to always work directly with settings.json , you can set «workbench.settings.editor»: «json» so that File > Preferences > Settings and the keybinding ⌘, (Windows, Linux Ctrl+, ) always opens the settings.json file and not the Setting editor UI.

Settings file locations

Depending on your platform, the user settings file is located here:

Windows %APPDATA%\Code\User\settings.json
macOS $HOME/Library/Application\ Support/Code/User/settings.json
Linux $HOME/.config/Code/User/settings.json

Reset all settings

While you can reset settings individually via the Settings editor Reset Setting command, you can reset all changed settings by opening settings.json and deleting the entries between the braces . Be careful since there will be no way to recover your previous setting values.

Workspace settings

Workspace settings are specific to a project and can be shared across developers on a project. Workspace settings override user settings.

Note: A VS Code «workspace» is usually just your project root folder. Workspace settings as well as debugging and task configurations are stored at the root in a .vscode folder. You can also have more than one root folder in a VS Code workspace through a feature called Multi-root workspaces. You can learn more in the What is a VS Code «workspace»? article.

You can edit via the Settings editor Workspace tab or open that tab directly with the Preferences: Open Workspace Settings command.

Settings editor with Workspace tab highlighted

All features of the Settings editor such as settings groups, search, and filtering behave the same for Workspace settings. Not all User settings are available as Workspace settings. For example, application-wide settings related to updates and security can not be overridden by Workspace settings.

Workspace settings.json location

Similar to User Settings, Workspace Settings are also stored in a settings.json file, which you can edit directly via the Preferences: Open Workspace Settings (JSON) command.

The workspace settings file is located under the .vscode folder in your root folder.

The File Explorer displaying settings.json under the .vscode folder

Note: For a Multi-root Workspace, workspace settings are located inside the workspace configuration file.

When you add a Workspace Settings settings.json file to your project or source control, the settings for the project will be shared by all users of that project.

Language-specific editor settings

One way to customize language-specific settings is by opening the Settings editor, pressing on the filter button, and selecting the language option to add a language filter. Alternatively, one can directly type a language filter of the form @lang:languageId into the search widget. The settings that show up will be configurable for that specific language, and will show the setting value specific to that language, if applicable.

When modifying a setting while there is a language filter in place, the setting will be configured in the given scope for that language. For example, when modifying the user-scope diffEditor.codeLens setting while there is a @lang:css filter in the search widget, the Settings editor will save the new value to the CSS-specific section of the user settings file.

Editing the CSS-specific user-scoped diffEditor.codeLens setting in the Settings editor

Note: If you enter more than one language filter in the search widget, the current behaviour is that only the first language filter will be used.

Another way to customize your editor by language is by running the global command Preferences: Configure Language Specific Settings (command ID: workbench.action.configureLanguageBasedSettings ) from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) which opens the language picker. Select the language you want. Then, the Settings editor opens with a language filter for the selected language, which allows you to modify language-specific settings for that language. Though, if you have the workbench.settings.editor setting set to json , then the settings.json file opens with a new language entry where you can add applicable settings.

Configure language-specific settings command typed up in the Command Palette

Select the language via the dropdown:

Select language dropdown

Now you can start editing settings specifically for that language:

Settings editor showing a specific language filter

Or, if workbench.settings.editor is set to json , now you can start adding language-specific settings to your user settings:

Suggestions for language-specific settings shown in the settings JSON file

If you have a file open and you want to customize the editor for this file type, select the Language Mode in the Status Bar to the bottom-right of the VS Code window. This opens the Language Mode picker with an option Configure ‘language_name’ language based settings. Selecting this opens your user settings.json with the language entry where you can add applicable settings.

Language-specific editor settings always override non-language-specific editor settings, even if the non-language-specific setting has a narrower scope. For example, language-specific user settings override non-language-specific workspace settings.

You can scope language-specific settings to the workspace by placing them in the workspace settings just like other settings. If you have settings defined for the same language in both user and workspace scopes, then they are merged by giving precedence to the ones defined in the workspace.

The following example can be pasted into a settings JSON file to customize editor settings for the typescript and markdown language modes.

You can use IntelliSense in settings.json to help you find language-specific settings. All editor settings and some non-editor settings are supported. Some languages have default language-specific settings already set, which you can review in defaultSettings.json by running the Preferences: Open Default Settings command.

Settings precedence

Configurations can be overridden at multiple levels by the different setting scopes. In the following list, later scopes override earlier scopes:

Default settings — This scope represents the default unconfigured setting values.
User settings — Apply globally to all VS Code instances.
Remote settings — Apply to a remote machine opened by a user.
Workspace settings — Apply to the open folder or workspace.
Workspace Folder settings — Apply to a specific folder of a multi-root workspace.
Language-specific default settings — These are language-specific default values that can be contributed by extensions.
Language-specific user settings — Same as User settings, but specific to a language.
Language-specific remote settings — Same as Remote settings, but specific to a language.
Language-specific workspace settings — Same as Workspace settings, but specific to a language.
Language-specific workspace folder settings — Same as Workspace Folder settings, but specific to a language.

Setting values can be of various types:

String — «files.autoSave»: «afterDelay»
Boolean — «editor.minimap.enabled»: true
Number — «files.autoSaveDelay»: 1000
Array — «editor.rulers»: []
Object — «search.exclude»:

Values with primitive types and Array types are overridden, meaning a configured value in a scope that takes precedence over another scope is used instead of the value in the other scope. But, values with Object types are merged.

For example, workbench.colorCustomizations takes an Object that specifies a group of UI elements and their desired colors. If your user settings set the editor backgrounds to blue and green:

And your open workspace settings set the editor foreground to red:

The result, when that workspace is open, is the combination of those two color customizations, as if you had specified:

If there are conflicting values, such as editor.selectionBackground in the example above, the usual override behavior occurs, with workspace values taking precedence over user values, and language-specific values taking precedence over non-language-specific values.

Settings and security

Some settings allow you to specify an executable that VS Code will run to perform certain operations. For example, you can choose which shell the Integrated Terminal should use. For enhanced security, such settings can only be defined in user settings and not at workspace scope.

Here is the list of settings not supported in workspace settings:

git.path
terminal.external.windowsExec
terminal.external.osxExec
terminal.external.linuxExec

The first time you open a workspace that defines any of these settings, VS Code will warn you and then always ignore the values after that.

Settings Sync

You can share your user settings across your VS Code instances with the Settings Sync feature. This feature lets you share settings, keyboard shortcuts, and installed extensions across your VS Code installs on various machines. You can enable Settings Sync via the Turn on Settings Sync command on the right of the Settings editor or on the Accounts Activity Bar context menu.

You can learn more about turning on and configuring Settings Sync in the Settings Sync user guide.

Common questions

VS Code says «Unable to write settings.»

If you try to change a setting (for example turning on Auto Save or selecting a new Color Theme) and you see «Unable to write into user settings. Please open user settings to correct errors/warnings in it and try again.», it means your settings.json file is ill-formed or has errors. The error can be as simple as a missing comma or incorrect setting value. Open the settings.json file with the Preferences: Open Settings (JSON) command and you should see the error highlighted with red squiggles.

How can I reset my user settings?

The easiest way to reset VS Code back to the default settings is to clear your user settings.json file. You can open the settings.json file with the Preferences: Open Settings (JSON) command in the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ). Once the file is open in an editor, delete everything between the two curly braces , save the file, and VS Code will go back to using the default values.

When does it make sense to use workspace settings?

If you’re using a workspace that needs custom settings but you don’t want to apply them to your other VS Code projects. A good example is language-specific linting rules.

Is there a way to disable “MDN References Intellisense” popup (for HTML & CSS) in VS Code?

This is in reference to disabling this specific feature, while leaving all other code hinting features active.

I am very familiar with the Settings GUI as well as settings.json and have searched extensively but none of the Intellisense/hints/suggestions configuration seems to apply to this particular popup.

Annotated screenshot indicating the popup I wish to disable

Answer

Just going to Code -> Preferences -> Settings
Search “editor hover enabled” and disable checkbox.

Attribution
Source : Link , Question Author : Scott , Answer Author : Artyom Knyazev

[css][html] Option to disable MDN Reference popups only (without effecting other functionalities) #97979

Pretty please give us an option to disable ONLY and ONLY those ‘MDN Reference’ info boxes but NOT the hover boxes alltogether.

Disabling Editor > Hover in Settings also disables other useful things like ColorPicker popup plugins depending on it etc. MDN info may be useful for some but most of the time it is just a HUGE annoyance for others.

Taking this idea one step further MDN Reference may be removed alltogether and/or make it an optional download for whoever needs it. I know it is there to help but it is also a source of problem too eager to get in the way between you and your code.

The text was updated successfully, but these errors were encountered:

Mainly HTML and CSS

Would like to see the same. Very annoying.

You are talking about the MDN Reference link, or the whole text?

I’m talking about the whole «box». Very intrusive, popping all the time, blocking my way when i need to see or select some text, element etc. When i try to click with mouse to select some code and all of a sudden MDN reference box pops open, i find myself accidentally clicked the link, my default browser launches. I know i can set a longer delay for the box to open but some really useful plugins (like color picker) would be delayed too. Just because of this i returned to Atom editor. Why not give a choice to disable/remove MDN Reference box?

You can turn off the automatic hover ( «editor.hover.enabled»: false ) and manually trigger it when you need it (e.g. for the colors): Command Show Hover (Ctrl + K, Ctrl + I) . Is that useful?
There are many extensions that provide hovers and ask each extensions author to provide settings for hover would work too, but might not happen for all extensions.

Sorry but not the same thing, hover functionality is really useful and very easy to get bits of information real quick (without key clicks or anything). If «hover» functionality is solely created for MDN Reference box in mind and other 3rd party plug-in developers kind of «hijacked» it for their own purpose then i can understand it would be a hard decision to «remove» or «disable» it from the codebase of VS Code. On the other hand if it is not the case and hover using plug-ins and MDN Reference hover boxes can coexist without effecting each other that means (at least to me) something is wrong with the logic the way this function is represented to users. It’s looking like «You like hover? You’ll have MDN whether you like it or not».
Answer to your question: I know i can turn-off hover, i turned it off and regretted it because of the side effects with the plugins. Using a color-picker (or whatever) with a hover gesture is way easy and way useful than enabling it with a key stroke. I stand by my request, i wish MDN Reference SHOULD be optional or better «opt-in» rather than mandatory.

Agree with megavolkan. MDN Reference should be optional.

If I understood correctly @megavolkan want’s neither the MDN Reference link nor the description.

If I understood correctly @megavolkan want’s neither the MDN Reference link nor the description.

I’d prefer the MDN Reference popup (and yes naturally including MDN reference link and the description) totally gone. But NOT the hover+popup functionality which has a purposeful usacase for plugins.
By the way i’m not against the «MDN Reference» itself. I understand it may be helpful for those who would prefer to display it for some reason. Therefore it should be initially disabled and then enabled in the settings if need be.

If I understood correctly @megavolkan want’s neither the MDN Reference link nor the description.

There are two different things, informations (MDN popup hovers), and tools (color picker).
MDN pop up is annoying, but color picker is awesome.

I want to disable the whole MDN box pop-up and not the other pop-ups. A way to disable it?

I want to disable the whole MDN box pop-up and not the other pop-ups. A way to disable it?

No. Not to my knowledge at least. This topic is aiming to make devs hear/acknowledge the issue and users demanding a solution.

It’d probably be better to pull the mdn hover functionality into it’s own plugin that’s installed by default (Built-in extension), but can be disabled independently.

That way it helps everyone in this thread above and could be updated/improved independently of vscode (for things like showing default css values).

I agree the general purpose of the pop up is good (e.g. color selector). I don’t use the MDN reference but I see how people could find it useful. However, I cannot count the number of times I randomly clicked the MDN link and it’s the only one annoying thing about VS code. I think other user suggestions of making it a third party plugin that people can choose to install is a great solution to this problem.

Maybe just change the delay to say something like 1000 that way if it is something you want it you can wait and it will show otherwise it gives you time to select something without it popping up right away.

Maybe just change the delay to say something like 1000 that way if it is something you want it you can wait and it will show otherwise it gives you time to select something without it popping up right away.

I have tried it. It is not practical and doesn’t address the main problem, just sliding it under the carpet.

I agree it would be nice to have the ability to remove just the MDN but setting the delay to 1000 actually solves my issue of accidentally clicking on it in a fast code entry instance. Just a thought not a perfect solution but for me it is better.

I agree it would be nice to have the ability to remove just the MDN but setting the delay to 1000 actually solves my issue of accidentally clicking on it in a fast code entry instance. Just a thought not a perfect solution but for me it is better.

Thanks for the tip — I didn’t think about increasing the delay. It isn’t an actual solution, as mentioned, but it is much less annoying with a longer delay. I’d rather wait a couple of seconds for something I need than to have it pop over what I’m looking at or accidently hitting that goofy MDN link.