From: Ihor Radchenko <yantar92@posteo.net>
To: Peyton Okubo <okubo012@umn.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Description list matches in verbatim/code block [9.6.23 ( @ /nix/store/ag7ag7i6zw56ql05bvk1xinz5gp8q5kd-emacs-packages-deps/share/emacs/site-lisp/elpa/org-9.6.23/)]
Date: Wed, 22 May 2024 11:56:19 +0000 [thread overview]
Message-ID: <87fruajc0s.fsf@localhost> (raw)
In-Reply-To: <74012FDD-B67E-46D9-93E1-838588525C60@umn.edu>
Peyton Okubo <okubo012@umn.edu> writes:
> I have the following org markup:
>
> - morphisms: =f :: a -> b maps to F f :: F a -> F b=
>
> "morphisms" is being emphasized the double colons in the verbatim block
> are being matched as description lists. This breaks the verbatim block
> on export. I am able to reproduce this with code blocks as well.
>
> Fairly new to org. But I couldn't find any sources stating that this is
> the intended behavior. I think a user should be able to use a double
> colon in a verbatim block (in a list item).
You are hitting an edge case in Org mode markup.
:: sequence in list items is unconditionally marking description lists.
Normally, we suggest to use zero-width space to resolve such edge
cases. However, you are using =verbatim= markup and zero-width space may
not be suitable.
What you can do instead is move the list item to the next line:
-
morphisms: =f :: a -> maps to F f :: F a -> F b=
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-05-22 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 2:45 [BUG] Description list matches in verbatim/code block [9.6.23 ( @ /nix/store/ag7ag7i6zw56ql05bvk1xinz5gp8q5kd-emacs-packages-deps/share/emacs/site-lisp/elpa/org-9.6.23/)] Peyton Okubo
2024-05-22 11:56 ` Ihor Radchenko [this message]
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=87fruajc0s.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=okubo012@umn.edu \
/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).