-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Preview what actions will be run in commandline mode of the CmdPal #8344
Comments
@zadjii-msft - we need to consider the UX as I already put the history into the palette.. |
Yea, I've been thinking about that. The history is definitely better - but is there a sensible way of having both these things? (too lazy to bold results in the mockup) So in this case, the user is typing a command, and they could select the |
@zadjii-msft - some off-topics
Here how it goes:
So you can:
|
It's an app called XAML Studio, which is an absolute lifesaver. I certainly like the "tab complete" functionality you've suggested here. I dunno how hard it'd be to actually implement, I'm not sure how hard it would be to have multiple styles of text in a single text box. Maybe there's another type of control that would allow for it, but my XAML-fu is not that strong. |
Thanks! I will try to use it! |
Hey. I played for an hour with this. I will open a PR for some initial step 😊 |
Y A Y |
🎉This issue was addressed in #8515, which has now been successfully released as Handy links: |
This commit introduces another optional text block in palette that will be shown in the command line mode (above the history). This text block will either contain a list of parsed command lines or a description why the parsing failed Closes microsoft#8344 Closes microsoft#7284
So we've already got an open work item tracking "display the parse error (if any) in commandline mode", #7284. What if, when we determine that the commandline is valid, we then display what commands are about to be executed, instead of the parse error?
So if you type in
We'll parse that, and that won't generate an error message, it'll instead successfully turn into a
newTab(commandline="ssh user@server.com")
action. We'll then take that action, and callGenerateName
on it, and we'll get "Open a new tab, commandline: ssh user@server.com". We'll then display that text to the user, as a preview of what they're about to run.The text was updated successfully, but these errors were encountered: