From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: Ctrl-[ ? Date: Fri, 07 Jun 2019 20:20:29 +0200 Message-ID: <87v9xhntoy.fsf@telefonica.net> References: <08AC8151-5911-40FA-8B20-818B839D00AB@traduction-libre.org> <86h892nk2g.fsf@zoho.eu> <9379C01B-80E3-49DD-B830-46CED773DC2C@traduction-libre.org> <83lfydrkde.fsf@gnu.org> <874l51q0s4.fsf@telefonica.net> <83ef45rdij.fsf@gnu.org> <87zhmto6fa.fsf@telefonica.net> <8336klqxxy.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="170505"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jun 07 22:04:30 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hZL6A-000iCV-Rx for geh-help-gnu-emacs@m.gmane.org; Fri, 07 Jun 2019 22:04:26 +0200 Original-Received: from localhost ([::1]:52576 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hZL69-0004uO-QB for geh-help-gnu-emacs@m.gmane.org; Fri, 07 Jun 2019 16:04:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48740) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hZJU1-00054J-Gf for help-gnu-emacs@gnu.org; Fri, 07 Jun 2019 14:21:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hZJTz-0001jo-Lg for help-gnu-emacs@gnu.org; Fri, 07 Jun 2019 14:20:56 -0400 Original-Received: from [195.159.176.226] (port=39728 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hZJTx-0001KF-RG for help-gnu-emacs@gnu.org; Fri, 07 Jun 2019 14:20:54 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hZJTg-000v8Q-21 for help-gnu-emacs@gnu.org; Fri, 07 Jun 2019 20:20:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:g+NOdfbxfgrgLphHrPSV8Ze/j+I= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120816 Archived-At: Eli Zaretskii writes: >> >> There is no reason whatsoever to disallow binding C-[ on GUI Emacs >> >> the same way you can bind any other key. >> > >> > My understanding of what Stefan wrote was that this is NOT disallowed. >> >> The key phrase is "the same way you can bind any other key." Stefan's >> suggestion does not comply with that. > > For me, the key part was "disallowed". If *-set-key functions don't work with those combinations, as far as the user is concerned, he is disallowed to bind them. Not everyone has a Stefan at hand to come with a hack to work around the limitation. >> One thing that I'll like to know is why the hard restriction about >> C-[/C-i exists at all. > > That was already explained: the reason is history and the desire to > have identical behavior by default on all frame types. It is easy to understand from where it came, what is puzzling is the fact that it remained to this day. >> It is understandable that the default bindings mimic what you get on >> the terminal, but forcing the user to jump through hoops to rebind >> those keys helps no one. > > I don't see how we can avoid jumping through hoops when the text > terminal produces an ASCII key code whereas a GUI terminal doesn't. I > invite you to read keyboard.c and keymap.c, where you will find a few > more "accidents" like this. It is not possible (and even more practical than sprinkling the C code base with special cases) to bind those key combinations to the terminal-emulation functionality using the normal methods (keymaps) when running as a gui? Or is it the problem that gui and tty frames can't have different keymaps?