-
Notifications
You must be signed in to change notification settings - Fork 150
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
One or two sed bugs #1627
Comments
Probably element-hq/element-web#22456 Matrix messages work like multipart emails; ie. senders write the same content in multiple formats, and receivers only pick one of the formats. Here, Element sends different content in each format, and matrix-appservice-irc does not read the same format that most Matrix clients do. |
Thanks for the extremely swift reply. [Written before your edit above] A (different) user reasonably pointed out that the escaping might have been done intentionally by the (above) user, to remove unwanted mark-up. I did look at the message on the Matrix side before reporting this and didn't see any formatting, but now I notice both ‘versions’ are in fact identical in Element: https://www.tobias.gr/temp.png I'm aware that this isn't the Element bug tracker, but am I misunderstanding how history works? |
That'd be a bug, yes :)
Yeah, that's not ideal. Off the top of my head the only way to improve it without adding massive amounts of noise would be to use the regex adverbs that Raku (formerly Perl 6) uses, like |
Hi! Not a severe bug report, but I just saw a strange
s/…/
cross the bridge and thought you might be interested.When a Matrix user edited
user: I am new to guix. When reading https://guix.gnu.org/manual/devel/en/html_node/Using-the-Configuration-System.html, I says "Rust is currently unavailable on non-x86_64 platforms". Is that still true?
into
user: I am new to guix. When reading https://guix.gnu.org/manual/devel/en/html_node/Using-the-Configuration-System.html, it says "Rust is currently unavailable on non-x86_64 platforms". Is that still true?
the bridge produced:
user[m]: s/html_node/html\_node/, s/I/it/, s/x86_64/x86\_64/
I'm not entirely sure whether
s/I/it/
is strictly a bug or an attempt to emulate how humans uses/…/
informally, expecting the reader to know whichI
was obviously wrong.If so, maybe that heuristic could be tweaked to avoid the extreme ambiguity here, or maybe it's working as designed. Or it's a bug :-)
The other two are just bogus. It looks like a string is mistakenly escaped twice before being fed into the diff — but interestingly, only on one side?
…wait, why is
_
being escaped at all?The text was updated successfully, but these errors were encountered: