qutebrowser/doc
Florian Bruhin 7c39600508 Change default bindings for Up/Down in command mode
Those now look at the history again.
Looking at the behavior in different applications:

- vim: History
- spacemacs: Completion if open, else history
- luakit: Completion if open, else history
- dwb: Always completion (has no history?)
- vimb: Nothing if completion open, else history
- vimperator: Always history

So this is consistent with at least some of them - the much more important
factor is that <Tab> is probably intuitively easy to discover if up/down doesn't
do what's expected, but <ctrl-p>/<ctrl-n> are not.
2017-09-15 14:08:37 +02:00
..
help Change default bindings for Up/Down in command mode 2017-09-15 14:08:37 +02:00
img Update screenshots 2017-04-10 08:47:43 +02:00
backers.asciidoc backers: Add Bostan 2017-06-19 15:30:09 +02:00
quickstart.asciidoc Replace OS X with macOS 2017-07-08 11:12:43 +02:00
qutebrowser.1.asciidoc Initial doc update with new settings 2017-07-04 15:08:03 +02:00
stacktrace.asciidoc Improve Archlinux section in stacktrace.asciidoc 2016-09-14 12:42:19 +02:00
userscripts.asciidoc Replace OS X with macOS 2017-07-08 11:12:43 +02:00