| Age | Commit message (Collapse) | Author |
|---|
|
trigger evaluated strings (closes #1624)
|
|
operator in ${if:xxx} (closes #1627)
To force evaluation of the expression before doing the comparison (less safe),
the "${eval_cond:xxx}" can be used.
With the old behavior we had:
>> ${if:a==b}
== [0]
>> ${if:${raw:a==b}}
== [0]
>> ${if:${eval_cond:${raw:a==b}}}
== [0]
And with the new behavior, we have:
>> ${if:a==b}
== [0]
>> ${if:${raw:a==b}}
== [1]
>> ${if:${eval_cond:${raw:a==b}}}
== [0]
|
|
|
|
This used pointer1 and pointer2 which are pointers to the buffers, but
it should use ptr_hotlist1 and ptr_hotlist1 which are pointers to the
hotlists it is trying to compare.
|
|
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
|
|
|
|
and in hdata)
These two formats are now supported, if "pointer_name" is present in the
"pointers" hashtable:
* "${pointer_name}": value of pointer (example: "0x1234abcd")
* ${buffer[pointer_name].full_name}: use of a pointer name instead of pointer
value or list name
|
|
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).
|
|
|
|
sec.crypt.passphrase_command
|
|
|
|
|
|
if buflist is disabled (issue #1618)
|
|
|
|
|
|
|
|
Regression was introduced in version 2.7 by commit
93d2dbf3e1ef30e676a6edd56ab2b9bd2ddd70d9.
|
|
|
|
Use "!" instead of "@" to separate nick from host, like it is done in IRC
protocol.
The nick and host is now displayed as "nick!user@host" instead of
"nick@user@host".
|
|
|
|
|
|
(closes #1613)
|
|
|
|
|
|
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.
|
|
sec.crypt.passphrase_command (closes #141)
The command is used to read the passphrase on startup, for example using your
favorite password manager.
Note: only the passphrase is read from the program, the secured data is still
stored encrypted in sec.conf and handled by WeeChat itself.
|
|
|
|
|
|
|
|
irc_nick_is_nick
|
|
adding channel type on join
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This fixes the following warning:
/usr/bin/xgettext: warning: msgid 'server' is used without plural and with plural.
./src/plugins/irc/irc-bar-item.c:136: Here is the occurrence without plural.
./src/plugins/irc/irc.c:154: Here is the occurrence with plural.
Workaround: If the msgid is a sentence, change the wording of the sentence; otherwise, use contexts for disambiguation.
|
|
|
|
API reference)
|
|
|
|
Now a single -d in command /eval shows less debug messages than previous
versions.
To get the same debug messages than previous versions, two -d must be used.
|
|
|
|
Now, /eval -n -c "a" == "a" returns True instead of False.
When quotes were removed, the condition evaluated was: a" == "a (which is
False).
|
|
"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)
|
|
|
|
|
|
|
|
|
