View Single Post
Old 01-02-2020, 06:50 AM   #8
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by pickyaxe View Post
I was reading them with KOReader. I intentionally put them into a directory with a name that starts with a dot, so that Nickel won't index them. At some point a couple months ago, Nickel started indexing them. I couldn't be bothered to fix it (since I don't use Nickel for much these days except Pocket) so I left it alone, until now.
Which was a change in firmware version 4.17.13651. And a few days later Kobo released 4.17.13694 which uses a config file option to exclude folders from the import process. Plus it has some that it ignores.
Quote:
Yes, the files themselves were deleted from storage. It didn't touch file formats that Nickel doesn't index or the directory structure. Interestingly, this made KOReader repeatedly panic on launch, since it was set to "open last file" and the entire history was pointing at files that didn't exist.
From my understanding, deleting the files is was what nickel always did in these circumstances. But, we probably rarely saw it triggered before these firmware versions. And it would only affect files that nickel can import.
davidfor is offline   Reply With Quote