Skip to content

Add useful info to Getting Started #2231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add useful info to Getting Started #2231

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f2ed66f
Update getting_started.md with colorscheme troubleshooting step
924312 May 27, 2025
ce59dc8
Update getting_started.md - Added troubleshooting for brackets after …
924312 May 27, 2025
39d71de
Update getting_started.md - Added link to reference with more additio…
924312 May 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/guide/getting_started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -112,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
Expand All @@ -122,3 +133,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)