Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/unset-ing options with literal asterisk in its name will unset any matching options #112

tomoe-mami opened this Issue Jun 27, 2014 · 1 comment


None yet
2 participants
Copy link

commented Jun 27, 2014

/set allows literal asterisk to be used in option name (for example, /set plugins.var.perl.* foo) but /unset treats asterisk as wildcard which means if I try to /unset plugins.var.perl.* all options created by perl scripts under plugins.var.perl will be removed too. I think Weechat should forbids asterisk in option name or provides a way for /unset to specify literal option name.

I'm using Weechat 1.0-dev (6cdcb6f) [compiled on Jun 25 2014 03:15:29] on Slackware 14.1.

@flashcode flashcode added the bug label Jun 29, 2014

@flashcode flashcode self-assigned this Jun 29, 2014

@flashcode flashcode added this to the 1.0 milestone Jun 29, 2014


This comment has been minimized.

Copy link

commented Jul 12, 2014

In fact, asterisk can be used in option names, for example the script can use that, example: irc.freenode.*.hotlist_max_level_nicks_add = "weebot:-1" (to set hotlist max level to -1 for nick "weebot" on all channels of "freenode" server).
So instead of forbidding the asterisk, I'll update the /unset command to unset by default only one option (that can have asteriks inside). And add an extra parameter to unset more than one option (which is dangerous aynway, so forcing the user to add an extra parameter is not bad for me).

@flashcode flashcode closed this in e0312f7 Jul 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.