-
Notifications
You must be signed in to change notification settings - Fork 293
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
Only show notebook commands in Command Palette when a notebook is active #2636
Comments
Thanks for the suggestion. I'm not sure if we can control that, but I'll take a look. |
I saw there is |
Yeah, I'm not fully sure if we want to make this distinction. But at this point we do have a lot of data science specific commands, so it might be worth giving them their own category. We'll discuss it at triage. |
I think it's better to hide the unnecessary commands, once that's done, we might not need a separate category. If in notebook hide refactoring commands as those aren't supported. Doing this will reduce the commands. I think the main problem is the fact that we don't do a good job at hiding commands when they aren't relevant. It's just turning into a poorly managed (or unmanaged) list. |
There are a couple options here. Maybe both. We can disable and hide commands that shouldn't be visible in our command palette. And we can create a new prefix. We should figure out what we should do. |
Talking to Rong, we decided that the best course of action is to just filter out commands that are no applicable to our scenarios. We'll need to coordinate with the core extension to define the execution contexts. |
This is mostly working except for 'Run Selection in Interactive window' does not seem to show up as a command. That used to be there (seems like a regression then). I'll enter another bug for that. |
When I call out the Command Palette while using notebook editor, there are too many commands appearing which doesn't support the notebook editor at all.
Please consider a way to only show notebook editor commands or make them distinguishable from other Python script commands.
The text was updated successfully, but these errors were encountered: