diff --git a/goldlib/gcfg/gxsquish.cpp b/goldlib/gcfg/gxsquish.cpp index 6f8f73e..a17d5a1 100644 --- a/goldlib/gcfg/gxsquish.cpp +++ b/goldlib/gcfg/gxsquish.cpp @@ -82,8 +82,6 @@ void gareafile::ReadSquishFile(char* path, char* file, char* options, char* orig case CRC_AREASBBS: strcpy(buf2, val); MakePathname(buf2, path, buf2); - if(striinc("/NOCHK", options) or striinc("-NOCHK", options)) - strcat(buf2, " /NOCHK"); ReadAreasBBS(buf2); break; case CRC_NETAREA: diff --git a/manuals/gold_ref.tei b/manuals/gold_ref.tei index 851be23..20a6a55 100644 --- a/manuals/gold_ref.tei +++ b/manuals/gold_ref.tei @@ -2340,7 +2340,7 @@ APP OtherProg IRQ 5 Default: - LONG + + - AREAFILE <type> [path/file] [switches] + AREAFILE -

- GoldED+ can read the area setup of many popular mailers, - mail processors and BBS'es, thereby making it much easier - and simpler to configure GoldED+ for the mail areas you - receive, by eliminating the need to write AREA lines for all - or most of your areas. -

-

- - - - type - - - Name of the program. - - - - - path/file - - - Filename or path to the area setup files. - - - - - switches - - - Msgbase specific switches. - - -
-

-

- For most programs, GoldED+ can automatically find the path - or filename using environment variables. By default, - GoldED+ will look for the area setup files in the - AREAPATH. -

-

- There are switches for sorting the areas, and for turning off an - update-check when GoldED+ starts up. -

-

- GoldED+ can handle enviroment variables correctly in paths - specified in connection with this keyword. -

-

- This keyword is explained in greater detail in the - chapter. -

+ + + + <type> [path/file] + [switches] + + + + + + + + + + + + Name of the program. + + + + + path/file + + + Filename or path to the area setup files. + + + + + + + Areafile specific switches. + + +
+
+ + + For most programs, GoldED+ can automatically find the + path or filename using environment variables. By default, + . + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + + +
- AREAFILEGROUPS <(yes)/no> + AREAFILEGROUPS -

- In some AREAFILE setups, you can groups the areas using single - letters (A-Z) or numbers (#1-999). If this keyword is enabled, - GoldED+ will use the area groupid instead of the area - echoid when gathering area specific information from the Random System. -

-

- See chapter for details. -

+ + + + <YES/NO> + + + + In some setups, you can + groups the areas using single letters (A-Z) or numbers (#1-999). + + + + If this keyword is enabled, GoldED+ will use the area + groupid instead of the area echoid when gathering area specific + information from the Random System + group. + + + + + + + This have only sence if you using Random + System groups. + + + + Mail reader. + + + + chapter + +
AREAFORWARDDIRECT -

+ + + + <YES/NO> + + + + This keyword controls whether forward functions should bypass area + selection screen. The destination area should be set with + keyword. + + + + If enabled, the destination area selection list is bypassed, thereby + making possible a + + + + + + This keyword can be used globally and in a + Random System group. + + + + Mail reader. + + + + , + , + , + + +
- AREAFREQDIRECT <yes/(no)> + AREAFREQDIRECT -

- If enabled, the destination area selection list is bypassed, thereby - making possible a seamless file request in the default - destination area. The destination area should be set with - AREAFREQTO. -

-

- TIP: If you (like most) only have one mailer netmail area, - you should enable the AREAFREQDIRECT keyword globally for - simpler file requests. -

-

- This keyword can be used globally and in a Random System group. -

+ + + + <YES/NO> + + + + This keyword controls whether filerequest functions should bypass + area selection screen. The destination area should be set with + keyword. + + + + If enabled, the destination area selection list is bypassed, thereby + making possible a + + + + + + This keyword can be used globally and in a + Random System group. + If you (like most) only have one mailer netmail area, you can enable + this feature globally for simpler file requests. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + +
- AREAFREQTO <echoid(first netmail area)> + AREAFREQTO -

- Sets the default area for the filerequest function. You should set - this to the netmail area where you normally put the filerequest - messages. -

-

- Note that if AREAFREQTO is not specified, it defaults to the - first netmail area found. -

-

- This keyword can be used globally and in a Random System group. -

-

- Related keywords: AREACOPYTO, - AREAREPLYTO. -

+ + + + + + + Sets the default area for the filerequest functions. + + + + The default destination area for the filerequest functions. + + + + First netmail area. + + + + This keyword can be used globally and in a + Random System group. + The forward function uses the + area instead. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + , + + +
- AREAINCL <echoid mask> + AREAINCL -

- With this keyword, you can define the echoids of areas which should be - reincluded by GoldED+, if they have been excluded with the - AREAEXCL keyword. DOS/4DOS-style - wildcards (* and ?) can be used in the echoid mask. -

-

- Examples: + + + + + + + With this keyword, you can define the echoids of areas which should + be reincluded by keyword. + + + + The 4DOS-style + wildcards ( + + + You can use the . + This keyword must be placed before any of + , + , + or keywords. + + + + Mail reader. + + + + , + , + , + , + + + + AREAINCL * ; Includes all areas. AREAINCL *INTER* ; Includes all areas containing INTER anywhere in the ; echoid. AREAINCL INT*.* ; Includes all areas beginning with INT and ; containing a dot anywhere in the echoid. -

-

- You can use the AREAINCL keyword to reinclude areas which have - been excluded with AREAEXCL. -

-

- NOTE that this keyword must be placed before any of - AREA, AREADEF or AREAFILE keywords. -

+ +
+ + + + + AREAISEMAIL <echoid> @@ -5736,7 +6026,7 @@ AREASEP !C "Group C" C Local]]> Feed (12d) character after each message.

- + FRQEXT <.ext> @@ -5757,7 +6047,7 @@ AREASEP !C "Group C" C Local]]> Example: FRQEXT .XYZ

- + FRQNODEMAP <to-node> <from-node> @@ -5781,7 +6071,7 @@ AREASEP !C "Group C" C Local]]> 2:236/99.

- + FRQOPTIONS <options> @@ -5827,7 +6117,7 @@ AREASEP !C "Group C" C Local]]> the .REQ file and NOT also touch/create a .?LO flowfile.

- + FRQWAZOO <yes/no> @@ -7222,7 +7512,7 @@ AREASEP !C "Group C" C Local]]> selected from the EDITSAVEMENU.

- + OUTBOUNDPATH <path> @@ -9446,16 +9736,6 @@ keyword is: Available options:

--NoChk -

-

- Normally GoldED+ will check the areafile timestamps when starting - up, and recompile the configuration if a file was changed. If this - option is given for any AREAFILE, those areafiles will not be - checked. This can be useful in cases like TosScan, GEcho, IMail - and several others which "touch" their files every time they run. -

-

-S<sortspec>