You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like the ability to configure Element so by default it doesn't go through markdown unless I specify it.
Why would you like to do it?
Some messages get mangled due to markdown being always-on unless I use /plan, for example if I'm sending irc-style hostmasks, ie !@*.hostname.tld in a irc channel results in the *'s being interpreted as <em></em>. Its nice to have markdown but coming from a IRC background I'm much more used to sending plain messages.
How would you like to achieve it?
A preference option for this would be nice, when I mentioned it in a room someone also mention it'd be nice to have as a per-room option as well.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
It seems you're not the only one to have come across this bug, as it's been reported previously. I'm going to close this issue now so we can focus on the older issue. Please watch, vote or comment on that issue if there is any additional information you can provide.
Your use case
What would you like to do?
I would like the ability to configure Element so by default it doesn't go through markdown unless I specify it.
Why would you like to do it?
Some messages get mangled due to markdown being always-on unless I use /plan, for example if I'm sending irc-style hostmasks, ie !@*.hostname.tld in a irc channel results in the *'s being interpreted as
<em></em>
. Its nice to have markdown but coming from a IRC background I'm much more used to sending plain messages.How would you like to achieve it?
A preference option for this would be nice, when I mentioned it in a room someone also mention it'd be nice to have as a per-room option as well.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: