From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: RE: C-h C-b to view "Reporting Bugs" section of the manual Date: Tue, 22 May 2012 13:12:45 +0900 Message-ID: <87aa10q2f6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <41txz9pboj.fsf@fencepost.gnu.org> <3C645B82A25242F7AF3BE16B9CB9BCAA@us.oracle.com> <87hav9oyq3.fsf@uwakimon.sk.tsukuba.ac.jp> <9404D5B04C754DFAA8733E1027D8BDF5@us.oracle.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: dough.gmane.org 1337659979 23483 80.91.229.3 (22 May 2012 04:12:59 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 22 May 2012 04:12:59 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 22 06:12:58 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SWgSv-0002wW-6F for ged-emacs-devel@m.gmane.org; Tue, 22 May 2012 06:12:57 +0200 Original-Received: from localhost ([::1]:44587 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWgSu-0006zj-Gq for ged-emacs-devel@m.gmane.org; Tue, 22 May 2012 00:12:56 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:36306) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWgSr-0006zd-Sy for emacs-devel@gnu.org; Tue, 22 May 2012 00:12:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SWgSp-0003Ui-Tc for emacs-devel@gnu.org; Tue, 22 May 2012 00:12:53 -0400 Original-Received: from mgmt1.sk.tsukuba.ac.jp ([130.158.97.223]:45805) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWgSp-0003UC-JA for emacs-devel@gnu.org; Tue, 22 May 2012 00:12:51 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt1.sk.tsukuba.ac.jp (Postfix) with ESMTP id B057E3FA0845; Tue, 22 May 2012 13:12:45 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 7429C1A31AE; Tue, 22 May 2012 13:12:45 +0900 (JST) In-Reply-To: <9404D5B04C754DFAA8733E1027D8BDF5@us.oracle.com> X-Mailer: VM undefined under 21.5 (beta31) "ginger" 5d3bb1100832 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 130.158.97.223 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:150593 Archived-At: Drew Adams writes: > > > `C-h M-k' for `describe-keymap' > > > > Speaking of redundant bindings (C-h m ...) > > Not at all. Have you tried it? There is nothing similar anywhere, AFAIK. It > is not like `C-x b' (current bindings, all maps) or `C-h m' (mode description - > variable and always incomplete wrt a keymap). Try finding the keys bound in a > minibuffer keymap, in a human-readable form. *shrug* For me, it's a YAGNI; I've never wanted that, so M-x describe-keymap would be good enough in case I ever want it in the future. Maybe other people would like it to be on key though, and I grant that bindable keys are now a scarce resource. > When you look for the doc about a command (including `r-e-b'), why > not have immediately a set of links to its doc in the manuals (with > the manual names and nodes in the links). Well, my answer is "that's ugly and harder to invoke (gotta goose the rat) than C-h C-f RET which already works" (at least in XEmacs, C-h f foo RET gives you the docstring for foo and leaves point on `foo' so that C-h C-f defaults to the right thing). IMO YMMV FWIW etc. Furthermore, here the purpose of putting the Bugs node on a key is to make it immediately available to bug reporters. This isn't about documenting the use of r-e-b, it's about good style in bug reports. So it would need to be special-cased somehow (I guess you could have a generic function that would apropos the obarray and/or the known Info nodes, but that might be expensive since it would probably have to hit the disk a lot, possibly including decompressing compressed Info files). The proposal to special-case it as a help key is going in the right direction by making it very inexpensive to get to the Bugs node, but I question its usefulness because of discoverability concerns.