Beyond undoc.txt

[Uncwilly]

It seems to me that there are a number of switches/settings that are not included in the help file or undoc.txt.

Could those that know some of them document them here?
Prehaps this could be stickized. There are several other things like an explanation of worktodo.ini that might be set as sticky for reference purposes.

[Xyzzy]

The only undocumented one I know is

FullBench=1

[PrimeCruncher]

Undocumented functions not in the undocumented functions file.

[nitro]

Originally posted by PrimeCruncher
Undocumented functions not in the undocumented functions file.

Of course simply scanning the source code would suffice

[PrimeCruncher]

Originally posted by nitro
Of course simply scanning the source code would suffice

True, but that's the point of HAVING undoc.txt, so that you don't have to and so that people unexperienced with programming can still use advanced features.

[Gary Edstrom]

Originally posted by Uncwilly
It seems to me that there are a number of switches/settings that are not included in the help file or undoc.txt.

Could those that know some of them document them here?
Prehaps this could be stickized. There are several other things like an explanation of worktodo.ini that might be set as sticky for reference purposes.

Of course, by putting the undocumented features into the file "undoc.txt", they become documented features. This, of course, means that they should not be listed in "undoc.txt". But if you leave them out, the become undocumented features, but...

[cheesehead]

Originally posted by nitro
Of course simply scanning the source code would suffice

Simply scanning the source code may not sufficeth without supplementally seeking strategic schemes of the source coder, but scanning source code with sufficiently sagacious subtlety sometimes sufficeth to satisfy the scanner's search for that which seems insufficiently documented.

Ommm...

[Maybeso]

Originally posted by cheesehead
Simply scanning the source code may not sufficeth without supplementally seeking strategic schemes of the source coder, but scanning source code with sufficiently sagacious subtlety sometimes sufficeth to satisfy the scanner's search for that which seems insufficiently documented.

Ommm...

So speaks the sage.

Or, as a well known would say it:

Thimply thcanning the thourthe code may not thuffitheth without thupplementally theeking thtrategic thchemeth of the thourthe coder, but thcanning thourthe code with thuffithiently thagathiouth thubtlety thometimeth thuffitheth to thatithfy the thcanner'th thearch for that which theemth inthuffithiently documented.