Skip to content
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.

'f' key conflicts with 'cmd + f' search function #88

Closed
1 of 2 tasks
caesarjuly opened this issue Oct 23, 2017 · 8 comments · Fixed by #132
Closed
1 of 2 tasks

'f' key conflicts with 'cmd + f' search function #88

caesarjuly opened this issue Oct 23, 2017 · 8 comments · Fixed by #132
Labels
Milestone

Comments

@caesarjuly
Copy link

caesarjuly commented Oct 23, 2017

I'm opening this issue because:

  • I'll report a bug
  • I'll propose a new feature

Description

I find that 'cmd +f' doesn't work on my mac book. When I press these two keys, the 'f' key works instead. This is really annoying.

System configuration

  • Operating system:
    macOS Sierra 10.12.6
  • Firefox version:
    firefox version 57.0b10
  • Vim-Vixen version:
    0.2

Console logs

Any relevant log in developer tools:

@ueokande ueokande added the bug label Oct 23, 2017
@linnik
Copy link

linnik commented Oct 24, 2017

I can't find mention of this in documentation, but maybe you should use / keybinding for search?

@ueokande
Copy link
Owner

/ is a Firefox's bindings.
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly#w_search

@caesarjuly
Copy link
Author

caesarjuly commented Oct 24, 2017

@linnik @ueokande Thank u guys. After a few months without vim, I almost forget to use/. It works well.

@pengux
Copy link

pengux commented Oct 25, 2017

How do you go to the next occurrence with Quick Find? Pressing Cmd+G doesn't work

@linnik
Copy link

linnik commented Oct 25, 2017

@pengux cmd+G works for me. docs

@ueokande ueokande mentioned this issue Nov 4, 2017
2 tasks
@ueokande ueokande modified the milestones: 0.4, 0.5 Nov 4, 2017
@jubalh
Copy link

jubalh commented Dec 11, 2017

According to Firefox info I run vim vixen 0.7, but / in combination with n for the next result still don't work for me.

@pengux
Copy link

pengux commented Dec 11, 2017

@jubalh Try cmd + G

@jubalh
Copy link

jubalh commented Dec 11, 2017

right, so n will not be implemented I guess?

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

Successfully merging a pull request may close this issue.

5 participants