all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rustom Mody <rustompmody@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Improving input-methods docs
Date: Fri, 2 Oct 2015 08:23:48 +0530	[thread overview]
Message-ID: <CAJ+TeofGUdE_XdQy+6XKdTMahrb524gxRAu4rjecYd5i_m+9GQ@mail.gmail.com> (raw)

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.

Ok
First a basic question:
When I do describe-input-method
I see a lot of stuff 'described'
However unlike describe-function|variable etc that links to the relevant stuff
here there is no such.

Is there any way to get to the input method (source) from an activated
input-method?

Strangely even describe-key shows (say) self-insert-command for "\" in
tex-input-method
which seems strange if not plain wrong.
[Yeah I ran grep on the elisp sources and found a quail and an international
and ... Just asking if there is easier way to not get lost]



             reply	other threads:[~2015-10-02  2:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  2:53 Rustom Mody [this message]
2015-10-02  5:23 ` Improving input-methods docs Chris Feng
2015-10-02  5:31   ` Rustom Mody
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+TeofGUdE_XdQy+6XKdTMahrb524gxRAu4rjecYd5i_m+9GQ@mail.gmail.com \
    --to=rustompmody@gmail.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 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.