From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Ctrl-[ ? Date: Mon, 10 Jun 2019 02:23:43 +0200 Message-ID: References: <08AC8151-5911-40FA-8B20-818B839D00AB@traduction-libre.org> <6F55E018-B15E-42B0-8794-21F55BBA23D3@traduction-libre.org> <34E3289C-10EE-4A23-AEE4-80D984DB2EDE@gnu.org> <6A538FF9-94C8-491D-B1B9-5C0D09FE7C39@acm.org> <838suesw93.fsf@gnu.org> <3580dbb9-73a8-d26a-5466-5799e3726c34@gmail.com> <83tvd2rd8b.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="167117"; mail-complaints-to="usenet@blaine.gmane.org" To: Eli Zaretskii , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 10 02:24:17 2019 Return-path: Envelope-to: ged-emacs-devel@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 1ha86i-000hLs-VD for ged-emacs-devel@m.gmane.org; Mon, 10 Jun 2019 02:24:17 +0200 Original-Received: from localhost ([::1]:39264 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha86h-0005sH-C8 for ged-emacs-devel@m.gmane.org; Sun, 09 Jun 2019 20:24:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36270) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha86Y-0005rE-BS for emacs-devel@gnu.org; Sun, 09 Jun 2019 20:24:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ha86X-0000NZ-Dn for emacs-devel@gnu.org; Sun, 09 Jun 2019 20:24:06 -0400 Original-Received: from mail-wm1-f47.google.com ([209.85.128.47]:53428) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ha86Q-0000GB-Vg; Sun, 09 Jun 2019 20:24:00 -0400 Original-Received: by mail-wm1-f47.google.com with SMTP id x15so6817581wmj.3; Sun, 09 Jun 2019 17:23:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=zOdHxLPBUMI89LKf/i7gWLkVloQMwJuugUmcMyV0vgE=; b=iWORIkdfm/Wk7+fi95mihEaiWKChD+AIwWD9VfzyThWY9hCVAKPXzgrQueFil9kiKi rXi1wL0PT1CpGzfuekoixxa0sntCrwmGyf/LmifAWWnaKYO8LwmL2Q3O1pdNTg+LSYFJ kS/eUU66uM2lbQWGrPuJZv69E5i7ov2aUl0S2KhfWemDPqhB7MdHs/fKMPoeixP/e1TW C6es0Vqp5xplDXkwN1EEMUcjRTSY2QauZNeDOe0E7t19ANIXjTPlzoiVWjpJOeHIRBBt J06KD9CWB3VOVz+wVQgIe8P8B3rdmg5DoPU0nDrUQhawb4/Wi+/bj/Ag3bzcR0QTOy/x Rgxw== X-Gm-Message-State: APjAAAXh+AkmwXoesb3wkWoiI4aCCfOX30wNfmtgNDhElYSMKALU9KCt 9nFCRFeoFsPFVhuQ07r4jrJH2+4DQ0xbXc2G4de65KT9 X-Google-Smtp-Source: APXvYqx+k6EGDkMkVWykK8vMAn+VwYyOEdDhXKJ7ZvH3LD1gqKmF0VCcmpZR2MGWVhCQlIwTVhK/eIVE0tFxYbhSmEo= X-Received: by 2002:a1c:b6d4:: with SMTP id g203mr11262493wmf.19.1560126235454; Sun, 09 Jun 2019 17:23:55 -0700 (PDT) In-Reply-To: <83tvd2rd8b.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.128.47 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237383 Archived-At: Eli Zaretskii writes: > IMO, being able to bind C-[ to something else is not an important > feature, not enough to break the compatibility. But that's me. Perhaps it makes sense from a compatibility standpoint, but I suspect that many users would be surprised by the inability to rebind C-[ or C-i. (Binding C-i also rebinds TAB.) Would it make sense to show a warning when trying to bind keys such as C-[ or C-i? (Or, perhaps better, to show it in the "*Help*" buffer? C-h k C-[ only shows "ESC- " when I try, though.) Would it make sense to introduce a variable to turn this behaviour off in a graphical environment? The default could stay as is. Thanks, Stefan Kangas