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

Vim swapfile issues: E72: Close error on swap or E200: *ReadPre autocommands made the file unreadable #194

Open
TiBeN opened this issue Feb 26, 2018 · 5 comments

Comments

@TiBeN
Copy link

TiBeN commented Feb 26, 2018

I use my Google Drive mainly for storing notes *.md (Markdown) files. I have some issues editing theses files with Vim. With no ~/.vimrc file (no custom configuration), the file takes a lot of time to be opened with vim, then triggers the following error on close:

E72: Close error on swap

I think this is because Vim is not able to create the swap file. Now if i put set noswapfile into a ~/.vimrc file to disable swap file creation, Vim triggers the following error on file opening, leaving the editor with a blank page (file is not opened at all):

E200: *ReadPre autocommands made the file unreadable

I'm using Vim 7.4 on Ubuntu 16.04.

@cyanpencil
Copy link

I currently have the same error on Vim 8.1 with archlinux. Did you find a solution eventually?

@TiBeN
Copy link
Author

TiBeN commented Jan 22, 2019

Hi,
I don't use this project anymore but google-drive-ocamlfuse : https://github.com/astrada/google-drive-ocamlfuse. I don't have problems editing files in vim with this one.

@dsoprea
Copy link
Owner

dsoprea commented Jan 27, 2019

I had actually originally tested the implementation, specifically, on VIM. There were issues with all of the opening and closing of so many different files all at once when first opening a single file, but they were cleared up. I'll take a look at this after clearing up some other issues.

It's not good etiquette to market for alternative projects from the issues of another.

@TiBeN
Copy link
Author

TiBeN commented Jan 28, 2019

@dsoprea,
I'm sorry, my purpose was not to market anything but just answer to @cyanpencil question about the solution that worked for me.
I have true respect for the work you do on this project and will probably take another look at it when this issue will be solved.

@cyanpencil
Copy link

It's not good etiquette to market for alternative projects from the issues of another.

Yes, in this case it actually is. He pointed out an open-source alternative that doesn't have this specific issue. This is not marketing, nor him nor the author of google-drive-ocamlfuse gain anything by having one more user, as it's an open source product: that's why it's called an alternative, not a competitor. It's just that google-drive-ocamlfuse fits better one particular use case (editing files with vim) ; I'm sure there are a lot of other specific use cases where your product is better.
If anything, you should be thankful to @TiBeN: he opened this issue, pointing out a problem you weren't aware of; he also linked to a solution, as nothing stops you to go look in that project source code and see how they managed to avoid this issue.

@TiBeN Thank you for opening this issue. Thank you also for suggesting an alternative that doesn't have this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants