From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Peter_Dyballa@Web.DE, emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: Can't isearch 'ö'
Date: Sun, 17 Apr 2005 23:27:38 -0400 [thread overview]
Message-ID: <877jj07owm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200504180252.LAA20878@etlken.m17n.org> (Kenichi Handa's message of "Mon, 18 Apr 2005 11:52:33 +0900 (JST)")
> No, I can't. But shouldn't we avoid such an incompatible
> change at this stage?
Can be. But since it's about a year now since we called a freeze and I see
no sign of getting to the pretest stage, I figure I don't understand enough
what "feature freeze" means: I just propose changes and I'll let someone
else decide whether they should be installed.
I think it's The Right Way to solve the problem, so that's what I use in my
local code, but if someone wants to write a "quick&safe" fix instead and use
that instead I see no problem with it. I'm still interested to know whether
I'm right or not in thinking that my fix is The Right Way.
>> Hypothetical examples aren't too interesting since we can also
>> concoct such examples where the current "translate in
>> self-insert-command" can be made to fail.
> I didn't know that self-insert-command also uses
> translation-table-for-input. I have thought that the
> variable is for an input method as in this docstring:
> Char table for translating self-inserting characters.
> This is applied to the result of input methods, not their input. See also
> `keyboard-translate-table'.
> Anyway, could you show me such an example?
Let's see:
(insert (with-current-buffer foo
(buffer-substring (point)
(progn
(call-interactively 'self-insert-command)
(point)))))
Yes, it's silly,
Stefan
next prev parent reply other threads:[~2005-04-18 3:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ea747b3b2d97aa98d6f831fd50b24adf@Web.DE>
[not found] ` <m18y3qitbv.fsf-monnier+emacs@gnu.org>
[not found] ` <296c27822efac3bf0271bf82f19ca485@Web.DE>
[not found] ` <m1r7hih67o.fsf-monnier+emacs@gnu.org>
[not found] ` <606b3ca39653eb6a62837e841402d5c8@Web.DE>
[not found] ` <87fyxtxwku.fsf-monnier+emacs@gnu.org>
2005-04-14 23:42 ` Can't isearch 'ö' Kenichi Handa
2005-04-15 12:36 ` Stefan Monnier
2005-04-18 2:52 ` Kenichi Handa
2005-04-18 3:27 ` Stefan Monnier [this message]
2005-04-18 5:16 ` Kenichi Handa
2005-04-18 12:59 ` Stefan Monnier
2005-04-25 6:32 ` Kenichi Handa
2005-04-26 10:06 ` Richard Stallman
2005-04-28 11:31 ` Kenichi Handa
2005-04-29 10:15 ` Richard Stallman
2005-04-30 2:25 ` Luc Teirlinck
2005-05-01 20:33 ` Stefan Monnier
2005-05-02 0:29 ` Kenichi Handa
2005-04-18 21:05 ` Richard Stallman
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=877jj07owm.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=Peter_Dyballa@Web.DE \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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).