Created attachment 948532 [details] gvim screencast Description of problem: The cursor in gvim is broken. It behaves as it would be one character to the left. Version-Release number of selected component (if applicable): vim-common-7.4.475-2.fc20.x86_64 vim-enhanced-7.4.475-2.fc20.x86_64 vim-filesystem-7.4.475-2.fc20.x86_64 vim-minimal-7.4.475-2.fc20.x86_64 vim-X11-7.4.475-2.fc20.x86_64 How reproducible: Sometimes. Steps to Reproduce: I have no idea. Actual results: The cursor behaves as it's one character to the left, see attached screencast. Expected results: The cursor should modify the characters around it. Additional info: I also have vim-plugin-powerline-0.0.1-7.20140508git9e7c6c.fc20.noarch and the following plugins: pathogen, ack.vim, MatchTag, nerdtree, systemtap, vim-colors-solarized, vim-distinguished, vim-fugitive, vim-surround, Zenburn.
First make sure that you can reproduce the issue without any plugins. You can do that with 'gvim -u NONE -U NONE'. If the issue is gone, one of the plugins is responsible for the problem. You can also try the latest vim, although currently available for rawhide only. Please make sure to report any findings here
Ok, I'll try to run it without any plugins, although as mentioned in the original the issue seems to appear randomly, so it might take some time until I'll be able to reproduce it. I'd also like to add that I did not have this issue until around last week, so maybe one of the most recent updates to vim had something to do with this.
This setting seems to be the culprit: set showbreak=↳ " … Continuations of long lines are affected in both the terminal and X11 versions.
:help showbreak shows this: Only printable single-cell characters are allowed, excluding <Tab> and comma (in a future version the comma might be used to separate the part that is shown at the end and at the start of a line). ↳ with ascii code 8627 is not supported. AFAIK the bug is not that the cursor behaves incorrectly, the bug is that ↳ should not be accepted when setting showbreak.
Ok, but it worked fine until recently... or I didn't notice this, although I doubt it.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.