From: Christopher Dimech <dimech@gmx.com>
To: Arash Esbati <arash@gnu.org>
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, 9 Sep 2022 22:45:01 +0200 [thread overview]
Message-ID: <trinity-83741925-198f-4712-881c-178237e6810c-1662756301601@3c-app-mailcom-bs02> (raw)
In-Reply-To: <86y1us5oij.fsf@gnu.org>
> Sent: Saturday, September 10, 2022 at 7:36 AM
> 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
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > Auctex and Cdlatex could continue seperately, for more exotic features
> > like as today.
>
> I can't tell for cdlatex since I've never used it, but I don't consider
> many features provided by AUCTeX as exotic.
Perhaps not. The argument is that it would be difficult for all auctex functionality
to be incorporated and maintained as part of emacs. Consequently, I see the value
of continuing with auctex as separate package. But we have to fix the problematic
parts of auctex so that users can comfortably use auctex tools whilst being able
to easily switch to the tex and latex built-in modes in emacs when they want to.
next prev parent reply other threads:[~2022-09-09 20:45 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
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 [this message]
[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=trinity-83741925-198f-4712-881c-178237e6810c-1662756301601@3c-app-mailcom-bs02 \
--to=dimech@gmx.com \
--cc=alessandro.bertulli96@gmail.com \
--cc=arash@gnu.org \
--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).