Skip to content
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

backslashes still treated as escapes in messages with no other markdown #3521

Closed
dbkr opened this issue Mar 27, 2017 · 1 comment
Closed

Comments

@dbkr
Copy link
Member

dbkr commented Mar 27, 2017

eg. foo & bar loses the backslash: it probably should not be treated as markdown at all, ie should keep the slash

@dbkr
Copy link
Member Author

dbkr commented Mar 28, 2017

Actually this is intentional: #2870

Agree it's confusing though, but the fix for this is to make markdown not the default, ie. land the rich text editor.

@dbkr dbkr closed this as completed Mar 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant