miniblog.

← Back to all posts
Jul 26, 2016 at 21:44
How do you add extension to markdown/commonmark? There's no official extension syntax, but custom URIs is elegant:
Sorely confused about "Extensions"
Sorely confused about "Extensions"
I think the extension point for your bug tracker syntax would be bogus URL schemes, e.g. [App crashes](bug://CM-2345). These could be handled easily by either a pre-processor or a post-processor or by a custom plugin to your CM parser. I’m not quite sure how I would like Discourse to extend the existing quote syntax using the > line prefix, maybe something like this: > Currently the focus is on completing the core spec, > with extensions coming later -- [chrisalley](topic:1872#2) It wouldn’t m...

Related Posts

Aug 29, 2024 at 15:54
One interesting design choice in Emacs that I haven't seen in other editors: reserved shortcuts. An Emacs extension shouldn't use F5 through F12, or Ctrl-c LETTER. This lets users configure their own shortcuts. https://www.gnu.org/software/emacs/manual/html_node/emacs/Key-Bindings.html Does it exist elsewhere? I miss it in VS Code, where e.g. all the Fn keys are already assigned.
Key Bindings (GNU Emacs Manual)
Key Bindings (GNU Emacs Manual)
Aug 29, 2024 at 15:53
One interesting design choice in Emacs that I haven't seen in other editors: reserved shortcuts. An Emacs extension shouldn't use F5 through F12, or Ctrl-c LETTER. This lets users configure their own shortcuts. https://www.gnu.org/software/emacs/manual/html_node/emacs/Key-Bindings.html Does it exist elsewhere?
Key Bindings (GNU Emacs Manual)
Key Bindings (GNU Emacs Manual)
May 31, 2024 at 15:29
It's always seemed odd to me that the Rust stdlib is so lean (no random numbers, regex, HTTP) yet clippy is so big (correctness, performance, style preferences, even 'too many arguments'). Maybe it's because cargo is mature but clippy doesn't have an extension ecosystem?