-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
Fontify Grimoire code blocks if possible #2007
Conversation
67a9bd1
to
c1ec450
Compare
Looks good! Just add a changelog entry, refer in the commit message to the ticket this is solving and take care of the byte-compilation warnings. |
c1ec450
to
5e8cef9
Compare
I'm not 100% sure if I'm also not sure why build 4636.5 failed while others pass. Is it just a stricter setting that treats certain warnings as errors? Update: seems like the recommended way (using |
f779e28
to
82b85b1
Compare
@@ -35,6 +35,8 @@ | |||
|
|||
(require 'url-vars) | |||
|
|||
(declare-function markdown-mode "markdown-mode.el") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You also have to declare markdown-toggle-fontify-code-blocks-natively
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more thing - for this work markdown-mode
should actually be present. You can just add markdown-mode
to the dev dependencies in Cask.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
82b85b1
to
26fa6cf
Compare
26fa6cf
to
62eca97
Compare
👍 |
Follow-up on #1959 and the discussion with @bbatsov r.e. fontifying code blocks in the markdown buffer returned by
cider-grimoire
.Thanks to @jrblevin for addressing jrblevin/markdown-mode#185.