-
Notifications
You must be signed in to change notification settings - Fork 8
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
foreign_keys and exit options do not overwrite color as noted in README #37
Comments
It seems like there's an inconsistency between the docs and the code here. |
going back to when that code was written, the docs said the same thing. Guess it just slipped through at the time and hasn't been caught since. However, I'm not sure fixing this will even fix the problem you're having. edit. I guess in this case, |
ahh okay, makes sense that it does not work how I expect it to if the documentation is inconsistent. Okay, if I understood you correctly: with the current implementation it is basically not possible to have an -- I'll use a different terminology here -- async hydra (pink) that uses |
Yeah currently impossible. I'd be open to changing it though (at the very least I will update the docs). I'm not sure how hard it would be to do though. |
I mean sure, I am keen on this feature, so I'd be glad if you tried it. |
Hello everyone,
there's a sentence in the README that describes that
foreign_keys
andexit
configuration options actually overwrite the behavior specified by a color. At least I could not get it working.What is my problem?
I want to create a DAP hydra that has the policy of an
amaranth
hydra. However, since DAP stepping/continuing is asynchronous, I have to use a pink hydra. When using a pink hydra and specifying{ foreign_keys = 'warn', exit = true }
, the behavior of the hydra does not change, i.e. it still processes inputs that are not mapped to a head.What would solve my problem?
foreign_keys
andexit
and the configuration actually changes the behavior of the hydra{ on_key = function() vim.wait(20) end, color = 'amaranth' }
that is used in the proposed git hydra, however that does not work as expected with the DAP since when i usedap.continue()
it actually pastes some text into the popup created bydap.continue()
Example code:
The text was updated successfully, but these errors were encountered: