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 Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category core
  • Assigned To No-one
  • Operating System Linux
  • Severity Medium
  • Priority Normal
  • Reported Version Irssi 0.8.11
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 0
  • Private No
Attached to Project: Irssi core bugs
Opened by Sean Whitton (spwhitton) - 2008-06-08

FS#599 - Newly created queries and empty windows from /layout save not being stuck to their container

I have a split window named snotes where I have various things directed for my staffing on a two networks. Snotes go there by a set level, and a script prints other stuff to that window. If I switch accidentally to this window, and then switch back to a query or something, and then close this query, my split is made my active window again so I lose the fact that I have two on the screen. It destroys the split. This obviously isn't quite a bug because I can then restore the window by doing /window new, putting snotes in it and resticking the window.

However, I can't do this and have to restart my client every time I make this mistake of letting my snotes window be moved out of its split position. This is because it seems new queries created in my lower section by people talking to me, and also windows that are empty from a /layout save that are awaiting content when I connect to other networks, are now inaccessible via the usage of Alt-Arrow keys. The only way to get to queries is to look at their number in my act bar and use a script to do /num which takes me then to the window. I can't get to it any other way and this is only fixed by restarting Irssi.

Looking at the output of /window tells me that it seems new windows being created and also these empty windows are not being stuck to their container (the non-snotes split of my screen). This is why I can't get to them. Surely new windows should be stuck when the only other container/area on the screen (sorry I get confused with this vocab) has something stuck to it, otherwise rendering them inaccessible? Hope this makes sense, thanks for a great app.

This task does not depend on any other tasks.