From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Let `C-h i' open all Info buffers that were quit? Date: Sat, 29 Jul 2006 12:02:59 +0300 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1154163830 24704 80.91.229.2 (29 Jul 2006 09:03:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 29 Jul 2006 09:03:50 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 29 11:03:42 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G6kjD-0001tY-I3 for ged-emacs-devel@m.gmane.org; Sat, 29 Jul 2006 11:03:23 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G6kjC-0007xO-OA for ged-emacs-devel@m.gmane.org; Sat, 29 Jul 2006 05:03:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G6kiw-0007wY-01 for emacs-devel@gnu.org; Sat, 29 Jul 2006 05:03:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G6kit-0007up-0N for emacs-devel@gnu.org; Sat, 29 Jul 2006 05:03:05 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G6kis-0007ug-KS for emacs-devel@gnu.org; Sat, 29 Jul 2006 05:03:02 -0400 Original-Received: from [192.114.186.20] (helo=nitzan.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G6kl3-00016G-DJ for emacs-devel@gnu.org; Sat, 29 Jul 2006 05:05:17 -0400 Original-Received: from HOME-C4E4A596F7 (IGLD-84-228-215-112.inter.net.il [84.228.215.112]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id EHG44636 (AUTH halo1); Sat, 29 Jul 2006 12:03:00 +0300 (IDT) Original-To: "Drew Adams" In-reply-to: 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:57775 Archived-At: > From: "Drew Adams" > Date: Fri, 28 Jul 2006 18:01:10 -0700 > > Post-release feature request - > > You can use `M-n' (`clone-buffer') in Info, to have more than one Info > buffer open. I don't know if other people use Info this way very much, using > different parts of Info in different buffers, but I do. I'm a heavy user of this feature. > If you quit Info and reenter, apparently only the first Info buffer is > reentered (displayed) - the clones are not. The clone Info buffers are still > available, so you can get to them, e.g., via `C-x C-b', but `C-h i' doesn't > automatically display them. You need to give `C-h i' an argument. For example, `C-u 3 C-h i' goes to the buffer `*info*<3>'. > Anyway, my real suggestion here is this: It would be handy if `C-h i' opened > (displayed) *all* of the Info buffers. Perhaps what you lack is this piece of information: `C-x C-b' shows the Info manual's identification next to its *info* buffer name, instead of the file name for buffers that have an associated file. So, if what you want is a fast way of getting back to a specific Info buffer, type `C-x C-b' and select the manual you want from the list. I implemented this feature because I couldn't remember which buffer has what manual. > Even users who know about `q' followed by `C-h i' might not know that all of > their Info buffers are still available - that is, they might not think to > use `C-x b' to access them. Why would a user think that Emacs killed one or more buffers without a good reason? `q' is not documented to kill a buffer. For that matter, I don't understand why do you use `q' in Info. All it does is bury the Info buffer, then switch to another buffer. I'd simply use `C-x b', or even `C-x 5 b'. > I imagine that there will usually only be relatively few Info buffers at any > time This evidently is not so in my case. I currently have 14 different Info buffers in this session, each one displaying a different manual which I frequently need to look in. (I also dedicate a separate frame to those buffers.) I cannot imagine how Emacs could manage to display all of those 14 buffers in any useful way.