Irssi core bugs

Notice: Undefined index: tasklist_type in /var/www/bugs.irssi.org/includes/class.tpl.php(128) : eval()'d code on line 85 Notice: Undefined index: tasklist_type in /var/www/bugs.irssi.org/includes/class.tpl.php(128) : eval()'d code on line 90
  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Feature Request
  • Category core
  • Assigned To No-one
  • Operating System Linux
  • Severity Low
  • Priority Normal
  • Reported Version Irssi SVN
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 0
  • Private No
Attached to Project: Irssi core bugs
Opened by Irssi Fan (irssi_fan) - 2005-02-22

FS#200 - [PATCH] add new levels for server-related connection messages

Connection errors and such currently use CLIENTNOTICE and CLIENTERROR. I would like those messages to remain in other windows, while receiving notices and errors generated by MY commands (like an invalid "/ command" or a notice generated by a "/ command") in the foreground window. I have added two new levels: SERVERNOTICE and SERVERERROR, to allow disconnection/reconnection activities to remain in the background windows.

Furthermore, I have added a boolean option, window_prefer_empty (default TRUE), which allows the user to enable or disable the current behavior of sending messages to windows with zero items in them. It is my desire that CRAP and CLIENT* messages remain in the foreground, as they are almost always generated as the result of some command I have issued.

I have also modified the WINDOW_LEVEL_MATCH code so that it takes server-sticky windows into account. This allows messages involving the reconnection of a disconnected server to continue to be printed to the background window belonging to that server, instead of cluttering up some other window.

This task does not depend on any other tasks.

Loading...