-
Notifications
You must be signed in to change notification settings - Fork 234
Simplify PSES CLI so startup with non-Code editors is easier #1855
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
Comments
How definitive is this? Do you intend to completely rewrite the CLI/introduce "breaking changes" with this? I imagine that any changes you would make would have to be backwards compatible. But I have to ask, since my PSES manual controller is dependent on how your CLI works. |
I don't intend to make breaking changes. The best coverage I have for that is PowerShellEditorServices/test/emacs-test.el Lines 48 to 54 in 9416a8a
and PowerShellEditorServices/test/vim-test.vim Lines 6 to 13 in 9416a8a
|
**** |
It takes way too many arguments to launch PSES correctly, which is blocking #1829. Once we simplify this, we could conceivably add a
-lsp
flag to PowerShell itself that would simplify it even further.The text was updated successfully, but these errors were encountered: