-
Notifications
You must be signed in to change notification settings - Fork 21
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
It doesn't work in VISUAL Mode! #108
Comments
Define "doesn't work" please. I'm not seeing an issue in my install. |
What do you mean paste fail? |
No output after "p". |
Not seeing this, please provide more detail on your environment, vim version, etc. |
Also if you can reproduce with vanilla vim and a stripped down vimrc with just easyclip alone that would be great |
Following your guide "vimrc with just easyclip alone". But, I want to set clipboard=unnamed, as you point in part of "Clipboard setting"... |
What was it set to that caused the issue? |
I don't know the specific reason. It will have some problem after add vim8.0. Centos. |
Ohh ok, I think I know what's happening. It's probably related to #23 . Having clipboard set to unnamed should work fine, I think we have to address that issue for it to work though |
@svermeulen can confirm this bug. This is following the recent changes that were made in the last month or so. Easyclip has become unusable for me on Arch linux as well.
My easyclip settings are:
Any idea how to resolve this? |
I have the following setting:
If I copy line with |
I noticed this today while comparing files with Plug 'rickhowe/diffchar.vim'
set diffopt+=vertical
set diffopt+=iwhite
set diffexpr=""
if &diff | colorscheme molokai | endif
set clipboard=unnamedplus
let g:EasyClipAutoFormat = 1
let g:EasyClipPreserveCursorPositionAfterYank = 1
let g:EasyClipShareYanks = 1
let g:EasyClipShareYanksDirectory = '$HOME/.vim'
nmap M <Plug>MoveMotionEndOfLinePlug Reproduce by positioning the cursor over a word, then |
It doesn't work in master branch!
I found that it's fine in VisualModeFixAttempt branch, certainly, some problem already.
Do you have plan to fix it?
thank you!
The text was updated successfully, but these errors were encountered: