From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: RE: Info-build-node-completions has an extra `*' node Date: Sun, 17 Feb 2008 16:02:58 -0800 Message-ID: <008301c871c1$9f45d5c0$2d58908d@us.oracle.com> References: <006901c871b3$f4da48d0$2d58908d@us.oracle.com><006a01c871b5$33b5a260$2d58908d@us.oracle.com> <87tzk7godg.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1203293030 32231 80.91.229.12 (18 Feb 2008 00:03:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Feb 2008 00:03:50 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org To: "'Juri Linkov'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 18 01:04:12 2008 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 1JQtUS-0007LV-Ey for ged-emacs-devel@m.gmane.org; Mon, 18 Feb 2008 01:04:12 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQtTy-0008FO-5b for ged-emacs-devel@m.gmane.org; Sun, 17 Feb 2008 19:03:42 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JQtTs-0008F1-TF for emacs-devel@gnu.org; Sun, 17 Feb 2008 19:03:36 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JQtTr-0008Em-9V for emacs-devel@gnu.org; Sun, 17 Feb 2008 19:03:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQtTr-0008Ej-7N for emacs-devel@gnu.org; Sun, 17 Feb 2008 19:03:35 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JQtTq-0007ju-OA for emacs-devel@gnu.org; Sun, 17 Feb 2008 19:03:34 -0500 Original-Received: from mail.gnu.org ([199.232.76.166] helo=mx10.gnu.org) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JQtTq-0001t1-Jf for emacs-pretest-bug@gnu.org; Sun, 17 Feb 2008 19:03:34 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JQtTn-0007jW-9l for emacs-pretest-bug@gnu.org; Sun, 17 Feb 2008 19:03:34 -0500 Original-Received: from rgminet01.oracle.com ([148.87.113.118]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JQtTn-0007jS-01 for emacs-pretest-bug@gnu.org; Sun, 17 Feb 2008 19:03:31 -0500 Original-Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id m1I03S5x024350; Sun, 17 Feb 2008 17:03:28 -0700 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by rgmgw1.us.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id m1HNpKw0018836; Sun, 17 Feb 2008 17:03:28 -0700 Original-Received: from inet-141-146-46-1.oracle.com by acsmt350.oracle.com with ESMTP id 3578778181203292962; Sun, 17 Feb 2008 16:02:42 -0800 Original-Received: from dradamslap1 (/141.144.88.45) by bhmail.oracle.com (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 17 Feb 2008 16:02:42 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <87tzk7godg.fsf@jurta.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: AchxvECAkcOZbEZMR8qV8qTEkZdgVgAAcVlA X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-detected-kernel: by monty-python.gnu.org: 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:89421 gmane.emacs.pretest.bugs:21171 Archived-At: > > I should have added that after you do `Info-goto-node *' > > the Info buffer is widened, so you see all of the node headers > > in raw form. So this is a worse bug than simply allowing an > > extra `*' completion that doesn't do anything > > except mess up the mode line. > > How funny that you thought this feature is a bug :) Dunno if "funny" is the right word. How is this a feature? ;-) > Please read the Info manual at (info "(info) Go to node") that says: > > The node name `*' specifies the whole file. So you can > look at all of the current file by typing `g*' or > all of any other file with `g(FILENAME)*'. I see. Guess I haven't read the Info manual in a long time. Out of curiosity, why was this feature added? What is the need that it satisfies? And why is only `*' written in the mode line as the node name, rather than, say, `*** All Nodes ***' or `*** Whole Manual ***' (the `***' or something similar indicating that this is not just a node name). I'm afraid that `*' is not very noticeable in the mode line. There are already other `*' there, so you see, for example, `*info* (emacs) *'. And it is not immediately obvious that the entire manual is in fact visible. I thought that it had just revisited the current node, until I scrolled a bit and noticed that from the node headers that it was widened. Someone falling into this state by accident might well get confused, IMO. And `*' is the first completion candidate listed in *Completions*. It might seem cute that `*' is the name for this pseudo-node (a wildcard, presumably), but the behavior and meaning are not obvious. Why `go to node' would have an alternative action of `show all nodes' is not clear to me - why associate this behavior with `Info-goto-node'? I suppose you'll say that that's what we do for wildcards with `find-file'. It's also not obvious how to get out of this view-whole-raw-info-file mode, once you fall into the black hole. Things like `C-l' and `u' (Node has no Up) don't help. It turns out that using `g' again, and picking some real node name this time, will restore Info to its normal self (whew!). There might be additional ways to get back to normal; I don't know. But I don't think it is obvious, and I do think it is potentially confusing. At the very least, a message should inform the user: (a) what has happened, and (b) how to get back to normal. Interesting to know, at least... On n'arrete pas le progres.