From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: C-h C-i Date: 18 Jun 2004 03:18:08 -0500 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87brjh1dq7.fsf@floss.red-bean.com> References: <877jxty4gg.fsf@emacswiki.org> <87vflafi4g.fsf@emptyhost.emptydomain.de> <873c6sogur.fsf@mail.jurta.org> <87wu26xjey.fsf@mail.jurta.org> <87pt7y32au.fsf@floss.red-bean.com> <87smcts5e4.fsf@mail.jurta.org> Reply-To: kfogel@red-bean.com NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1087569933 30535 80.91.224.253 (18 Jun 2004 14:45:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 18 Jun 2004 14:45:33 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Jun 18 16:44:50 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BbKbp-0007vu-00 for ; Fri, 18 Jun 2004 16:44:49 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BbKbp-0000jW-00 for ; Fri, 18 Jun 2004 16:44:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BbKcv-0001I0-BQ for emacs-devel@quimby.gnus.org; Fri, 18 Jun 2004 10:45:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BbKcn-0001HO-Os for emacs-devel@gnu.org; Fri, 18 Jun 2004 10:45:49 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BbKcm-0001Gl-1g for emacs-devel@gnu.org; Fri, 18 Jun 2004 10:45:49 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BbKcl-0001Gb-UC for emacs-devel@gnu.org; Fri, 18 Jun 2004 10:45:48 -0400 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BbKbb-00089I-IM for emacs-devel@gnu.org; Fri, 18 Jun 2004 10:44:35 -0400 Original-Received: from [207.115.63.78] (helo=pimout6-ext.prodigy.net) by mx20.gnu.org with esmtp (Exim 4.34) id 1BbKSb-0002uN-GV for emacs-devel@gnu.org; Fri, 18 Jun 2004 10:35:18 -0400 Original-Received: from floss.red-bean.com (adsl-65-42-91-60.dsl.chcgil.ameritech.net [65.42.91.60]) by pimout6-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id i5IEZ1RB153460; Fri, 18 Jun 2004 10:35:01 -0400 Original-Received: from kfogel by floss.red-bean.com with local (Exim 3.34 #1 (Debian)) id 1BbEZc-0004GV-00; Fri, 18 Jun 2004 03:18:08 -0500 Original-To: Juri Linkov Emacs: anything free is worth what you paid for it. In-Reply-To: <87smcts5e4.fsf@mail.jurta.org> Original-Lines: 36 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:25083 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:25083 Juri Linkov writes: > Karl Fogel writes: > > `C-h C-i' may be unbound now, but another use might be found for it > > later, one better than simply duplicating what `C-h i' does right now. > > If we bind it to something common and important like `info', it'd be > > hard to change that later. > > I don't suggest to make `C-h C-i' an official keybinding for `info' > by documenting it everywhere. What I propose is only to add it > to help.el as a catcher for cases when users mistype `C-h i' > which now is very probable when switching between Info buffer with > key sequences like C-1 C-h i C-2 C-h i C-3 C-h i C-4 C-h i C-5 C-h i. > > If we find a better use for `C-h C-i' later, we can freely rebind it, > since we don't advertise it as an official keybinding for `info'. (Has Emacs ever used such an "unofficial keybinding" policy before?) I really don't think it's worth optimizing for such narrow use cases by making a special keybinding, especially when the consequence of mistyping right now is merely that nothing happens. There are two possible outcomes here, both undesirable IMHO: 1. That key sequence is not used very often... In which case, the benefit of adding this keybinding is correspondingly small. or 2. That key sequence is used fairly often... In which case, the new binding would be something people *do* grow to depend on, whether we document it "officially" or not, and therefore we'd effectively lose the ability to bind it to something different in the future. -Karl