You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@adusamr It is not clear to me from the issue description what is expected and what is actually happening. Can you please update the issue and let us know what you expect and what you are observing. Thanks.
Then the real problem or undocumented behavior is "single language-specific settings is preceding to multiple language-specific settings" even if the single language-specific settings are default settings and the multiple language-specific settings are user settings.
In the image, the right column is user's settings.json.
The middle column is plaintext and its font size is 20 and word wrap is off. The "[markdown][plaintext]" user settings is correctly working.
The left column is markdown.
Its font size is 8, which means the "[markdown]" user settings is preceding to the "[markdown][plaintext]" user settings.
And word wrap is on, which means the "[markdown]" default settings is preceding to the "[markdown][plaintext]" user settings.
If you uncomment the "editor.wordWrap": "off" line in the "[markdown]" user settings (and reopen markdown.md), now you can see word wrap is off.
Yes, single language specific settings takes precedence over multiple language specific settings. I will move this to our docs repo to make sure it is documented.
sandy081
changed the title
Cannot overwrite file type specific settings unless exactly specify that file type
Document that single language specific settings take precedence over multi language specific settings
Nov 13, 2024
Does this issue occur when all extensions are disabled?: Yes/No
defaultSettings.json is like this:
In user's settings.json,
or
do not overwrite these settings in markdown.
Only
can overwrite these settings.
I don't know whether this happens for other settings.
I found this when testing microsoft/vscode#233503 (comment)
The text was updated successfully, but these errors were encountered: