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: Wed, 27 Feb 2008 16:28:02 +0900 [thread overview]
Message-ID: <E1JUGhu-00044X-4c@etlken.m17n.org> (raw)
In-Reply-To: <jwvhcfvdrod.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 26 Feb 2008 22:10:26 -0500)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=ISO-2022-JP-2, Size: 1007 bytes --]
In article <jwvhcfvdrod.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > C-s ^[$(D**^[(B ^[$B"y^[(B ^[$(D**^[(B ^[$B"y^[(B ^[$(D**^[(B ^[$B"y^[(B C-g C-g C-g C-g ESC x r e p o TAB r
> Hmm... "^[$(D**^[(B ^[$B"y^[(B" in latin-1 is "0xC3 0xB6" which is the utf-8 codes for ^[$(D+S^[(B,
> so the C-h l output indicates your terminal sends utf-8 sequences and
> Emacs gets them fine, but if you say that instead of ^[$(D+S^[(B you saw some ^[$B"y^[(B,
> it may indicate that your keyboard-coding-system somehow is set to use
> latin-1 coding system rather than utf-8, or maybe the binary codes get
> treated as latin-1 by the unicode-charset.
It seems that something is broken in isearch-x.el (although
unicode merge didn't change it). I'm now investigating.
But, perhaps, it's time to implement the decoding of
keyboard input by C. After multi-tty merge, we have the
function tty_read_avail_input. I think that is the right
place to do that decoding.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-02-27 7:28 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1JUGhu-00044X-4c@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 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.