From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Typing raw bytes
Date: Mon, 21 Jan 2013 10:38:20 -0500 [thread overview]
Message-ID: <jwvpq0y5z2g.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83622rp517.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 21 Jan 2013 05:51:32 +0200")
>> Subsequent messages explain it seems to be due to the C-q NNN char being
>> passed through keyboard-coding-system: that seems to be a bug.
> How is that a bug?
AFAIK C-q NNN should insert the char whose internal character code is
NNN (in Emacs's own encoding, not in the keyboard's), so the
keyboard-coding-system should not have any influence.
> Keyboard input decoding is not the issue here; how
> the result is inserted into a buffer is, IMO.
In a unibyte buffer, a character code NNN (where NNN is less than 256)
should be inserted as that byte without any loss.
Stefan
next prev parent reply other threads:[~2013-01-21 15:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 20:10 Typing raw bytes Eli Zaretskii
2013-01-20 20:50 ` Ivan Andrus
2013-01-20 20:55 ` Michael Welsh Duggan
2013-01-20 21:33 ` Eli Zaretskii
2013-01-20 21:43 ` Michael Welsh Duggan
2013-01-20 20:59 ` Benjamin Riefenstahl
2013-01-20 21:35 ` Eli Zaretskii
2013-01-21 14:47 ` Benjamin Riefenstahl
2013-01-21 17:26 ` Eli Zaretskii
2013-01-21 19:38 ` Benjamin Riefenstahl
2013-01-21 20:02 ` Eli Zaretskii
2013-01-20 20:59 ` Andreas Schwab
2013-01-20 21:31 ` Eli Zaretskii
2013-01-20 23:02 ` Andreas Schwab
2013-01-20 23:22 ` Kenichi Handa
2013-01-21 3:50 ` Eli Zaretskii
2013-01-21 17:39 ` Eli Zaretskii
2013-01-21 1:40 ` Stefan Monnier
2013-01-21 3:51 ` Eli Zaretskii
2013-01-21 15:38 ` Stefan Monnier [this message]
2013-01-21 17:38 ` Eli Zaretskii
2013-01-22 0:59 ` Stefan Monnier
2013-01-21 14:19 ` Richard Stallman
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=jwvpq0y5z2g.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.