-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
[RFC] vim-patch:7.4.{569,573} #2621
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
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.
Before, mapped_ctrl_c
was a Boolean value, where true
indicated that Ctrl-C was mapped and false
that it wasn't mapped. Now that mapped_ctrl_c
is an int
with mode flags, the true
case becomes 'all flags turned on', which I think can be expressed as MAP_ALL_MODES
. Correct?
(Why is Ctrl-C always 'mapped' when entering the terminal though? I don't understand this.)
Test failure. It passed locally but now I see there is some indeterminism in this test. Look at the failing test results, they're not all the same. Hmm. |
Still failing! Frustrating. Does anybody know why these tests fail and how to make them pass in the CI? It's quite bad with these brittle functional tests at the moment. Is this a fundamental problem in the test infrastructure? |
It looks like the quickbuild-related issue (with the functional tests timing out) could be fixed if you rebased on master. The tests were hanging on QB because a necessary executable was not being built, and the tests didn't really do well picking up on that. I wish I knew about the Travis ones. I know we've got a couple that are a bit racy, but I'm not sure what's happening here. :-( |
blimey the test passed on Travis 🍸 No idea why. Now on to clean up the mess I made. |
Problem: Having CTRL-C interrupt or not does not check the mode of the mapping. (Ingo Karkat) Solution: Use a bitmask with the map mode. (Christian Brabandt) vim/vim@v7-4-569
Problem: Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat) Solution: Call get_real_state() instead of using State directly. vim/vim@v7-4-573 The code change in src/ui.c was already applied in src/nvim/os/input.c in patch 7.4.569. Also split monolithic test into four "it" blocks because of persistent non-deterministic test failures on CI.
Rebased, no changes. |
LGTM. |
restarted build (in case anyone missed it: travis infrastructure problems appear to be the cause of the many build failures in May; they have been running smoothly since then) |
@glts Can you fix the conflicts? |
Problem: Having CTRL-C interrupt or not does not check the mode of the mapping. (Ingo Karkat) Solution: Use a bitmask with the map mode. (Christian Brabandt) vim/vim@651863c Problem: Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat) Solution: Call get_real_state() instead of using State directly. vim/vim@5000869
Problem: Having CTRL-C interrupt or not does not check the mode of the mapping. (Ingo Karkat) Solution: Use a bitmask with the map mode. (Christian Brabandt) vim/vim@651863c Problem: Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat) Solution: Call get_real_state() instead of using State directly. vim/vim@5000869
vim-patch:7.4.569 vim-patch:7.4.573 Helped-by: @glts neovim#2621 Problem: Having CTRL-C interrupt or not does not check the mode of the mapping. (Ingo Karkat) Solution: Use a bitmask with the map mode. (Christian Brabandt) vim/vim@651863c Problem: Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat) Solution: Call get_real_state() instead of using State directly. vim/vim@5000869
vim/vim@v7-4-569
Original patch:
vim/vim@v7-4-573
Original patch: