From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org, thorn+news@fastmail.fm
Subject: Re: 23.0.60; Cannot isearch for non-ascii chars with emacs -nw -Q
Date: Thu, 28 Feb 2008 14:03:35 +0900 [thread overview]
Message-ID: <E1JUavf-0002Ln-SR@etlken.m17n.org> (raw)
In-Reply-To: <jwvy79593wl.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 27 Feb 2008 23:05:54 -0500)
In article <jwvy79593wl.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> > It seems that something is broken in isearch-x.el (although
>>> > unicode merge didn't change it). I'm now investigating.
> > I found that when isearch-printing-char is called,
> > last-command-char is already what decoded by
> > encoded-kbd-mode.
> That's good, right?
I hope so.
> > But, when I wrote isearch-x.el, last-command-char was the first byte
> > of utf-8 sequence. So, isearch-x.el pushed back that byte in
> > unread-command-events and re-read the whole utf-8 sequence.
> I see your patch doesn't remove this use of unread-command-events.
> Is it still needed?
This part in isearch-process-search-multibyte-characters
(isearch-x.el) is still necessary because it seems that the
user key is not yet handled by an input method.
(if isearch-input-method-function
...)
but the following part is not necessary any more (but not
harmful even if it is there).
(if (and (not str) (keyboard-coding-system))
(setq unread-command-events
(cons 'with-keyboard-coding
(cons last-char unread-command-events))
str (read-string prompt nil 'junk-hist)))
I'll delete that part after confirming it is ok.
>>> Now that we've moved the keyboard decoding to input-event-map,
> > Ah! Is that the change I wrote above?
> I don't see why that change would have such an effect.
> Actually, it seems that this "new" behavior is already present in the 22
> branch, maybe even in Emacs-22.1.
But, it was before the release of 21 when I modified
isearch-x last time.
> > Yes. I think it can be done by adding less than 100 lines
> > of C code (mostly for handling meta-key) in
> > tty_read_avail_input and removing most of encoded-kb.el (we
> > still need the code of calling set-input-mode property).
> Might worth trying,
I'll work on it after the current problems of font selection
are all solved.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-02-28 5:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 22:19 23.0.60; Cannot isearch for non-ascii chars with emacs -nw -Q Tassilo Horn
2008-02-27 3:10 ` Stefan Monnier
2008-02-27 7:28 ` Kenichi Handa
2008-02-27 16:13 ` Stefan Monnier
2008-02-28 2:02 ` Kenichi Handa
2008-02-28 4:05 ` Stefan Monnier
2008-02-28 5:03 ` Kenichi Handa [this message]
2008-02-28 8:12 ` Tassilo Horn
2008-02-27 8:13 ` Tassilo Horn
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=E1JUavf-0002Ln-SR@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=thorn+news@fastmail.fm \
/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).