You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
I just posted teo commits: 169a3f6 restores the functionality, and adds a sanity check for long pages, in a way that I think was the original intent for the check that I criticized above. However, I then proceeded to remove that in the next commit 6fdff93 because I don't see that the check ever makes any sense, because it would only be invoked when the user explicitly changes the defcustom value w3m-db-history-page-size, in which case the user has already told us his preference!
I also did sneakily change the default for that value to make it more a sane 100 instead of based upon 500 entries.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.