A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-April/023347.html below:

[Python-Dev] Re: reading info files

[Python-Dev] Re: reading info files [Python-Dev] Re: reading info filesMartin v. Loewis martin@v.loewis.de
18 Apr 2002 00:23:33 +0200
Jack Jansen <Jack.Jansen@oratrix.com> writes:

> The problem I always have with info files is the navigation if you
> want to do more than prev/next/up. Plus the often deeply nested
> structure that you can't break out of (which is why you want more
> navigation commands). A book is nice: TOC, chapters, index. A good
> manpage is nice: a 1-3 page document on a single command. Info with
> its deep structure that it won't reveal to you is cumbersome. And you
> can't even print it to read it offline (at least: I always end up with
> an unstructured mess of ASCII lines).

You don't print the info file. Instead, you use the texinfo file to
convert it to TeX, then print that. For GNU software, you can even
order printed manuals from the FSF.

Regards,
Martin





RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4