From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 5235@debbugs.gnu.org
Subject: bug#5235: 23.1; Unibyte keyboard input problem
Date: Tue, 29 Dec 2009 13:48:28 -0200 [thread overview]
Message-ID: <m2hbr9bx95.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <83ws08dvtv.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 27 Dec 2009 22:07:56 +0200")
> This is expected, I think. I could make it honor the `coding' cookie
> even in that case, but I'd like first to know if this kind of solution
> is acceptable (below).
This aproach looks OK, actually, yes. Basially, the user would set
-*- coding: cp1250; select-safe-coding-system-respect-auto-coding: t -*-
tho in such a context a shorter varname would make sense, like
`coding-cookie-force'. And then it'd be OK to obey it no matter what
(i.e. regardless of the default coding system, locale, etc...).
Stefan
next prev parent reply other threads:[~2009-12-29 15:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 13:30 bug#5235: 23.1; Unibyte keyboard input problem Tomasz Zbrożek
2009-12-27 20:07 ` Eli Zaretskii
2009-12-29 15:48 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-26 19:19 Tomasz Zbrożek
2009-12-26 21:24 ` Eli Zaretskii
2009-12-26 17:03 Tomasz Zbrożek
2009-12-26 17:52 ` Eli Zaretskii
2009-12-16 21:17 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
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
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=m2hbr9bx95.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=5235@debbugs.gnu.org \
--cc=eliz@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.