unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: tumashu@163.com, rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: pyim
Date: Tue, 23 Feb 2021 17:18:12 +0200	[thread overview]
Message-ID: <83ft1mvmmj.fsf@gnu.org> (raw)
In-Reply-To: <jwvczwrqsph.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 23 Feb 2021 00:07:34 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: rpluim@gmail.com,  tumashu@163.com,  emacs-devel@gnu.org
> Date: Tue, 23 Feb 2021 00:07:34 -0500
> 
> >> ;;;###autoload
> >> (register-input-method "pyim" "euc-cn" 'pyim-start (nth 0 pyim-titles))
> >> 
> >> is that a problem?
> >
> > I was talking about the installation.  What would that have to do, and
> > how would it do it?
> 
> I don't understand the question: the above line shows that the package
> autoloads this `register-input-method` call.  IOW if the user has that
> package activated (which is the default for all packages that the user
> installed), then the above line will be executed between `early-init.el`
> and `init.el`.

Is that enough to correctly set up the user's language environment?

Also, leim-list.el is not just for register-input-method calls; even
if pyim doesn't need anything else (does it?), input methods in
general will, so if we want to install input methods from elpa's, we
need to support that somehow.

But in general (see my first point) I think input methods should be in
core, available in "emacs -Q" etc.



  parent reply	other threads:[~2021-02-23 15:18 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
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 [this message]
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=83ft1mvmmj.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).