From: Samuel Wales <samologist@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using backticks for the inline code delimeter?
Date: Wed, 31 Mar 2021 17:25:30 -0700 [thread overview]
Message-ID: <CAJcAo8sWbCFhjv=RpNhhptC75rUbCUEiXQ6Yc=RovcxaheGw2Q@mail.gmail.com> (raw)
In-Reply-To: <87sg4baqel.fsf@gmail.com>
just personal opinion but i wouldn't want org's syntax to get more
heterogeneous and non-orthogonal/non-factored.
i could see room for an orthogonal/factored flexible syntax, like
"parsing risk" and "extensible syntax" threads on this ml. this would
be the one syntax to rule them all, /vaguely/ similar to how you can
do stuff with cl's parser....
...which here would require user-definability so that the user can
specify that $[emphasis :type 'code :hide t :marker ?`] shows as `.
the general idea would be desirable if new syntax is needed, but if it
is only used for this purpose it would imo be overkill*n.
On 3/31/21, Tim Cross <theophilusx@gmail.com> wrote:
>
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>
>> George Mauer <gmauer@gmail.com> writes:
>>> - lists with dashes, org supports that just fine
>>
>> or stars (not possible with org) or plus (in org).
>>
>>> *bold text* with stars, again org already does this
>>
>> Note that this does not match markdown: Markdown uses *emphasis* and
>> **strong**.
>>
>>> `backtick code`, org doesn't handle this and actually uses the tilde as
>>> a
>>> delimeter which is extra jarring since its a strikethrough in many chat
>>> apps
>>
>> tilde or equals.
>>
>> - list
>> *bold*
>> =code=
>>
>> Adding more syntax is a slippery slope, because then `foo` can never be
>> used for anything else, and there is a limited amount of usable syntax
>> elements.
>>
>
> Yes, I think this is potentially a bad idea. Org parsing is already slow
> enough without adding yet more syntax and font-locking complexity.
>
> I also suspect this is not as simple as just adding this to org parsing
> - all backends and many contributed packages would likely also need to
> be updated to understand the new syntax. So probably not a trivial
> change and a change which is likely to have real impact wrt backwards
> compatibility.
>
> Part of the issue here is that there is no markdown 'standard'. There
> are a number of markdown 'flavors' or dialects. Org is just another one
> (and one of the older ones at that).
>
> --
> Tim Cross
>
>
--
The Kafka Pandemic
Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
next prev parent reply other threads:[~2021-04-01 0:26 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJcAo8sWbCFhjv=RpNhhptC75rUbCUEiXQ6Yc=RovcxaheGw2Q@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@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 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.