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

Completely empties the file on open on Windows with "set encoding = utf8" on vimrc. #367

Open
GoogleCodeExporter opened this issue Aug 21, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

This is a very weird issue I saw on Windows. Right click-> edit in vim, the 
file is open and emptied and saved emptied on its own. If I recopy it it 
non-empty it just empties it again on open.

I recently added "set encoding = utf8" in vimrc.

If I remove it, it doesn't empty it!

Also, if the NAME of the file is renamed to something non-unicode, it also 
doesn't empty it!

There must be a bug with that option and unicode file names.

Original issue reported on code.google.com by [email protected] on 19 May 2015 at 1:54

@GoogleCodeExporter
Copy link
Author

Ah, it must be also related to long paths!1 It does not happen on a very short 
directory, even with a unicode filename.

The bug in general appears related to long paths, potentially long unicode 
paths.

Original comment by [email protected] on 19 May 2015 at 1:57

@GoogleCodeExporter
Copy link
Author

I can confirm it happens even with latin characters, if I make the filename big 
enough.

I can understand a quirk with long paths/filenames, but completely deleting the 
data?

That's breaking.

Original comment by [email protected] on 19 May 2015 at 2:04

@GoogleCodeExporter
Copy link
Author

It appears by pasting the binary folder (64bit) from this website into the 
windows binary folder, took the issue away:

https://tuxproject.de/projects/vim/

I guess it might be fixed or other.

Original comment by [email protected] on 19 May 2015 at 2:27

@GoogleCodeExporter
Copy link
Author

Final thought, the windows version from the official site absolutely needs an 
update. 99% of people will use that. And that version is ancient.

Original comment by [email protected] on 19 May 2015 at 3:14

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

1 participant