unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: emacs-devel@gnu.org
Subject: Re: How do you write input methods?
Date: Mon, 30 Aug 2021 12:24:44 -0400	[thread overview]
Message-ID: <b27cbaaf-1ee3-0cdb-781e-f36293d389fc@piermont.com> (raw)
In-Reply-To: <83pmtvj5v9.fsf@gnu.org>

On 8/30/21 11:43, Eli Zaretskii wrote:
>>> Alas, we don't have anyone like that on board.  However, adding simple
>>> input methods, like those where you type a small number of ASCII
>>> characters to produce a non-ASCII character, is easy enough by looking
>>> at existing input methods for various Latin languages.  It's pretty
>>> much boilerplate code.
>> Can you suggest an input method that follows exactly that pattern as a
>> model?
> Any input method defined in latin-post.el or latin-pre.el, for
> example.

Those seem to fit the bill nicely, thank you.


Perry





  reply	other threads:[~2021-08-30 16:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30  1:10 How do you write input methods? Perry E. Metzger
2021-08-30 11:15 ` Stephen Berman
2021-08-30 11:24   ` Joost Kremers
2021-08-30 11:48     ` Stephen Berman
2021-08-30 16:23       ` Perry E. Metzger
2021-08-30 20:26         ` Stephen Berman
2021-08-30 11:46 ` Eli Zaretskii
2021-08-30 13:40   ` Perry E. Metzger
2021-08-30 14:00     ` Eli Zaretskii
2021-08-30 14:22       ` Perry E. Metzger
2021-08-30 15:43         ` Eli Zaretskii
2021-08-30 16:24           ` Perry E. Metzger [this message]
2021-08-30 14:29 ` André A. Gomes
2021-08-30 15:54   ` Eli Zaretskii
2021-08-30 20:12     ` André A. Gomes
2021-08-31 12:02       ` Eli Zaretskii
2021-09-01 17:50       ` Filipp Gunbin
2021-09-01 17:57         ` Eli Zaretskii
2021-09-01 20:33           ` Filipp Gunbin
2021-09-02  6:23             ` Eli Zaretskii
2021-09-02  6:34               ` tomas
2021-09-03  0:59                 ` Michael Welsh Duggan
2021-09-03  6:10                   ` tomas
2021-09-02 10:47               ` Filipp Gunbin

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=b27cbaaf-1ee3-0cdb-781e-f36293d389fc@piermont.com \
    --to=perry@piermont.com \
    --cc=emacs-devel@gnu.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).