From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: lekktu@gmail.com, jasonr@gnu.org, emacs-devel@gnu.org, handa@m17n.org
Subject: Re: kbd vs read-key-sequence
Date: Fri, 30 Mar 2007 20:38:24 -0400 [thread overview]
Message-ID: <jwvodmatfpy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1HXOYv-0000nE-TI@fencepost.gnu.org> (Richard Stallman's message of "Fri\, 30 Mar 2007 17\:23\:09 -0400")
> No, the bug in the use of encoded-kbd-mode.
> Maybe they are both bugs.
I don't think so: encoded-kbd-mode was specifically written to handle
terminal input (i.e. sequences of bytes), so it fulfills this role fine.
It's just that the w32 code abuses it by passing it non-terminal events
(i.e. non-bytes).
> The decoding should be
> done elsewhere, as is done in X11.
> Perhaps it should be, and perhaps after the release we will change
> that. But that has no effect on what to do now. Right now, this
> is done with encoded-kbd-mode, and we are not planning to change that now.
Why should we add hacks to encoded-kbd-mode to work around a bug in the w32
support, rather than fix this w32 code? Especially since encoded-kbd-mode
is used on every platform, so we would risk introducing bugs for users on
favored platforms like GNU/Linux for the sake of users on w32???
Fixing it right shouldn't be hard, really. No harder than changing
encoded-kbd-mode. We just need someone to do it.
If we can't find this someone, then we should probably leave this bug.
After all it's been there in one form or another since Emacs-20.
Stefan
next prev parent reply other threads:[~2007-03-31 0:38 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 22:27 kbd vs read-key-sequence Juanma Barranquero
2007-02-28 22:40 ` Andreas Schwab
2007-02-28 22:50 ` Lennart Borgman (gmail)
2007-02-28 23:32 ` Juanma Barranquero
2007-03-01 1:35 ` Juanma Barranquero
2007-03-01 5:28 ` Stefan Monnier
2007-03-01 12:48 ` Juanma Barranquero
2007-03-01 15:32 ` Stefan Monnier
2007-03-01 17:30 ` Juanma Barranquero
2007-03-01 23:23 ` Stefan Monnier
2007-03-01 23:53 ` Juanma Barranquero
2007-03-02 0:03 ` Juanma Barranquero
2007-03-02 9:09 ` Jason Rumney
2007-03-02 9:48 ` Juanma Barranquero
2007-03-02 16:47 ` Stefan Monnier
2007-03-02 17:29 ` Juanma Barranquero
2007-03-02 17:57 ` Jason Rumney
2007-03-02 18:15 ` Juanma Barranquero
2007-03-02 18:20 ` David Kastrup
2007-03-02 21:03 ` Stefan Monnier
2007-03-03 0:31 ` Juanma Barranquero
2007-03-03 22:13 ` Richard Stallman
2007-03-03 23:01 ` Stefan Monnier
2007-03-05 2:55 ` Richard Stallman
2007-03-05 17:10 ` Stefan Monnier
2007-03-11 20:01 ` Richard Stallman
2007-03-12 15:19 ` Stefan Monnier
2007-03-13 1:17 ` Kenichi Handa
2007-03-13 3:12 ` Stefan Monnier
2007-03-13 4:06 ` Kenichi Handa
2007-03-13 14:47 ` Stefan Monnier
2007-03-19 5:14 ` Richard Stallman
2007-03-19 12:25 ` Kenichi Handa
2007-03-19 14:19 ` Kim F. Storm
2007-03-26 3:52 ` Richard Stallman
2007-03-26 7:22 ` Kenichi Handa
2007-03-26 23:14 ` Richard Stallman
2007-03-27 0:30 ` Kenichi Handa
2007-03-27 16:42 ` Richard Stallman
2007-03-28 0:29 ` Kenichi Handa
2007-03-29 15:32 ` Richard Stallman
2007-03-29 16:11 ` Stefan Monnier
2007-03-30 21:23 ` Richard Stallman
2007-03-31 0:38 ` Stefan Monnier [this message]
2007-03-31 10:07 ` Eli Zaretskii
2007-03-31 23:20 ` Richard Stallman
2007-04-01 3:09 ` Eli Zaretskii
2007-04-01 13:59 ` Richard Stallman
2007-04-01 19:14 ` Stefan Monnier
2007-04-01 20:18 ` Jason Rumney
2007-04-01 20:35 ` Stefan Monnier
2007-04-02 12:00 ` Eli Zaretskii
2007-04-02 2:27 ` Kenichi Handa
2007-04-02 11:58 ` Eli Zaretskii
2007-04-02 12:31 ` Kenichi Handa
2007-04-02 12:46 ` Eli Zaretskii
2007-04-02 14:33 ` Stefan Monnier
2007-04-02 16:14 ` Jason Rumney
2007-04-02 23:24 ` Davis Herring
2007-04-03 6:58 ` Jason Rumney
2007-04-03 7:46 ` Richard Stallman
2007-04-03 8:42 ` Eli Zaretskii
2007-04-03 14:58 ` Stefan Monnier
2007-04-03 15:34 ` Eli Zaretskii
2007-04-03 17:59 ` Stefan Monnier
2007-04-03 18:20 ` Eli Zaretskii
2007-04-03 18:33 ` Stefan Monnier
2007-04-04 14:02 ` Richard Stallman
2007-04-04 14:02 ` Richard Stallman
2007-04-03 9:05 ` Jason Rumney
2007-04-03 9:37 ` Eli Zaretskii
2007-04-03 10:24 ` Jason Rumney
2007-04-04 14:02 ` Richard Stallman
2007-04-03 10:12 ` Eli Zaretskii
2007-04-04 14:02 ` Richard Stallman
2007-04-04 18:03 ` Eli Zaretskii
2007-03-31 20:42 ` Richard Stallman
2007-03-31 21:44 ` Eli Zaretskii
2007-03-31 22:06 ` Juanma Barranquero
2007-03-30 0:47 ` Kenichi Handa
2007-03-30 3:25 ` Stefan Monnier
2007-03-31 10:03 ` Eli Zaretskii
2007-03-31 20:27 ` Stefan Monnier
2007-03-30 21:22 ` Richard Stallman
2007-03-31 10:02 ` Eli Zaretskii
2007-03-19 5:14 ` Richard Stallman
2007-03-26 23:14 ` Richard Stallman
2007-03-28 0:57 ` Stefan Monnier
2007-03-28 16:09 ` Richard Stallman
2007-03-28 19:52 ` Stefan Monnier
2007-03-29 17:59 ` Richard Stallman
2007-03-30 23:47 ` Chong Yidong
2007-03-31 9:08 ` Eli Zaretskii
2007-03-03 22:13 ` Richard Stallman
2007-03-02 18:21 ` Juanma Barranquero
2007-03-02 19:04 ` Jason Rumney
2007-03-03 10:39 ` Eli Zaretskii
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=jwvodmatfpy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=jasonr@gnu.org \
--cc=lekktu@gmail.com \
--cc=rms@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).