all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 14:33:52 +0200	[thread overview]
Message-ID: <trinity-de323ed4-497d-4389-874b-9b6f873e310f-1662726832227@3c-app-mailcom-bs02> (raw)
In-Reply-To: <86sfl1vt1m.fsf@gnu.org>

> Sent: Friday, September 09, 2022 at 8:41 PM
> 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:
>
> > 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?

A One-Stop-Shop.  Not at all.  Just to have some of the essential functionality
as a built-in core at emacs release.  Currently, tex-mode and latex-mode already
includes some functionality that has been considered valuable for some time by
users.

For instance, tex-mode and latex-mode do provide a preview tool that uses
"prettify-symbols".  Being able to introduce keywords rapidly (more efficiently
than can be achieved with text completion) is also valuable for users, currently
provided by cdlatex.  The problem with cdlatex is that it also depends upon
texmathp which currently forces users to either pick the file and add it to their
emacs configuration or install auctex.  Which immediately makes the various CamelCase
version of modes and hooks come up.

cdlatex functionality is great but the design has been found to be fragile.
For instance, even though the following commands share the same structure,
hitting "fr<TAB>", the fr does not expand to \frac{}{}, even though `a expands
to \alpha and equ<TAB> expands to an equation environment as expected.

The cdlatex functionality can be introduced into tex-mode and latex-mode.
Getting the community to improve it would be highly beneficial if the possibilities
are included as emacs built-in.

Auctex and Cdlatex could continue seperately, for more exotic features like as today.

For auctex, the recommendation is to reject TeX-mode and LaTeX-mode (and related hooks),
using instead auctex-tex-mode and auctex-latex-mode (and corresponding hooks).

In summary, the focus is on these things

1. Improve design of tex-mode and latex-mode such that common structures
   are separated into a "core-file" applicable to both, with some minor
   tweaks in tex-mode and latex-mode if requires.
2. Reevaluate the preview tool that uses prettify-symbols, to see whether
   there exists possibility of improvement by looking how auctex does things.
3. Introduce rapid insertion of tex and latex keywords and environments by
   studying the cdlatex functionality.


> > 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.

Am not the best person to decide on python, but if users face the same
nomenclature problem, it would be valuable to rethink the design.  But,
one needs the people using the many aspects of python to tell us what is not
working for them.  I can scrutinise only things within my experience,
and have others lead on the implementation details of things like python.



  reply	other threads:[~2022-09-09 12:33 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-de323ed4-497d-4389-874b-9b6f873e310f-1662726832227@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.