-
Notifications
You must be signed in to change notification settings - Fork 83
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
When file is not modified, Codi updates on every cursor move #54
Labels
Comments
Can't seem to reproduce with same macOS, |
With vimrc: filetype plugin indent on
syntax on
packloadall and contents of .vim:
I'm still getting the described behaviour. Are there any dependencies I'm not thinking of, or anything else I could have configured differently? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
When I'm using Codi while editing a Lua file in MacVim, if the file is not modified, Codi updates every time I move the cursor. This is in contrast to what happens when the file is modified, when Codi updates every time the text changes (when
TextChanged
orTextChangedI
fires). As far as I can tell, this only happens with Lua files.Steps to reproduce:
mvim foo.lua
print(os.date())
:w
):Codi
)Now Codi is updated whenever the cursor is moved, even though text hasn't changed.
print("foo")
)The frantic updating stops, and Codi now updates as expected, when text is changed.
u
)The buffer is no longer
'modified'
, and erratic behaviour resumes.After modifing the buffer the first time after saving (here with
print("foo")
), Codi works as expected, even after saving again, until I useu
to undo into a state where the buffer is not modified.Other undesirable behaviours include syntax highlighting flickering off and on whenever Codi is erratically updating, and the undo history sometimes (seemingly randomly) being clobbered.
Environment
Running macOS Sierra (10.12.1)
Last line of
script
manpage is BSD December 4 2013The log file is over two thousand lines long, generated in about 30 seconds. Almost every keypress generates several log lines when this issue is happening, which may make the log hard to read.
Output of
mvim --version
:The text was updated successfully, but these errors were encountered: