From: Ihor Radchenko <yantar92@gmail.com>
To: Perry Smith <pedz@easesoftware.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode "style sheet" for software documentation
Date: Fri, 09 Sep 2022 13:09:53 +0800 [thread overview]
Message-ID: <87bkrpdtge.fsf@localhost> (raw)
In-Reply-To: <F0F15991-CE51-4A63-BD59-B33F41B6CFC1@easesoftware.com>
Perry Smith <pedz@easesoftware.com> writes:
> So… it seems I didn’t the two BORDER characters do not need to match. So I’m off trying to figure out a way to create more emphasis MARKERS. In the old days, we had only about 43 non-alphanumeric characters to play with but now with Emacs being 8 bit clean for countless years we have another 128 characters and with UTF-8 we have bazillians more!
>
> So I’m gently poking around in the code to see how hard it would be to define more.
We currently do not support extensions to emphasis, though we may do it
in future. See https://orgmode.org/list/87letvrege.fsf@localhost
Implementing new emphasis markers will require introducing a new syntax
object into org-element.el. Such object will unlikely be using a
single-char markers - single-char markers are problematic in numerous
edge cases; we should better introduce something closer to inline src
block syntax to allow arbitrary emphasis extensions.
--
Ihor Radchenko,
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
next prev parent reply other threads:[~2022-09-09 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 16:20 Org mode "style sheet" for software documentation Perry Smith
2022-09-08 20:38 ` Perry Smith
2022-09-09 5:09 ` Ihor Radchenko [this message]
2022-09-09 12:42 ` Perry Smith
2022-09-10 4:44 ` Ihor Radchenko
2022-09-09 15:00 ` Max Nikulin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkrpdtge.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=pedz@easesoftware.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.