-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
'git add --interactive' built-in doesn't exit list menu on empty input #2729
Comments
Are you sure about that? I can reproduce, but only with pseudo console support enabled... |
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes git-for-windows#2729 Signed-off-by: Johannes Schindelin <[email protected]>
@satsuper once https://dev.azure.com/git-for-windows/git/_build/results?buildId=58748&view=logs&j=5437d6e9-5c1a-5300-9fd3-4614558e3141 finishes, could you download the installer or PortableGit from its artifacts and verify that #2730 fixes this? |
@dscho I can confirm it works with Pseudo Consoles enabled with your build.
So it turns out I must have installed with that option enabled some time ago and then installed a newer version without that option enabled. In |
Oy, that's a bug in the installer, then... I'll try to take care of that later today. |
As noted in git-for-windows/git#2729 (comment), when a user enabled support for Pseudo Consoles and then reinstalled to disable it, by mistake the Pseudo Console support would _still_ be enabled. The reason? We only write `/etc/git-bash.config` to enable the Pseudo Console support, but not when we disable it (because it is disabled by default, anyway). However, we failed to remove that file upon uninstall/upgrade. Signed-off-by: Johannes Schindelin <[email protected]>
@satsuper I just opened and merged git-for-windows/build-extra#299, and then started https://dev.azure.com/Git-for-Windows/git/_build/results?buildId=58754&view=results to build new Git artifacts for testing. |
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
A bug with enabled Pseudo Console support, where `git add -i` [would not quit the file selection mode upon an empty input](git-for-windows/git#2729), has been fixed. Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
@dscho Tested the installer from the artifacts and it removes the git-bash.config file on uninstall. Thank you for your work! |
@satsuper excellent! |
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes git-for-windows#2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
As of Git for Windows v2.27.0, there is an option to use Windows' newly-introduced Pseudo Console support. When running an interactive add operation with this support enabled, Git will receive CR/LF line endings. Therefore, let's not pretend that we are expecting Unix line endings. This fixes #2729 Signed-off-by: Johannes Schindelin <[email protected]>
Setup
defaults?
to the issue you're seeing?
Details
Git Bash and Powershell through Windows Terminal
Minimal, Complete, and Verifiable example
this will help us understand the issue.
After the empty input it should exit the list menu for adding untracked items and go back to the main list menu
It presented the list menu for adding untracked items again
URL to that repository to help us with testing?
The text was updated successfully, but these errors were encountered: