unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hans Lonsdale <hanslonsdale@mailfence.com>
To: Jean Louis <bugs@gnu.support>, help-gnu-emacs@gnu.org
Subject: Re: Latex superscripts, subscripts and curly braces
Date: Tue, 3 Jan 2023 15:13:36 +0100 (CET)	[thread overview]
Message-ID: <1154802084.953770.1672755216055@ichabod.co-bxl> (raw)
In-Reply-To: <Y7QrInhVPX35h5EF@protected.localdomain>



> ----------------------------------------
> From: Jean Louis <bugs@gnu.support>
> Sent: Tue Jan 03 14:18:26 CET 2023
> To: <help-gnu-emacs@gnu.org>
> Subject: Re: Latex superscripts, subscripts and curly braces
> 
> 
> * Emanuel Berg <incal@dataswamp.org> [2023-01-03 00:14]:
> > 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?
> 
> There is LyX and TeXmacs, excellent tools.

This is about working with latex-mode in emacs.

> LyX | LyX – The Document Processor:
> https://www.lyx.org/
> 
> Welcome to GNU TeXmacs (FSF GNU project):
> https://www.texmacs.org/tmweb/home/welcome.en.html
> 
> -- 
> Jean
> 
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
> 
> In support of Richard M. Stallman
> https://stallmansupport.org/
> 


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



  reply	other threads:[~2023-01-03 14:13 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 [this message]
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=1154802084.953770.1672755216055@ichabod.co-bxl \
    --to=hanslonsdale@mailfence.com \
    --cc=bugs@gnu.support \
    --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).