From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier" Newsgroups: gmane.emacs.help Subject: Re: global-set-key [? =?utf-8?b?XCBNLcO2?=] Date: 28 May 2003 16:29:28 -0400 Organization: Yale University Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <5l1xyirf13.fsf@rum.cs.yale.edu> References: <3EC936AD.41BBBEC8@gmx.net> <87of1ybr5p.fsf@bach.composers> <3ECB2DA2.107EDA4@gmx.net> <5lr86o8jox.fsf@rum.cs.yale.edu> <5l4r3frv9z.fsf@rum.cs.yale.edu> <5ln0h7q7p3.fsf@rum.cs.yale.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1054155889 11551 80.91.224.249 (28 May 2003 21:04:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 28 May 2003 21:04:49 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Wed May 28 23:04:48 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19L86J-00030B-00 for ; Wed, 28 May 2003 23:04:48 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19L87i-000169-Ny for gnu-help-gnu-emacs@m.gmane.org; Wed, 28 May 2003 17:06:14 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!canoe.uoregon.edu!news.wss.yale.edu!rum.cs.yale.edu!rum.cs.yale.edu Original-Newsgroups: gnu.emacs.help Original-Lines: 30 Original-NNTP-Posting-Host: rum.cs.yale.edu Original-X-Trace: news.wss.yale.edu 1054153772 30313 128.36.229.169 (28 May 2003 20:29:32 GMT) Original-X-Complaints-To: news@news.wss.yale.edu Original-NNTP-Posting-Date: Wed, 28 May 2003 20:29:32 +0000 (UTC) User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Original-NNTP-Posting-Host: rum.cs.yale.edu X-Original-Trace: 28 May 2003 16:29:28 -0400, rum.cs.yale.edu Original-Xref: shelby.stanford.edu gnu.emacs.help:113811 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:10304 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:10304 > My failing memory keeps telling me that a coding cookie was not always > enough, e.g. if the various language-environment specific aspects are > set up _after_ the non-ASCII keybinding is read. Again, I might be > out of touch with the current codebase. But assuming the coding-system of the file is the same as the one of the keyboard, the only possible problem is if reading the .emacs (and other things) end up changing the behavior of that coding-system. Most coding-systems have an immutable behavior. The only exception I know of is coding-systems that do some form of unification upon decoding and might unify into different charsets at different times. I guess I could build a setup where the problem manifests itself, but I don't know how common it is and I suspect that any such setup would require significant changes to make it work with a unibyte .emacs. ... Hmmm.... it seems that there's one case where a unibyte answer might make sense: the user wants to use latin-9 but also has some latin-1 files and doesn't want to suffer from the corner cases of encode-only unification, so he turns on decode-unification in his .emacs. His keyboard coding system is set to latin-9, but unification translates most of those to latin-1 chars, so his .emacs should be read as latin-1 for most non-ASCII keybindings. A unibyte cookie in the .emacs won't directly help, but if you additionally set the keyboard-coding-system to nil, it might end up working. Stefan