qqq wrote:Well, it takes all sorts![]()
The only question that bothers me now is how do I change it so that I don't have to edit default key bindings on every build.
I believe you can put them in Base File.sublime-settings
qqq wrote:Well, it takes all sorts![]()
The only question that bothers me now is how do I change it so that I don't have to edit default key bindings on every build.
qqq wrote:How do you change this behaviour using your user key bindings file?
{ "keys": ["tab"], "command": "next_field", "context":
[
{ "key": "last_command", "operator": "equal", "operand": "insert_best_completion" },
{ "key": "setting.tab_completion", "operator": "equal", "operand": true },
{ "key": "has_next_field", "operator": "equal", "operand": true }
]
}
{ "keys": ["tab"], "command": "pass", "context":
[
{ "key": "last_command", "operator": "equal", "operand": "insert_best_completion" },
{ "key": "setting.tab_completion", "operator": "equal", "operand": true }
]
}
Goto Anything no longer smooth scrolls
"tab_completion": falsetheblacklion wrote:Jon, can you somehow give tab triggers more priority?
jps wrote:What do you have in mind?
theblacklion wrote:I think the first behavior is wrong. A completion only makes sense if no tab trigger could be found/executed. Tab triggers should always have a higher prio / being checked first.
Users browsing this forum: No registered users and 6 guests