From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: TeX input method
Date: Wed, 04 Oct 2006 11:55:51 +0900 [thread overview]
Message-ID: <E1GUwvH-0003Px-00@etlken> (raw)
In-Reply-To: <jwvmz8dxz0v.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 03 Oct 2006 10:29:23 -0400)
In article <jwvmz8dxz0v.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> So in essence you consider it more important to stick as close as possible
> to TeX for those potential users who may want to abuse the input method as
> a sort of coding-system, even if if means annoying the actual daily users of
> this input method?
> In this case I think we should "fix" the TeX input method to be more like
> TeX? E.g. map `SPC SPC SPC ...' to " "?
> More seriously: the TeX input method is really not like TeX. It's only
> using TeX as a basis so that people who know TeX get the benefit of reusing
> the same names for the same chars.
I tend to agree with that. An input method should be
designed to make inputting the most convenient. It may be
ok to use a data of some input method as a sort of
coding-system, but that priority should be lower than the
original intention of an input method.
So, the only question is whether Stefan's change is worth
breaking backward compatiblity or not.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-10-04 2:55 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 [this message]
2006-10-05 5:30 ` Miles Bader
2006-10-05 7:26 ` David Kastrup
2006-10-05 13:39 ` Stefan Monnier
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
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=E1GUwvH-0003Px-00@etlken \
--to=handa@m17n.org \
--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 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).