From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using backticks for the inline code delimeter?
Date: Mon, 19 Apr 2021 11:27:07 +0200 [thread overview]
Message-ID: <87k0oyd3pw.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <s4ht8r$jdp$1@ciao.gmane.io> (Maxim Nikulin's message of "Tue, 6 Apr 2021 22:03:54 +0700")
Hello,
Maxim Nikulin <manikulin@gmail.com> writes:
> On 05/04/2021 06:06, Nicolas Goaziou wrote:
>> Joost Kremers writes:
>>
>>> I tend to agree that allowing local modifications of Org's syntax is pretty much
>>> pointless, but then why is `org-emphasis-alist` a user option?
>> In practice, the faces, i.e., the values, are meant to be
>> customizable,
>> not the keys.
>
> It would be great to have more clear statement in the doc string. Even
> in the manual it could be stressed stronger.
Patch welcome!
> Unsure if the current phrase really forbids extension, I would rather
> tend to interpret it as invitation to customize the list: "To narrow
> down the list of available markup syntax, you can customize
> ~org-emphasis-alist~."
It depends. IMO, narrowing down the list means removing some markup from
fontification, i.e., setting a nil face. However, it shouldn't prevent
Org from interpreting such syntax. You can use zero-width space for
that.
> Maybe the code interpreting this variable could spit a warning on
> attempt to add new emphasizing characters.
As a first step, the type of the defcustom shouldn't be '(repeat ...),
but a fixed list.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-04-19 9:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 18:48 Using backticks for the inline code delimeter? George Mauer
2021-03-31 19:16 ` autofrettage
2021-03-31 19:19 ` Timothy
2021-04-01 6:03 ` Marcin Borkowski
2021-04-20 13:30 ` Matt Price
2021-04-20 20:24 ` John Kitchin
2021-04-21 22:37 ` Matt Price
2021-04-20 22:30 ` Tim Cross
2021-04-21 19:22 ` John Kitchin
2021-04-21 19:49 ` Tim Cross
2021-03-31 19:24 ` Sébastien Miquel
2021-04-01 16:49 ` Maxim Nikulin
2021-04-01 17:05 ` Timothy
2021-04-01 18:43 ` Samuel Wales
2021-04-01 23:14 ` Tim Cross
2021-04-01 23:30 ` Joost Kremers
2021-04-02 0:28 ` Tim Cross
2021-04-04 1:13 ` Tom Gillespie
2021-04-04 10:03 ` Joost Kremers
2021-04-04 12:19 ` Nicolas Goaziou
2021-04-04 16:46 ` Bill Burdick
2021-04-04 17:24 ` Nicolas Goaziou
2021-04-04 19:33 ` Joost Kremers
2021-04-04 23:06 ` Nicolas Goaziou
2021-04-06 15:03 ` Maxim Nikulin
2021-04-19 9:27 ` Nicolas Goaziou [this message]
2021-03-31 19:28 ` Timothy
2021-03-31 19:55 ` autofrettage
2021-03-31 20:31 ` Diego Zamboni
2021-03-31 21:51 ` George Mauer
2021-03-31 22:27 ` Dr. Arne Babenhauserheide
2021-03-31 22:38 ` Tim Cross
2021-04-01 0:25 ` Samuel Wales
2021-04-01 1:11 ` Bill Burdick
2021-04-01 3:42 ` Greg Minshall
2021-04-01 9:32 ` autofrettage
2021-04-02 11:23 ` Andreas Eder
2021-04-04 17:06 ` Maxim Nikulin
-- strict thread matches above, loose matches on Subject: below --
2022-03-19 3:17 chris
2022-03-19 3:24 ` chris
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=87k0oyd3pw.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.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 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).