From: Augusto Stoffel <arstoffel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Math symbols
Date: Sat, 24 Sep 2022 08:36:30 +0200 [thread overview]
Message-ID: <87edw1nus1.fsf@gmail.com> (raw)
In-Reply-To: <831qs1parl.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Sep 2022 09:05:50 +0300")
On Sat, 24 Sep 2022 at 09:05, Eli Zaretskii wrote:
> Maybe I don't understand in enough detail what you want to propose.
> What other features, except input methods, may need the TeX names of
> these characters and for what purposes?
There can be a variant of `insert-char' that reads the TeX name instead
of the Unicode name. Also a hierarchical menu like `emoji-insert'.
Then tex-mode probably wants to suggest those symbols in its
completion-at-point. And so on.
> We could, I think, add an alternative input method to latin-ltx.el,
> which will be identical to the existing one, except for changes in the
> above-mentioned areas.
This is done: it's the package I linked in my original message.
An alternative is to make the TeX IM customizable. But this, again,
raises the question: should there be an alist of 2500 symbols defined in
latin-ltx.el, or should this info be stored in some shared place so
various features can benefit from it? (I'm not sure, and I'm not
advocating for either.)
next prev parent reply other threads:[~2022-09-24 6:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 19:25 Math symbols Augusto Stoffel
2022-09-23 19:43 ` Andreas Schwab
2022-09-23 19:54 ` Augusto Stoffel
2022-09-23 20:14 ` Eli Zaretskii
2022-09-23 20:54 ` Augusto Stoffel
2022-09-24 6:05 ` Eli Zaretskii
2022-09-24 6:36 ` Augusto Stoffel [this message]
2022-09-24 7:21 ` Eli Zaretskii
2022-09-24 7:41 ` Augusto Stoffel
2022-09-24 7:57 ` Eli Zaretskii
2022-09-24 14:02 ` Augusto Stoffel
2022-09-24 14:17 ` Eli Zaretskii
2022-09-24 17:46 ` Juri Linkov
2022-09-23 20:56 ` Stefan Monnier
2022-09-24 6:06 ` Eli Zaretskii
2022-09-24 6:37 ` Augusto Stoffel
2022-09-24 7:24 ` Eli Zaretskii
2022-09-24 7:45 ` Augusto Stoffel
2022-09-24 7:58 ` Eli Zaretskii
2022-09-24 8:47 ` Visuwesh
2022-09-25 11:14 ` Eric S Fraga
2022-09-25 13:55 ` Eli Zaretskii
2022-09-25 15:55 ` Eric S Fraga
2022-09-24 13:34 ` Stefan Monnier
2022-09-24 13:55 ` Augusto Stoffel
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=87edw1nus1.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.
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).