| Age | Commit message (Collapse) | Author |
|---|
|
|
|
(max) bar size was described to be in chars, though this only applies to the left/right bars. This change clarifies that top/bottom bars would have their size defined in lines.
|
|
|
|
|
|
If you run /input jump_next_visited_buffer right after switching to a
buffer, weechat changes to the first buffer in the visited buffers list.
That is, it wraps around and goes to the buffer you visited the longest
ago. This patch fixes that.
The reason it happens is that when you switch to a buffer (normally,
i.e. in another way than using jump_previously_visited_buffer/
jump_next_visited_buffer) gui_buffers_visited_index is set to -1 (in
gui_buffer_visited_add). This makes gui_buffer_visited_get_index_next
return 0 because it returns gui_buffers_visited_index + 1, which makes
gui_input_jump_next_visited_buffer jump to the first buffer in the list
of visited buffers.
Fixes #1591
|
|
on SIGHUP when not running headless (closes #1595)
New options to customize behavior on signals received, with the default
behavior:
- weechat.signal.sighup: quit in normal mode, reload config in headless
- weechat.signal.sigquit: quit
- weechat.signal.sigterm: quit
- weechat.signal.sigusr1: no command executed by default
- weechat.signal.sigusr2: no command executed by default
The signals SIGUSR1 and SIGUSR2 are introduced by this commit, so it's now
possible to run commands when they are received.
The SIGHUP signal makes now WeeChat quit, it was the behavior before version
2.9 of WeeChat (see commit de1e61f7cd50cbd1a99777fe6611642a51abf5f6).
|
|
|
|
Regression was introduced in version 2.7 by commit
93d2dbf3e1ef30e676a6edd56ab2b9bd2ddd70d9.
|
|
|
|
weechat.look.read_marker_update_on_buffer_switch
Both default to "on" (no change to previous behavior).
If hotlist_update_on_buffer_switch is "off", then when switching away from a
buffer, the hotlist is not cleared.
If read_marker_update_on_buffer_switch is "off", then when switching away from
a buffer, the read marker is not set to the end of the buffer.
This allows users to choose to have fully manual control over when hotlist
counts and buffer read markers are reset.
Fixes #992.
|
|
|
|
"localvar" to "listvar"
The option "localvar" (introduced long time ago, in WeeChat 0.3.0) is still
recognized by WeeChat, to stay compatible with any extension/script calling
it (or referencing it in the documentation).
It is deprecated and will be removed in a future release.
|
|
(closes #1600)
When this local variable is set, it overrides the value of option
"weechat.completion.default_template".
It is evaluated, that means the global default template can be used to append
some custom completion. For example:
/buffer set localvar_set_completion_default_template ${weechat.completion.default_template}|%(my_completion)
|
|
|
|
This fixes a compiler warning complaining about a too small buffer for
snprintf, even if this should never happen.
|
|
|
|
|
|
(closes #1565)
|
|
on nick functions (issue #1565)
Functions tested:
- gui_nick_hash_djb2_64
- gui_nick_hash_djb2_32
- gui_nick_hash_sum_64
- gui_nick_hash_sum_32
- gui_nick_get_forced_color
- gui_nick_strdup_for_color
- gui_nick_find_color
- gui_nick_find_color_name
|
|
|
|
|
|
After these calls to malloc the memory is set to zero, so it's better to call
calloc that does it already.
|
|
(only if tag "notify_none" is not in the line) (issue #1529)
|
|
only if tag "notify_none" is not in the line (issue #1529)
|
|
is not in the line (issue #1529)
|
|
|
|
gui_line_get_nick_tag
|
|
gui_line_has_tag_no_filter
|
|
|
|
(closes #1529)
|
|
(closes #1450)
|
|
|
|
|
|
|
|
|
|
(issue #1257)
|
|
|
|
|
|
The bar item "buffer_nicklist_count" is now the number of displayed nicks
only (not groups).
New bar items:
- "buffer_nicklist_count_groups": number of groups displayed
- "buffer_nicklist_count_all": number of nicks and groups displayed
|
|
content (closes #1485)
|
|
|
|
|
|
first buffer is created
|
|
Relates to #1498
|
|
This allows blank lines to be displayed in the input bar when you input
multiple consecutive newlines.
Relates to #1498
|
|
Supporting multiple lines in the input bar is useful even for buffers
without input_multiline set, because it enables you to compose multiple
lines at once, even if it is sent as multiple messages. It is
particularly useful when you paste multiple lines and want to edit some
of it before you send the message.
|
|
(issue #984, issue #1063)
|
|
This allows the input callback function for a buffer to receive multiple
lines at once, instead of the message being split on newline before
being sent to the callback. It adds a new flag, input_multiline, to
control this. This flag defaults to 0 which is the current behavior.
|
|
modifier callback (closes #42)
|
|
The completion context can be "GUI_COMPLETION_NULL" if there's no base word
found (for example empty input).
|
