Closed savchenko closed 4 months ago
The error message should be thrown from the uv
lib, it's an async library that allow writing async lua code.
The uv
library is embedded into Neovim, and the user manual is here: https://neovim.io/doc/user/luvref.html. For the uv
library itself, the repository is hosted here: https://github.com/luvit/luv.
And for the error message payload: "ENOSPC: no space left on device"
. It's usually a C-level error message, I googled it and found:
Since most of the caches that fzfx writes are in these directories:
:lua print(vim.fn.tempname())
, it's usually managed by OS itself. In linux, it's usually the /tmp
directory. In your cases, can you check if the /home/user/.cache/TMPDIR
directory has enough disk space?:stdpath("data")
directory: in Neovim, you could find it by type: :echo stdpath('data')
, in Linux, it's usually ~/.local/share/nvim
. Please check if it has enough disk space.BTW, you can also try add this command in your .bashrc
or .bash_profile
:
ulimit -n 200000
It can fix the "Too many open files"
error, not sure if it helps for this case.
The reason was a stray DBus connector after the system update (!). Nothing to do with FZFX, sorry.
P.S. Increasing fs.inotify.max_user_watches
would help.
Odd bug, started appearing after an upgrade to Debian 12.
LuaJIT:
There is plenty of space left on all mounts.
Any clues?