Testers needed for history completion

Florian Bruhin me at the-compiler.org
Sat Mar 14 23:11:47 CET 2015


@toofar on github and I started working on history completion, and it
seems to work pretty well by now! However I want some feedback
(especially on performance) before merging this.

Can you please test the histcomplete branch? When you got the git
repo, you can simply do 'git pull' and 'git checkout histcomplete'.

Then check how using 'o' feels, and if the performance is acceptable.
If it is,  :set completion web-history-max-items -1   then restart
qutebrowser and test again.

Things which potentially could be sluggish:

- Opening the completion the first time with 'o'.
- Using 'o' after the first time.
- Using 'o' and typing (without using the completion)
- Scrolling the completion (with tab and scrollbar/mousewheel)

Also, it'd be good to know what this says for you:

    sort ~/.local/share/qutebrowser/history | cut -d' ' -f2 | uniq | wc -l

See https://github.com/The-Compiler/qutebrowser/pull/547 for



http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.schokokeks.org/pipermail/qutebrowser/attachments/20150314/c094a0a0/attachment.asc>

More information about the qutebrowser mailing list