| Age | Commit message (Collapse) | Author |
|---|
|
Now the modifiers for mouse keys are in the same order as other keys: `alt-`
then `ctrl-`.
|
|
|
|
When raw code and alias for a key are both matching, the raw code must always
have higher priority.
This commit fixes this behavior and gives priority to raw code.
|
|
|
|
|
|
Changes:
- add function gui_key_debug_print_key
- change message "no key" by "no key binding"
- remove messages ""insert into input" / "ignored"
- add color for delimiters
|
|
|
|
|
|
(missing comma)
|
|
|
|
The raw key code is kept as-is, so for example "meta2-A" becomes "meta-[A".
|
|
mouse context
|
|
|
|
|
|
|
|
With this fix, fset buffer shows the key as modified only if the user actually
changed the command bound to the key.
|
|
`/fset` commands
|
|
Add missing safe keys: "backspace" and "return".
Add missing unsafe keys: "comma", "space".
|
|
|
|
|
|
|
|
Legacy keys are automatically converted to new names when loading configuration
file `weechat.conf`.
Examples:
"ctrl-I" => "tab"
"meta2-1;3A" => "meta-up"
"meta2-Z" => "shift-tab"
"meta-wmeta-meta2-A" => "meta-w,meta-up"
"ctrl-Cb" => "ctrl-c,b"
|
|
|
|
|
|
debug
|
|
|
|
gui_chat_printf_y_date_tags (closes #1883)
|
|
When the input buffer contains non word characters at the end, /input
move_next_word will stop moving at the end of the last word. This is
a bit confusing and not in line with what readline does (think bash).
When there are no words left in the input buffer, make /input
move_next_word go to the end of line.
Signed-off-by: Robin Jarry <robin@jarry.cc>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(issue #1875)
|
|
#1875)
|
|
gui_key_get_expanded_name (issue #1875)
|
|
|
|
matters (issue #1872)
|
|
|
|
(issue #1872)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
