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

E227: mapping already exists for f #55

Open
ekaunt opened this issue Mar 31, 2020 · 9 comments
Open

E227: mapping already exists for f #55

ekaunt opened this issue Mar 31, 2020 · 9 comments

Comments

@ekaunt
Copy link

ekaunt commented Mar 31, 2020

when i add

let g:qs_highlight_on_keys = ['f', 'F', 't', 'T']

to my vimrc, i get an error

~ > vim .vimrc
Error detected while processing ~/.vim/plugged/quick-scope/plugin/quick_scope.vim:
line   66:
E227: mapping already exists for f
Press ENTER or type command to continue

then it only highlights for f, but not for F, t, or T

@bradford-smith94
Copy link
Collaborator

What is the output of :verbose map f without the let g:qs_highlight_on_keys line in your vimrc?

@ekaunt
Copy link
Author

ekaunt commented Apr 1, 2020

o  f             YRMapsExpression("<SNR>29_", "f", 1)                                      
        Last set from ~/dotfiles/.vim/plugged/YankRing.vim/plugin/yankring.vim line 1712

guess its a problem with yankring.vim conflicting, huh

@bradford-smith94
Copy link
Collaborator

Seems like it, I'm not sure if there is any way around this.

@againxx
Copy link

againxx commented May 4, 2020

An other problem with vim-sneak, after I press s/S to invoke vim-sneak. The ;/, key can only be used to repeat last sneak search, not the quick-scope f/F/t/T one, even after I pressed f/F/t/T again.

It turns out that vim-sneak has a reset function which will be called after native f/F/t/T is pressed. Would it be possible for quick-scope to provide a way to call that function?
A reference from vim-sneak

@ayyess
Copy link
Contributor

ayyess commented May 16, 2020

An other problem with vim-sneak, after I press s/S to invoke vim-sneak. The ;/, key can only be used to repeat last sneak search, not the quick-scope f/F/t/T one, even after I pressed f/F/t/T again.

It turns out that vim-sneak has a reset function which will be called after native f/F/t/T is pressed. Would it be possible for quick-scope to provide a way to call that function?
A reference from vim-sneak

You can reset sneak in quick_scope#Ready(): ayyess@a40654d

@againxx
Copy link

againxx commented May 17, 2020

An other problem with vim-sneak, after I press s/S to invoke vim-sneak. The ;/, key can only be used to repeat last sneak search, not the quick-scope f/F/t/T one, even after I pressed f/F/t/T again.
It turns out that vim-sneak has a reset function which will be called after native f/F/t/T is pressed. Would it be possible for quick-scope to provide a way to call that function?
A reference from vim-sneak

You can reset sneak in quick_scope#Ready(): ayyess@a40654d

Thank you! It works great!

@againxx
Copy link

againxx commented May 29, 2020

An other problem with vim-sneak, after I press s/S to invoke vim-sneak. The ;/, key can only be used to repeat last sneak search, not the quick-scope f/F/t/T one, even after I pressed f/F/t/T again.
It turns out that vim-sneak has a reset function which will be called after native f/F/t/T is pressed. Would it be possible for quick-scope to provide a way to call that function?
A reference from vim-sneak

You can reset sneak in quick_scope#Ready(): ayyess@a40654d

FYI, this patch will break f and t in macro, maybe there can be some improvement.

@thepenguinthatwants
Copy link

Seems like this happens also with plugin.
rhysd /clever-f.vim

ayyess added a commit to ayyess/vim-sneak that referenced this issue Jun 26, 2020
Improves solution on quickscope side of mapping[0][1]

[0]: unblevable/quick-scope#55 (comment)
[1]: ayyess/quick-scope@a40654d
@ixil ixil mentioned this issue May 7, 2021
@bradford-smith94
Copy link
Collaborator

Has anyone else following this issue tried out the patch in #73?

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

No branches or pull requests

5 participants