Skip to content

Conversation

@ajaspers
Copy link
Contributor

This avoids "No such nick" responses to +draft/typing TAGMSG, etc.

This avoids "No such nick" responses to +draft/typing TAGMSG, etc.
@DanielOaks
Copy link
Member

Really nice cleanup mate, awesome work


user := server.clients.Get(target)
if user == nil {
if histType != history.Notice {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or, possibly a simpler fix, this could be "if histType != history.Notice && histType != history.Tagmsg" ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either way works for me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we reply with "No such nick" errors in response to TAGMSG in general?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, yep

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, then the current fix is better. Thanks.

@slingamn
Copy link
Member

This is great, thanks!

@slingamn slingamn added this to the v2.1 milestone May 25, 2020
@slingamn slingamn merged commit 29165de into ergochat:master May 25, 2020
@ajaspers ajaspers deleted the services branch May 25, 2020 15:07
slingamn added a commit to slingamn/ergo that referenced this pull request May 25, 2020
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