unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hans Lonsdale <hanslonsdale@mailfence.com>
To: Emanuel Berg <incal@dataswamp.org>, help-gnu-emacs@gnu.org
Subject: Re: Latex superscripts, subscripts and curly braces
Date: Tue, 3 Jan 2023 00:02:19 +0100 (CET)	[thread overview]
Message-ID: <1248695745.893202.1672700539860@ichabod.co-bxl> (raw)
In-Reply-To: <87y1qkahh2.fsf@dataswamp.org>



> ----------------------------------------
> From: Emanuel Berg <incal@dataswamp.org>
> Sent: Mon Jan 02 20:01:29 CET 2023
> To: <help-gnu-emacs@gnu.org>
> Subject: Re: Latex superscripts, subscripts and curly braces
> 
> 
> Hans Lonsdale wrote:
> 
> >> Are we talking when you edit the source?
> >
> > Yes. After editing the source I would like to see a hint of
> > how things would look like, and also to make it easy for me
> > to follow the latex code itself. I also use it in
> > conjunction with prettify-symbols.
> 
> But that's the whole point, you have one language to express
> what should be shown and then a compiler to produce a document
> according to what you express in that language. There is no
> bridging those to in an Emacs buffer to any extent that will
> ever matter, sorry.
> 
> But you can have a layer in between, some WYSIWYG editor that
> can also produce LaTeX which in turn is compiled, but then you
> loose the only edge there really is to LaTeX, namely the
> ability to get it exactly the way you want it down to the
> tiniest detail - so if you let that go, you are better of with
> something else anyway - I don't know - Markdown, Org-mode etc?

The scope is to hove some form of simple structure even on the latex 
source code.  This facility already exists and can improved a little bit more.
 
> >> What do you input then, exactly?
> >
> > For instance, consider
> >
> > {\begin{aligned}
> > \langle \psi _{{jk}},\psi _{{lm}}\rangle 
> > &=  \int _{{-\infty }}^{\infty }\psi _{{jk}}(x)\overline {\psi _{{lm}}(x)}dx\\
> > &= \delta _{{jl}}\delta _{{km}}
> > \end{aligned}}
> >
> > I would not like to have the _ and {} showing in the
> > expression \psi_{jk}
> 
> It's possible but I don't believe it this whole idea or
> attitude, it is such an uphill battle it is insane, you need
> to let that go or approach it in another way.
> 
> > But for industrial applications [...] In industrial
> > applications, equations are customarily very terse with lot
> > of spaces wasted printing _ ^ { }
> 
> I don't think there are industrial applications of LaTeX that
> differ in this sense from any one else's applications, sorry.

Not industrial application of latex.  But industrial applications involve more 
complicated equation frameworks.  The ability to show some identifying  
structure in the source code would be something separate from the final
result.


> underground experts united
> https://dataswamp.org/~incal
> 
> 


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



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