Skip to content

@arcticicestudio arcticicestudio released this Apr 11, 2019 · 1 commit to develop since this release

Release Date: 2019-04-11 Project Board Milestone

Features

UI

Background color of inactive keyboard focused list items#107#116 (⊶ 3e35efb) by @octref
↠ Added support for list.inactiveFocusBackground theme key used for the background color of the selected item when navigating the file explorer list with the keyboard and moving the focus to another UI component (like the editor).
It has been set to nord2 with a opacity of 80% to match the style of inactive list items that were focused without the keyboard (list.inactiveSelectionBackground).

Before

After

Improvements

Syntax

Perl sigils same color as variables#67 (⊶ 698d9ba) by @marcusramberg
↠ To ensure a consistent highlighting Perl Sigils are now also colorized like variables since they are actually part of the variable. They are now less distracting by using the same color like the variable itself instead of handling them as prefixed characters or a keyword.

Before

After

Correct colors for JavaScript objects#115 / #97 (⊶ b0c399c) by @samchamberland
↠ Previously JavaScript objects colorized with nord7 caused by a superfluous definition of the meta.var.expr scope selector. This has been changed. This has been changed to correctly use nord4 for variables.

Before

After

Better function parameter highlighting in Python#108#113 (⊶ 840b36c) by @Al2Me6
↠ Previously the highlighting for function parameters in Python were colorized with the same color like the function itself (nord8) instead of nord4. This has been improved by removing the too generic scope meta.function-call from the source.python scope.

Before

After

Improved interpolated string literals#106#114 (⊶ e13ded1) by @varog-norman
↠ Improved the color for function braces in string templates to use nord6 instead of nord14. Begin and end characters of an interpolated string literal ${} are now also colorized as keyword (nord9) for better visual distinction.

Before

After

Comment Color Brightness#117/#14/#72#118 (⊶ 7e3881b)
↠ Implemented the frequently requested and long-time outstanding increase of the comment color (nord3) brightness by 10% from a lightness level of ~35% to ~45%.

Please see arcticicestudio/nord#94 for all details about this design change decision!

For users who would like to use the previously used coloring VS Code allows to customize and override styles of a specific theme through the user settings. To override the highlighting color of comments only for Nord the following snippet can be added to the settings (JSON) file:

Before

After

"editor.tokenColorCustomizations": {
  "[Nord]": {
    "comments": "#4C566A"
  }
}

Please see the official documentation about user and workspace settings for more details how to customize and configure VS Code.

UI

Decreased opacity for peek view match highlighting#99#112 (⊶ 7d9547e) by @octref
↠ Previously the opacity for peek view match highlighting was too bright that made it almost impossible to read the underlying text. This has been improved by decreasing the opacity of the used color (nord8) to 30%.

Before

After

Cleaner Git diff view highlighting#105 (⊶ 63fa7d9) by @danfo

Previously the Git diff view used nord14 with a opacity of 30% to highlight added/modified elements causing some syntax elements like comments to be bad readable. This has now been changed to use nord9 with a opacity of 20% instead to ensure a better readability and general clearer visual appearance. Also the previously used theme keys diffEditor.insertedTextBorder and diffEditor.removedTextBorder have been removed for a more clutter-free style.

Before

After

There is still a lot of potential to improve the highlighting for Git diff views. The feature request Microsoft/vscode#71663 has been requested from the VS Code team to allow theme authors to improve the styles of syntax elements within Git diff scopes which would solve the problem of unreadable elements.

Bug Fixes

UI

Tabs in split views can not be dragged and moved#98#104 (⊶ 924c190) by @mdogadailo and @sdr0x07b6
↠ Previously the editorGroup.border theme key used a transparent color that caused tabs in split views to not being moveable anymore since the underlying logic removes some requires CSS classes. This has been fixed by to a opacity of 1% to fix the tab usage while still keeping the theme ambience (almost invisible for the human eye).


The full changelog ist available here

Assets 2
You can’t perform that action at this time.