Skip to content
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

Fixed bug with coilon inside message string #133

Closed
wants to merge 1 commit into from
Closed

Fixed bug with coilon inside message string #133

wants to merge 1 commit into from

Conversation

ralphtheninja
Copy link

If you write e.g. "this is a message with : a colon in it" the resulting string is ":this" because it parses the last colon found, not the first.

@quentinxs
Copy link
Contributor

Already fixed (though not committed), please see the comments under #128.

quentinxs added a commit to quentinxs/node-irc that referenced this pull request Jan 19, 2013
This fixes issues martynsmith#122, martynsmith#128 and martynsmith#133.

Example lines include:
    :some.irc.net 324 webuser #channel +Cnj 5:10
    :nick!user@host QUIT :Ping timeout: 252 seconds
    :nick!user@host PRIVMSG #channel :so : colons: :are :: not a problem ::::
@martynsmith
Copy link
Owner

I'm going to close this now (pull request #137 from @qsheets fixed this issue I believe).

If you still have issues, please pull master and look at the tests I've written, if you can extend the tests with your own failing examples, that will provide a much better basis for trying out new patches).

Thanks,

uiur pushed a commit to uiur/node-irc that referenced this pull request Feb 2, 2013
This fixes issues martynsmith#122, martynsmith#128 and martynsmith#133.

Example lines include:
    :some.irc.net 324 webuser #channel +Cnj 5:10
    :nick!user@host QUIT :Ping timeout: 252 seconds
    :nick!user@host PRIVMSG #channel :so : colons: :are :: not a problem ::::
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants