Irssi core bugs

Notice: Undefined index: tasklist_type in /var/www/ : eval()'d code on line 85 Notice: Undefined index: tasklist_type in /var/www/ : eval()'d code on line 90
  • Status New
  • Percent Complete
  • Task Type Bug Report
  • Category core
  • Assigned To No-one
  • Operating System Linux
  • Severity Low
  • Priority Normal
  • Reported Version irssi 0.8.15
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 0
  • Private No
Attached to Project: Irssi core bugs
Opened by Blacklight Shining (blacklightshining) - 2011-12-23
Last edited by Jase Thew (bazerka) - 2011-12-23

FS#828 - Some special messages are logged incorrectly

If a user sends an Op-message to #channel (with /msg @#channel), irssi logs it correctly (adding it to the current transcript for #channel). However (and I'm not sure with how many other types of messages it does this with), if a user sends an Admin-message (/msg &#channel), irssi will create a new transcripts folder called &#channel and start a new transcript just for that message, rather than adding it to the transcript in the #channel folder.

(I'm not sure how many versions are affected by this bug, but I found it on an Ubuntu machine running irssi v0.8.15.)

This task does not depend on any other tasks.

Jase Thew (bazerka)
Friday, 23 December 2011, 09:09 GMT
Irssi doesn't currently recognise &#channel (msg to all channel admins) or %#channel (msg to all channel half-ops) as being valid channel targets, so it logs and displays them incorrectly.
Blacklight Shining (blacklightshining)
Sunday, 01 January 2012, 10:59 GMT
Or +#channel (msg to all channel Voices). I'm not sure if the network considers !#channel a valid target, but you may want to look into that as well, for opers…although I don't imagine that it'd be used too often.