From: VanL <van@scratch.space>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: suggest using E-M-S 3-line notation from HAL/S for super/subscripting
Date: Tue, 18 Feb 2020 00:43:55 +1100 [thread overview]
Message-ID: <m24kvps50k.fsf@scratch.space> (raw)
In-Reply-To: <871rqtbp4t.fsf@bzg.fr> (Bastien's message of "Mon, 17 Feb 2020 09:21:22 +0100")
Bastien <bzg@gnu.org> writes:
> VanL <van@scratch.space> writes:
>
>> I was picturing a way to edit the
>> super/subscripts in expanded immediate mode using the EMS notation and
>> then collapsing that to single line pretty printing. Hope that makes sense.
>
> well, it kinda makes more sense now that I can better visualize it but
> (1) I'm not sure the editing experience would be so smooth and (2) the
> implementation would be quite complex -- enough, at least, for me to
> not undertake anything about it.
The nearest thing to it I can think of is the way
org-insert-structure-template works or org-insert-link works. That,
would apply to a sequence of prefix_sub^super/symbol/postfix_sub^super,
which, would expand to the three E-M-S notation on editing as in
HAL/S [1], and, pretty print as a single line for reading.
> You might want to share this idea with emacs-orgmode@gnu.org, perhaps
> someone can hack something useful to you and others interested.
I will cc this reply to that list.
Have a look at ^{3}He and ^{21}Ne in the following linked article.
#+name: see-3He-21Ne-as-prefix-superscript [2]
#+begin_example
We determined that at least 12 of the analyzed grains were parts of
aggregates in the interstellar medium: The large difference in nuclear
recoil loss of cosmic ray spallation products 3He and 21Ne enabled us
to estimate that the irradiated objects in the interstellar medium
were up to 30 times larger than the analyzed grains.
#+end_example
Question for the list. Can the HAL/S notation be used for editing a
symbol, in expanded form, with prefix/postfix sub/superscript? The
collapsed form is a single line pretty printing tiny sub/superscript
before and after the symbol.
PS. Please reply to the list if
there is interest as I won't be
able to reply directly.
Footnotes:
[1] https://www.hq.nasa.gov/office/pao/History/computers/contents.html
[2] https://www.pnas.org/content/117/4/1884
-- VL
next parent reply other threads:[~2020-02-17 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2imk85qhb.fsf@scratch.space>
[not found] ` <878sl473s5.fsf@bzg.fr>
[not found] ` <m28sl3uhon.fsf@scratch.space>
[not found] ` <871rqtbp4t.fsf@bzg.fr>
2020-02-17 13:43 ` VanL [this message]
2020-02-17 16:04 ` suggest using E-M-S 3-line notation from HAL/S for super/subscripting Fraga, Eric
2020-02-18 7:07 ` VanL
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=m24kvps50k.fsf@scratch.space \
--to=van@scratch.space \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).