Allow the Member in class: prompt to be easily skipped under ido-mode
#3501
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
When using completion for Java interop, one normally browses the options by repeatedly pressing
<down>or<up>.However, if one completion is ambiguous (as for its Java class) we will perform a
completing-read. Sample:This
completing-readbreaks the user flow. Say I want to press<down>, <down>(go two candidates down). Then after the first candidate, thecompleting-readwill interrupt the experience.One can only exit this pressing RET (to choose an arbitrary one) or C-g. Both require excessive awareness of what's going on and how to remediate it.
Also, ambiguity happens quite often, so requiring users to press
<down>, RETonce for each ambigious candidate is a pretty irritating experience.Proposed solution
Temporarily redefine the up and down keys to mean 'abort'. This way, completion can proceed.
Only ido-mode is affected. Other modes can be tackled in a future.
I've tried this and it works as intended.
Cheers - V