> I did a quick test, and it seems > that =prettify-symbols-alist= (which is what this code uses) can only > replace for a single character, so I was not able to make it display > the three backticks, but there might be other techniques that can be > used.
Yes, there is another technique. See part of my config below: (defun yant/str-to-glyph (str) "Transform string into glyph, displayed correctly." (let ((composition nil)) (dolist (char (string-to-list str) (nreverse (cdr composition))) (push char composition) (push '(Br . Bl) composition)))) (append pretty-symbol-patterns `(((yant/str-to-glyph " ") org-specific ,(format "^\\(\\*\\{%d,%d\\}\\)\\*[^*]" (1- org-inlinetask-min-level) (1- org-inlinetask-max-level)) (org-mode) 1) ((yant/str-to-glyph "⇒⇒⇒") org-specific ,(format "^\\(\\*\\{%d,%d\\}\\)\\(\\*\\)[^*]" (1- org-inlinetask-min-level) (1- org-inlinetask-max-level)) (org-mode) 2) (?╭ org-specific "^[ ]*#[+]NAME" (org-mode)) (?╭ org-specific "^[ ]*#[+]name" (org-mode)) (?├ org-specific "[ ]*#[+]begin_src" (org-mode)) (?├ org-specific "[ ]*#[+]BEGIN_SRC" (org-mode)) (?╰ org-specific "[ ]*#[+]end_src" (org-mode)) (?╰ org-specific "[ ]*#[+]END_SRC" (org-mode)) ((yant/str-to-glyph "📁📁📁") org-specific ":\\(ATTACH\\):" (org-mode) 1) ((yant/str-to-glyph "☠D") org-specific "\\<DEADLINE:" (org-mode)) ((yant/str-to-glyph "◴S") org-specific "\\<SCHEDULED:" (org-mode)))) Diego Zamboni <di...@zzamboni.org> writes: > Hi Daryl, > > If it's for display purposes only, you might be able to simply use > display substitutions for things to appear the way you want. For > example, I use the technique described here: > https://pank.eu/blog/pretty-babel-src-blocks.html to replace the > begin/end_src strings with symbols. I did a quick test, and it seems > that =prettify-symbols-alist= (which is what this code uses) can only > replace for a single character, so I was not able to make it display > the three backticks, but there might be other techniques that can be > used. > > --Diego > > On Sun, May 3, 2020 at 6:24 PM Daryl Manning <dwm+orgm...@wakatara.com> wrote: >> >> While using C-c C-, is easy enough for insertion and such, I was wondering >> if there was any way of having org-mode honour markdown conventions for >> things like code fences and quotes. >> >> ``` elisp >> #+begin_src >> #+end_src >> >> #+begin_quote >> #+end_quote >> ``` >> >> being a bit nicer to read with >> >> ``` go >> code block >> ``` >> as well as >> >> > And gentlemen in England now-a-bed. >> > Shall think themselves accurs'd they were not here, >> > And hold their manhoods cheap whiles any speaks. >> > That fought with us upon Saint Crispin's day. >> >> Just curious as to whether that's possible. YMMV before you start debating >> on whether you think this is a good idea or not... =] >> >> Of course, I'd want the code highlighting especially to work that way, >> though... =] Less concerned with whether it works in export modes for the >> moment, more about display atm. >> >> thanks! >> Daryl. >> >> >> >> >> > -- Ihor Radchenko, PhD, Center for Advancing Materials Performance from the Nanoscale (CAMP-nano) State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China Email: yanta...@gmail.com, ihor_radche...@alumni.sutd.edu.sg