Adam Porter

> Excluding the sender field from the matching wouldn't have any of the mentioned issues. I think we must be miscommunicating. If the message body has one of these bridged...

> The way I've been avoiding this in practice is by using `ement-notify--room-unread-p` instead of `ement-room--event-mentions-user-p`. That has the problematic side-effect of notifying for every subsequent message after a mention....

> I think it's obvious by looking at the code I posted, but the way I'm > doing it is by looking at the entire message body and seeing whether...

> Ah, the docstring got messed up when I pasted the code, sorry about that. It's fixed now. > > In a way, the function already works in "positive terms"...

@sergiodj It seems that I was looking at https://github.com/alphapapa/ement.el/issues/281#issuecomment-2198437824 while you were updating the code in https://github.com/alphapapa/ement.el/issues/281#issue-2371217306.

@sergiodj I'm not sure what you mean; https://github.com/alphapapa/ement.el/issues/281#issuecomment-2198447771 has no code in it.

Well, those errors are certainly weird: * `plz-error :curl-error (26 . "Read error. Various reading problems."` * `Network error: 9: FTP access denied.` They suggest that something is very unusual,...

Well, v0.9 of plz has been released, so you could install that, but it's unlikely to matter. I don't know what's going on here. It's bizarre. You'll probably have to...

I don't know. Like I said, this is utterly bizarre. If it's feasible, my best advice is to try reproducing the problem in a virtual machine running a different Linux...

It would be best if you tried to use the same versions of Emacs and curl that you got the errors on. Otherwise we do not narrow the problem space,...