From: Arash Esbati <arash@gnu.org>
To: Christopher Dimech <dimech@gmx.com>
Cc: Alessandro Bertulli <alessandro.bertulli96@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
wilnerthomas@tutanota.com, help-gnu-emacs@gnu.org
Subject: Re: Rainbow-delimiters highlighting { and } for tex and latex
Date: Fri, 09 Sep 2022 10:41:25 +0200 [thread overview]
Message-ID: <86sfl1vt1m.fsf@gnu.org> (raw)
In-Reply-To: <trinity-13b28c69-f8fd-4abb-b382-d1ca9b4e3f46-1662649351121@3c-app-mailcom-bs16> (Christopher Dimech's message of "Thu, 8 Sep 2022 17:02:31 +0200")
Christopher Dimech <dimech@gmx.com> writes:
> As all these tools are part of Gnu, it would be more suitable to
> integrate all the tex and latex functionality in simple way within
> emacs. [...] There is good functionality in the auctex and cdlatex
> modes for emacs that a least the core should be put in just a single
> mode.
Does it mean you want to create a One-Stop-Shop for (La)TeX writing
within Emacs, i.e., merging AUCTeX, cdlatex etc. into a core library?
Or just put part of AUCTeX/cdlatex in core? If the latter, how do you
pull the rest?
> Other major modes do not work in confusing ways like tex and latex.
Does python also fit the bill above? There is the builtin python.el and
external packages like python-mode.el which have their pros and cons.
Best, Arash
next prev parent reply other threads:[~2022-09-09 8:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 11:07 Rainbow-delimiters highlighting { and } for tex and latex wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 13:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-07 13:10 ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 13:14 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-07 13:23 ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 13:34 ` Stefan Monnier
2022-09-07 19:29 ` Christopher Dimech
2022-09-08 4:13 ` tomas
2022-09-08 10:13 ` Christopher Dimech
2022-09-08 12:08 ` Alessandro Bertulli
2022-09-08 13:25 ` Christopher Dimech
2022-09-08 13:58 ` Alessandro Bertulli
2022-09-08 15:02 ` Christopher Dimech
2022-09-08 15:04 ` Alessandro Bertulli
2022-09-09 8:41 ` Arash Esbati [this message]
2022-09-09 12:33 ` Christopher Dimech
2022-09-09 19:36 ` Arash Esbati
2022-09-09 20:13 ` Christopher Dimech
2022-09-09 20:45 ` Christopher Dimech
[not found] ` <jwvleqvmhqj.fsf-monnier+emacs@gnu.org-NBNA5jg----2>
2022-09-07 15:03 ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 15:16 ` tomas
2022-09-07 15:29 ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 15:59 ` tomas
2022-09-07 16:43 ` Stefan Monnier
[not found] ` <jwvczc7b0jf.fsf-monnier+emacs@gnu.org-NBNqAf0----2>
2022-09-08 10:35 ` wilnerthomas--- via Users list for the GNU Emacs text editor
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=86sfl1vt1m.fsf@gnu.org \
--to=arash@gnu.org \
--cc=alessandro.bertulli96@gmail.com \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=wilnerthomas@tutanota.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).