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
With a vanilla installation and no custom configuration, file operations like copy, paste, creation, and deletion do not update the view inside a directory. Unless I manually perform a reload, the result of these operations isn't visible.
Files are created using $touch and $mkdir and deleted using the built-in :delete command. Copying and Pasting were also done using the built in command.
Is this behavior intended? Even with the following options in ~/.config/lf/lfrc,
set nodircache
set period 1
there's no change in this strange behavior. Is it expected to perform a reload for each and every file operation? I'm apprehensive about doing that because every reload operation flickers the entire terminal lf screen for an instant, which is pretty jarring.
The text was updated successfully, but these errors were encountered:
I've managed to solve this issue. For posterity, I was using mergerfs and this issue was visible only on mergerfs mounts. After trying several different options, I found that using func.getattr=newest or category.search=newest in the mergerfs mount options resolves this issue.
With a vanilla installation and no custom configuration, file operations like copy, paste, creation, and deletion do not update the view inside a directory. Unless I manually perform a reload, the result of these operations isn't visible.
Files are created using
$touch
and$mkdir
and deleted using the built-in:delete
command. Copying and Pasting were also done using the built in command.Is this behavior intended? Even with the following options in
~/.config/lf/lfrc
,there's no change in this strange behavior. Is it expected to perform a reload for each and every file operation? I'm apprehensive about doing that because every reload operation flickers the entire terminal lf screen for an instant, which is pretty jarring.
The text was updated successfully, but these errors were encountered: