-
Notifications
You must be signed in to change notification settings - Fork 31
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
Markdown support. #30
Comments
Ricin now supports bolded, italicized, underlined and |
It should also support |
@rugk commented on 21 Nov 2015, 12:51 GMT+1:
Hmm, I guess this is a bad idea cuz it would permit people to "spoof" links. What if someone send you a link like: |
hovering over the named link should give the link itself |
@gmscs Hmm, maybe i should add this so. |
This can be closed since this comment seems to be the one that will be approved → Tox/Tox-Client-Standard#25 (comment) |
Ricin should provide a way to use (basic) Markdown to format messages. This is not really hard to do but the real issue is for client compatibility. I guess this shouldn't be a major issue since markdown was reflexed to be readable, even in plaintext.
(Pseudo-) Markdown "balises" we could provide:
**bold** text
: Permit to bold a message's part._italic_ text
: Permit to italicize a message's part.~~striked~~ text
: Permit tostrikea message's part.--underlined-- text
: Permit to underline a message's part.Ricin (with Markdown lite support):
µTox (with no Markdown support):
Also, see the qTox issue about that: qTox/qTox#2497
It was an issue opened on Tox-STS repo: Tox-Archive/Tox-STS#74
And @subliun opened a new issue: Tox/Tox-Client-Standard#19
The text was updated successfully, but these errors were encountered: