View Single Post
Old 08-25-2022, 06:56 AM   #15
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,211
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by BetterRed View Post
When I read the opening post my reaction was 'Ah-hah, a fellow minimalist'. I regarded everything following "However, ..." as the OP having a bit of a rant. And the initial reply Sirtel provided was what I thought was the correct response, and in essence I still think that.

Within a couple of days of installing calibre in 2012, I decided the device connect feature was too bothersome for me, so I disabled the drivers for Android & Kindle. I thought I did that via Prefs->Ignore devices, but I see now I must have done it via Prefs->Plugins, but it shows up in Prefs-Ignore devices.

I only keep what I'm currently reading on my devices - Android phone, Surface GO, and an old Kindle. Because I mainly read histories and biographies, they can take me weeks to read, so its no hardship to add and delete an occasional file manually. I often extract back matter into a separate file so that I can read the body on the GO and use the phone to refer to footnotes, references etc.

BR
When I read the OP's post, I was thinking that he wanted the Kobo not to connect to Calibre because of the error he was getting. And that's an error that really should be solved.
JSWolf is online now   Reply With Quote