Make around-next only affect the next button

[slotThe]

Closes #166

I'm not merging this myself as, while it's technically a bug fix, it
possibly introduces a regression; see the discussion in #166 for all
information.

Before this change, around-next was able to change more buttons than just
the very next one, provided the next button was released after some
other buttons were pressed. For example, suppose we had

(defalias
  nsh (around-next sft))

Then the old behaviour would give

T@nsh Ta Tb       ==> Ab
T@nsh Pa Pb Ra Rb ==> AB

while the intended behaviour (and the one that this commit introduces)
would be

T@nsh Ta Tb       ==> Ab
T@nsh Pa Pb Ra Rb ==> Ab

[david-janssen]

Hmmm, I pulled this branch locally and then made some changes and pushed those changes hoping they'd be reflected here, but instead they turned into a branch on the main repo. Not toooo handy with git and GitHub yet. I have 2 options for you:

• You give me the greenlight and I'll just merge that branch (around-next-167, currently visible as a branch on KMonad) into master. No fuss for you.
• You pull the changes from that branch into the pull request and then I'll approve it through this avenue. A bit more fiddling, but I think you get credit somewhere on GitHub, and I wouldn't want to rob you of that without checking with you first.

[slotThe]

Hmmm, I pulled this branch locally and then made some changes and pushed those changes hoping they'd be reflected here, but instead they turned into a branch on the main repo. Not toooo handy with git and GitHub yet.

I once tried this in an xmonad pr: I think what you can do is push directly to my branch on my fork of the repository (i.e. directly to https://github.com/slotThe/kmonad/tree/around-next). I did this with magit, if I recall correctly, but have also since forgotten the exact steps.

* You give me the greenlight and I'll just merge that branch (`around-next-167`, currently visible as a branch on KMonad) into master. No fuss for you.

This is completely fine; as long as the issue is fixed that's enough satisfaction for me, no extra github dopamine needed :)

[david-janssen]

Oooohh wow, it DID recognize it when I just did the no-github-dopamine version (I couldn't figure out how to push to your copy). Technology, sufficiently advanced, is indistinguishable from magic :-)

[ghost]

Thank you!

[slotThe]

Quite magical indeed! :)