From: Timothy <tecosaur@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Tom Gillespie <tgbugs@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Bug: inconsistent escaping of coderef regexp
Date: Fri, 02 Apr 2021 00:09:06 +0800 [thread overview]
Message-ID: <87sg4adm1p.fsf@gmail.com> (raw)
In-Reply-To: <877dlmhuu9.fsf@nicolasgoaziou.fr>
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Switches predate Babel and its header arguments. Also, they are
> orthogonal to Babel. I don't know what a sound design would be here,
> tho.
Breaking backwards comparability is a tough call, but somehow I feel
that it would be appropriate here. A number of reasons why they should
go come to mind:
- Rarely used. Searching github I found 146k results for "#+begin_src"
but as soon as I added a switch (I tried -n and +n) that dropped to 0
results
- Easily replaced by a more consistent syntax, which has multiple benefits IMO
+ Simplify parsing a bit
+ Less forms for a new user to learn
+ Better consistency
Perhaps a less sudden approach would to be mark them as depreciated,
implement equivalents with the standard syntax, update manual to use the
new/standard syntax, then remove at some point in the future? In that
case I think it would also be acceptable for new things built for Org
(e.g. a grammar) to ignore them.
Thoughts?
--
Timothy
next prev parent reply other threads:[~2021-04-01 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 20:33 Bug: inconsistent escaping of coderef regexp Tom Gillespie
2021-04-01 15:45 ` Nicolas Goaziou
2021-04-01 16:09 ` Timothy [this message]
2021-04-04 22:01 ` Tom Gillespie
2021-04-04 23:12 ` Nicolas Goaziou
2021-04-05 5:22 ` Tom Gillespie
2021-04-05 7:42 ` Tom Gillespie
2021-04-07 17:58 ` Nicolas Goaziou
2021-04-07 19:44 ` Tom Gillespie
2021-04-09 22:19 ` Nicolas Goaziou
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=87sg4adm1p.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=tgbugs@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).