aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/keymap.lua
diff options
context:
space:
mode:
authorabdulahmoda <abahmoda@qnx.com>2026-05-29 14:24:22 -0400
committerGitHub <noreply@github.com>2026-05-29 14:24:22 -0400
commit4b5f026ac924d8f3d8efb4d66b00c2e3ebcf6757 (patch)
tree940b4ec062199b13e97f9bb6b6ebc5314184225a /runtime/lua/vim/keymap.lua
parentac352a6df62254666fdeb59764294237fd743f89 (diff)
downloadrneovim-4b5f026ac924d8f3d8efb4d66b00c2e3ebcf6757.tar.gz
rneovim-4b5f026ac924d8f3d8efb4d66b00c2e3ebcf6757.tar.bz2
rneovim-4b5f026ac924d8f3d8efb4d66b00c2e3ebcf6757.zip
fix(vim.fs): fs.dir() may return nil "type" on some filesystems #39749
Problem: Currently, only some filesystems (Btrfs, ext2, ext3, ext4) have full support of accessing the `dirent` entry-type. On other filesystems, `uv.fs_scandir_next` may return `nil` for an existing but unsupported entry-type. This means consumers (such as `fs.dir()`), cannot know if `nil` means "non-existent" or "unsupported". Solution: Fall back to `uv.fs_lstat` when `etype` is `nil`; return "unknown" if it fails.
Diffstat (limited to 'runtime/lua/vim/keymap.lua')
0 files changed, 0 insertions, 0 deletions