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
Exclude all keys except ____ #1560
Comments
I just did exactly this 3 minutes ago. I went through the list of shortcuts and set the gmail-excluded keys to jkhlgGzduryivVabceoOTbB[]m`nNHLKJtxXW<>? (this may not work for you; i've already made other config changes) I'm not sure OP's proposed solution is the best though. A simpler solution that would cover most cases and not require a bunch of parsing code is: have a switch which changes the field from 'disable these keys' to 'only enable these keys'. That's more the kind of thing you could do in an hour if you knew the vimium codebase. |
Some considerations:
The actual backend code changes should be reasonably easy, very little would need to change there to support this. |
I don't oppose fancy text config per se, but is there a simpler feature On Wed, May 6, 2015 at 6:20 PM, Matthew Ryan notifications@github.com
|
But is this the right thing to do? Personally I'd feel happier landing #1368 (I'll ping Steve and see if that's a possibility) and making the feature "only the keys and combinations in the passkeys field will be recognised by Vimium", so we don't take anyone by surprise.
For the most part people won't read the documentation, so the UI has to be pretty self-explainatory. I'll try it with an 'invert' checkbox when I get round to doing this.
Agreed. I'd wanted it a few times to change some mappings on pages where our and the page's mappings overlap, and both are useful — but it's probably overkill here. |
On Thu, May 7, 2015 at 2:19 PM, Matthew Ryan notifications@github.com
|
This isn't my project, and I'm not an official contributer, so I'm just trying to keep within the design goals with this feature. But this might be a good candidate for Vimium Labs (#1542) while the details are worked out. |
On the idea of an exclude/include toggle... Would that (re-)introduce the issue that the ordering of multiple matching rules would matter? |
If we take them as "disable" vs "allow only", then we could apply all the "allow only" rules first and subtract the "disabled" rules from the result, so the order shouldn't matter. |
I'm not familiar with the previous discussion of the issue, but can you a. order them to fix it. I mean, I suppose maybe a user wants to ignore W for all google apps, but I suppose it wouldn't be too much additional development work to make the Can anyone think of a realistic counterexample to the above? Maybe "I never On Thu, May 7, 2015 at 9:08 PM, Matthew Ryan notifications@github.com
|
Seems entirely reasonable when a user only wants some keys enabled for a whole site, and further wants to drop some keys for a specific page/part of the site. For example: allow only:
disable:
|
oh yeah On Fri, May 8, 2015 at 8:46 PM, Matthew Ryan notifications@github.com
|
A good use case for this is using JIRA. I use most shortcuts for JIRA (which is a lot), but I'd still like o to search a new tab, and f to follow links. I can type the whole alphabet in the box and that's ok, but a reverse rule would be simpler :) |
@smblott-github Can you please revise this? I also have similar needs, like using just the "f" key on some websites that have many key shortcuts on their own (JIRA, GMAIL, YOUTUBE, etc.). Thanks a lot! |
Please do this, I would like to use Vimium only for "f" functionallity, as I already know many chrome shortcuts, this is the only thing I need |
@DamirCiganovic-Jankovic. You can unmap the keys you never use on the options page. |
@smblott-github I see this was closed due to lack of interest. Is there any chance of reopening this if enough interest is generated? 😄 To add my own personal story, I used Vimium faithfully for years until about 2 years ago when I realized that most of the sites I used most often (gmail, github, reviewable) had too many clashing shortcuts. So I ended up having Vimium disabled on most sites I used, so I just ditched Vimium. It would be fantastic if I could just whitelist a few of the most common Vimium shortcuts on those sites ( (Future readers, please give a thumbs up on the top-level comment on this thread to register your interest!) |
Seems #3272 also reports this problem, and there're quite a few similar issues. Is there someone interested in my idea in #3272 (comment)? |
I find this an essential feature and think this should be reopened. I am glad to go through the code but did not have the time yet. So, here is the workaround I'll try to use to avoid all the clashing while not having to completely disable vimium all over the place. Here are all the keys that vimium uses, to my best of knowledge -
|
@mikemajara, I've expanded your list to a bigger subset of ascii keys. This way, even if vimium adds more keyboard shortcuts in the future, the list should still be fairly complete.
|
Thanks for this, but I also find that a proper 'whitelist/blacklist' feature would be preferrable to copying and pasting a long list of characters into a tiny text box. Especially when Oo & Ff are pretty much always what I want to keep enabled. |
Just use Vimium-C |
Instead of going through the list of keys, I configured to unmap all keys and re-map my favorite (
It works great for a small number of keys :) |
But this works globally, right? I mean, it cannot be applied to only one website. |
Came here to show interest about this feature. This would be really helpful. |
I ended up using Vimium C
|
You can easily disable All Keys or Individual Keys for a site, it's difficult to disable All Keys Except Keys x y z. For example, mail.google.com has all keys disabled by default. I would like to use the "f" command from vimium in Gmail. How would I do this? I would have to copy every single Gmail shortcut into the box and take out f which seems very tedious and inneficient.
A better method would be to put a plus sign in front of the keys you want to use from Vimium. ie "+f" would mean "Keep disabling all keys but allow 'f' from Vimium to be used".
The text was updated successfully, but these errors were encountered: