-
Notifications
You must be signed in to change notification settings - Fork 626
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
tig jumps to a match after canceling search #627
Milestone
Comments
rolandwalker
added a commit
to rolandwalker/tig
that referenced
this issue
Jul 7, 2017
Fixes jonas#627 * maintain the distinction between null pointers and strings of length zero, representing canceled input and empty input, respectively * at the input boundary, capture the distinction by setting a flag in the readline signal handler * when configured --without-readline change the way read_prompt() calls read_prompt_incremental() to avoid regressions
rolandwalker
added a commit
to rolandwalker/tig
that referenced
this issue
Jul 7, 2017
Fixes jonas#627 * maintain the distinction between null pointers and strings of length zero, representing canceled input and empty input, respectively * at the input boundary, capture the distinction by setting a flag in the readline signal handler * when configured --without-readline change the way read_prompt() calls read_prompt_incremental() to avoid regressions
rolandwalker
added a commit
to rolandwalker/tig
that referenced
this issue
Jul 7, 2017
Fixes jonas#627 * maintain the distinction between null pointers and strings of length zero, representing canceled input and empty input, respectively * at the input boundary, capture the distinction by setting a flag in the readline signal handler * when configured --without-readline change the way read_prompt() calls read_prompt_incremental() to avoid regressions
jonas
pushed a commit
that referenced
this issue
Jul 9, 2017
Fixes #627 * maintain the distinction between null pointers and strings of length zero, representing canceled input and empty input, respectively * at the input boundary, capture the distinction by setting a flag in the readline signal handler * when configured --without-readline change the way read_prompt() calls read_prompt_incremental() to avoid regressions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to reproduce:
The text was updated successfully, but these errors were encountered: