From 4d436e3ac653b9face748afbe4d3c96b797469b4 Mon Sep 17 00:00:00 2001 From: Sebastien Helleu Date: Fri, 2 Nov 2012 15:40:15 +0100 Subject: core: expand buffer local variables in evaluation of expressions (command /eval and function "string_eval_expression" in plugin API) --- doc/it/autogen/user/weechat_commands.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'doc/it/autogen/user') diff --git a/doc/it/autogen/user/weechat_commands.txt b/doc/it/autogen/user/weechat_commands.txt index ba77936b3..1bd978ad3 100644 --- a/doc/it/autogen/user/weechat_commands.txt +++ b/doc/it/autogen/user/weechat_commands.txt @@ -230,7 +230,8 @@ To force a string comparison, add double quotes around each expression, for exam Some variables are replaced in expression, using the format ${variable}, variable can be, by order of prioity : 1. the name of an option (file.section.option) - 2. a hdata name/variable (the value is automatically converted to string), by default "window" and "buffer" point to current window/buffer. + 2. the name of a local variable in buffer + 3. a hdata name/variable (the value is automatically converted to string), by default "window" and "buffer" point to current window/buffer. Format for hdata can be one of following: hdata.var1.var2...: start with a hdata (pointer must be known), and ask variables one after one (other hdata can be followed) hdata(list).var1.var2...: start with a hdata using a list, for example: -- cgit v1.2.3