-
Notifications
You must be signed in to change notification settings - Fork 60
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
Unable to reply to a multi-line message using any line's short thread ID #480
Comments
Try PR #482 this should fix the issue |
Thanks for this, now we can clearly identify multi line messages. Although, if I might nitpick, this change breaks 2 things:
Maybe we need to also prefix current thread ID and suffix |
Nice, thanks! |
* Do not split message on newlines This fixes #480 and as a bonus also fixes #426 as this is now just 1 big message for irc See also #483 * Check code block start on multiple lines * Ensure prefixcontext/suffixcontent shown for all lines in a multi-line message (#483) * Ensure prefixcontext/suffixcontent shown for all lines in a multi-line message * Make showing context for multi-line messages configurable * Fix to handle empty lines now that we're splitting elsewhere * Restore changes to MsgSpoofUser() and Spoof() per review * Allow overriding max. line length * Fix to correctly add message thread context * Refactor and remove duplicate code per review Co-authored-by: Haw Loeung <haw.loeung@canonical.com>
When using short thread IDs, if someone sends a multi-line message, matterircd sends the messages to the client with auto-incremented short IDs for each line of the message.
Then when an IRC user wants to reply to the thread, it seems they need to use the last short thread-ID only, else matterircd will fail to detect which thread it belongs to, and will send @@xxx prefix in the message, without a warning it could not find the thread ID.
Also, there is absolutely no indication that a received line is part of a multi-line message, or that every line of these message belong to a specific thread ID, hence there is no way for a user to know they should reply using the last message's thread ID.
Example from IRC client side:
From Mattermost side:
Thank you
The text was updated successfully, but these errors were encountered: