Joe Lim

This is caused by the `dircache` feature, which caches `dir` data structures by its `path`: https://github.com/gokcehan/lf/blob/b47cf6d5a525c39db268c2f7b77e2b7497843b17/nav.go#L419-L430 The problem is that when deleting a directory, the corresponding entry is not deleted...

> If you set "nodircache" lf does not remember what you selected the last time and deletes (if you delete) where you are on at the moment. I had this...

@dase78 I tried it just now with a config file containing nothing but `set nodircache`, using a few files named from `a` to `e`. But I still couldn't reproduce your...

BTW, this is the code that performs the actual delete. The first thing it does is call `nav.currFileOrSelections`, which returns a list of selected files, or the file at the...

Oh, and also I am starting to think that this is a separate problem and a new issue should be created, rather than discussing it here.

> I could reproduce my failure but I guess it was, because I had set: map :delete; reload, so when I pushed , it asked for confirmation for the right...

I think it's also worth pointing out that this issue also occurs when you rename the original directory to something else instead of deleting it. The original example given was:...

This is now officially supported by #1674

I don't think an option like `previewpreload` as you described makes sense to implement because: 1. `lf` doesn't really have this kind of mechanism for working with files above/below the...

> @DusanLesan my preview script is setup to cache images and metadata that it needs so it doesn't have to get them every time, even though it gets stuff from...