Phil Do you use Ement ? I see your emacsd repository on GitHub wasn't updated since a year, and I was interested to see your ement configuration :)

dionisos: For no good reason I've been running from a wip branch for quite a long time, but my ement config is actually uncommitted as yet, so it's not even in that. Send me a private message to remind me, and I'll share it with you later (am busy right now).

In reply to rrix

In reply to @alphapapa:matrix.org

FYI, I've released v0.15 of Ement.el: https://github.com/alphapapa/ement.el/releases/tag/v0.15

Great looking release, congrats everyone and especially Phil's saintly work (sorry)

Cheers rrix!

In reply to Phil

dionisos: For no good reason I've been running from a wip branch for quite a long time, but my ement config is actually uncommitted as yet, so it's not even in that. Send me a private message to remind me, and I'll share it with you later (am busy right now).

Yes I just thought of that some hours ago (because I saw you also created a wip branch for your push request on Ement), and checked but didn't find you Ement config, happy that it is just because it is not committed 🙂

What does wip means btw ?

Work In Progress.

I actually run Ement in its own Emacs instance with an entirely separate config (albeit with some stuff copied from my regular config), so it's just a whole separate thing at the moment.

Oh ok, so this is why, this made sense

In reply to dionisos

Hi ! When I edit a message, every reactions on the message get deleted (this happened before the update, I was hopping for the update to fix it). The emoji are still here on Element-Desktop. Also, after a message is edited, if I had an emoji, it appears in Ement, but not in Element.

I've noticed that too, but hadn't reported it. Could you raise a github issue about it? I imagine it may relate to https://github.com/alphapapa/ement.el/issues/230 so I'd reference that in the new issue.

I will try to do it today

Also I am wondering, is there a way to avoid the <p></p> tags around the message when using the compose org-mode format ? (the problem is that it removes simple line break and also it adds a final line break for Element users)

You need to use two newlines to force a new paragraph if you're using the org export.

I don't know of a trivial way to omit the <p> tags, though – no doubt you can interact with the shr rendering, but I'm not sure that's a good idea… Matrix uses HTML for fancy message formatting, so I think those paragraph tags should be supported in a sane way by any client, really.

(I wouldn't expect Element to render "foo" and "<p>foo</p>" differently, in other words; and if it does, I think that's a bug in Element.)

In reply to Phil

You need to use two newlines to force a new paragraph if you're using the org export.

I don't know of a trivial way to omit the <p> tags, though – no doubt you can interact with the shr rendering, but I'm not sure that's a good idea… Matrix uses HTML for fancy message formatting, so I think those paragraph tags should be supported in a sane way by any client, really.

Is there a simple way to add only one line break ?

In reply to Phil

You need to use two newlines to force a new paragraph if you're using the org export.

I don't know of a trivial way to omit the <p> tags, though – no doubt you can interact with the shr rendering, but I'm not sure that's a good idea… Matrix uses HTML for fancy message formatting, so I think those paragraph tags should be supported in a sane way by any client, really.

Yes I agree with this, but removing the <p> tag would have been a simple way to deal with this problem while waiting for a fix from their part (I mean, if it was simple to do it).

I will try to see what it is possible to do with the shr rendering, even if I agree it should just display in a sane way to begin with.

I think you either set org-export-preserve-breaks (see (info "(org) Export Settings")) or else use the verse block type (see (info "(org) Paragraphs")).

https://github.com/alphapapa/ement.el/issues/277

In reply to Phil

I think you either set org-export-preserve-breaks (see (info "(org) Export Settings")) or else use the verse block type (see (info "(org) Paragraphs")).

This works perfectly, thank you 🙂

Do you think this issue is linked to the fact that when we edit reply it breaks the reply ?

What do you mean by "breaks" ?

In reply to Phil

What do you mean by "breaks" ?

Like that

Btw, the new way to send reactions, and the new way to send message with the buffer below the room, is way better, thank you 🙏🙂

I also like that it is easy to give alternative names to emoji with emote-search

Oh, right. No, I believe that's a different issue. The message being replied to is trivially available when initially writing the reply, but it's more indirect when editing the reply, and what you end up editing is a less-fancy version of the quote which is included in the plain text portion of the reply event.

Longer term there's https://github.com/alphapapa/ement.el/pull/150 for "rich reply" support, and that issue probably falls under that umbrella.

In reply to dionisos

I also like that it is easy to give alternative names to emoji with emote-search

For people who don't like losing time for emojis which also ask for a color with emote-search, it is possible to remove it likes that :

(setq emoji--derived (make-hash-table :test 'equal))