From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Kenichi Handa <handa@m17n.org>
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 11:13:18 -0500 [thread overview]
Message-ID: <jwv8x162xdz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1JUGhu-00044X-4c@etlken.m17n.org> (Kenichi Handa's message of "Wed, 27 Feb 2008 16:28:02 +0900")
>> > C-s à ¶ à ¶ à ¶ C-g C-g C-g C-g ESC x r e p o TAB r
>> Hmm... "Ã ¶" in latin-1 is "0xC3 0xB6" which is the utf-8 codes for ö,
>> 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 ö you saw some ¶,
>> 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.
Thanks.
> 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.
Now that we've moved the keyboard decoding to input-event-map, I'm not
sure what would be the benefit. Of course, if we can just reuse C code
and get rid of the encoded-kbd code, that's good.
Stefan
next prev parent reply other threads:[~2008-02-27 16:13 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 [this message]
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
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=jwv8x162xdz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-pretest-bug@gnu.org \
--cc=handa@m17n.org \
--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).