Hi Bram, you have already merged my pull request, but I looked at the
corresponding commit in Neovim that got spawned from this change, and it
referenced this commit in libuv that has more details:
https://github.com/libuv/libuv/pull/2135
>From that commit I think we are currently missing a case
> If others are curious about this, follow the thread on
> https://github.com/macvim-dev/macvim/issues/861. A recent Vim build
> (8.1.915) broke this.
That patch was supposed to make it work better. Does someone know why it
causes this error? And how to fix?
--
A radioactive cat has
If others are curious about this, follow the thread on
https://github.com/macvim-dev/macvim/issues/861. A recent Vim build
(8.1.915) broke this.
On Tue, Feb 19, 2019 at 3:54 PM Eduardo Kortright
wrote:
> After I upgraded MacVim to v. 8.1.950 (155) today, I can no longer save
> files to any
After I upgraded MacVim to v. 8.1.950 (155) today, I can no longer save files
to any network folder.
I can still save files to folders on my local disk, but when I try to save to a
shared (mounted as smbfs) folder, I get an error:
E667: Fsync failed
Changes to the file are not saved
