-
Notifications
You must be signed in to change notification settings - Fork 636
Deactivate command completion on empty lines, to avoid long pause times #657
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
Conversation
When attempting command completion on an empty/blank line, Bash will attempt to resolve all possibilities, which can take several seconds. Worse yet, this is easy to trigger -- accidentally press tab after enter instead of before. So, deactivating by default. Signed-off-by: David Alayachew <[email protected]>
…ty or blank lines Signed-off-by: David Alayachew <[email protected]>
|
This resolves git-for-windows/git#5289. |
|
/updpkgsums The workflow run was started. |
Signed-off-by: Matthias Aßhauer <[email protected]>
dscho
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
|
/deploy git-extra The i686/x86_64 and the arm64 workflow runs were started. |
|
/add relnote feature Pressing the Tab key in an empty line in Git Bash no longer causes the session to "freeze". The workflow run was started |
Pressing the Tab key in an empty line in Git Bash [no longer causes the session to "freeze"](#657). Signed-off-by: gitforwindowshelper[bot] <[email protected]>
When attempting command completion on an empty/blank line, Bash will attempt to resolve all possibilities, which can take several seconds. Worse yet, this is easy to trigger -- accidentally press tab after enter instead of before.
So, deactivating by default.