Support and General Use > User Interface and Voice

.cfg file

<< < (3/3)

whatchamacallit:
Well, I won't argue with now. As far as I'm concerned, I've downloaded the latest manual from where you get the bleeding edge builds and the stuff on making your own .cfg file is subject 7.3 which is about a third of a page, a lot less than in the Wiki unless you know a different Wiki or a different downloadable manual...
Greetings,

whatchamacallit

Febs:
(1) The text in section 5.4.6 of the manual has more detail  than the wiki page regarding how .cfg files are created and used.

(2) Section 7.3 of the manual cross-references Appendix C.  Appendix C contains a detailed chart of configurable options similar to the chart on the wiki page.  The difference is that the the chart in the manual is platform specific and up-to-date, while the one on the wiki is not.

I'm going to clean up that section of the manual.  It looks like 5.4.6 is out of place (the manage settings menu is not a submenu of system options) and the current section 5.4.6 and section 7.3 are redundant.

EDIT:  OK, I have merged section 5.4.6 with section 7.3 so that all of the discussion of creating, editing, and using .cfg files is in one place in section 7.3.  (The .cfg file options are still contained in an appendix.)  These changes have been committed to CVS, so they should appear in tomorrow's daily build manual.

bascule:

--- Quote from: Febs on August 12, 2006, 10:31:12 AM ---EDIT:  OK, I have merged section 5.4.6 with section 7.3 so that all of the discussion of creating, editing, and using .cfg files is in one place in section 7.3.  (The .cfg file options are still contained in an appendix.)  These changes have been committed to CVS, so they should appear in tomorrow's daily build manual.

--- End quote ---

Thanks for that, Febs. I've done a couple of Wiki updates, but the effort involved in making those same amendments to the manual (download, install, learn and configure CVS, learn what source code looks like, make updates, build a manual to check etc., etc.) would just use time I haven't got at the moment :( )

I'm thankful that someone else has the energy to do it.

Is it sufficient to flag up in threads where manual changes are required, or should I be thinking about a bug submission for anything that seems v. important to me?

Febs:
I do tend to read most of the threads on the forum, but I always prefer to see a bug report.  On any given day when I sit down to make updates to the manual, I may or may not remember something I read in the forums, but it's very easy to search flyspray for all bugs and feature requests for category "manual."

bascule:
OK, I'll bear that in mind :)

Navigation

[0] Message Index

[*] Previous page