rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Explain timeout vs partial-timeout better in docs.

Browse Source
This commit is contained in:
Ryan Roden-Corrent 2016-04-25 23:27:58 -04:00
parent 0c1e82a103
commit 86f95c302d
2 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/help/settings.asciidoc
View File

@ -863,12 +863,16 @@ Options related to input modes.
=== timeout
Timeout for ambiguous key bindings.
If the current input forms both a complete match and a partial match, the complete match will be executed after this time.
Default: +pass:[500]+
[[input-partial-timeout]]
=== partial-timeout
Timeout for partially typed key bindings.
If the current input forms only partial matches, the keystring will be cleared after this time.
Default: +pass:[1000]+
[[input-insert-mode-on-plugins]]

8
qutebrowser/config/configdata.py
View File

@ -470,11 +470,15 @@ def data(readonly=False):
('input', sect.KeyValue(
('timeout',
SettingValue(typ.Int(minval=0, maxval=MAXVALS['int']), '500'),
"Timeout for ambiguous key bindings."),
"Timeout for ambiguous key bindings.\n\n"
"If the current input forms both a complete match and a partial "
"match, the complete match will be executed after this time."),
('partial-timeout',
SettingValue(typ.Int(minval=0, maxval=MAXVALS['int']), '1000'),
"Timeout for partially typed key bindings."),
"Timeout for partially typed key bindings.\n\n"
"If the current input forms only partial matches, the keystring "
"will be cleared after this time."),
('insert-mode-on-plugins',
SettingValue(typ.Bool(), 'false'),