Hi Jose, i agree on the completion problem. It now seems to search not only in the command names but also the description of the commands. Thats why 'search' comes first in your completion example. Thats not a huge problem but I would like the behaviour of first showing all result where the characters are in the name of the command and the ones where only the description matches after that. Would make more sense honestly.
I also agree that the browser somehow feels slower. But i do not really know why that is because the completion engine should be faster than the old one. Anyhow, thanks to Florian and all the other contributers for their hard work! Greetings, Lukas On Tue, Oct 17, 2017 at 05:51:27PM +0000, José Alberto Orejuela García wrote:
Hi, I was very excited about qutebrowser 1.0 and now (hype is not good ever) I feel disappointed about some things, mostly when interacting with commands. I don't exactly know which ones are all the differences, but I find the completion (url based on history or general command completion) very strange to me. I cannot test as I won't have access to another of my computers (with still outdated qutebrowser) until December, but these are two things I find strange: - Default behaviour for moving between completions is tab or shift-tab. I know that I can make arrow keys also do the job in settings, but what is the point of having that disabled by default now? I think it was default behaviour before, but maybe I changed it in settings long time ago and I don't remember... =P - Completion is sometimes sorted differently. For example, when I wanted to clear downloads, I used to write ":clear" and hit tab, the two results were download-clear history-clear and they were alphabetically sorted. Now, the completions for that are search history-clear download-clear config-clear and I cannot see what the pattern is, but it's not alphabetically in command or command description, for sure. Why is this now happening? By the way, relating completions, there are three things I have always found a little annoying in qutebrowser: - Not being able to go back to original. I think it could be useful to undo completion, for example, writing something, hitting tab (or down arrow) and then shift-tab (or up arrow). When I hit tab accidentally I have to start from scratch. - Taking into account substitutions in urls. For example, if I want to find an url that contained a bang, I cannot find it using ":open !" because that won't give any result as ! was changed to %21 in the url. - Completion until next difference: when I write ":set col" and hit tab, it'd be nice if it completed to color before completing directly to colors.completion.category.bg. This is certainly the feature that I see hardest to being useful given a proper implementation, because normally there could be a lot of partial different coincidences, for example typing "duckduck" maybe it should be changed to duckduckgo based on urls or DuckDuckGo based on page titles. It's also the thing I miss the least of these three. The other thing that disappoints me is that the browser is now significantly slower. For example, when I use DDG bangs, redirections are much slower than before. Overall, I'm not feeling bad about the update and I'd like to thank Florian and all the contributors for all the work you've done. =) Regards, José Alberto
