Documentation

[Jon]

Have a blank line (or table entry) before the next new include.au3 entry.

Not sure about the colour of the include files , try a light grey

[Jos]

Have a blank line (or table entry) before the next new include.au3 entry.

Not sure about the colour of the include files , try a light grey

what about this one ??

[Jon]

Better, but still need a blank line before each new include.au3 line.

Edit: Oh, and it's #include not #Include (all lower case).

[Jos]

Better, but still need a blank line before each new include.au3 line.

Edit: Oh, and it's #include not #Include (all lower case).

.. had that... then wanted to remove the blank line before the first file, which did it for all

its now adding them correctly...

[Jon]

Perfect. I'll just go now

[Jos]

Perfect.  I'll just go now

me too... will mail you this version of the script.... laters..

[jlandes]

On the pages that list the actual documentation for the function, can we remove the version information from the top, so that it just displays the function's description? Also, at the top each include file reads as "Library Function Reference:File.au3". It should have a space to read something like "Library Function Reference: File.au3". Also, I like what you've done with the reference page.

[Jos]

Edit: Oh, and it's #include not #Include (all lower case).

Made the change and some other changes for Jeremy... just uploaded the latest test helpfile for final check and will sent the updated script when its ok...

[CyberSlug]

What would you think about an appendix page that lists certain programs / command-line tools that are available in the different versions of windows?

For example, see this site

[GEOSoft]

What would you think about an appendix page that lists certain programs / command-line tools that are available in the different versions of windows?

For example, see this site

I'm not sure that you want to get to deeply into that. For instance that page does not get to involved in it and from what I saw they are strictly for Win XP (probably will work on 2000 as well) , but if you start doing it for all the systems there is going to be endless questions. I have pages and pages of Command line swithes for various Windows (and othe MS) programs and the problem is that they keep changing with different versions and there are so many that are undocumented. For example I could list all of the format command switches used since DOS 3.0 and some are not documented for a very good reason. There are two particular switches that used individualy are just fine but if you use them together your drive is headed into the garbage, no if's ands or buts about it. Even going back to the days of RegClean, how many people know that there is a switch that would run it in an advanced mode that gave you a lot more flexibility.