From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: tor.a.s.kringeland@ntnu.no, emacs-devel@gnu.org, juri@linkov.net
Subject: Re: Support for shorthand emoji input
Date: Fri, 03 Dec 2021 09:29:57 +0200 [thread overview]
Message-ID: <83fsra87t6.fsf@gnu.org> (raw)
In-Reply-To: <E1mt0CP-00035F-CJ@fencepost.gnu.org> (message from Richard Stallman on Thu, 02 Dec 2021 23:29:29 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: juri@linkov.net, tor.a.s.kringeland@ntnu.no, emacs-devel@gnu.org
> Date: Thu, 02 Dec 2021 23:29:29 -0500
>
> > A facility to let users specify text replacements to be done
> > on-the-fly as you type. It should be similar to what the abbrevs do,
> > just extended to handle non word-constituent characters, including
> > punctuation and symbols. For example, replacing -- with the em-dash
> > character — or 1/2 with ½ or (C) with © or <== with ←.
>
> It sounds useful, but may be hard to implement efficiently.
> Abbrevs are efficient because it does lookup of a word at the end
> of that word.
I very much doubt that comparing a bunch of characters before point
with a list of strings could be so inefficient as to make this feature
unusable.
But it's all highly academic unless someone produces a working code.
next prev parent reply other threads:[~2021-12-03 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 14:35 Support for shorthand emoji input Tor Kringeland
2021-11-30 17:59 ` Juri Linkov
2021-11-30 18:35 ` Eli Zaretskii
2021-12-02 4:30 ` Richard Stallman
2021-12-02 7:55 ` Eli Zaretskii
2021-12-02 9:18 ` Juri Linkov
2021-12-02 10:11 ` Eli Zaretskii
2021-12-03 4:29 ` Richard Stallman
2021-12-03 7:29 ` Eli Zaretskii [this message]
2021-12-03 13:14 ` Stefan Monnier
2021-12-03 13:34 ` Eli Zaretskii
2021-11-30 18:52 ` Tor Kringeland
2021-12-01 4:29 ` Lars Ingebrigtsen
2021-12-01 4:28 ` Lars Ingebrigtsen
2021-12-01 12:39 ` Tor Kringeland
2021-12-01 14:35 ` Lars Ingebrigtsen
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=83fsra87t6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=rms@gnu.org \
--cc=tor.a.s.kringeland@ntnu.no \
/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).