deleted files no longer in trash but .caltrash

[ownedbycats]

I don't think Kovid will go for disabling it entirely.

Is there a reason that clear upon exit wouldn't work?

[JSWolf]

Originally Posted by ownedbycats

I don't think Kovid will go for disabling it entirely.

Is there a reason that clear upon exit wouldn't work?

Kovid would end up with complains of lost data. So it's not going to happen.

[ownedbycats]

My main suggestion was a 'clear bin' menu entry, which would have a warning prompt by default. Then Action Chains could be used to run that at Calibre exit.

I should mention it wasn't marked as a 'wontfix' - so I'm guessing Kovid is thinking on it.

[lostinlodos]

Originally Posted by ownedbycats

My main suggestion was a 'clear bin' menu entry, which would have a warning prompt by default. Then Action Chains could be used to run that at Calibre exit.

I should mention it wasn't marked as a 'wontfix' - so I'm guessing Kovid is thinking on it.

That would also solve the issue for me.
Though the folder not being cleared completely will still cause problems for a rare few.

[Quoth]

Originally Posted by ownedbycats

I don't think Kovid will go for disabling it entirely.

Is there a reason that clear upon exit wouldn't work?

1 day (the minimum) is nearly "clear on exit".

[ownedbycats]

Originally Posted by Quoth

1 day (the minimum) is nearly "clear on exit".

If you don't use Calibre daily, the files can sit around quite a while.

[jbacelar]

Originally Posted by ownedbycats

If you don't use Calibre daily, the files can sit around quite a while.

Unless you delete them before leaving Calibre.

[ownedbycats]

Originally Posted by jbacelar

Unless you delete them before leaving Calibre.

Hence my solution, which would pretty much automate that process.

[ownedbycats]

https://github.com/kovidgoyal/calibr...d3b0df91de32ec

Trash bin: Allow setting removed books to be permanently deleted on library close.

[un_pogaz]

Clearly, for me, this is a even better solution, because as it's a perfect compromise between the powerful ".caltrash" feature and its restoration system, and the little too radical "disable storing deleted files" option that instant delete the file.
If you make a mistake, you can always undo the deletion (as long as you're fast enough to do it in the same calibre session). But if you're sure of what you're doing and careful, calibre will delete all files of the ".caltrash" without user external intervention.

(damn, that was a hell of a conversation to follow)

[lostinlodos]

Originally Posted by un_pogaz

(damn, that was a hell of a conversation to follow)

What happened here was a change for the intended base users broke or disrupted a small subset of the “other” (conversion) user population.

I admit the complaint rate is from a super minority. The Op uses off machine storage.
In my case I’m making consistent backups of ‘deleted’ files on an LTO platform. I can’t recover that lost space.

I don’t usually close calibre because I use the news feed downloader.
And again, not everyone has tiny 200k books.
The dread central and ars articles can be dozens or hundreds of megs in size.
Technical books with massive schematic photos can get to a gig or more.

Size is one of the reasons there is a setting to break up internal content sizes for lesser readers. Amazon, Apple, and Boox all have high quality readers with few major issues. Lesser apps can choke on large files.

Anyone ever try storybundle? Their video game and computing book offerings can get quite large to, many hundreds of megs.

When time allows I’ll look into a plugin to add a teach bin to the toolbar to:
Clear trash
Open trash location
Restore trash

[bizzybody]

Calibre having its own trash folder got in the way of how I use it. I only use it for updating metadata, covers, and format conversion. The vast majority of what it can do I never touch.

After I'm done with some books, I open the library folder, use Agent Ransack (because Windows refuses to allow its own Search to work in parts of where Calibre's default library location is) to find all *.azw3 files then I copy and paste from there to folders on two different storage devices and books I'll be reading soon I copy to the Kindle folder in internal storage on my phone. Then in Calibre I delete everything and only when I have some more books do I use it again.

That's how I've done my ebooks on many devices since 2004, with various software.

But with Calibre hanging onto everything, Agent Ransack would find all the "deleted" AZW3 files too.

Any time any software author adds what they think is an awesome new feature, they should also add an option to disable it because it's a near certainty some people are just going to flat out hate it forever.

[theducks]

What?
The only thing that hits calibre trash is BOOK DELETES, not metadata edits

[JSWolf]

Originally Posted by theducks

What?
The only thing that hits calibre trash is BOOK DELETES, not metadata edits

It deletes metadata edits if they are for that deleted book. But if you restore that deleted book, the metadata comes back as well.

[BetterRed]

Originally Posted by theducks

What?
The only thing that hits calibre trash is BOOK DELETES, not metadata edits

Format file removes are effected by a move to the .caltrash/f directory, from which they can be restored. Prior to the advent of calibre's trash can, a format file remove was permanent - i.e. equivalent of a Shift+Del in Windows.

@bizzybody could probably do what he does from within calibre if made use of the Search and Save to disk features - and set the Trash Can to clear itself when calibre exits.

BR