From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Add support for $…$ latex fragments followed by a dash
Date: Thu, 27 Jan 2022 19:11:08 +0000 [thread overview]
Message-ID: <b40815fa-6c92-f3ff-6a99-3420216b6bb8@posteo.eu> (raw)
In-Reply-To: <CA+G3_PO8dwjeqF7XshP0QNrECGMPCzei9aZi7Q8_juFSHfq3Sw@mail.gmail.com>
Hi,
Tom Gillespie writes:
>> The change is local and minor.
> We can't know that.
I meant that the change to the syntax would be minor and local, with
respect to the linked syntax document.
> #+begin_src org
> I spent $20 on food and was paid$-10 dollars by friends so
> I am down $10.
> #+end_src
> [...]
> #+begin_src org
> Text a $A_BASH_VAR
> Text b some-$-lisp-var
> #+end_src
>
> The proposed change would break any file with a pattern like
> this.
As you say, your first example is a typo. As for the second example,
it's a very uncommon pattern, and if such variable names occur in a
document, they should either be inside src blocks, or inside verbatim
or code markers. In both case, there's no breakage with respect to
parsing, export and tangling. The fontification may fail though. It
wont fail if your src blocks are fontified natively, and the
fontification of $…$ can be globally disabled.
> We have no way of seeing every org file that users have
> written so we don't know the extent of the impact, and thus
> have to assume that there would be some impact. Making
> such a change with an unknown blast radius in the midst of
> considering removing support for that syntax altogether is
> inviting disaster.
We can make an educated guess. It is quite likely that this change
will fix more documents than it breaks. Hardly a disaster.
Regards,
--
Sébastien Miquel
next prev parent reply other threads:[~2022-01-27 19:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 16:42 [PATCH] Add support for $…$ latex fragments followed by a dash Sébastien Miquel
2022-01-25 7:56 ` Eric S Fraga
2022-01-25 10:32 ` Sébastien Miquel
2022-01-26 17:15 ` Rudolf Adamkovič
2022-01-27 8:28 ` Ihor Radchenko
2022-01-27 19:15 ` Tim Cross
2022-01-28 14:37 ` Max Nikulin
2022-01-28 16:37 ` Timothy
2022-01-30 15:28 ` Max Nikulin
2022-02-01 14:26 ` Max Nikulin
2022-01-27 19:34 ` Sébastien Miquel
2022-02-01 21:00 ` Rudolf Adamkovič
2022-02-02 2:48 ` João Pedro de Amorim Paula
2022-02-06 19:45 ` Rudolf Adamkovič
2022-02-07 0:00 ` Tim Cross
2022-01-26 6:33 ` Tom Gillespie
2022-01-26 17:49 ` Sébastien Miquel
2022-01-26 21:49 ` Tom Gillespie
2022-01-27 19:11 ` Sébastien Miquel [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-25 18:09 Goran Zuzic
2022-01-27 18:54 autofrettage
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=b40815fa-6c92-f3ff-6a99-3420216b6bb8@posteo.eu \
--to=sebastien.miquel@posteo.eu \
--cc=emacs-orgmode@gnu.org \
--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).