From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Hans Lonsdale Newsgroups: gmane.emacs.help Subject: Re: Latex superscripts, subscripts and curly braces Date: Tue, 3 Jan 2023 00:02:19 +0100 (CET) Message-ID: <1248695745.893202.1672700539860@ichabod.co-bxl> References: <1340099776.589320.1672406590250@fidget.co-bxl> <87358vcn0n.fsf@dataswamp.org> <1857439239.722101.1672523846071@ichabod.co-bxl> <87y1qkahh2.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36612"; mail-complaints-to="usenet@ciao.gmane.io" To: Emanuel Berg , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 03 00:53:04 2023 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCUc4-0009Lz-Hj for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 03 Jan 2023 00:53:04 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pCUbL-0000VC-QP; Mon, 02 Jan 2023 18:52:19 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pCUbJ-0000Uk-23 for help-gnu-emacs@gnu.org; Mon, 02 Jan 2023 18:52:17 -0500 Original-Received: from mailout-l3b-97.contactoffice.com ([212.3.242.97]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pCUbG-0000NM-Q6 for help-gnu-emacs@gnu.org; Mon, 02 Jan 2023 18:52:16 -0500 Original-Received: from hologram (hologram.co-bxl [10.2.0.17]) by mailout-l3b-97.contactoffice.com (Postfix) with ESMTP id 9C7D1698; Tue, 3 Jan 2023 00:52:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1672703528; s=20210208-e7xh; d=mailfence.com; i=hanslonsdale@mailfence.com; h=Date:From:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=2578; bh=l/qmqi9B05eFauHnNjQZdK5XsotY071piAKi6nfJydo=; b=mccBeezpp4YZpOg7e78AvJKZwMYAOQXhruTbYsj1N7zMmdO8BkCs4nvfItV8ylWj 2NApbqfF2mgc2eXC8gmjx8kSxivfvt9A1LiWiEKnmxkvZqH5LFbB7quoJesyjHUJX8y CPma0m6WUlUn9FRWUiyzD3I5KICCHrxvZ2m561UKUXZJpQZJGsfVuoKgaasl05Dqlh8 OdseActX8ECZcPLxreLCOT3Yr/eWTfhyfDfTBZRzZmCBznbmoXevJ4qT6fBERH7LtWf YVEIKDcwqmXT2rlCVrKVaMFkuVoLvS6oXWf7c+SEYv5IAM333d+ketcn+Ip0ZHtAp/n brKwvMttZw== In-Reply-To: <87y1qkahh2.fsf@dataswamp.org> X-Mailer: ContactOffice Mail X-ContactOffice-Account: com:377787701 Received-SPF: pass client-ip=212.3.242.97; envelope-from=hanslonsdale@mailfence.com; helo=mailout-l3b-97.contactoffice.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:142100 Archived-At: > ---------------------------------------- > From: Emanuel Berg > Sent: Mon Jan 02 20:01:29 CET 2023 > To: > 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