Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit ea34995

Browse files
Add note about accidentally disabling completions (#4062)
Per #4059.
1 parent bb8aaca commit ea34995

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

‎docs/troubleshooting.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,19 @@ Script analysis is provided by the [PSScriptAnalyzer][] project on GitHub. If th
3636
message starts with `[PSScriptAnalyzer]` or if you are getting faulty script diagnostics
3737
(red and green squiggly lines under PowerShell in scripts) please [open an issue there][].
3838

39+
## Completions aren't appearing
40+
41+
First, please ensure that the extension itself has properly started. Do this by opening
42+
the PowerShell Integrated Console and checking the value of the variable `$psEditor`,
43+
it should return a version and other fields. If it does not, you're probably in a
44+
different "PowerShell" terminal in VS Code, and not the extension's integrated console.
45+
So please open a bug about your extension failing to start instead.
46+
47+
If the extension _is_ started and the PSIC functional, completions should appear! Please
48+
double-check that your `editor.suggest.showFunctions` VS Code setting is `true`, as
49+
setting it to `false` _will_ disable completions (from all extensions). You may also want
50+
to check other related settings under "Text Editor -> Suggestions" in VS Code.
51+
3952
## Double-click isn't selecting the whole variable
4053

4154
VS Code provides a default set of word separators, that is, characters that split words

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /