From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Improving input-methods docs
Date: Wed, 30 Sep 2015 20:05:44 -0400 [thread overview]
Message-ID: <jwvio6rh2t4.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: e04a7a35-3602-413c-aacc-b090912f2f09@googlegroups.com
> 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.
Stefan
prev parent reply other threads:[~2015-10-01 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 3:28 Improving input-methods docs Rusi
2015-10-01 0:05 ` Stefan Monnier [this message]
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=jwvio6rh2t4.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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.
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).