From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.help Subject: RE: printing info pages Date: Sat, 16 Feb 2008 22:23:58 -0800 Message-ID: <003401c8712d$ae2a3d90$2d58908d@us.oracle.com> References: <47B6F1E0.8040101@gmail.com> <87ejbcpfdf.fsf@lion.rapttech.com.au> 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 1203229501 20928 80.91.229.12 (17 Feb 2008 06:25:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 17 Feb 2008 06:25:01 +0000 (UTC) To: "'Tim X'" , Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Feb 17 07:25:22 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JQcxm-0002un-Ba for geh-help-gnu-emacs@m.gmane.org; Sun, 17 Feb 2008 07:25:22 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQcxH-0000ID-Hm for geh-help-gnu-emacs@m.gmane.org; Sun, 17 Feb 2008 01:24:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JQcwz-0000I8-VS for help-gnu-emacs@gnu.org; Sun, 17 Feb 2008 01:24:34 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JQcwx-0000Hw-DK for help-gnu-emacs@gnu.org; Sun, 17 Feb 2008 01:24:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQcwx-0000Ht-5Y for help-gnu-emacs@gnu.org; Sun, 17 Feb 2008 01:24:31 -0500 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JQcww-0007vI-NR for help-gnu-emacs@gnu.org; Sun, 17 Feb 2008 01:24:30 -0500 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id m1H6OLg7029222; Sun, 17 Feb 2008 00:24:21 -0600 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m1H5RBf5020082; Sat, 16 Feb 2008 23:24:20 -0700 Original-Received: from inet-141-146-46-1.oracle.com by acsmt351.oracle.com with ESMTP id 3578617631203229427; Sat, 16 Feb 2008 22:23:47 -0800 Original-Received: from dradamslap1 (/141.144.88.45) by bhmail.oracle.com (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 16 Feb 2008 22:23:46 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <87ejbcpfdf.fsf@lion.rapttech.com.au> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: AchxBlf9RJg2UvOnQ6GKOZXaqM3PKwAJMuog 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-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:51606 Archived-At: > >> I started using ECB and use th einfo pages to read the > >> documentation. Is it possible to convert these info pages into a > >> printable document? > > > > Sure. Use `ps-print-buffer' or `ps-print-buffer-with-faces'. > > > > ,----[ C-h f ps-print-buffer RET ] > > | ps-print-buffer is an interactive compiled Lisp function > > | in `ps-print.el'. > > While this would work OK, it is going to be a bit tedious to > do this for each page. > > An alternative approach would be to use th texinfo sources > for the info pages. Yo will find that the info pages are > generated from texinfo sources. There are utilities out > there to convert the texinfo pages into various forms, > including pdf and postscript. You then just have to send > the file tot he printer. That's no doubt the best solution, but here's another possibility, if you just want a quick way to combine Info nodes so you don't have to print them separately. With info+.el (http://www.emacswiki.org/cgi-bin/wiki/InfoPlus), you can merge Info nodes any way you like, creating one big buffer with all nodes if you like, or any number of buffers, each with some of the nodes. Then just print the buffer(s). Command `Info-merge-subnodes' (bound to `+') merges an Info node with its subnodes into the same buffer. ,----[ C-h f Info-merge-subnodes RET ] | Info-merge-subnodes is an interactive compiled Lisp function in | `info+.el'. | | | (Info-merge-subnodes &optional RECURSIVE-DISPLAY-P RECURSIVE-CALL-P) | | Integrate current node with nodes referred to in its Menu. | | Displays the current Info node, together with the nodes in its Menu. | Buffer `*Info: NODE*' is used for the display, where NODE is the name | of the current node. The contents of this node's subnodes (the nodes | named in this node's Menu) are included in the buffer, following the | contents of the current node. | | Optional arg RECURSIVE-DISPLAY-P (prefix arg if interactive) governs | the way menus of subnodes are treated: | | If nil, nothing additional happens. Subnode menus are not explored. | Only the current node and its immediate subnodes are documented, in | the single display buffer `*Info: NODE*'. | | If non-nil, then the subnodes of a node are treated in the same way | as the parent node, recursively: If any of them has, itself, a Menu, | then that menu's subnodes are also explored, and so on. | | If RECURSIVE-DISPLAY-P is zero, then a single display buffer is | used for all of the nodes explored. Otherwise, a separate display | buffer is used for each subnode that has a Menu (see next). | | Use this when you want a single, flat compilation of the current | node and all of its subnodes. It is less appropriate when the | current node has several levels of subnodes: The flattened | result can be difficult to read. | | If RECURSIVE-DISPLAY-P is positive, then the contents of each | subnode are displayed twice: once in the parent node's display, | and once in the subnode's own display. | | Use this when the current node has several levels of subnodes | and you want each display buffer to be self-contained. | | If RECURSIVE-DISPLAY-P is negative, then there is no redundancy: A | subnode's contents are only displayed in its parent's buffer. The | subnode's own display buffer only contains the contents of its own | subnodes. | | Use this when the current node has several levels of subnodes | and you want no redundancy between the display buffers. | | The user option (variable) `Info-subtree-separator' is a string to be | inserted by `Info-merge-subnodes' just before the title of each | node (preceding its description). By default it is "\n* ", producing | a node title resembling a menu item. Setting this to "\f\n* " will | cause a page break before each node description. For more on setting | this variable, type `C-h v Info-subtree-separator'. | | ------ | | Optional second arg RECURSIVE-CALL-P is only for internal use. It is | used to indicate whether (non-nil) or not (nil) this is a recursive | (i.e. not a top-level) call to `Info-merge-subnodes'. Non-nil | means that this is a subnode, and that its contents should only be | included in the present display if RECURSIVE-DISPLAY-P is also | non-nil. For proper operation when RECURSIVE-DISPLAY-P is zero, the | non-nil value of RECURSIVE-CALL-P should be the node name of the | top-level call to `Info-merge-subnodes'. | | [back] `----