From: chris <inkbottle007@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using backticks for the inline code delimiter? (now with `org-publish-all`)
Date: Thu, 07 Dec 2023 02:02:25 +0000 [thread overview]
Message-ID: <4548214.LvFx2qVVIh@nixos> (raw)
In-Reply-To: <87leaam80y.fsf@localhost>
On Monday, December 4, 2023 1:06:37 PM UTC you wrote:
> chris <inkbottle007@gmail.com> writes:
> > The code below is working fine as long as I stay in `org-mode`. But it
> > shows its limitations when I do `M-x org-publish-all`, at which time,
> > instead of having the text with style verbatim, I get the text within
> > backticks.
> >
> > Is there any improvement you could think of that would fix that?
>
> You will need to patch the parser in org-element.el.
Yes, that seems a very good idea.
I've never "patched" emacs before: in the hack I've been using so far I was
doing some `(advice-add 'org-do-emphasis-faces :override #'org-do-emphasis-
faces-fixed)` thing.
In any case the problem (or part of it) lies in `org-element.el` because I've
observed the backticks constructions were not recognised as an "element".
But okay, patch emacs, no worries. Since I'm using NixOS, it will take a bit
of time for me to figure out how to do it the NixOS way.
>
> We do not officially support extending markup syntax. So, even changing
> org-element may still leave other bugs. Caveat emptor.
The backticks for inline code or verbatim are very pleasing to the eye, and
are used literally universally.
next prev parent reply other threads:[~2023-12-07 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 3:17 Using backticks for the inline code delimeter? chris
2022-03-19 3:24 ` chris
2023-11-27 7:54 ` Using backticks for the inline code delimiter? (now with `org-publish-all`) chris
2023-12-04 13:06 ` Ihor Radchenko
2023-12-07 2:02 ` chris [this message]
2023-12-07 15:13 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4548214.LvFx2qVVIh@nixos \
--to=inkbottle007@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).