I better elaborate a little the above. You can control it by setting a number in the preference places.history.expiration.max_pages. I talked about this earlier and, in my case, for 2 months, I need a number of about 20000.
Note that places.history.expiration.max_pages and places.history.expiration.transient_current_max_pages are linked, so change both values at once and restart K-meleon. Even though the second is a copy of the first.
Maybe the first digit is about the number of months then.
If you don't trust me, go here:
It is just a coincidence that I visit about 20000 every two months. But, at the same time, if, for whatever reason, I visit more this week, I could drop from the history more addresses, therefore, my history would be less than two months. And, of course, the opposite.
It is tricky, but to determine a time frame, I had to open places.sqlite with the SQuilte Manager extension, take note of the number of places I had in moz_places table in the database and sort all by last visited, take the lower number and convert the epoch time to human readable.
If after that you found that it is too much for you, you can lower the limit of urls in the database, if you find that find that you have very few, you will have to set a higher number. And, that, without forgetting that, depending on how many sites do you visit in a given time frame, it will make to have a larger time frame of history urls or shorter.
Edited 1 time(s). Last edit at 04/18/2017 06:13AM by JohnHell.