H.G.Muller wrote:You are right. I checked the code, and it turns out I already use a case-insensitive compare to test if an incoming tell matches the Chat partner.
Can it be that there inadvertently was a space entered before or after the name in the Chat partner field? This would explain the behaviour, as it would spoil the equality of the handle extracted from the tell command (which is always stripped of surrounding spaces) and the contents of the Chat partner field. While an extra space in the sent command would be ignored by the ICS, which doesn't care if you separate name and message by one or two spaces. (In the worst case it would consider the extra space part of the message, but I don't even think it does that.) And it would not be obvious from the screen shot.
I am just guessing here, but this would explain everything (including the fact why in other cases everything seemed to work as intended). Perhaps I should make sure leading and trailing spaces are stripped off, when a new Chat partner is entered, to guard against this possibility.
I just tried to send a tell in a channel by adding a white space in front of the channel number. What it does is that it indeed sends the tell to that channel, but my text is not echoed into the ICS window, be it in the chat or in the background. I know I could send the text because I typed a command in FICS that sends me the tells from the last 5 minutes and my text appeared, even though it is totally invisible to me.
I tried to add a white space (and then 5 white spaces) after the channel number. What it does is that whenever I send a tell, there are white space in front of my text.
So it seems to me that this wasn't the case with what happened with AcCoNcIo. It is not the first time I experience the bug with acconcio and I don't know how to reproduce it.