From: Rustom Mody <rustompmody@gmail.com>
To: Chris Feng <chris.w.feng@gmail.com>
Cc: handa@etl.go.jp, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Improving input-methods docs
Date: Fri, 2 Oct 2015 11:01:09 +0530 [thread overview]
Message-ID: <CAJ+TeoeotfUYqXn_pq+tH0oJgQKo5adgkfgrVSdFa6Lyy1U0gw@mail.gmail.com> (raw)
In-Reply-To: <CAP4=87FNU9_GvaquW+oH-LO-OfWK4pynxd1NVW_2oQZ5Hx98jw@mail.gmail.com>
Thanks Chris
On Fri, Oct 2, 2015 at 10:53 AM, Chris Feng <chris.w.feng@gmail.com> wrote:
>> Stefan Monnier wrote (on gnu.emacs.help list):
>>> Rusi Mody wrote:
>>> > I see (info "(elisp)input methods")
>>> > that in emacs including 25, docs are still at
>>> >
>>> > | How to define input methods is not yet documented in this manual,
>>> > | but here we describe how to use them.
>>> >
>>> > Is there something I can do (within my capacity!) to move this forward?
>>
>>> Start to document what you know? Or try to document what you think
>>> should be there, and if you don't know what to write because you don't
>>> know how it works, then ask on emacs-devel.
>
> AFAIK to define a new input method it only requires one to register it
> to `input-method-alist' and feed `input-method-function' a customized
> function. But it seems most input methods in Emacs are defined as
> Quail packages, so an intro to `quail-define-package' (and perhaps
> other parts of Quail) may also be helpful.
What's quail?
Why is it there? [or] What's its relation to (define)-input-method?
Sorry if I seem obtuse but I gather there is a close relation but I
cant make out what...
next prev parent reply other threads:[~2015-10-02 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 2:53 Improving input-methods docs Rustom Mody
2015-10-02 5:23 ` Chris Feng
2015-10-02 5:31 ` Rustom Mody [this message]
2015-10-02 5:42 ` Chris Feng
2015-10-02 6:50 ` Rustom Mody
2015-10-02 7:41 ` Eli Zaretskii
2015-10-02 7:09 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2015-09-27 3:28 Rusi
2015-10-01 0:05 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ+TeoeotfUYqXn_pq+tH0oJgQKo5adgkfgrVSdFa6Lyy1U0gw@mail.gmail.com \
--to=rustompmody@gmail.com \
--cc=chris.w.feng@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=handa@etl.go.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.