Module history 

Recall of previously submitted values for super::TextInput.

Each history has an id, which is also the name of the cache file it is persisted to, so the query, SQL and fuzzy inputs each keep their own list. Loading is lazy: nothing touches the disk until the user actually walks back through the history or submits a value.

Reading and writing go through CacheManager, which holds a lock across the whole read-modify-write. Two datui instances submitting a query at the same moment then merge instead of one overwriting the other.

Functions

push_entry

Append an entry, skipping it when it repeats the previous one.