weechat - The extensible chat client.

Age	Commit message (Collapse)	Author
2018-01-05	core: update copyright dates	Sébastien Helleu

2017-10-17	core: allow floating point and hexadecimal numbers in comparison of ↵	Sébastien Helleu
	evaluated values
2017-08-12	core: fix cast of time_t (to "long long" instead of "long") (closes #1051)	Sébastien Helleu

2017-05-28	core: remove unused variable "index" in function eval_hdata_get_value	Sébastien Helleu

2017-05-20	core: allow index for hdata arrays in evaluation of expressions	Sébastien Helleu

2017-04-29	core: add wildcard matching operators to eval (closes #608)	Simmo Saan

2017-04-25	core: fix check of condition in ${if:...} (evaluated strings)	Sébastien Helleu

2017-04-25	core: add new cut formats in function comment	Sébastien Helleu

2017-04-24	core: add a way to count the suffix length in max chars displayed in cut of ↵	Sébastien Helleu
	string ("cut:" and "cutscr:") (closes #963) The format to use is one of: - ${cut:+max,suffix,string} - ${cutscr:+max,suffix,string} With the "+" before max, WeeChat ensures there are at most "max" chars in output, including the length of suffix string.
2017-03-30	core: add ${re:#} to get the index of last group captured in evaluation of ↵	Sébastien Helleu
	expressions
2017-03-27	core: add cut of string with max chars displayed in evaluation of expressions	Sébastien Helleu
	The syntax is: ${cutscr:max,suffix,string}. The string is cut after max chars displayed on screen. If the string is cut, the optional suffix is added after.
2017-03-25	core: prevent infinite loop in evaluation of expression with extra_vars_eval	Sébastien Helleu
	When extra variables are evaluated, to prevent infinite loop if the evaluated variable is calling itself, it is removed from hashtable "extra_vars" before evaluation.
2017-03-25	core: add cut of string in evaluation of expressions	Sébastien Helleu
	The syntax is: ${cut:max,suffix,string}. The string is cut after max chars. If the string is cut, the optional suffix is added after.
2017-03-25	core: add ternary operator (condition) in evaluation of expressions	Sébastien Helleu

2017-01-01	core: update copyright dates	Sébastien Helleu

2016-08-18	core: move the extra_vars_eval argument after extra_vars	Sébastien Helleu

2016-08-18	core: fix empty comment	Sébastien Helleu

2016-08-18	Merge remote-tracking branch 'origin/pr/534'	Sébastien Helleu

2016-01-01	core: update copyright dates	Sébastien Helleu

2015-08-18	core: add extra_vars evaluation option to eval_expression	Simmo Saan

2015-07-04	core: add missing comments before functions when the result must be freed ↵	Sébastien Helleu
	after use
2015-06-30	api: add support of evaluated sub-strings and current date/time in function ↵	Sébastien Helleu
	string_eval_expression() and command /eval
2015-06-23	core: allow pointer as list name in evaluation of hdata (closes #450)	Sébastien Helleu

2015-04-26	api: add support of environment variables in function ↵	Sébastien Helleu
	string_eval_expression() and command /eval (issue #388)
2015-04-26	core: add support of full color option name in command /eval and API ↵	Sébastien Helleu
	function string_eval_expression()
2015-01-01	core: update copyright dates	Sébastien Helleu

2014-11-23	core: fix regex replace in eval_expression when regex or regex_replace is empty	Sébastien Helleu

2014-10-22	api: add regex replace feature in function string_eval_expression	Sébastien Helleu

2014-10-16	core: add hide of chars in string in evaluation of expressions	Sébastien Helleu
	The syntax is: ${hide:char,string}. All chars in string are replaced with char (which can be one or more chars).
2014-10-12	core: move default prefix/suffix for evaluation in wee-eval.h	Sébastien Helleu

2014-08-13	core: make argument "errors" optional in function string_replace_with_callback	Sébastien Helleu

2014-07-12	core: fix evaluation of expressions with regex condition (closes #63)	Sébastien Helleu
	The regex itself is not evaluated any more (so parentheses are kept). Before the fix: >> abcd =~ (?-i)^abc == [0] >> (abcd) =~ $abcd$ == [0] After the fix: >> abcd =~ (?-i)^abc == [1] >> (abcd) =~ $abcd$ == [1]
2014-04-04	core: fix evaluation of expression with regex when a comparison char is in ↵	Sébastien Helleu
	the regex
2014-03-06	core: fix recursive calls to function eval_expression	Sebastien Helleu

2014-03-02	core: fix memory leak in evaluation of sub-conditions	Sebastien Helleu

2014-02-28	api: add support of escaped strings in function string_eval_expression and ↵	Sebastien Helleu
	command /eval
2014-01-26	core: fix memory leak in regex matching when evaluating expression	Sebastien Helleu

2014-01-08	core: fix crash in /eval when config option has a NULL value	Sebastien Helleu

2014-01-05	core: fix crash with hdata_update on shared strings, add hdata type ↵	Sebastien Helleu
	"shared_string" (bug #41104)
2014-01-01	core: update copyright dates	Sebastien Helleu

2013-11-09	api: add support of infos with format `${info:name,arguments}` in function ↵	Sebastien Helleu
	string_eval_expression and command /eval
2013-08-25	core: fix evaluation of expressions with parentheses	Sebastien Helleu
	First evaluate sub-expressions between parentheses. Before the fix: >> 1 && (0 \|\| 0) == [1] After the fix: >> 1 && (0 \|\| 0) == [0]
2013-08-04	core: optimize creation of hashtable "pointers" in eval_expression if ↵	Sebastien Helleu
	argument is NULL The hashtable is created on first call to eval_expression with pointers == NULL. On next calls, the hashtable is cleared, then used again. The hashtable is freed on exit.
2013-08-04	api: add support of colors with format "${color:xxx}" in function ↵	Sebastien Helleu
	string_eval_expression and command /eval
2013-08-04	api: add argument "options" in function string_eval_expression, add option ↵	Sebastien Helleu
	"-c" for command /eval (to evaluate a condition)
2013-07-27	core: add secured data with optional encryption in file sec.conf	Sebastien Helleu

2013-07-24	core: fix priority of logical operators in evaluation of expression	Sebastien Helleu
	The AND ("&&") takes precedence over the OR ("\|\|"). Before the fix: >> 1 \|\| 1 && 0 == [0] After the fix: >> 1 \|\| 1 && 0 == [1] Since the "&&" has higher priority, expression is evaluated as: "1 \|\| (1 && 0)".
2013-07-08	core: fix crash in evaluation of expression when reading a string in hdata ↵	Sebastien Helleu
	with a NULL value (bug #39419)
2013-03-17	core: fix typos in many comments and some strings	Sebastien Helleu

2013-01-26	core: use size of 32 for hashtables (instead of 4, 8 or 16)	Sebastien Helleu
	A size of 32 will use a little more memory but will reduce collisions in key hashs, and then length of linked lists inside hash structure (faster search in hashtable).