Add a New Comment (Rich Markup)
If you use "/notice @#channel my message" you should get the expected behavior.
I've reported a similar bug for opnotices in the past (which got fixed), but apparently the behaviour still is broken for privmsgs to channels. Expected behaviour:
On #someChan: /msg @#someChan Hey guys, maybe we should kick this idiot. MsgOp -> #someChan: Hey guys, maybe we should kick this idiot. MsgOp(SomeOtherOp): Yeah, I agree.
Current behaviour:
On #someChan: /msg @#someChan Hey guys, maybe we should kick this idiot. On Server buffer: 192010 FiXato> MSG(@#someChan): Hey guys, maybe we should kick this idiot. SomeOtherOp replies with a /msg @#someChan and a query buffer with him opens: 192010 <SomeotherOp> Yeah, I agree.
Some, to summarise: Currently privmsg's to some level (ops, halfops, voiced, etc) on a specific channel show up in separate query buffers for those users, while the expected behaviour would be to have those message show up in the channel. (Just like with OpNotices and VoiceNotices)
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 3 latest changes.
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.11