-
Notifications
You must be signed in to change notification settings - Fork 27
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.
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
Add completions support to this plugin #69
Comments
We originally had vscode suggestions for subcommands but the thing that makes it difficult in nushell is that subcommands are delimited by space. So, every space you type would trigger the subcommand list. This because annoying so we removed it. I think the code may still be there but commented out. I'm sure there's a better way to do it. Generating parameters and such may be different though. We'd accept a PR for any piece of this, assuming it works better than the original implementation. :) |
What about generating completions by some shortcut for instance
I am not sure I personally can do it. |
We could do something like that but a big problem is that we don't have a LSP right now. So, I think that means that we'd have to put all these things in typescript i.e. all options, command parameters, etc. Or, we'd have to shell out and call nushell for each of these and parse the return - probably would be non-performant. |
Added. Tracking issue is here #91 |
Many thanks! ❤️ 🚀 It may be a game changer for me. |
Automatically obtain all available completions and use them while editing scripts: suggesting command options for instance. It would be a neat feature. 😄
The text was updated successfully, but these errors were encountered: