Skip to content
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

URI controls #200

Open
jannis-baum opened this issue Sep 18, 2023 · 3 comments
Open

URI controls #200

jannis-baum opened this issue Sep 18, 2023 · 3 comments

Comments

@jannis-baum
Copy link

Following into Wooshy's footsteps, I think kV would benefit from URI controls!

Some ideas/use cases for URIs, ordered by my perception of highest to lowest benefit-effort ratio:

  • Enter Normal mode
    This is useful for people who want to enter Normal mode in some personalized way with Karabiner, Hammerspoon, etc. Right now they would have to bind their trigger to emit a(nother) key event that triggers kV, this way they could just trigger the URI
  • Switch to a family on the fly
    Sometimes the frontmost app isn't enough to determine how kV should behave. Being able to switch the behavior to another family with a URI would enable people to hack whatever they need into place, at least from kV's side. This might solve Feature request: system-wide pause/disable #196 and Ability to disable kindaVim on certain websites #180
@godbout
Copy link
Owner

godbout commented Sep 19, 2023

first thoughts out loud (mostly for myself 😂️)

  • Enter Normal Mode
    it's gonna be trickier than Wooshy because there's several ways to enter Normal Mode, and that is handled within the Global Event Controller itself, so we can't call it directly like we do with Wooshy.
  • Switch to a Family on the fly
    as far as i remember the Family thing is deeply integrated within kV, at each movement level. so that means a "temporary" switch to a Family would be quite hard to do. but switching from one to another permanently could be done. basically we could have URLs to move to the next Family, previous one, or put in a specific one. not sure if the UX would be good tho.

@jannis-baum
Copy link
Author

To me kV is the lowest priority between the three apps in terms of adding URI controls.

I don't personally need the "entering Normal mode" part because I have jk mapped to escape everywhere anyways so kV is fine being set to go to Normal mode with escape. But this might be good to have for consistency with Wooshy and later Scrolla.

The "switching families" thing I thought might be interesting for the people who opened the issues I referenced. I currently also don't have any need for it :) If no one else says anything I guess you can also just swipe it under the rug🙈

@godbout
Copy link
Owner

godbout commented Sep 25, 2023

To me kV is the lowest priority between the three apps in terms of adding URI controls.

noted.

I don't personally need the "entering Normal mode" part because I have jk mapped to escape everywhere anyways so kV is fine being set to go to Normal mode with escape. But this might be good to have for consistency with Wooshy and later Scrolla.

noted bis.

The "switching families" thing I thought might be interesting for the people who opened the issues I referenced. I currently also don't have any need for it :) If no one else says anything I guess you can also just swipe it under the rug🙈

yeah, agreed. i'll digest. thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants