-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Quoted blocks removed when visiting topics #45
Comments
This might be a gfm-mode setting; did you check any variables that might be hiding markup? (My wife is hoarding my laptop right now but I think it's labeled as some sort of 'clean' mode.) |
I can't find anything that might be doing so, but you've given me an idea. It may be that markdown-mode may be interpreting the content as the lang of the code-block as the whole quoted text is one line with triple backticks |
Considering that's not how quotes are formatted in markdown, I'd say it's a safe bet that it's not going to be interpreted as a quote :-) Quotes are formatted thus: > this is a quote For posterity, I'm pretty sure the variable I was thinking of is |
@vermiculus Yes, I quote with |
I find it unlikely that markdown-mode will ever do what you're asking it to do (which is to effectively ignore the most basic syntax rules of markdown!), but you might be able to hack the regular expressions markdown-mode uses to recognize quote blocks. You'll have better luck convincing others to use markdown correctly, I think :-) It is odd though that from getting the fontified text in |
|
If the delimiters are just one or two backquotes, then it doesn't do that. At least
where The reason that setting (remove-from-invisibility-spec 'markdown-markup) |
Fixed with jrblevin/markdown-mode#492. |
In particular I've encountered this behaviour in this Pull Request
stumpwm/stumpwm#544 (comment)
Note that there is a line with one empty space where the quoted block should be. Also I verified in the SQLite database that the quoted blocks are present
The text was updated successfully, but these errors were encountered: