> On May 5, 2020, at 1:46 AM, Ihor Radchenko wrote:
>
>> I am assuming though, from the lack of answers back, that there appears to
>> be no way to have org-mode grok markdown code blocks (triple backticks)
>> when it parses as a substitute for `#+BEGIN_SRC` ?
>
> #+BEGIN_SRC is a part of org
> I am assuming though, from the lack of answers back, that there appears to
> be no way to have org-mode grok markdown code blocks (triple backticks)
> when it parses as a substitute for `#+BEGIN_SRC` ?
#+BEGIN_SRC is a part of org syntax, "```" is not.
You will need to modify the org-mode intern
Hi Daryl,
I am assuming though, from the lack of answers back, that there appears to
> be no way to have org-mode grok markdown code blocks (triple backticks)
> when it parses as a substitute for `#+BEGIN_SRC` ?
>
I am no expert in the Org internals, but a quick search shows the strings
BEGIN/END
This looks great (your elisp-fu is impressive) and definitely fulfills
making it look markdown-ish. Thanks! Will plug it in tonight and take it
for a pain.
I am assuming though, from the lack of answers back, that there appears to
be no way to have org-mode grok markdown code blocks (triple backti
Ihor,
Awesome, thanks for the tip. Using your code, the following config (inside
the code from https://pank.eu/blog/pretty-babel-src-blocks.html) produces a
display with the backticks instead of begin/end_src:
(defun yant/str-to-glyph (str)
"Transform string into glyph, displayed co
> 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
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 qu
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
`
