-
Notifications
You must be signed in to change notification settings - Fork 421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event on successful pm #56
Comments
Well certainly in all the clients I've ever used if you do Apart from the fact that I'm not entirely sure by what you mean message went through, I'm not sure there's even a reliable way of determining that. Can you provide me an example of an existing IRC client that behaves as you specify? |
Colloquy on Mac does open a new window for Apparently the behavior distinction you mentioned is somewhat of a convention:
I was surprised to discover that neither The biggest issue here is that messages appears to go through even when the nick doesn't exist. Know any way to avoid that? |
Turns out this is emitted by the server when sending a message to a bogus nick:
I wonder if it would be useful to handle this in node-irc? Or if I should just deal with it in the client through the |
I think errors such as that should just be handled by the client. It's not really the place of the library to go interpreting all that stuff in too much detail I think. Also, you would never get an immediate response with your window, there's always server lag, and given you get no "everything worked fine" response from the server, how long should you wait before opening your window? It's impossible to know. |
Sounds good, I wasn't aware that this error was sent from the server when I filed the issue. I already coded it to open a new window immediately when a message is sent. My plan is to continue to let that happen, but throw a big obvious error in the channel window indicating the no such nick/channel error. |
When sending a PRIVATEMSG to someone, it would be helpful if node-irc emitted an event indicating that the message went through.
As designed now, if you want to open a new window when I send a pm (as opposed to receiving one), I have to special-case it (other windows are opened only after event is emitted from node-irc). And if the nick doesn't exist, you've just opened a window that shouldn't be there.
The text was updated successfully, but these errors were encountered: