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

The cursor moves on 3 symbols right #9

Closed
backdround opened this issue Aug 28, 2017 · 9 comments
Closed

The cursor moves on 3 symbols right #9

backdround opened this issue Aug 28, 2017 · 9 comments

Comments

@backdround
Copy link

backdround commented Aug 28, 2017

Whenever, i do some action, cursor moves on 3 symbols right. There is if autosave is enabled.
neovim/arch

@uipoet
Copy link

uipoet commented Sep 28, 2017

I experienced the same issue and resolved it by specifically disabling the trimming of whitespace on autosave:
let g:workspace_autosave_untrailspaces = 0

@freder
Copy link

freder commented Oct 13, 2017

same problem here.

I noticed it happens, when I'm editing .js files, but not when I'm editing .vim files. – hope that helps.

@snkshukla
Copy link

snkshukla commented Jan 14, 2018

For me, earlier cursor was moving 1 char right, now 2 chars right, is there a fix without disabling whitespace trimming? For me it only happens in .go files.

@heratech
Copy link

I think I am getting this issue or a linked issue using Ultisnip. When I have workspace enabled (plugin loaded) the ultisnip goes into the wrong position (2 or 3 spaces to the right of where it should)..

@maiconviking
Copy link

@uipoet Your solution solved the issue for me. Thank you.

@wayneforrest
Copy link

wayneforrest commented Apr 21, 2018

@uipoet Your solution works for me too.

@dustypaws
Copy link

@uipoet Thanks for saving my bacon, mate! 😄

@thaerkh
Copy link
Owner

thaerkh commented Nov 14, 2018

I wasn't able to replicate the issue until today - it looks like this happens in some file types (not all) when wrap is enabled by default, on lines that are wrapping (edit: at least that's my first observation, seeing this now in lines with tabs in them), and is likely due to the virtcol native method (getting different cursor numbers from what they're supposed to be), which might be a bug in Vim itself. I'll see to resolve the issue within the plugin.

@thaerkh
Copy link
Owner

thaerkh commented Nov 14, 2018

This should be resolved now with 892a00d (col was a more accurate call for this purpose as it was exact byte position)

@thaerkh thaerkh closed this as completed Jul 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants