unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hans Lonsdale <hanslonsdale@mailfence.com>
To: Thibaut Verron <thibaut.verron@gmail.com>,
	Emanuel Berg <incal@dataswamp.org>,
	help-gnu-emacs@gnu.org
Subject: Re: Latex superscripts, subscripts and curly braces
Date: Tue, 3 Jan 2023 15:17:43 +0100 (CET)	[thread overview]
Message-ID: <541670412.954007.1672755463023@ichabod.co-bxl> (raw)
In-Reply-To: <97a562b5-6b9e-934f-36e4-5ce3773b4a1a@gmail.com>



> ----------------------------------------
> From: Thibaut Verron <thibaut.verron@gmail.com>
> Sent: Tue Jan 03 15:09:24 CET 2023
> To: Hans Lonsdale <hanslonsdale@mailfence.com>, Emanuel Berg <incal@dataswamp.org>, <help-gnu-emacs@gnu.org>
> Subject: Re: Latex superscripts, subscripts and curly braces
> 
> 
> From: Emanuel Berg <incal@dataswamp.org>
> >> Sent: Sat Dec 31 21:54:16 CET 2022
> >> To: <help-gnu-emacs@gnu.org>
> >> Subject: Re: Latex superscripts, subscripts and curly braces
> >>
> >>
> >> 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?
> > Perhaps there can be two levels, one showing _^ {} and a setting to show things without them.
> 
> Hi,
> 
> org-mode can do it with (setq org-pretty-entities t) and (setq 
> org-pretty-entities-include-sub-superscripts).
> 
> I cannot find any setting to do the same thing with latex buffers, but 
> it should certainly be possible to at least reproduce org's implementation.

My intention is to also have that in tex-mode and latex-mode as well.
 
> For that it's worth, I usually *disable* such things, because they make 
> it very awkward to edit subscripts and superscripts. The effect is that 
> the ^ _ and the braces are hidden, but they can still be input and 
> deleted, and in my experience it's very easy to end up in broken 
> configurations with that.

My intention is to have a key binding to change the visualisation.  I usually 
make changes to the code rather  than to the prettified version.
 
> Instead, I use a proportional font, which makes the braces thin enough 
> to not be annoying. And the scripts are only shifted up or down without 
> changing their size -- that may come from my theme, I can't find 
> anything in my config for that. All together, even long scripts are very 
> easy to visualize and edit.
> 
> Best wishes,
> 
> Thibaut
> 


-- 
Sent with https://mailfence.com  
Secure and private email



  reply	other threads:[~2023-01-03 14:17 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
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 [this message]
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=541670412.954007.1672755463023@ichabod.co-bxl \
    --to=hanslonsdale@mailfence.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.org \
    --cc=thibaut.verron@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.
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).