From f2ed66fb9c04c96bc1ac9d77a1b7b969d9626526 Mon Sep 17 00:00:00 2001
From: 924312 <924312@gmail.com>
Date: Tue, 27 May 2025 19:34:21 +1200
Subject: [PATCH 1/3] Update getting_started.md with colorscheme
 troubleshooting step

---
 docs/guide/getting_started.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/guide/getting_started.md b/docs/guide/getting_started.md
index 696e102af..aca8785ef 100644
--- a/docs/guide/getting_started.md
+++ b/docs/guide/getting_started.md
@@ -101,6 +101,15 @@ lua << EOF
 EOF
 ```
 
+#### Theme Troubleshooting
+If you find that your colorscheme appears correctly for a second and then 
+changes to not having full highlighting, you'll need to disable semantic 
+highlighting. 
+Add this line to the `on_attach` function.
+```lua
+client.server_capabilities.semanticTokensProvider = nil
+```
+
 #### Configure Additional Settings
 To further configure the server, you can supply settings to the setup table.
 For example, you can set the code formatting preset to one true brace style

From ce59dc884d94b02fa5c3ddcd777d78be7ccc3beb Mon Sep 17 00:00:00 2001
From: 924312 <924312@gmail.com>
Date: Tue, 27 May 2025 19:40:46 +1200
Subject: [PATCH 2/3] Update getting_started.md - Added troubleshooting for
 brackets after cmdlets when autocompleting

---
 docs/guide/getting_started.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/guide/getting_started.md b/docs/guide/getting_started.md
index aca8785ef..048765204 100644
--- a/docs/guide/getting_started.md
+++ b/docs/guide/getting_started.md
@@ -131,3 +131,11 @@ require('lspconfig')['powershell_es'].setup {
 	settings = { powershell = { scriptAnalysis = { settingsPath = custom_settings_path } } }
 }
 ```
+
+#### Autocomplete Brackets Troubleshooting
+If you're using `blink.cmp` and you're getting brackets when autocompleting 
+cmdlet names, you'll need to add `{ "ps1", "psm1" }` to the blocked filetypes 
+for both `kind_resolution` and `semantic_token_resolution` in the plugin's 
+config file.
+
+[Blink.cmp completion reference](https://cmp.saghen.dev/configuration/reference#completion-accept)

From 39d71dec87c67d4c29c2508e6d44915446904434 Mon Sep 17 00:00:00 2001
From: 924312 <924312@gmail.com>
Date: Tue, 27 May 2025 19:45:21 +1200
Subject: [PATCH 3/3] Update getting_started.md - Added link to reference with
 more additional settings

---
 docs/guide/getting_started.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/guide/getting_started.md b/docs/guide/getting_started.md
index 048765204..aa27742f9 100644
--- a/docs/guide/getting_started.md
+++ b/docs/guide/getting_started.md
@@ -121,6 +121,8 @@ require('lspconfig')['powershell_es'].setup {
 	settings = { powershell = { codeFormatting = { Preset = 'OTBS' } } }
 }
 ```
+For a more complete list of options have a look at this schema: 
+[nvim-lsp-installer powershell_es reference](https://github.com/williamboman/nvim-lsp-installer/blob/main/lua/nvim-lsp-installer/_generated/schemas/powershell_es.lua)
 
 You can also set the bundled PSScriptAnalyzer's custom rule path like so:
 ```lua