I have a mount i frequently access under /mnt let's cal it /mnt/foo. And an automounted NAS also under /mnt let's call it /mnt/bar.
When I try to navigate to /mnt/foo the syncronous stating on /mnt/bar causes neovim to completly hang until the timeout is expired.
This is due to the mounting changing some properties like mtime. I don't know if there is some workaround in the stat call.
Best I could find is this unhelpful mailing list entry: https://autofs.vger.kernel.narkive.com/u1PkpsxR/should-stat-2-ing-an-automount-mount-point-trigger-the-automount.
#26 changed the stat call to be on every file instead of just when needed. Maybe this could be reverted? Though I'm not quite sure why this was done to begin with.
I have a mount i frequently access under
/mntlet's cal it/mnt/foo. And an automounted NAS also under/mntlet's call it/mnt/bar.When I try to navigate to
/mnt/foothe syncronousstating on/mnt/barcauses neovim to completly hang until the timeout is expired.This is due to the mounting changing some properties like
mtime. I don't know if there is some workaround in the stat call.Best I could find is this unhelpful mailing list entry: https://autofs.vger.kernel.narkive.com/u1PkpsxR/should-stat-2-ing-an-automount-mount-point-trigger-the-automount.
#26 changed the stat call to be on every file instead of just when needed. Maybe this could be reverted? Though I'm not quite sure why this was done to begin with.