From: Christopher Dimech <dimech@gmx.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: prettify-symbols-mode to handle "\alpha-\beta" ...
Date: Thu, 4 Feb 2021 19:15:01 +0100 [thread overview]
Message-ID: <trinity-de09e43b-2981-42ab-848d-2e74d2338fe4-1612462501456@3c-app-mailcom-bs01> (raw)
In-Reply-To: <jwvh7mrddac.fsf-monnier+emacs@gnu.org>
> Sent: Friday, February 05, 2021 at 4:12 AM
> From: "Stefan Monnier" <monnier@iro.umontreal.ca>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
> Subject: Re: prettify-symbols-mode to handle "\alpha-\beta" ...
>
> > We should find the best way to do this rather than a hack
> > that is likely to be rejected by emacs-devel.
>
> I don't know what hack you're referring to.
The way I see it, is that the improvement should be put in
prog-mode.el, and then the other major modes can rely on
prog-mode.el fon a minor mode that implements the prettify
functionality.
We need to get to some degree of agreement, as I
do not wish that people end up doing work of no
value to emacs.
> > Whilst texinfo.el takes care of texinfo commands, it completely
> > disregards the use of tex constructs and the focus on displaying
> > mathematical expressions within texinfo.
>
> `texinfo.el` deserves some extra love, yes.
> I don't think anyone has contributed to it in the last several years :-(
>
>
> Stefan
>
>
next prev parent reply other threads:[~2021-02-04 18:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 1:24 prettify-symbols-mode to handle "\alpha-\beta" pietru
2021-02-04 2:08 ` Óscar Fuentes
2021-02-04 3:03 ` pietru
2021-02-04 3:39 ` Óscar Fuentes
2021-02-04 3:46 ` Christopher Dimech
2021-02-04 3:51 ` pietru
2021-02-04 4:04 ` Stefan Monnier
2021-02-04 4:21 ` Christopher Dimech
2021-02-04 16:12 ` Stefan Monnier
2021-02-04 18:09 ` Christopher Dimech
2021-02-04 18:21 ` Stefan Monnier
2021-02-04 20:14 ` Christopher Dimech
2021-02-04 18:15 ` Christopher Dimech [this message]
2021-02-04 18:23 ` Stefan Monnier
2021-02-04 20:22 ` Christopher Dimech
2021-02-04 20:38 ` Stefan Monnier
2021-02-04 20:54 ` Christopher Dimech
2021-02-05 20:32 ` pietru
2021-02-05 21:01 ` Stefan Monnier
2021-02-05 21:05 ` Christopher Dimech
2021-02-05 21:54 ` Christopher Dimech
2021-02-05 21:57 ` Stefan Monnier
2021-02-05 22:09 ` Gregory Heytings
2021-02-05 22:22 ` pietru
2021-02-05 22:45 ` Gregory Heytings
2021-02-05 22:56 ` pietru
2021-02-05 23:04 ` Gregory Heytings
2021-02-05 23:15 ` pietru
2021-02-05 23:22 ` Gregory Heytings
2021-02-05 23:43 ` Christopher Dimech
2021-02-05 23:44 ` pietru
2021-02-06 0:05 ` pietru
2021-02-04 20:34 ` Christopher Dimech
2021-02-04 3:46 ` Ihor Radchenko
2021-02-04 3:59 ` Christopher Dimech
2021-02-04 8:44 ` tomas
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-de09e43b-2981-42ab-848d-2e74d2338fe4-1612462501456@3c-app-mailcom-bs01 \
--to=dimech@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ofv@wanadoo.es \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).