From: Thomas Dye <tsd@tsdye.online>
To: William Denton <william@williamdenton.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: [DISCUSSION] What should we do with undocumented x^(superscript inside /round/ braces) syntax? (was: Subscript with parenthesis)
Date: Sat, 17 Feb 2024 10:03:51 -1000 [thread overview]
Message-ID: <CB59932E-0213-4130-85E3-B12BC5CB5C76@tsdye.online> (raw)
In-Reply-To: <VY-wim_hLB5yT3D0OqspVjzsapnwXhVl5K629fSlP4-4A5dnB-tE2OvjhBMWshdR-aLUZxNwOT1n2hMZXMx3wGb5BVw1hIwwrFJ6YdzeFj8=@williamdenton.org>
+1
Tom
> On Feb 17, 2024, at 9:38 AM, William Denton <william@williamdenton.org> wrote:
>
> On Saturday, February 17th, 2024 at 07:07, Ihor Radchenko <yantar92@posteo.net> wrote:
>
>> I tentatively propose to remove the x^(2-i) example from the docstring
>> and mark the ^(...) syntax deprecated.
>>
>> WDYT?
>
> I think it's very sensible. It's surprising ^(...) works like this, and if anyone was using it (perhaps by accident) it will be easy to change when necessary.
>
>
> Bill
>
> --
> William Denton
> https://www.miskatonic.org/
> Librarian, artist and licensed private investigator.
> Toronto, Canada
>
>
next prev parent reply other threads:[~2024-02-17 20:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 22:45 Subscript with parenthesis Tom Alexander
2023-09-21 23:02 ` Tom Alexander
2023-09-22 9:14 ` Ihor Radchenko
2023-09-29 16:12 ` Tom Alexander
2024-02-17 14:06 ` [DISCUSSION] What should we do with undocumented x^(superscript inside /round/ braces) syntax? (was: Subscript with parenthesis) Ihor Radchenko
2024-02-17 19:36 ` William Denton
2024-02-17 20:03 ` Thomas Dye [this message]
2024-02-17 21:22 ` Mark Barton
2024-02-19 18:15 ` [DISCUSSION] What should we do with undocumented x^(superscript inside /round/ braces) syntax? Fraga, Eric
2024-02-19 18:30 ` Ihor Radchenko
2024-03-20 13:57 ` Ihor Radchenko
2024-04-21 9:44 ` Ihor Radchenko
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=CB59932E-0213-4130-85E3-B12BC5CB5C76@tsdye.online \
--to=tsd@tsdye.online \
--cc=emacs-orgmode@gnu.org \
--cc=william@williamdenton.org \
--cc=yantar92@posteo.net \
/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).