This pointer is the first argument received by callbacks, and the
existing argument "data" is now automatically freed by WeeChat when the
object containing the callback is removed.
With this new pointer, the linked list of callbacks in scripts has been
removed. This will improve speed of scripts (using a lot of hooks),
reduce memory used by scripts and reduce time to unload scripts.
Following functions are affected in the C API:
* exec_on_files
* config_new
* config_new_section
* config_new_option
* hook_command
* hook_command_run
* hook_timer
* hook_fd
* hook_process
* hook_process_hashtable
* hook_connect
* hook_print
* hook_signal
* hook_hsignal
* hook_config
* hook_completion
* hook_modifier
* hook_info
* hook_info_hashtable
* hook_infolist
* hook_hdata
* hook_focus
* unhook_all_plugin
* buffer_new
* bar_item_new
* upgrade_new
* upgrade_read
There was a bug with "num_displayed" in buffers when they are merged and
that one buffer is zoomed: now the num_displayed is > 0 for the active buffer,
and it is set to 0 for all merged non-active buffers (only in case of zoom).
A variable "zoomed" has been added in buffers to know if a buffer with this
number is zoomed or not (possibly another buffer).
The bug was introduced by commit 8fac1eea40
which purpose was to not scroll to the end of buffer with "/window scroll -N"
when the top of buffer is displayed.
This commit is adding the syntax "--N" to force a scroll from the end (only
used by "/window scroll_bottom").
New key: alt+"!", to swith to bare display (same key to come back to
standard display).
New options:
- weechat.look.bare_display_exit_on_input (default: on): by default
any changes in input will return to standard display
- weechat.look.bare_display_time_format (default: "%H:%M"): the format
of time used in bare display.
The bug is when all buffer lines are unread (so "last_read_line" pointer
is NULL), and that the option weechat.look.read_marker_always_show is on.
The read marker was displayed at bottom after switch to the buffer.
Thanks to Nils Görs.
Bug was visible with such colored string in IRC:
^Cc7,5 one ^Cc ^Cc7 two
Before the fix, the word "two" had a red background.
The "^Cc" should reset both color + background, so now it does not have
a background any more.
A regression was introduced by commit bee56c3b7f
(/window scroll_beyond_end).
Scenario to reproduce the problem, for example on an IRC channel with a long
history (more than two pages):
/window page_up
/window page_down
<type some text and send to channel>
It will display -MORE(1)- instead of automatically scrolling to bottom of
buffer.
Sébastien Helleu