From: Jason Rumney <jasonr@gnu.org>
To: "Tomasz Zbrożek" <scianagoryczy@wp.pl>
Cc: 5235@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org
Subject: bug#5235: 23.1; Unibyte keyboard input problem
Date: Fri, 25 Dec 2009 19:23:42 +0800 [thread overview]
Message-ID: <4B34A0BE.5060406@gnu.org> (raw)
In-Reply-To: <200912251203.29628.scianagoryczy@wp.pl>
Tomasz Zbrożek wrote:
> I started this bug-case to get the answer to the question: why in unibyte mode
> when I try to write in cp1250 I get codes like ^E instead of proper chars in
> buffer ?
Keyboard input on Windows is Unicode in 23.1. In previous versions it
was in the system default codepage.
> This behaviour is not correct even when comparing to previous Emacs
> version (22.3). So, my question is how to fix this strange keyboard input
> behaviour in unibyte mode ?
>
What is "correct" is undefined in unibyte mode, since unibyte deals with
bytes, not characters.
next prev parent reply other threads:[~2009-12-25 11:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 21:17 bug#5235: 23.1; Unibyte keyboard input problem Tomasz Zbrożek
2009-12-17 16:47 ` Jason Rumney
2009-12-17 19:25 ` Tomasz Zbrożek
2009-12-24 3:40 ` Stefan Monnier
2009-12-24 15:21 ` Jason Rumney
2009-12-24 19:27 ` Eli Zaretskii
2009-12-25 11:03 ` Tomasz Zbrożek
2009-12-25 11:23 ` Jason Rumney [this message]
2009-12-25 11:43 ` Tomasz Zbrożek
2009-12-26 12:45 ` Tomasz Zbrożek
2009-12-26 14:30 ` Eli Zaretskii
2009-12-25 20:42 ` Eli Zaretskii
2009-12-29 15:43 ` Stefan Monnier
2010-02-26 20:42 ` Tomasz Zbrożek
2010-02-26 23:42 ` Eli Zaretskii
2020-09-14 13:59 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2009-12-26 17:03 Tomasz Zbrożek
2009-12-26 17:52 ` Eli Zaretskii
2009-12-26 19:19 Tomasz Zbrożek
2009-12-26 21:24 ` Eli Zaretskii
2009-12-27 13:30 Tomasz Zbrożek
2009-12-27 20:07 ` Eli Zaretskii
2009-12-29 15:48 ` Stefan Monnier
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=4B34A0BE.5060406@gnu.org \
--to=jasonr@gnu.org \
--cc=5235@debbugs.gnu.org \
--cc=5235@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=scianagoryczy@wp.pl \
/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).