refactor: don't hardcode substitute highlight (#1991)

* fix(highlight): don't hardcode substitute highlight * fix: use inverted colors
vscode-neovim · May 21, 2024 · 1b6bb7b · 1b6bb7b
1 parent 4dc0ea0
commit 1b6bb7b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/package.json b/package.json
@@ -338,6 +338,10 @@
                         },
                         "Search": {
                             "backgroundColor": "theme.editor.findMatchHighlightBackground"
+                        },
+                        "Substitute": {
+                            "backgroundColor": "theme.editor.foreground",
+                            "color": "theme.editor.background"
                         }
                     }
                 },

diff --git a/runtime/lua/vscode-neovim/highlight.lua b/runtime/lua/vscode-neovim/highlight.lua
@@ -55,11 +55,7 @@ local function setup_globals()
     Visual       = {},
     VisualNC     = {},
     VisualNOS    = {},
-    -- By default, it's linked to Search.
-    -- But Search highlighting defaults to using VSCode ThemeColor, potentially with some opacity.
-    -- When the decoration is "virtText", having a background color with opacity can
-    -- cause the virtual text to blend with the original content.
-    Substitute   = { fg='#282c34', bg='#98c379' },
+    Substitute   = {},
     Whitespace   = {},
     LineNr       = {},
     LineNrAbove  = {},