Change:
default: false }, 'terminal.integrated.commandsToSkipShell': { <del> markdownDescription: localize('terminal.integrated.commandsToSkipShell', "A set of command IDs whose keybindings will not be sent to the shell but instead always be handled by VS Code. This allows keybindings that would normally be consumed by the shell to act instead the same as when the terminal is not focused, for example `Ctrl+P` to launch Quick Open.nn---nnMany commands are skipped by default. To override a default and pass that command's keybinding to the shell instead, add the command prefixed with the `-` character. For example add `-workbench.action.quickOpen` to allow `Ctrl+P` to reach the shell.nn*The following list of default skipped commands is truncated when viewed in Settings Editor. To see the full list, [open the default settings JSON](command:workbench.action.openRawDefaultSettings 'Open Default Settings (JSON)') and search for the first command from the list below.*nn---nnDefault Skipped Commands:nn{0}", DEFAULT_COMMANDS_TO_SKIP_SHELL.sort().map(command => `- ${command}`).join('n')), </del> <ins> markdownDescription: localize('terminal.integrated.commandsToSkipShell', "A set of command IDs whose keybindings will not be sent to the shell but instead always be handled by VS Code. This allows keybindings that would normally be consumed by the shell to act instead the same as when the terminal is not focused, for example `Ctrl+P` to launch Quick Open.nn&nbsp;nnMany commands are skipped by default. To override a default and pass that command's keybinding to the shell instead, add the command prefixed with the `-` character. For example add `-workbench.action.quickOpen` to allow `Ctrl+P` to reach the shell.nn&nbsp;nnThe following list of default skipped commands is truncated when viewed in Settings Editor. To see the full list, [open the default settings JSON](command:workbench.action.openRawDefaultSettings 'Open Default Settings (JSON)') and search for the first command from the list below.nn&nbsp;nnDefault Skipped Commands:nn{0}", DEFAULT_COMMANDS_TO_SKIP_SHELL.sort().map(command => `- ${command}`).join('n')), </ins> type: 'array', items: { type: 'string'

Discussion:
Issue Type: <bBug</bRepro settings Bug The setting description has a pair of white bars: <img width="1390" alt="Screen Shot 2020-07-25 at 12 57 39 AM" src="https://user-"These are markdown horizontal rules but look out of place. I think they are the only place I've seen them used in the settings UI VS Code version: Code - Insiders 1.48.0-insider (, 2020-07-24T05:51:27.957Z) OS version: Darwin x64 19.6.0 <details<summarySystem Info</summary </details<!-- generated by issue reporter --
I these as part of my PR . IMO this setting is unusual in its complexity, and the lines are intended to help the user parse the large quantity of information being presented.
I think they look alright personally, maybe a little heavy if anything?
This is the only setting I see that uses them so I feel they look out of place. A normal paragraph break the sections would probably work If we keep the horizontal rules, my recommendations would be: Add top and bottom padding to them Adjust the color to be less bright Potentially adjust the width to only span part of the text width may be able to provide better suggestions
I agree with suggestions
Using Developer Tools I the following to the first element created by the markdown: Result is: ! Then I and applied the styling to both lines to get this: ! And with the default light theme: ! Is that more acceptable?
What does it look like with a normal paragraph break?
! Or removing the italics and splitting that into its own para: !
The paragraphs are just as impactful as the rules imo.
The second example with the newlines look good to me. Thanks for taking a look! We may also want to check in the css to make the horizontal rules look better since settings from extensions could still use them