From: "Mr. Veli Suorsa" Sender: vjsuorsa AT Surfeu DOT Fi To: djgpp AT delorie DOT com Cc: Eli Zaretskii , VJSuorsa AT Surfeu DOT Fi Date: Mon, 19 Mar 2001 04:47:01 +0200 Subject: Re: Can you combine DOC- subdirectories X-Mailer: CWMail Web to Mail Gateway 2.6k, http://netwinsite.com/top_mail.htm Message-id: <3ab57325.79c.0@surfeu.fi> X-User-Info: 193.167.106.194 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com Thanks for your reply. >> It is just a waste of time to search documentation from >> un-standard directories. > >Why do you need to search? The docs directories hold >printed versions of the manuals. You are supposed to >print them, and then get rid of those monstrously large >files. I am not a beginner, who read everything, ten thousands of pages, from printed paper. I use docs from hard drive with programs and keep them in arch ives. >> >> Directory of C:\DJGPP\GNUDOCS >> >> BASH-2 04 >> >> FILUTIL3 16 >> >> GCC-2 952 >> >> - Why g77 / f77 documentation is here? >> > >> >Because g77 is part of the GCC package. >> >> Should directory's name be C:\DJGPP\GNUDOCS\G77 ? > >No, I don't think so. Why not? There were only 20 files about Fortran 77 docs. >> >What's not user-friendly about Info? >> >> So many stars-lines from start page and not even alphapetical order! > >They are in the logical order: the Info system itself >first (so that you could use Info), then the compiler, the >library, and the basic development tools such as the >debugger, then the utilities. You can do better, I suppose. >> You should use menus in info! > >The stand-alone Info reader was designed to run on >bare-bones text terminal without a mouse. If you want a >more graphical Info reader, get one of those mentioned in >section 5.1 of the DJGPP FAQ list. Not a bad idea, indeed. I take a look and try other well modelled programs too. >> >> and a direct port to Rhide (if possible). >> > >> >RHIDE already has an internal Info reader. >> >> Lets take an example: >> 1) I write a C program in Rhide. >> 2) I want to use intent program while writing. What >> F-key? >> 3) And read intent's instructions (was it really right, >> e.g. intent -mh -i1 done.c)? What F-key? > >I don't use RHIDE, so I wouldn't know. The stand-alone >Info reader has the --apropos option, so "info --apropos >indent" should give you what you want. For finding the >instruction to run a utility, use the option --usage, like >in "info --usage indent". Who is expert with Rhide? >I suggest to read the section in the file README.1ST >called "Reading the documentation, or A Crash Course in >Info". It describes some of the more efficient facilities >of the Info reader. It was not a crach course at all. I don't even get out of Info. I must tell you an experience two years ago, when I was eating spagetti, when writing a program. It was so hot that I had to spit out of my mouth and my fork fasten on to middle of the keyboard and jam my editor. That was a crach. I don't eat anymore spagetti (sorry italians, no more help) when writing. >> I can read C library (libc reference) from Rhide, but >where is Fortran (and pascal and other utilities) library? > >They probably don't exist. You get the documentation >which comes with the original GNU packages; whatever they >supply, you have on your machine. If they didn't supply >documentation for some library, it isn't available. This is recommended new feature in Rhide, that I hope they will do soon. Thank you! Veli Suorsa --- "People must believe to the future to be able to live!" ---------------------------------- J.V.Snellman, 1890. Oulu, FINLAND Mailto:VJSuorsa AT Surfeu DOT Fi http://members.surfeu.fi/veli.suorsa/ http://www.surfeu.fi