-
Notifications
You must be signed in to change notification settings - Fork 84
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
Add chanset bind #1524
base: develop
Are you sure you want to change the base?
Add chanset bind #1524
Conversation
Single setting:
Mask bind:
Multi-chan binds:
|
We should use the return value of the Tcl proc to deny the change as invalid. That could be in a new PR, but it is one of the main reasons for the bind, so you can reject a "setudef str" value if it's not valid for your use-case. |
Added @thommey great suggestion:
|
need-* settings can allow multiple strings (such as {putlog op me cuz I'm lame}- the attempted fix did not take this into account and would break things
Updated logic to allow other chanset values submitted in a single command that don't match the bind to proceed Using the same proc/bind as above:
Note +bitch was not set, but other values in the chanset command were. One more example that involves the other call to
|
Patch by: Geo
Fixes: #1393
This PR adds a bind that triggers when a channel setting is set via the chanset partyline command.