all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Kenichi Handa <handa@m17n.org>,
	emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: TeX input method
Date: Thu, 05 Oct 2006 09:39:26 -0400	[thread overview]
Message-ID: <jwv7ize6g1m.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <85d597ql3a.fsf@lola.goethe.zz> (David Kastrup's message of "Thu\, 05 Oct 2006 09\:26\:49 +0200")

> Well, I have to agree with Stefan that the sequences starting with {
> seem somewhat pointless for an input encoding.

OK, thanks.  I'll install that part.

> But ~ is a different beast.

The main problem for me with this is that it was difficult to figure out why
~ didn't work the way I expected it (it didn't occur to me at first that it
was linked to the input method).  E.g. C-h k ~ told me something like:

      (translated from ~  ) is bound to self-insert-command

    ...

then I looked for some weird key-mapping in key-translation-map and
function-key-map.  I know it wasn't my brightest moment, but still: this is
the only part of the TeX input method which remaps a single key rather than
a key-sequence.


        Stefan

  reply	other threads:[~2006-10-05 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 19:40 TeX input method Stefan Monnier
2006-10-03 13:17 ` David Kastrup
2006-10-03 13:50   ` Stefan Monnier
2006-10-03 13:56     ` David Kastrup
2006-10-03 14:29       ` Stefan Monnier
2006-10-04  2:55         ` Kenichi Handa
2006-10-05  5:30           ` Miles Bader
2006-10-05  7:26             ` David Kastrup
2006-10-05 13:39               ` Stefan Monnier [this message]
2006-10-05 13:59               ` Stefan Monnier
2006-10-05 14:19                 ` David Kastrup
2006-10-05 14:52                   ` Stefan Monnier
2006-10-06  8:16                     ` Kim F. Storm

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=jwv7ize6g1m.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=miles@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.