You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: custom-completions/dotnet/README.md
+3-30Lines changed: 3 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,33 +22,6 @@ For hand-crafted completions, see other completions like the ones generated from
22
22
23
23
## .NET SDK 10 and `dotnet completions`
24
24
25
-
From the .NET SDK version 10 onwards, the `dotnet` CLI offers `dotnet completions script nushell` that generaltes a Nushell external completer configuration.
26
-
Unfortunately, it is not directly pluggable, but more of a mix of generated forwarding completer and manual configuration integration guide:
27
-
28
-
```nushell
29
-
# Add the following content to your config.nu file:
30
-
31
-
let external_completer = { |spans|
32
-
{
33
-
dotnet: { ||
34
-
dotnet complete (
35
-
$spans | skip 1 | str join " "
36
-
) | lines
37
-
}
38
-
} | get $spans.0 | each { || do $in }
39
-
}
40
-
41
-
# And then in the config record, find the completions section and add the
42
-
# external_completer that was defined earlier to external:
43
-
44
-
let-env config = {
45
-
# your options here
46
-
completions: {
47
-
# your options here
48
-
external: {
49
-
# your options here
50
-
completer: $external_completer # add it here
51
-
}
52
-
}
53
-
}
54
-
```
25
+
From the .NET SDK version 10 onwards, the `dotnet` CLI offers `dotnet completions script nushell` which generaltes a Nushell external completer configuration,
26
+
but in an outdated format.
27
+
As such, it can not be used with current Nushell versions.
0 commit comments