You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vim.loader stores files stored in ~/.cache/nvim/luac and compiled files are encoded as full path to the original source file.
On linux OS when ecryptfs is enabled on home directory this leads to file names exceeding max file length (143 characters)
preventing plugin to be loaded.
This is similar but not exactly the same as #25008
Steps to reproduce
Enabling telescope with file-browser extension on Linux OS with ecryptfs enabled on home directory leads to the following error:
Failed to run `config` for telescope-file-browser.nvim
...m/lazy/telescope.nvim/lua/telescope/_extensions/init.lua:10: 'file_browser' extension doesn't exist or isn't installed: vim/loader.lua:0: ENAMETOOLONG: name
too long: /home/neg/.cache/nvim/luac/%2fhome%2fneg%2f.local%2fshare%2fnvim%2flazy%2ftelescope-file-browser.nvim%2flua%2ftelescope%2f_extensions%2ffile_browser%2
fmake_entry_utils.luac
# stacktrace:
- /telescope.nvim/lua/telescope/_extensions/init.lua:10 _in_ **load_extension**
- /telescope.nvim/lua/telescope/_extensions/init.lua:62 _in_ **load_extension**
- ~/.config/nvim/lua/plugins/telescope.lua:17 _in_ **config**
- ~/.config/nvim/init.lua:17
Expected behavior
Cached plugin file names should be wither hashes of target file names or stored in a way that file names does not exceed max file length.
Neovim version (nvim -v)
v0.10.0
Vim (not Nvim) behaves the same?
Operating system/version
Debian 6.7.12-1 (2024-04-24) x86_64 GNU/Linux
Terminal name/version
gnome-terminal
$TERM environment variable
xterm-256color
Installation
build from repo / official release binary
The text was updated successfully, but these errors were encountered:
Hashing the filepath is indirection which makes troubleshooting/debugging more cumbersome. Is that the only reason we don't hash the filepaths? Maybe it's worth the tradeoff.
Problem
vim.loader stores files stored in ~/.cache/nvim/luac and compiled files are encoded as full path to the original source file.
On linux OS when ecryptfs is enabled on home directory this leads to file names exceeding max file length (143 characters)
preventing plugin to be loaded.
This is similar but not exactly the same as #25008
Steps to reproduce
Enabling telescope with file-browser extension on Linux OS with ecryptfs enabled on home directory leads to the following error:
Expected behavior
Cached plugin file names should be wither hashes of target file names or stored in a way that file names does not exceed max file length.
Neovim version (nvim -v)
v0.10.0
Vim (not Nvim) behaves the same?
Operating system/version
Debian 6.7.12-1 (2024-04-24) x86_64 GNU/Linux
Terminal name/version
gnome-terminal
$TERM environment variable
xterm-256color
Installation
build from repo / official release binary
The text was updated successfully, but these errors were encountered: