From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Latex superscripts, subscripts and curly braces
Date: Sat, 31 Dec 2022 21:54:16 +0100 [thread overview]
Message-ID: <87358vcn0n.fsf@dataswamp.org> (raw)
In-Reply-To: 1340099776.589320.1672406590250@fidget.co-bxl
Hans Lonsdale wrote:
> I am using latex-mode, which is able to shift superscripts
> upwards, and subscripts downwards, using a smaller font.
> For simple cases the shifting works well.
Are we talking when you edit the source?
What do you input then, exactly?
> But for industrial applications ...
... :)
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-12-31 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 13:23 Latex superscripts, subscripts and curly braces Hans Lonsdale
2022-12-31 20:54 ` Emanuel Berg [this message]
2022-12-31 21:57 ` Hans Lonsdale
2023-01-02 19:01 ` Emanuel Berg
2023-01-02 23:02 ` Hans Lonsdale
2023-01-03 0:53 ` Emanuel Berg
2023-01-03 14:12 ` Hans Lonsdale
2023-01-03 13:18 ` Jean Louis
2023-01-03 14:13 ` Hans Lonsdale
2022-12-31 22:41 ` Hans Lonsdale
2023-01-03 14:09 ` Thibaut Verron
2023-01-03 14:17 ` Hans Lonsdale
2023-01-04 11:06 ` Michael Heerdegen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87358vcn0n.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@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.
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).