I cheked something and was right about what i thought the problem might be. Custom window names can be only 89 characters long, 90 including the @, and when decideding what window to go to looks like the /WINDOW command truncates whats between the " " to a max of 90 characters, if that 90 character window name doesnt exist then it errors. So if there is a file with a longfilename that makes the window over 90 charcters (note the SEND takes 5 characters S E N D SPACE or GET 4 and the nick also takes its number of characters + 1) then you cant access it, using /WINDOW -a " ".
An oddity occurs if for instance
you do
/write -c 12345678901234567890123456789012345678901234567890123456789012345678901234567890 tempfile
/write -c 123456789012345678901234567890123456789012345678901234567890123456789012345678901 tempfile
/dcc SEND BLAH 12345678901234567890123456789012345678901234567890123456789012345678901234567890
/dcc SEND BLAH 123456789012345678901234567890123456789012345678901234567890123456789012345678901
you get two windows as follows
SEND BLAH 12345678901234567890123456789012345678901234567890123456789012345678901234567890
SEND BLAH 123456789012345678901234567890123456789012345678901234567890123456789012345678901
if you go /window -a "SEND BLAH 123456789012345678901234567890123456789012345678901234567890123456789012345678901"
it focuses to "SEND BLAH 12345678901234567890123456789012345678901234567890123456789012345678901234567890" becuase thats the above truncated at 90 characters and the window also exists.
Now since this can cause an incorrect focus to occur not just a invalid window becuase its too long, I would say it can be called a real bug.
