From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: tumashu@163.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: pyim
Date: Mon, 22 Feb 2021 20:51:32 +0200 [thread overview]
Message-ID: <83r1l8uea3.fsf@gnu.org> (raw)
In-Reply-To: <878s7gc5eb.fsf@gmail.com> (message from Robert Pluim on Mon, 22 Feb 2021 19:40:44 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: monnier@iro.umontreal.ca, tumashu@163.com, emacs-devel@gnu.org
> Date: Mon, 22 Feb 2021 19:40:44 +0100
>
> >>>>> On Mon, 22 Feb 2021 20:28:02 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> >> 'quail-define-package' and 'quail-define-rules' work perfectly well to
> >> define private input methods, so Iʼm missing something here.
>
> Eli> So you want to do this every session?
>
> Do what every session? They go in .emacs
Who or what would put them there? We are talking about a package
installation, yes?
And what about register-input-method?
next prev parent reply other threads:[~2021-02-22 18:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 2:42 [ELPA] New package: pyim tumashu
2021-02-22 2:55 ` tumashu
2021-02-22 3:01 ` [ELPA] " Stefan Monnier
2021-02-22 3:20 ` tumashu
2021-02-22 4:42 ` Stefan Monnier
2021-02-22 4:56 ` tumashu
2021-02-22 6:31 ` Eric Abrahamsen
2021-02-22 6:49 ` tumashu
2021-02-22 8:19 ` Clément Pit-Claudel
2021-02-22 8:47 ` tumashu
2021-02-22 16:29 ` Zhu Zihao
2021-02-22 16:36 ` Zhu Zihao
2021-02-22 17:02 ` Clément Pit-Claudel
2021-02-23 6:11 ` tumashu
2021-02-22 15:09 ` Eli Zaretskii
2021-02-22 17:41 ` Robert Pluim
2021-02-22 18:28 ` Eli Zaretskii
2021-02-22 18:40 ` Robert Pluim
2021-02-22 18:51 ` Eli Zaretskii [this message]
2021-02-22 22:27 ` Stefan Monnier
2021-02-23 3:30 ` Eli Zaretskii
2021-02-23 5:07 ` Stefan Monnier
2021-02-23 9:08 ` tumashu
2021-02-23 15:18 ` Eli Zaretskii
2021-02-23 16:17 ` Stefan Monnier
2021-02-23 16:37 ` Eli Zaretskii
2021-03-07 8:44 ` William Xu
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=83r1l8uea3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
--cc=tumashu@163.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 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).