Michael Gallo

I solved this issue by deleting all viminfo files in my ~/local/share/vim directory ``` rm ~/local/share/vim/viminfo*``` local/share is my XDG_DATA_HOME so ```rm $XDG_DATA_HOME/vim/viminfo*``` is probably the more universal fix

I'm able to replicate this, 10% cpu usage if I ever touch the mountdir directory [It seems that this channel is somehow getting flooded with a ridiculous number of directories](https://github.com/gokcehan/lf/blob/master/app.go#L381)...

The modified time of a mounted cryfs directory always seems to be the current time. This is without any processes (other than cryfs) touching it  Just a thought, the...

Following up on detecting this Due to this weird behavior, the access, modify time, and change-time are always the same  This code successfully flags Cryfs directories for me without...

Just a thought Maybe whether we run this check could be a boolean option of some sort? I think it'll be a very small minority of users that are using...

The project only has 1.9k stars on Github ( https://github.com/cryfs/cryfs ) , and I also have never heard of it prior to reading this issue, and fundamentally I would say...

I opened PR #1607 to remove the call to `checkDir` and confirmed locally that it does fix the high CPU usage. Will wait for @gokcehan to confirm that this solution...

I think the map approach is more readable because it separates the options from the general `eval` logic, someone adding a new option now only needs to be concerned with...