From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: kbd vs read-key-sequence Date: Sun, 11 Mar 2007 16:01:26 -0400 Message-ID: References: <45E8657D.4080202@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1173643587 9317 80.91.229.12 (11 Mar 2007 20:06:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 11 Mar 2007 20:06:27 +0000 (UTC) Cc: lekktu@gmail.com, jasonr@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 11 21:06:21 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HQUJA-0005Bx-DQ for ged-emacs-devel@m.gmane.org; Sun, 11 Mar 2007 21:06:20 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HQUJj-0007xE-V6 for ged-emacs-devel@m.gmane.org; Sun, 11 Mar 2007 15:06:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HQUGo-0002iL-SY for emacs-devel@gnu.org; Sun, 11 Mar 2007 16:03:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HQUGn-0002fI-O1 for emacs-devel@gnu.org; Sun, 11 Mar 2007 16:03:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HQUGn-0002em-Hm for emacs-devel@gnu.org; Sun, 11 Mar 2007 15:03:53 -0500 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HQUGC-0000Lg-JN for emacs-devel@gnu.org; Sun, 11 Mar 2007 16:03:16 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1HQUEQ-0005iY-U8; Sun, 11 Mar 2007 16:01:26 -0400 In-reply-to: (message from Stefan Monnier on Mon, 05 Mar 2007 12:10:00 -0500) X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:67734 Archived-At: Off the top of my head: - saving may change the char thanks to unify-8859-on-encoding (e.g. you copy a iso-8859-15 char to your .emacs which you then save in iso-8859-1). Is there a procedure we can recommend for the user to avoid this? - the coding-system may not be properly detected, especially if you configure your auto-dtection in your .emacs: the configuration will apply to all files you open but not to the loading of .emacs Can you avoid this by specifying the coding-system explicitly in .emacs? We could recommend that users do so. > Anyway, if you want to bind a character with modifiers, you can just use > a construct in .emacs that applies the modifier to the desired base > character, such as \M- in a string, or (meta CHAR). > Is there a case where that doesn't work? Because the way the event is decoded through read-key-sequence is not necessarily the same. E.g. while ? may get turned into ?é, it may be the case that ?\M- stays unchanged. How does that happen? Maybe that is a bug; if so, we should fix it. We could recommend that people write (meta ?). That would eliminate this particular problem, right? These do not make things perfect, but I think they might be enough to enable users to get reliable results. What do you think?