Skip to content
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

Prompt user with info about terminal config, add settings search by @id, and add sendToShell setting #110987

Merged
merged 18 commits into from
Nov 23, 2020

Conversation

meganrogge
Copy link
Contributor

Use @id: to search for one or more comma separated settings ids

Use keyboard shortcuts on the terminal corresponding to terminal.integrated.commandsToSkipShell commands and see an alert to configure terminal settings. Clicking Configure or Don't show again should result in never seeing the prompt again as the same user. Clicking the x on the prompt will show the prompt again the next time it's triggered.

Set terminal.integrated.sendToShell: true and use any key-bindings that trigger something to happen in the terminal. They should work and not be handled by the workbench. For example, Ctrl+E should jump to the end of the line instead of opening the quick pick.

You should still be able to use Ctrl+1-9 to navigate around the editor groups.

@meganrogge meganrogge added this to the November 2020 milestone Nov 20, 2020
@meganrogge meganrogge self-assigned this Nov 20, 2020
@meganrogge meganrogge changed the title Add prompt alerting user about terminal config, settings search by @id, and sendToShell setting Prompt user with info about terminal config, add settings search by @id, and add sendToShell setting Nov 20, 2020
@roblourens roblourens self-requested a review November 21, 2020 19:48
Copy link
Member

@roblourens roblourens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Built this and tried it out and I'm wondering, maybe I should only ever see this notification once. It's really easy to trigger, and my muscle memory is just to press escape when I want it to go away. Then I end up seeing it over and over.

@roblourens
Copy link
Member

You don't have to keep merging master into your PR, unless there are conflicts to resolve or some new change that you want to base this on.

@egamma egamma mentioned this pull request Nov 23, 2020
65 tasks
@meganrogge
Copy link
Contributor Author

meganrogge commented Nov 23, 2020

Built this and tried it out and I'm wondering, maybe I should only ever see this notification once. It's really easy to trigger, and my muscle memory is just to press escape when I want it to go away. Then I end up seeing it over and over.

@roblourens made this change

@roblourens roblourens self-requested a review November 23, 2020 17:15
@meganrogge meganrogge force-pushed the merogge/terminal-settings branch from a8e6a2e to 8fe20e8 Compare November 23, 2020 19:17
@roblourens roblourens self-requested a review November 23, 2020 22:37
@roblourens roblourens merged commit 10d92e5 into master Nov 23, 2020
@roblourens roblourens deleted the merogge/terminal-settings branch November 23, 2020 22:51
@github-actions github-actions bot locked and limited conversation to collaborators Jan 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants