Skip to content
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.

Channel beep chanopt applied to wrong channels #1523

Open
VasVadum opened this issue Oct 26, 2015 · 3 comments
Open

Channel beep chanopt applied to wrong channels #1523

VasVadum opened this issue Oct 26, 2015 · 3 comments

Comments

@VasVadum
Copy link

I have two channels set to "beep on message" but sometimes, others suddenly set themselves to beep on message without any warning, and start beeping on message. I have no clue why or which channel it is either. I would like you to add a ♪ before the # on channels with beep on message turned on. But also stop channels that shouldn't have it from randomly being assigned. It often happens with that channel in issue #1522 , I think that it might even be the only one it's happened on thus far. I won't be saying the channel name publicly.

@TingPing TingPing changed the title [request] [Issue] Beep on Message Channel beep chanopt applied to wrong channels Oct 26, 2015
@TingPing
Copy link
Member

How are you setting this, and what does chanopt.conf look like?

@VasVadum
Copy link
Author

network = Furnet
channel = #PrivateChannel
alert_beep = 1

network = Furnet
channel = #starcraft
alert_beep = 1

That's what it looks like currently. Except the channel name on the top one. :P
I set it via right clicking the channel, hovering over Extra Alerts, clicking Beep on Message.

It seems after a disconnect/reconnect, sometimes this beep setting gets applied to other channels, especially after they've moved around.

@TingPing
Copy link
Member

Hmm, I suppose that makes sense. Chanopt is applied to a context and upon reconnect that context is reused for a different channel.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants