marvinkreis / rofi-file-browser-extended

Use rofi to quickly open files
MIT License
240 stars 15 forks source link

No content showing up at first #25

Closed Kabouik closed 3 years ago

Kabouik commented 4 years ago

This may not be an issue with rofi-file-browser-extended itself, but perhaps with the theme I am using, I am just trying to troubleshoot and wanted to ask if you would know where to look first.

I compiled rofi-file-browser-extended and added the mode to my rofi configuration. I am using a custom theme modified from that one and use it for all my rofi modes (actually I would be interested in showing more lines when showing the file-browser mode but I don't know how to do so). While it works for the file-browser mode too, it shows content only when I show that mode, then cycle to another, and then cycle back to the file-browser mode. See below:

First time I show the file-browser mode: ss-2020-04-29_180046

Second time when I cycle back to it without closing rofi: ss-2020-04-29_180058

I noticed that sometimes it did show the content, but with an empty space between the line showing the working directory and the content. Cycling to another mode and back fixed the issue too when it happened.

Since the theme seems to work with all modes, and to be properly picked up by by rofi-file-browser-extended too, is it possible that the issue comes from some delay between showing the mode and fetching the content to be displayed? The issue does not occur when setting the default directory to a directory with very few files, which I believe supports this hypothesis. If confirmed, would it be possible to add a delay option to rofi-file-browser-extended so that it displays the mode only when the content is fetched?

Kabouik commented 3 years ago

I believe I am no longer observing this. I didn't update rofi-file-browser-extended though, but perhaps rofi got updated with my package manager.

Kabouik commented 2 years ago

Just an update to clarify. I think I stopped observing that on a different machine, but it was still there on the first machine. What fixed it on that computer was rm ~/.cache/rofi3.filebrowsercache, so somehow the cache was borked on that computer and not on the others.