cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1999/08/29/21:47:39

From: ryot AT bigfoot DOT com (George Ryot)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: INFO usage in README.1ST
Message-ID: <37c9aa03.26909651@news.clara.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990829142901 DOT 9438f-100000 AT is>
X-Newsreader: Forte Agent 1.5/32.452
X-No-Archive: yes
MIME-Version: 1.0
Date: Sun, 29 Aug 1999 22:30:58 GMT
NNTP-Posting-Host: 195.8.91.61
X-Complaints-To: abuse AT clara DOT net
X-Trace: nnrp3.clara.net 935965858 195.8.91.61 (Sun, 29 Aug 1999 23:30:58 BST)
NNTP-Posting-Date: Sun, 29 Aug 1999 23:30:58 BST
Lines: 29
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

I am fairly new to info so probably a good candidate to try this
readme out on.  All the examples worked but when I tried to use my new
found knowledge to call up the index in the libc documentation (by
pressing i) it just beeped and said 'No indices found'.  If not all
info files have this feature then IMHO it would be better to change
the order of these paragraphs:

> To quickly search for a certain subject in the index of a manual,
> press `i' ...
> 
> For example, suppose you get the infamous message "ld.exe: ...
> 
> If you prefer to look up the subject in the index yourself, page
> through the top-level menu of the manual until you find ...

Those paragraphs could become:

  To look up a subject in the index, page through the top-level ...

  Some manuals allow you to search the index, to do this press 'i' ...

  For example, suppose you get the infamous message "ld.exe: ...


I would have found this guide very useful when starting with DJGPP.
-- 
george

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019