1<!doctype tei.2 public '-//TEI//DTD TEI Tools 0.1//EN'> 2<!-- $Id: gold_ref.tei,v 1.35 2003/12/10 08:35:16 asa Exp $ --> 3<TEI.2 lang='en'> 4<!-- --------------------------------------------------------------------- --> 5 <teiHeader> 6 <fileDesc> 7 <titleStmt> 8 <title> 9 GoldED+ Reference Manual 10 </title> 11 </titleStmt> 12 <sourceDesc> 13 <p> 14 Created in electronic form. 15 </p> 16 </sourceDesc> 17 </fileDesc> 18 <profileDesc> 19 <langUsage> 20 <language id="en"> 21 English 22 </language> 23 </langUsage> 24 </profileDesc> 25 </teiHeader> 26<!-- --------------------------------------------------------------------- --> 27 <text> 28<!-- --------------------------------------------------------------------- --> 29 <front> 30 <titlePage> 31 <docTitle> 32 <titlePart type=main> 33 GoldED+ 34 </titlePart> 35 <titlePart type=desc> 36 Reference Manual 37 </titlePart> 38 </docTitle> 39 <docAuthor> 40 Odinn Sorensen, Dirk A. Mueller, Alexander S. Aganichev and others 41 </docAuthor> 42 <docDate> 43 1990-2003 44 </docDate> 45 </titlePage> 46 <divGen type=toc> 47 </front> 48<!-- --------------------------------------------------------------------- --> 49 <body> 50<!-- --------------------------------------------------------------------- --> 51 <div1> 52 <head> 53 Introduction 54 </head> 55 <p> 56 <name/GoldED+/ is a successor of the wellknown <name/GoldED/ mail editor 57 originally written by <name/Odinn Sorensen/. 58 </p> 59 <p> 60 <name/GoldED+/ is run under <name/DOS/ with 32-bit <abbr/DPMI/ driver, 61 <name/Microsoft Windows/, <name>IBM OS/2</name>, <name/Linux/, 62 <name/FreeBSD/, <name/QNX/, and <name/BeOS/. There should be no serious 63 problem to compile it on other <name/UNIX/-like systems running on 64 <name/Intel/ <name/80x86/ architecture. Unlike the original version of 65 <name/GoldED/, <name/GoldED+/ is not supported on CPUs lower than 66 <name/80386/. 67 </p> 68 <p> 69 <name/GoldED+/ takes his history from the patch collection made by 70 <name/Alexander Aganichev/. A lot of code was contributed to 71 <name/GoldED+/ by different people around the world. At least, 72 <name/GoldED+/ contains portions of code written by the core team of 73 <name/GoldED/ (<name/Odinn Sorensen/, <name>Dirk A. Mueller</name>, and 74 <name/Leonid Lisovsky/), <name/Mike Smedley/, <name/Pavel Gulchouck/, 75 <name/Denis Zavorotny/, <name/Alexander Batalov/, <name/Eugene Roshal/, 76 <name/Igor Vanin/, <name/Alexey Froloff/, <name/Andrew Shakhmatov/, 77 <name/Roman Trunov/, <name/Alex Druinsky/, <name>Alexander 78 Tsvyashchenko</name>, <name/Pavel Tsekov/, <name/Alexander Reznikov/, 79 <name/Siarzhuk Zharski/ and 80 (of course) by the maintainers of <name/GoldED+/ (<name>Alexander 81 Aganichev</name> and <name/Jacobo Tarrio/). Some portions of code was 82 taken from C/C++ snippets collected by <name/Bob Stouts/ (personal thanks 83 goes to <name/Thad Smith/, <name/Raymond Gardner/, <name/Jeff Dunlop/, 84 <name/Mark G. Mendel/, <name/Gary S. Brown/, <name/John Rex/, and 85 <name/Walter Bright/) and some other from <name/GNU/ libraries 86 (thanks goes to <name/GNU/ C library maintainers, <name/Rob Swindell/, 87 <name/Frank Pilhofer/, <name/Haruhiko Okumura/, <name>Haruyasu 88 Yoshizaki</name>, <name/SLang/ maintainers, <name/TIN/ maintainers, and 89 <name/Eric Newton/). Also, there are portions of code which are courtesy 90 of various FTN software authors: <name/Scott J. Dudley/ and <name>Lanius 91 Corporation</name>, <name/Bit Bucket Software/, <name/Husky Team/, 92 <name/Thomas Waldmann/, <name/Peter Davies/, <name/Ron Clark/, 93 <name/Tobias Burchhardt/, <name/Andreas Klein/, <name>Folkert J. 94 Wijnstra</name>, <name/Gerard J. van der Land/, <name/Peter Stewart/ and 95 <name/InterZone Software, Inc./, <name/Marco Maccaferri/, 96 <name/Wynn Wagner III/, <name/Andrew Milner/ and <name>Continental 97 Software</name>, <name/Bjarne Maschoreck/, <name/Roger Kirchhoff/, 98 <name/Stefan Graf/, <name/Nicolai Dufva/, and <name/Morten Baun/. If you 99 feel that your name is missed here please drop an e-mail to the 100 <name/GoldED+/ maintainers. 101 </p> 102 <p> 103 We also need to thanks all that people who have contributed configuration 104 files: <name/Richard Menedetter/, <name/Peter Karlsson/, 105 <name/Daniel Hahler/, <name/Marco Van den Bovenkamp/, <name>Steve 106 Shapiro</name>, <name/Teddy Winstead/, <name/Richard Merit/, 107 <name/Thomas Kraft/, <name/Magnus Jacobsen/, <name/Lars Pehrsson/, 108 <name/Tony Van den Bogaert/, <name/Karsten Palmvig/, <name>Michael 109 Hembo</name>, <name/Thomas Endres/, <name/Nathan Moschkin/, 110 <name/Micheal Dunnagan/, <name/Joseph Carnage/, <name/Thomas Endres/, 111 <name/Niels Axelsson/, <name/Gustav Brock/, <name/Stig Jacobsen/, 112 <name/Erik Wachtmeester/, <name/Dirk Frieborg/, <name/Gd'A/, 113 <name/Cees Schouten/, <name/Andrew Voronin/, <name/Arkady Grikurov/, 114 <name/Mik Karlsson/, <name/K. Simonsen/, <name/Thomas Gradin/, 115 <name/Andre van de Wijdeven/, <name/Robert Bashe/, <name>Kees 116 Bergwerf</name>, <name/Ferdinand Grassmann/, <name/Laurent Jumet/, 117 <name/Andrew Porokhnyak/, and <name/Oleksandr Liutyi/. 118 </p> 119 <p> 120 Special thanks goes to <name/Fra`2k/ for helping in testing :-) 121 </p> 122 </div1> 123<!-- --------------------------------------------------------------------- --> 124 <div1> 125 <head> 126 License Agreement and Copyright Notices 127 </head> 128 <p> 129 <name/GoldED+/ - Copyright © 1990-1999 by <name/Odinn Sorensen/, 130 copyright © 1999-2002 by <name/Alexander S. Aganichev/, 131 <name/Jacobo Tarrio/ and others. 132 </p> 133 <p> 134 <name/GoldED+/ and the <name/Goldware Utilities/ are covered by the 135 <name/GNU General Public License</name> (<name/GPL/), version 2. 136 For details see the file <code/COPYING/. 137 </p> 138 <p> 139 The <name/Goldware Library/ is licensed under the <name>GNU Library 140 General Public License</name> (<name/LGPL/), version 2. For the full 141 text of the license, see the file <code/COPYING.LIB/. If necessary to 142 comply with <name/GPL/, <name/the Goldware Library/ is also licensed 143 under <name/GPL/, version 2. 144 </p> 145 <p> 146 Additionally, permission is hereby specifically given to link 147 <name/GoldED+/, the <name/Goldware Utilities/ and the <name>Goldware 148 Library</name> with any software or software library that meets the 149 <name/Open Source Definition/, as given on 150 <xref type='URL'>http://www.opensource.org</xref>. This includes 151 <name/GPL/, <name/LGPL/, <name/BSD/, <name/X Consortium/, 152 <name/Artistic/, <name/MozPL/, <name/QPL/ and most derivatives of 153 <name/MozPL/. 154 </p> 155 <p> 156 The additional permission to link with <name>non-GPL/LGPL</name> software 157 may be slightly controversial. The intent is to allow developers a 158 greater freedom to create specialized versions of GoldED. Examples could 159 be a <abbr/GUI/ <name/KGoldED/ linked with <name/QT/, a <name/MozGoldED/ 160 mail/news component for <name/Mozilla/ using <name/NGLayout/ for 161 displaying <abbr/HTML/, a <name/GoldED+/ with an embedded <name/Perl/ 162 scripting engine or whatever. However, we cannot allow the core 163 <name/GoldED+/ or <name/Goldware Library/ to be dependent on these 164 specialized versions, so developers should take care to make their 165 specialized modifications modular and <q/stubifiable/ if necessary. 166 </p> 167 <p> 168 Parts of the <name/Goldware Library/ is derived from the source of the 169 old shareware <name/CXL/ 5.2 library by <name/Mike Smedley/, from which 170 <name/Odinn Sorensen/ bought a source license many years ago. 171 <name/Odinn/ has made very extensive modifications (for example, the 172 original was <name/DOS/ only), but much code is essentially unchanged 173 (<code/gwin*.cpp/). <name/CXL/ was taken over from <name/Mike Smedley/ 174 by <name/Innovative Data Concepts/ (<name/IDC/), which renamed it 175 <name/TCXL/ and continued development along somewhat different lines, 176 which <name/Odinn/ did not agree with (or at least not easily port 177 <name/GoldED/ to). However, it seems that <name/TCXL/ never really became 178 successful. At least <name/Odinn/ could not find anything new about 179 <name/TCXL/ and <name/Innovative Data Concepts/ on the <name/Internet/ 180 (as of november 15, 1998). <name/Odinn/ could not even find 181 <name/IDC/'s website, so in this day and age where any succesful business 182 has a website, <name/Odinn/ suspects that they no longer exist. 183 <name/Odinn/ even tried to find <name/Mike Smedley/, but apparently he 184 has vanished off the face of the earth, or has lost interest in 185 programming entirely. <name/Odinn/ found some postings (on 186 <name/DejaNews/) on a sports newsgroup by a <name/Mike Smedley/, but 187 he doubts that it's the same guy. 188 </p> 189 <p> 190 So, even though parts of the <name/Goldware Library/ technically are 191 still copyrighted by <name/Mike Smedley/, <name/Odinn/ see so serious 192 problems in using them. If anyone should happen to know <name>Mike 193 Smedley</name> and how to contact him, <name/Odinn Sorensen/ would very 194 much appreciate to get the information, so we can clear up this issue. 195 </p> 196 <p> 197 <name/Squish/ and <name/Maximus/ are trademarks of <name>Lanius 198 Corporation</name>. 199 </p> 200 <p> 201 <name/JAM(mbp)/ - Copyright © 1993 <name/Joaquim Homrighausen/, 202 <name/Andrew Milner/, <name/Mats Birch/, <name/Mats Wallin/. 203 </p> 204 <p> 205 Products and company names listed are trademarks or trade names of their 206 respective companies. 207 </p> 208 </div1> 209<!-- --------------------------------------------------------------------- --> 210 <div1> 211 <head> 212 The Message Database Formats 213 </head> 214 <div2> 215 <head> 216 Opus, FTS-0001 217 </head> 218 <p> 219 These are two variants of the same type of msgbase. It works by using 220 one physical file per message (<code/1.msg/, <code/2.msg/ etc.), 221 collecting them in a directory for each area. Depending on the 222 clustersize on the harddisk, this can be a very wasteful and slow 223 way to store messages. With a clustersize of about 512 bytes, the 224 waste may be acceptable, but the access speed can be dramatically 225 slow if there are many <code/*.msg/ files, due to the file system. 226 Cache adjustments can improve it, but there are limits. 227 </p> 228 <p> 229 In echomail areas, this format has a special quirk: The first message 230 (<code/1.msg/) is normally used to store the so-called 231 <q/highwatermark/. The highwatermark tells the echomail processor 232 where it should start scanning for new messages entered by users. 233 By deleting (zapping) the highwatermark, you can make the echomail 234 processor re-scan the whole area again. This may cause messages to 235 be sent out as <q/dupes/, so this should be used sparingly and 236 carefully, if at all! The highwatermark can also be <q/heated/ - 237 which means that it is set to the last msg in the area. This 238 prevents the echomail processor from finding newly entered 239 unscanned msgs. Use with care. 240 </p> 241 <p> 242 The variants: The <name/Opus/ format originated in the <name/Opus/ 243 <abbr/BBS/ system. It put some <name/Fido/ undocumented (?) fields to 244 use as date/time stamps. The <name/FTS-0001/ (defined in FTS-0001, 245 revision 12 and later) format uses the undocumented fields to set the 246 zone/point information for the message. To the authors knowledge, the 247 <name/Opus/ variant is the dominant, and the <name/FTS-0001/ variant 248 is doomed to oblivion. If in doubt, use the <name/Opus/ format. 249 </p> 250 </div2> 251 <div2> 252 <head> 253 QuickBBS, RemoteAccess, and Hudson 254 </head> 255 <p> 256 This msgbase format was invented by <name/Adam Hudson/, and was first 257 used in his <name/QuickBBS/ package. Later several other 258 <abbr/BBS/'es were cloned from <name/QuickBBS/ (like 259 <name/RemoteAccess/ and <name/SuperBBS/). 260 </p> 261 <p> 262 The format limits the total size of <code/msgtxt.bbs/ to a maximum of 263 16MB, which translates to about 16000 msgs of <q/average/ length. 264 <name/GoldED+/ automatically warns you if the limit is close to being 265 reached, and advises you to pack the messagebase. 266 </p> 267 <p> 268 The first incarnations of <name/QuickBBS/ did not support <q/sharing/ 269 of the msgbase. This became more and more important in later years as 270 multitaskers and networks got cheaper. <name/RemoteAccess/ <abbr/BBS/ 271 was the first to implement a useful method, and later a better method 272 was evolved (known as <name/RA/ 1.01 or <name/RA/ 1.1x), which is now 273 the standard for all modern software that supports msgbase sharing. 274 <name/GoldED+/ fully supports the new standard of course. 275 </p> 276 <p> 277 The main virtue of this format is that it is very fast to access the 278 msgbase. 279 </p> 280 <p> 281 The main disadvantage is that it can be very sensitive to disk 282 problems, and it is a common horror story that people loose their 283 entire msgbase because the disk developed bad clusters or some 284 program went berserk and messed up the msgbase files. 285 </p> 286 </div2> 287 <div2> 288 <head> 289 Goldbase 290 </head> 291 <p> 292 This is an enhanced version of the <name/Hudson/ format, introduced 293 in <name/QuickBBS/ 2.80 by the <name/QuickBBS/ group. 294 </p> 295 <p> 296 The <name/Goldbase/ format removes the 16MB size limit and allows up 297 to 500 message areas instead of the 200 in <name/Hudson/. 298 </p> 299 </div2> 300 <div2> 301 <head> 302 Squish 303 </head> 304 <p> 305 The <name/Squish/ format was invented by <name/Maximus/ <abbr/BBS/ 306 author <name/Scott Dudley/ in 1991, and was first used in 307 <name/Maximus CBCS/ v2.00. 308 </p> 309 <p> 310 The use of a database for each area - instead of one file per msg, 311 or all msgs in one big database - makes this format fast, very 312 safe and resistant to disk problems. Even if something messed up a 313 <name/Squish/ area, it can almost always be fixed and recovered, 314 using the <name/SQFIX/ or <name/SQREIDX/ utilities that come with the 315 <name/Squish/ echomail processor. 316 </p> 317 <p> 318 A special feature of <name/Squish/ areas is that they can be 319 self-maintaining. You can setup a <name/Squish/ area so that it may 320 only contain a maximum of so-and-so many msgs, and then it will 321 automatically re-use the space used by old msgs when the limit is 322 reached, and so it will practically stop growing. It will still need 323 packing, but not nearly as often as a <name/Hudson/ msgbase has to. 324 </p> 325 </div2> 326 <div2> 327 <head> 328 Ezycom 329 </head> 330 <p> 331 <name/Ezycom/ format is supported by <name/GoldED+/. Status is not 332 known. 333 </p> 334 </div2> 335 <div2> 336 <head> 337 JAM 338 </head> 339 <p> 340 <name/JAM/ format as defined in the <name/JAM(mbp)/ revision 001. 341 Also <name/CrashMail/, <name/CrashEcho/, and <name/SMAPI/ (<name/HPT/) 342 highwater marks are supported. 343 </p> 344 <p> 345 <name/GoldED+/ currently ignores revision number of header structure 346 and assumes that future revisions will remain backward compatible. 347 When creating new msgs, <name/GoldED+/ uses the revision 1 header 348 structure. 349 </p> 350 <p> 351 <name/GoldED+/ currently doesn't support passwords to access the 352 message base and/or indiviual messages. When creating a new 353 <name/JAM/ msgbase and/or new <name/JAM/ msgs, <name/GoldED+/ sets 354 the password to FFFFFFFFh. If you change an existing message which 355 has a password, the password is <hi/NOT/ preserved, but reset to 356 FFFFFFFFh. 357 </p> 358 <p> 359 The <name/JAM/ lastread file is designed such that is has to be 360 searched for a user ID/CRC, because one cannot assume that the 361 records are in a specific order. The <name/JAM/ <abbr/API/ searches 362 the userid field. However <name/GoldED+/ searches for the user CRC, 363 not the user ID. In any case, it seems that <name/RemoteAccess/ 2.x 364 sets both the user ID and CRC to the same value. 365 </p> 366 <p> 367 <name/GoldED+/ currently doesn't support the escaping described in 368 the <name/JAM/ specs. The specs state that the current revision of 369 <name/JAM/ does not support it either, so it seems to be not great 370 loss. 371 </p> 372 <p> 373 <name/GoldED+/ does not supports the following <name/JAM/ subfields: 374 <q/Force pickup/, and <q>Msg may not be displayed to user</q> (always 375 displayed). 376 </p> 377 <p> 378 <name/GoldED+/ optionally may use tricky method invented by 379 <name/Odinn/ and aprooved by the <name/JAM/ developers when deleting 380 messages. The configuration keyword 381 <ref target=JAMHARDDELETE><kw/JAMHARDDELETE/</ref> specifies which 382 method to use. 383 </p> 384 </div2> 385 <div2> 386 <head> 387 PCBoard 388 </head> 389 <p> 390 The supported <name/PCBoard/ messagebase corresponds to the v15.x of 391 <name/PCBoard/ <abbr/BBS/. 392 </p> 393 <p> 394 <name/GoldED+/ is aware of <name/PCBoard/ v15.x extended headers in 395 the message text. The <gi/TO/, <gi/TO2/, <gi/FROM/, <gi/FROM2/ and 396 <gi/SUBJECT/ extended headers are directly supported and 397 <q/swallowed/ when reading a message. Other extended headers are 398 currently treated like normal message text and is therefore not 399 hidden to the reader. 400 </p> 401 <p> 402 Passwords are not supported. 403 </p> 404 <p> 405 The <gi/Private/, <gi/Received/, <gi/Crash/, and <gi/Direct/ attributes 406 are supported. 407 </p> 408 <p> 409 <name/GoldED+/ reads the <code/pcboard.dat/ file to determine whether 410 to use E3h or 0Dh (<gi/CR/) as the line/paragraph termination 411 character when reading and writing message text. 412 </p> 413 <p> 414 The mail waiting flags are updated when you write to people that are 415 named in the userbase. 416 </p> 417 <p> 418 When changing a message, the new edition is saved as if it were a new 419 message, with a new message number, and then the old edition is 420 deleted. This behaviour is consistent with the way <name/PCBoard/ 421 itself works when changing a message. The old edition will still 422 exist with the <gi/DEL/ attribute. 423 </p> 424 </div2> 425 <div2> 426 <head> 427 AdeptXBBS 428 </head> 429 <p> 430 The implementation is based on the documentation in version 1.05, 431 experimentation and questions to the authors. Thanks go to 432 <name/Frank Jacobberger/ for the initial testing and prodding of the 433 authors to answer <name/Odinns/ questions. 434 </p> 435 <p> 436 The <name/AdeptXBBS/ format does not have a quick method of finding 437 deleted messages via the index file. This means that deleted messages 438 left in the messagebase marked with the <gi/DEL/ attribute. 439 </p> 440 <p> 441 Mixing of netmail and echomail or other types of mail in the same 442 area is not directly supported. If an area is setup as both netmail 443 and echomail, <name/GoldED+/ will treat it as netmail. If an area is 444 neither netmail nor echomail, <name/GoldED+/ wil treat it as a local 445 area. 446 </p> 447 <p> 448 <name/GoldED+/ detects <name/Usenet/ (newsgroup) and <name/Internet/ 449 e-mail areas in the <name/AdeptXBBS/ setup and uses them as such, but 450 it has not yet been tested if <name/GoldED+/ and <name/AdeptXBBS/ are 451 compatible in the way they store and process <name/Internet/ header 452 information. 453 </p> 454 <p> 455 The <name/AdeptXBBS/ personal mail feature (the index in the 456 <code/Personal_Mail/ directory) is supported for mails you write to 457 other users on the <abbr/BBS/. However, personal mail for you via 458 this feature or by other means is not yet supported. 459 </p> 460 <p> 461 The replylinking method used by <name/AdeptXBBS/ (whatever the method 462 is??!) is not yet supported. This means that links to other messages 463 are missing. 464 </p> 465 </div2> 466 <div2> 467 <head> 468 WildCat! 469 </head> 470 <p> 471 The <name/WildCat!/ 4.x format does not have a quick method of 472 finding deleted messages via the index file. This means that deleted 473 messages left in the messagebase marked with the <gi/DEL/ 474 attribute. 475 </p> 476 <p> 477 WildCat features which are not supported yet: 478 <list type=simple> 479 <item/The userbase./ 480 <item/The message unread chain./ 481 <item>The message from/to title.</item> 482 <item/The message network name./ 483 <item/The message internal and external attach./ 484 </list> 485 </p> 486 <p> 487 There is a keyword 488 <ref target=WILDCATUSERNO><kw/WILDCATUSERNO/</ref>, which works just 489 like the other <kw><msgbase>USERNO</kw> keywords. By default 490 <name/GoldED+/ will use the first record in the lastread file 491 (<code/*.lrd/), so if you are not the first person in the userbase, 492 or you are sharing the messagebase with others, you may have to 493 change this user number. The userbase is currently not supported 494 (i.e.: you can't set the number to -1 to let <name/GoldED+/ find the 495 correct user and lastread automatically). 496 </p> 497 <p> 498 <hi/Note/: The <name/WildCat!/ support is currently not very 499 well-tested, so use it with caution. Limited testing shown that 500 <name/GoldED+/ not damages the messagebases, but you should probably 501 test it on less important areas and/or make backups until it is 502 determined that it is safe. 503 </p> 504 </div2> 505 <div2> 506 <head> 507 Synchronet 508 </head> 509 <p> 510 <name/Synchronet/ message base as described in <name>Synchronet 511 Message Base Specification</name> version 1.21. <name/GoldED+/ 512 currently linked with <name/SMBLib/ taken from the <name/Synchronet/ 513 <abbr/BBS/ sources slightly adopted to the <name/GoldED+/ internal 514 definitions. 515 </p> 516 <p> 517 Just like <name/WildCat!/ format, <name/Synchronet/ format does not 518 have a quick method of finding deleted messages via the index file. 519 This means that deleted messages left in the messagebase marked with 520 the <gi/DEL/ attribute. 521 </p> 522 <p> 523 <hi/Note/: The <name/Synchronet/ support is currently not tested at 524 all. 525 </p> 526 </div2> 527 </div1> 528<!-- --------------------------------------------------------------------- --> 529 <div1> 530 <head> 531 Nodelist and Userlist Support 532 </head> 533 <p> 534 <name/GoldED+/ supports the <name/FrontDoor/, <name/Version 7(+)/ 535 nodelist indexes as well as a plain <code/fidouser.lst/. However, if you 536 run software that doesn't use any of these formats, you may want to use 537 <name/GoldED+/'s own nodelist index. 538 </p> 539 <p> 540 In order to enable nodelist/userlist lookup and browsing, <name/GoldED+/ 541 needs to use a set of special nodelist index files, created by the 542 <name/GoldNODE/ nodelist compiler. 543 </p> 544 <p> 545 <name/GoldED+/ normally uses and displays information from the nodelist 546 when browsing, but it doesn't really need the nodelist for anything. The 547 index files contains sufficient information for lookup and browsing of 548 names or addresses. This means that you can delete or pack away the 549 nodelists and/or userlists after compiling with <name/GoldNODE/, if you 550 want to save space and you don't need them for anything else. 551 </p> 552 </div1> 553 <div1> 554 <head> 555 Routing Diagram Drawing Tool 556 </head> 557 <p> 558 Routing diagram drawing tool intended to analyse files created by 559 pressing key defined for <!-- FIX ME!!! --> <kw>READmakepathreport</kw> 560 action. <name/RDDT/ builds routing tree and display it on the screen if 561 requested. 562 </p> 563 </div1> 564<!-- --------------------------------------------------------------------- --> 565 <div1 id=COMMANDLINE> 566 <head> 567 Commandline Reference 568 </head> 569 <div2> 570 <head> 571 Mail Reader Commandline Syntax 572 </head> 573 <p> 574 Invocation:<eg> 575golded [options] [keystacking]</eg> 576 </p> 577 <p> 578 Depending on used platform <name>GoldED+</name> could be called 579 <code>geddjg</code>, <code>gedcyg</code>, <code>gedemx</code>, or 580 <code>gedlnx</code>. Available options are (all options are case 581 insensitive): 582 <list type=gloss> 583 <label> 584 <code>-?</code> 585 </label> 586 <item> 587 Displays a help screen with all available commandline options. 588 </item> 589 <label> 590 <code>-c<configname></code> 591 </label> 592 <item> 593 Specifies another configuration file than the default. See also 594 <ref target=GOLDED><kw/GOLDED/</ref> environment variable. 595 </item> 596 <label> 597 <code>-d</code> 598 </label> 599 <item> 600 Disable old configuration keywords. For backward compatibility, 601 <name>GoldED+</name> still supports a number of old names for 602 some configuration keywords. It is recommended that you use 603 <code>-d</code> sometimes and rename the keywords that are 604 reported as unknown. 605 </item> 606 <label> 607 <code>-e<echoid></code> 608 </label> 609 <item> 610 If specified, <name>GoldED+</name> starts directly in the 611 specified echo, bypassing the arealist screen. See the 612 <ref target=AREASTART><kw>AREASTART</kw></ref> configuration 613 keyword for more info. 614 </item> 615 <label> 616 <code>-exportsoup</code> 617 </label> 618 <item> 619 Calls the <name>SOUP</name> packet export feature during the 620 startup phase. This is the same as starting it from the 621 areascan <code>SOUP Packet->Export</code> menu 622 item. The <name>SOUP</name> export happens immediately after the 623 regular startup area scanning (if that is enabled) and after 624 <name>SOUP</name> import. 625 </item> 626 <label> 627 <code>-f</code> 628 </label> 629 <item> 630 Force recompile of most configuration files, but not all. Does not 631 recompile the <code>*.chs</code> files. 632 </item> 633 <label> 634 <code>-ff</code> 635 </label> 636 <item> 637 Force complete recompile of all configuration files, regardless of 638 whether they are up-to-date or not. This is equivalent to deleting 639 all the <code>*.ge?</code> files. 640 </item> 641 <label> 642 <code>-h</code> 643 </label> 644 <item> 645 Same as option <code>-?</code>. 646 </item> 647 <label> 648 <code>-install[=path]</code> 649 </label> 650 <item> 651 Start the quick install procedure. You should give a path to your 652 other mail software if it cannot be found using environment 653 variables or in current directory. 654 </item> 655 <label> 656 <code>-importsoup</code> 657 </label> 658 <item> 659 Calls the <name>SOUP</name> packet import feature during the 660 startup phase. This is the same as starting it from the areascan 661 <code>SOUP Packet->Import</code> menu item. The 662 <name>SOUP</name> import happens immediately after the regular 663 startup area scanning (if that is enabled). 664 </item> 665 <label> 666 <code/-m/ 667 </label> 668 <item> 669 Mute. Disables all sounds in <name/GoldED+/. The same functionality 670 provided by the <ref target=BEEPNOISES><kw/BEEPNOISES/</ref> 671 keyword in the configuration file. 672 </item> 673 <label> 674 <code>-n</code> 675 </label> 676 <item> 677 No share. If used, this prevents <name>GoldED+</name> from using 678 <code>SHARE</code> compatible file-open calls, which are used by 679 default. Works only until the 680 <ref target=SHAREMODE><kw>SHAREMODE</kw></ref> keyword is used in 681 the configuration file. This keyword is normally not useful, but 682 may be used to debug your setup or something. 683 </item> 684 <label> 685 <code>-noscan</code> 686 </label> 687 <item> 688 Disable the automatic startup area scanning (if that is enabled). 689 This is useful for automated <abbr>SOUP</abbr> import/export in a 690 batch file. For example,<eg> 691golded -noscan -importsoup @x y</eg> 692 imports <name>SOUP</name> then exits. 693 </item> 694 <label> 695 <code>-p</code> 696 </label> 697 <item> 698 Since it seems that increasing the thread priority for the 699 <name/Win32/ version is a mixed blessing, the default is to 700 <hi/not/ increase the priority. From other side <name>OS/2</name> 701 version runned with reduced priority by default. This option 702 increases the priority (<name/Win32/ and <name>OS/2</name> only). 703 </item> 704 <label> 705 <code>-q</code> 706 </label> 707 <item> 708 Quiet. Turns off verbose config compile. On by default. This could 709 be used on the commandline to disable a <code>-v</code> option in 710 the <ref target=GEDCMD><kw/GEDCMD/</ref> environment variable. 711 </item> 712 <label> 713 <code>-s<sortspec></code> 714 </label> 715 <item> 716 Sort all areas according to <ident>sortspec</ident>. See 717 the <ref target=AREALISTSORT><kw/AREALISTSORT/</ref> config 718 keyword for details. 719 </item> 720 <label> 721 <code>-t<seconds></code> 722 </label> 723 <item> 724 Set the timeout value. A value of zero (0) means never timeout. 725 See the <ref target=TIMEOUT><kw/TIMEOUT/</ref> config keyword 726 for details. 727 </item> 728 <label> 729 <code>-v</code> 730 </label> 731 <item> 732 Turns on verbose config compile. When used, <name>GoldED+</name> 733 will display the full filename of each main config file it 734 compiles. It also displays the name of the detected multitasker, if 735 any. This can be useful for debugging your setup, and see if 736 <name>GoldED+</name> accesses the files (especially the 737 <ref target=AREAFILE><kw/AREAFILE/</ref>'s) it is supposed to. 738 </item> 739 <label> 740 <code>-vv</code> 741 </label> 742 <item> 743 Same as <code>-v</code>, but also displays all the active lines 744 while compiling. This could be used to find the exact spot if it 745 crashes or stops while compiling. 746 </item> 747 <label> 748 <code>-w</code> 749 </label> 750 <item> 751 If used, <name/GoldED+/ will create (and overwrite if existing) the 752 file <code/goldarea.inc/, which will then contain all areas in the 753 <ref target=AREADEF><kw/AREADEF/</ref> form, sorted by your 754 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref> specification. 755 This is very useful for converting your 756 <ref target=AREAFILE><kw/AREAFILE/</ref>'s to a form you can edit 757 with your favorite text editor and use in <name/GoldED+/. It is 758 also useful if you have used the new 759 <ref target=AREADESC><kw/AREADESC/</ref> keyword or the 760 <ref target=AREAFILE><kw/AREAFILE/</ref> 761 <ref target=ECHOLIST><gi/EchoList/</ref> reader. The 762 <code>goldarea.inc</code> file (created in the 763 <ref target=GOLDPATH><kw/GOLDPATH/</ref>) can be used by adding<eg> 764INCLUDE goldarea.inc</eg> 765 to your configuration files. When creating the file, <name/GoldED+/ 766 will use <q/./ if an aka is the same as the main aka, and leave out 767 the optional origin if it's the same as the first 768 <ref target=ORIGIN><kw/ORIGIN/</ref> in your configuration files. 769 This makes it easier to share the same <code/goldarea.inc/ between 770 different setups. 771 </item> 772 <label> 773 <code>-x</code> 774 </label> 775 <item> 776 Reserved for debugging purposes. 777 </item> 778 <label> 779 <code>-y</code> 780 </label> 781 <item> 782 Reserved for debugging purposes. 783 </item> 784 <label> 785 <code>-z</code> 786 </label> 787 <item> 788 Reserved for debugging purposes. 789 </item> 790 </list> 791 </p> 792 <p> 793 Any non-option characters on the commandline are stuffed into the 794 keyboard buffer. See the chapter on keyboard definition and the 795 <ref target=KEYBSTACK><kw>KEYBSTACK</kw></ref> keyword for more info. 796 </p> 797 <p> 798 For example,<eg> 799golded @S A</eg> 800 makes <name>GoldED+</name> go to the area scanning menu <Alt-S>, 801 and select scanning of <A> all areas. 802 </p> 803 <p> 804 See the <ptr target=MACROSANDKEYSTACKING> chapter for more info. Note, 805 that only those combinations described in the 806 <ref target=KEYBSTACK><kw>KEYBSTACK</kw></ref> chapter are allowed 807 here. 808 </p> 809 </div2> 810 <div2> 811 <head> 812 <name/GoldED+/ Batchfile Errorlevels 813 </head> 814 <p> 815 For operation in batch files, <name>GoldED+</name> has a set of 816 errorlevel values: 817 <table rows=5 cols=2> 818 <row> 819 <cell> 820 032 or higher 821 </cell> 822 <cell> 823 Error exit (check the logfile for details). 824 </cell> 825 </row> 826 <row> 827 <cell> 828 004 829 </cell> 830 <cell> 831 Echomail entered. 832 </cell> 833 </row> 834 <row> 835 <cell> 836 002 837 </cell> 838 <cell> 839 Netmail entered. 840 </cell> 841 </row> 842 <row> 843 <cell> 844 001 845 </cell> 846 <cell> 847 Local mail entered. 848 </cell> 849 </row> 850 <row> 851 <cell> 852 000 853 </cell> 854 <cell> 855 No errors. No mail entered. 856 </cell> 857 </row> 858 </table> 859 </p> 860 <p> 861 Add values together to find the combined error levels. For example, error 862 level 6 is returned if netmail and echomail (2+4) was entered. 863 </p> 864 <p> 865 Example of <code>rungold.bat</code> file:<eg> 866golded.exe 867if errorlevel 007 goto e_n_l 868if errorlevel 006 goto e_n__ 869if errorlevel 005 goto e___l 870if errorlevel 004 goto e____ 871if errorlevel 003 goto __n_l 872if errorlevel 002 goto __n__ 873if errorlevel 001 goto ____l 874if errorlevel 000 goto nomail 875:error 876 echo GoldED+ error exit! 877 goto end 878:e_n_l 879 echo **** New echo, net and local mail entered. 880 goto end 881:e_n__ 882 echo **** New echo and netmail entered. 883 goto end 884:e___l 885 echo **** New echo and local mail entered. 886 goto end 887:e____ 888 echo **** New echomail entered. 889 goto end 890:__n_l 891 echo **** New net and local mail entered. 892 goto end 893:__n__ 894 echo **** New netmail entered. 895 goto end 896:____l 897 echo **** New local mail entered. 898 goto end 899:nomail 900 echo **** No new mail entered. 901:end 902 echo. 903 echo Thank you for using GoldED+! :-)</eg> 904 </p> 905 </div2> 906 <div2> 907 <head> 908 Nodelist Compiler Commandline Syntax 909 </head> 910 <p> 911 Invocation:<eg> 912goldnode [options] [configfile]</eg> 913 </p> 914 <p> 915 Depending on used platform <name>GoldNODE</name> could be called 916 <code>gndjg</code>, <code>gncyg</code>, <code>gnemx</code>, or 917 <code>gnlnx</code>. Available options: 918 <list type=gloss> 919 <label> 920 <code>-c</code> 921 </label> 922 <item> 923 Conditional compile. 924 </item> 925 <label> 926 <code>-d</code> 927 </label> 928 <item> 929 Remove duplicate nodes from index. 930 </item> 931 <label> 932 <code>-f</code> 933 </label> 934 <item> 935 Forced compile. 936 </item> 937 <label> 938 <code>-q</code> 939 </label> 940 <item> 941 Quite compiled. No screen output improves speed. 942 </item> 943 <label> 944 <code>-s<size></code> 945 </label> 946 <item> 947 Set the max size of names. Normally not used. 948 </item> 949 <label> 950 <code>-u<file></code> 951 </label> 952 <item> 953 Create sorted <code/fidouser.lst/ userlist file. 954 </item> 955 </list> 956 </p> 957 <p> 958 The <ident/configfile/ is the path and filename of the configuration 959 file to read. If no filename is given and it could not be found by 960 using environment variables then current path is used. 961 See also <ref target=GOLDNODE><kw/GOLDNODE/</ref> and 962 <ref target=GOLDED><kw/GOLDED/</ref> environment variables. 963 </p> 964 <p> 965 The nodelist index files are named <code/goldnode.gx?/ are are 966 placed in the path pointed to by the 967 <ref target=NODEPATH><kw/NODEPATH/</ref> keyword. 968 </p> 969 <p> 970 The <name>V7+</name> index is automatically used if your 971 <ref target=NODEPATHV7><kw/NODEPATHV7/</ref> is set correctly. If 972 <name/GoldED+/ shows<eg> 973xxxx / nodex.dtp</eg> 974 at the bottom of the browser window, the displayed information is taken 975 from the raw nodelist entry, taken from the <name>V7+</name> index. 976 </p> 977 <p> 978 <name>GoldNODE</name> can read the german <name>POINTS24</name>-format 979 directly! 980 </p> 981 <p> 982 <hi/NOTE/: If you use the 983 <ref target=EXCLUDENODES><kw/EXCLUDENODES/</ref> and 984 <ref target=INCLUDENODES><kw/INCLUDENODES/</ref> keywords, please note 985 that the <ident>addressmask<ident> does <hi>not</hi> accept <q/ALL/ 986 or <q/WORLD/, etc. You must use wildcard <q/*/ instead. 987 </p> 988 </div2> 989 <div2> 990 <head> 991 Routing Diagram Drawing Tool Commandline Syntax 992 </head> 993 <p> 994 Invocation:<eg> 995rddt <routefile> [options] [address or name]</eg> 996 </p> 997 <p> 998 Depending on used platform <name>RDDT</name> could be called 999 <code>rddtdjg</code>, <code>rddtcyg</code>, <code>rddtemx</code>, or 1000 <code>rddtlnx</code>. Available options: 1001 <list type=gloss> 1002 <label> 1003 <code>-d</code> 1004 </label> 1005 <item> 1006 Reserved for debugging purposes. 1007 </item> 1008 <label> 1009 <code>-i<n></code> 1010 </label> 1011 <item> 1012 Sets indent to <ident>n</ident>. 1013 </item> 1014 <label> 1015 <code>-l<link address></code> 1016 </label> 1017 <item> 1018 This option used to specify yours link address. Requires option 1019 <code>-n</code>. 1020 </item> 1021 <label> 1022 <code>-n<address></code> 1023 </label> 1024 <item> 1025 Use this option to specify your address. 1026 </item> 1027 <label> 1028 <code>-p</code> 1029 </label> 1030 <item> 1031 Decode path. 1032 </item> 1033 </list> 1034 </p> 1035 <p> 1036 Example:<eg> 1037RDDT path.rpt -n2:5020/604.19 -l2:5020/604 2:5020/604.19 -p</eg> 1038 </p> 1039 </div2> 1040 </div1> 1041<!-- --------------------------------------------------------------------- --> 1042 <div1> 1043 <head> 1044 Environment Variables 1045 </head> 1046 <p> 1047 These are the <name>GoldED+</name> specific environment variables: 1048 <list type=gloss> 1049 <label id=GOLDED> 1050 <kw/GOLDED/, <kw/GED/ 1051 </label> 1052 <item> 1053 Path to the <code/golded.cfg/ configuration file. Note, that 1054 <name/Win32/ version tries to open <code/gedw32.cfg/ first, and 1055 <name>OS/2</name> version tries to open <code/ged2.cfg/ first. 1056 You may specify path <hi/and/ filename of configuration file here. 1057 It is recommended to set this variable, but don't forget to change it 1058 if you move your <name>GoldED+</name> setup to a different directory! 1059 </item> 1060 <label> 1061 <kw/GED2/ 1062 </label> 1063 <item> 1064 Same as above, but for <name>OS/2</name> version only. 1065 </item> 1066 <label> 1067 <kw/GEDW32/ 1068 </label> 1069 <item> 1070 Same as above, but for <name/Win32/ version only. 1071 </item> 1072 <label id=GEDCMD> 1073 <kw/GEDCMD/ 1074 </label> 1075 <item> 1076 Specifies additional commandline options. Use this if you want to 1077 specify options, but need to run <name>GoldED</name> without them 1078 (for example when renaming <code>GOLDED.EXE</code> to 1079 <code>DBEDIT.EXE</code> in older versions of <name>D'Bridge</name>). 1080 You can override the environment options with commandline options. 1081 </item> 1082 <label id=GOLDNODE> 1083 <kw/GOLDNODE/ 1084 </label> 1085 <item> 1086 The path where <name/GoldNODE/ can find a configuration file to use. 1087 See also <ref target=GOLDED><kw/GOLDED/</ref> environment variable. 1088 </item> 1089 <label> 1090 <kw/MAXIMUS/, <kw/SQUISH/ 1091 </label> 1092 <item> 1093 If <ref target=SQUISHUSERPATH><kw/SQUISHUSERPATH/</ref> is not 1094 defined in the configuration file then value of these variables are 1095 used. 1096 </item> 1097 <label> 1098 <kw/FD/ 1099 </label> 1100 <item> 1101 Path where <code/names.fd/ could be found if not explicitly defined 1102 by the <ref target=NAMESFILE><kw/NAMESFILE/</ref> keyword. 1103 </item> 1104 <label> 1105 <kw/ESCDELAY/ 1106 </label> 1107 <item> 1108 This variable is only used by <name/Linux/ and <name/FreeBSD/ 1109 versions compiled with <name/ncurses/ support. See <name/ncurses/ 1110 reference for details. If not devined then default value <q/50/ is 1111 used. 1112 </item> 1113 </list> 1114 </p> 1115 <p> 1116 When using the <ref target=AREAFILE><kw/AREAFILE/</ref> feature to read 1117 external area configuration from the other programs, the individual 1118 <ref target=AREAFILE><kw/AREAFILE/</ref>'s may use specific environment 1119 variables to find the files. Please read the 1120 <ptr target=AREACONFIGURATION> chapter for specific details of each 1121 supported <ref target=AREAFILE><kw/AREAFILE/</ref>. 1122 </p> 1123 </div1> 1124<!-- --------------------------------------------------------------------- --> 1125 <div1> 1126 <head> 1127 Configuration Keyword Reference 1128 </head> 1129 <p> 1130 The following special symbols are used in the keyword parameter lists: 1131 <table rows=6 cols=2> 1132 <row> 1133 <cell> 1134 <ident>[]</ident> 1135 </cell> 1136 <cell> 1137 Optional parameter. 1138 </cell> 1139 </row> 1140 <row> 1141 <cell> 1142 <ident><></ident> 1143 </cell> 1144 <cell> 1145 Required parameter, not optional. 1146 </cell> 1147 </row> 1148 <row> 1149 <cell> 1150 <q></q> 1151 </cell> 1152 <cell> 1153 Parameter must be inclosed in quotes. 1154 </cell> 1155 </row> 1156 <row> 1157 <cell> 1158 <ident>/</ident> 1159 </cell> 1160 <cell> 1161 Separates mutually exclusive values. 1162 </cell> 1163 </row> 1164 <row> 1165 <cell> 1166 <ident>,</ident> 1167 </cell> 1168 <cell> 1169 Separates possible values for the keyword. 1170 </cell> 1171 </row> 1172 </table> 1173 </p> 1174 <p> 1175 There's no mandatory keywords but the mail reader should have defined at 1176 least name, address and area; nodelist compiler should have address and 1177 either nodelist or userlist defined. 1178 </p> 1179 <p> 1180 Whenever path is expected you may use environment variables enclosed in 1181 percent signs, f.e. <code>%FIDO%/myfile.txt</code>. This also valid for 1182 input prompts where path is expected :-) 1183 </p> 1184 <div2 id=REM> 1185 <head> 1186 Remarks 1187 </head> 1188 <list type=gloss> 1189 <label> 1190 Synopsis: 1191 </label> 1192 <item> 1193 <kw/REM/ <ident/[text]/ 1194 </item> 1195 <label> 1196 Description: 1197 </label> 1198 <item> 1199 Signifies a remark (comment) line. 1200 </item> 1201 <label> 1202 Parameters: 1203 </label> 1204 <item> 1205 The <ident/text/ contains remark line. The line is ignored. 1206 </item> 1207 <label> 1208 Notes: 1209 </label> 1210 <item> 1211 Any non-alphabetic non-whitespace character at the beginning of a 1212 line makes the line a comment. By tradition, the semicolon is the 1213 standard comment character. The semicolon (and only that) can also 1214 be used to add a comment at the end of a configuration line. 1215 </item> 1216 <label> 1217 Processed by: 1218 </label> 1219 <item> 1220 Mail reader and nodelist compiler. 1221 </item> 1222 <label> 1223 Example: 1224 </label> 1225 <item><eg> 1226REM This is a comment 1227; This is a comment 1228% This is a comment 1229* This is a comment 1230// This is a comment 1231/* This is a comment */ 1232ADDRESS 2:236/77 ; Main address. 1233AKA 2:236/77.1 ; SysOp point.</eg> 1234 </item> 1235 </list> 1236 </div2> 1237 <div2 id=CONDITIONALS> 1238 <head> 1239 Conditionals 1240 </head> 1241 <list type=gloss> 1242 <label> 1243 Synopsis: 1244 </label> 1245 <item> 1246 <kw/IF/ <ident/<condition>/<lb> 1247 <kw/ELIF/ <ident/<condition>/<lb> 1248 <kw/ELSEIF/ <ident/<condition>/<lb> 1249 <kw/ELSE/<lb> 1250 <kw/ENDIF/ 1251 </item> 1252 <label> 1253 Description: 1254 </label> 1255 <item> 1256 These control keywords can be used to setup sections of configuration 1257 which enable different sets of keywords depending on which version 1258 that is used. 1259 </item> 1260 <label> 1261 Parameters: 1262 </label> 1263 <item> 1264 The following conditions can be used: 1265 <table rows=8 cols=2> 1266 <row> 1267 <cell> 1268 <ident/DOS/, <ident/386/, <ident/DPMI32/ 1269 </cell> 1270 <cell> 1271 true, if <name>DPMI32</name> version is used 1272 </cell> 1273 </row> 1274 <row> 1275 <cell> 1276 <ident>OS/2</ident>, <ident/OS2/ 1277 </cell> 1278 <cell> 1279 true, if <name>OS/2</name> version is used 1280 </cell> 1281 </row> 1282 <row> 1283 <cell> 1284 <ident/WIN32/, <ident/W32/, <ident/NT/ 1285 </cell> 1286 <cell> 1287 true, if <name>Win32</name> version is used 1288 </cell> 1289 </row> 1290 <row> 1291 <cell> 1292 <ident>Linux, UNIX</ident> 1293 </cell> 1294 <cell> 1295 true, if <name/Linux/ or <name/FreeBSD/ version is used 1296 </cell> 1297 </row> 1298 <row> 1299 <cell> 1300 <ident>Firebird</ident> 1301 </cell> 1302 <cell> 1303 true, if <name/GoldED/ 3.xx or <name/GoldED+/ is used 1304 </cell> 1305 </row> 1306 <row> 1307 <cell> 1308 <ident>ASA</ident> 1309 </cell> 1310 <cell> 1311 true, if <name/GoldED-asa/ or <name/GoldED+/ is used 1312 </cell> 1313 </row> 1314 <row> 1315 <cell> 1316 <ident>Yes</ident>, <ident>True</ident>, <ident>On</ident> 1317 </cell> 1318 <cell> 1319 always true 1320 </cell> 1321 </row> 1322 </table> 1323 </item> 1324 <label> 1325 Processed by: 1326 </label> 1327 <item> 1328 Mail reader and nodelist compiler. 1329 </item> 1330 <label> 1331 Example: 1332 </label> 1333 <item><eg> 1334IF OS2 1335 EDITOR c:\qedit\os2\q.exe @file -n@line 1336 EDITSPELLCHECK c:\os2\cmd.exe /c c:\ss\ss.exe @file 1337ELIF DOS 1338 EDITOR c:\qedit\dos\q.exe @file -n@line 1339 EDITSPELLCHECK c:\ss\ss.exe @file 1340ELIF WIN32 1341 EDITOR c:\progra~1\far\far.exe -i -e@line @file 1342 EDITSPELLCHECK c:\fido\goldkorr\goldkorr.exe @file /A /Q 1343ENDIF</eg> 1344 </item> 1345 </list> 1346 </div2> 1347 <div2 id=IGNORE> 1348 <head> 1349 IGNORE 1350 </head> 1351 <list type=gloss> 1352 <label> 1353 Synopsis: 1354 </label> 1355 <item> 1356 <kw/IGNORE/ 1357 </item> 1358 <label> 1359 Description: 1360 </label> 1361 <item> 1362 This tells the configuration file reader to ignore all subsequent 1363 lines until another <kw/IGNORE/ or <kw/IF/ keyword is encountered. 1364 Useful for testing and quickly switching portions of configuration. 1365 However it is probably more useful to use the 1366 <ref target=CONDITIONALS/conditionals/ control keywords. 1367 </item> 1368 <label> 1369 Bugs: 1370 </label> 1371 <item> 1372 This keyword may cause unpredicable results if used within 1373 <ref target=CONDITIONALS/conditionals/ control keywords. 1374 </item> 1375 <label> 1376 Processed by: 1377 </label> 1378 <item> 1379 Mail reader. 1380 </item> 1381 <label> 1382 See also: 1383 </label> 1384 <item> 1385 <ref target=CONDITIONALS/Conditionals/ 1386 </item> 1387 </list> 1388 </div2> 1389 <div2 id=ADDRESS> 1390 <head> 1391 ADDRESS 1392 </head> 1393 <list type=gloss> 1394 <label> 1395 Synopsis: 1396 </label> 1397 <item> 1398 <kw/ADDRESS/ 1399 <ident><zone:net/node[.point][@domain] 1400 [,pointnet]></ident> 1401 </item> 1402 <label> 1403 Description: 1404 </label> 1405 <item> 1406 Your network address, <name/FidoNet/-style. More than one address can 1407 be specified if you are member of more than one network. The keywords 1408 <kw/ADDRESS/ and <ref target=AKA><kw/AKA/</ref> can be used 1409 interchangeably. 1410 </item> 1411 <label> 1412 Parameters: 1413 </label> 1414 <item> 1415 If a <ident/pointnet/ is specified with a point address, 1416 <name/GoldED+/ will use the so-called <term/3D/ addressing method in 1417 netmail msgs, otherwise the <term/4D/ method is used. The <term/3D/ 1418 method works by putting the address 1419 <ident>zone:pointnet/point.0</ident> in the msg header, instead of 1420 the <term/4D/ format <ident>zone:net/node.point</ident>. Most modern 1421 mailers and mail processors now supports the <term/4D/ format, 1422 but if you are a point, you should always consult your boss about 1423 which format to use.<lb> 1424 The optional <ident/@domain/ part can be used to specify a 1425 <term/fifth/ dimension to the <term/4D/ address. It is normally not 1426 necessary to specify a domain. Domains are never shown in the header. 1427 </item> 1428 <label> 1429 Notes: 1430 </label> 1431 <item> 1432 This keyword can be used globally and in a 1433 <ref target=RANDOMSYSTEM>Random System</ref> group. 1434 </item> 1435 <label> 1436 Processed by: 1437 </label> 1438 <item> 1439 Mail reader and nodelist compiler. 1440 </item> 1441 <label> 1442 See also: 1443 </label> 1444 <item> 1445 <ref target=AKA><kw/AKA/</ref>, 1446 <ref target=NETNAME><kw/NETNAME/</ref> 1447 </item> 1448 <label> 1449 Example: 1450 </label> 1451 <item><eg> 1452ADDRESS 2:236/77 ; Node address 1453ADDRESS 2:236/77.1 ; Point address (4D) 1454ADDRESS 2:236/77.1, 16077 ; Point address (3D) 1455ADDRESS 2:236/77@fidonet ; Node address with domain</eg> 1456 </item> 1457 </list> 1458 </div2> 1459 <div2> 1460 <head> 1461 ADDRESSBOOKADD 1462 </head> 1463 <list type=gloss> 1464 <label> 1465 Synopsis: 1466 </label> 1467 <item> 1468 <kw/ADDRESSBOOKADD/ <ident><YES/NO/ALWAYS></ident> 1469 </item> 1470 <label> 1471 Description: 1472 </label> 1473 <item> 1474 This keyword controls whether <name/GoldED+/ will add unknown 1475 addressees into the addressbook when writing new or quoted mails. 1476 </item> 1477 <label> 1478 Parameters: 1479 </label> 1480 <item> 1481 Setting this keyword to <ident/ALWAYS/ means that <name/GoldED+/ will 1482 always add unknown addressees to the addressbook when writing new or 1483 quoted mails automatically. If you set the value to <ident/YES/, 1484 <name/GoldED+/ will add them only if it's a netmail/email. Setting to 1485 <ident/NO/ disables this feature entirely. 1486 </item> 1487 <label> 1488 Default: 1489 </label> 1490 <item> 1491 <ident/YES/ 1492 </item> 1493 <label> 1494 Notes: 1495 </label> 1496 <item> 1497 <name/GoldED+/ won't add unknown users if their name match one of the 1498 following criterias: 1499 <list type=simple> 1500 <item> 1501 It's a <ref target=ROBOTNAME><kw/ROBOTNAME/</ref> 1502 </item> 1503 <item> 1504 It's a <ref target=USERNAME><kw/USERNAME/</ref> 1505 </item> 1506 <item> 1507 It's the <ref target=WHOTO><kw/WHOTO/</ref> 1508 </item> 1509 <item> 1510 It's the mailinglist's sender address 1511 </item> 1512 <item> 1513 It's an UUCP 1514 </item> 1515 <item> 1516 It's already an email address 1517 </item> 1518 <item> 1519 Address/aka is unknown 1520 </item> 1521 <item> 1522 It's an <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref> 1523 </item> 1524 </list> 1525 </item> 1526 <label> 1527 Processed by: 1528 </label> 1529 <item> 1530 Mail reader. 1531 </item> 1532 <label> 1533 See also: 1534 </label> 1535 <item> 1536 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 1537 <ref target=INTERNETGATE><kw/INTERNETGATE/</ref>, 1538 <ref target=MAILINGLIST><kw/MAILINGLIST/</ref>, 1539 <ref target=ROBOTNAME><kw/ROBOTNAME/</ref>, 1540 <ref target=USERNAME><kw/USERNAME/</ref>, 1541 <ref target=WHOTO><kw/WHOTO/</ref> 1542 </item> 1543 </list> 1544 </div2> 1545 <div2> 1546 <head> 1547 ADDRESSLOOKUPFIRST 1548 </head> 1549 <list type=gloss> 1550 <label> 1551 Synopsis: 1552 </label> 1553 <item> 1554 <kw/ADDRESSLOOKUPFIRST/ <ident><MSGID/ORIGIN></ident> 1555 </item> 1556 <label> 1557 Description: 1558 </label> 1559 <item> 1560 This keyword defines the first source to lookup address. If valid 1561 address could not be found in the specifyed location then second 1562 source is used. 1563 </item> 1564 <label> 1565 Parameters: 1566 </label> 1567 <item> 1568 If defined to <ident/ORIGIN/ then address of sender taken from 1569 <gi/Origin/ line. If this keyword set to <ident/MSGID/ then 1570 <name/GoldED+/ looks for correct <abbr/FTN/ address in <gi/MSGID/ 1571 kludge first. 1572 </item> 1573 <label> 1574 Default: 1575 </label> 1576 <item> 1577 <ident/ORIGIN/ 1578 </item> 1579 <label> 1580 Processed by: 1581 </label> 1582 <item> 1583 Mail reader. 1584 </item> 1585 </list> 1586 </div2> 1587 <div2 id=ADDRESSMACRO> 1588 <head> 1589 ADDRESSMACRO 1590 </head> 1591 <list type=gloss> 1592 <label> 1593 Synopsis: 1594 </label> 1595 <item> 1596 <kw/ADDRESSMACRO/ <ident/<macro>, <name>, <address> 1597 [,<q>subject</q>] [,attribs]/ 1598 </item> 1599 <label> 1600 Description: 1601 </label> 1602 <item> 1603 Defines a short name for often used addresses. Typical uses are for 1604 <name/AreaFix//<name/AreaMgr/, your uplink, boss, points or others 1605 you write to often. To use a defined address macro, you just type it 1606 in the <gi/To:/ name field. 1607 </item> 1608 <label> 1609 Parameters: 1610 </label> 1611 <item> 1612 If (and <hi>only</hi> if) the subject is enclosed in quotes (<q// 1613 or ''), <name/GoldED+/ will look for message attributes after the 1614 <ident/subject/ field. See the <ptr target=MESSAGEATTRS> for the 1615 valid attributes. You cannot have quotes within quotes (not the same 1616 type anyway). The attribues are <hi/added/ to the ones already there, 1617 they do <hi/not/ replace them.<lb> 1618 A special format is supported for <abbr/UUCP/ or <name/Internet/ 1619 gateways. The special format is indicated with a <q/@/ as the first 1620 character in the <ident/name/ field. You may specify <name/Internet/ 1621 gate name here if it other then default specifyed with 1622 <ref target=INTERNETGATE><kw/INTERNETGATE/</ref> keyword, just put 1623 gate name right after the <q/@/ and terminate it with the slash 1624 (<q>/</q>). 1625 </item> 1626 <label> 1627 Notes: 1628 </label> 1629 <item> 1630 The address macros can also be specified in an external file, like 1631 the <code/names.fd/ file supported by the <name/FrontDoor/ 1632 mailer/editor and <name/Maximus/ <abbr/BBS/. See the keyword 1633 <ref target=NAMESFILE><kw/NAMESFILE/</ref> for details. However, you 1634 should not use the syntax with the attributes in the <code/names.fd/ 1635 file, because <name/FrontDoor/ and <name/Maximus/ do not know this 1636 syntax.<lb> 1637 When used in the <name/Internet/ area, <q/@/ as the first character 1638 in the <ident/name/ field may be omitted. 1639 </item> 1640 <label> 1641 Processed by: 1642 </label> 1643 <item> 1644 Mail reader. 1645 </item> 1646 <label> 1647 See also: 1648 </label> 1649 <item> 1650 <ref target=INTERNETGATE><kw/INTERNETGATE/</ref>, 1651 <ref target=NAMESFILE><kw/NAMESFILE/</ref> 1652 </item> 1653 <label> 1654 Examples: 1655 </label> 1656 <item><eg><![ CDATA [ 1657ADDRESSMACRO afup,AreaFix,2:236/512,"password -q -l",K/S 1658ADDRESSMACRO ffup,FileFix,2:236/512,password 1659ADDRESSMACRO odin,Odinn Sorensen,2:236/77,GoldED - What else? :-) 1660ADDRESSMACRO jfu,@fallesen@diku.dk,2:310/33 1661ADDRESSMACRO vp,@vasya@pupkin.ru (Vasya Pupkin),2:5020/128 1662ADDRESSMACRO dn,@INTERNET/david@csource.oz.au,2:241/999]]></eg> 1663 </item> 1664 </list> 1665 </div2> 1666 <div2 id=ADEPTXBBSPATH> 1667 <head> 1668 ADEPTXBBSPATH 1669 </head> 1670 <list type=gloss> 1671 <label> 1672 Synopsis: 1673 </label> 1674 <item> 1675 <kw/ADEPTXBBSPATH/ <ident/<path>/ 1676 </item> 1677 <label> 1678 Description: 1679 </label> 1680 <item> 1681 Specifyes the path where you keep your <name/AdeptXBBS/. 1682 </item> 1683 <label> 1684 Parameters: 1685 </label> 1686 <item> 1687 The <ident/path/ where you keep your <name/AdeptXBBS/. 1688 </item> 1689 <label> 1690 Processed by: 1691 </label> 1692 <item> 1693 Mail reader. 1694 </item> 1695 <label> 1696 See also: 1697 </label> 1698 <item> 1699 <ptr target=AREACONFIGURATION> chapter, 1700 <ref target=ADEPTXBBSUSERNO><kw/ADEPTXBBSUSERNO/</ref> 1701 </item> 1702 </list> 1703 </div2> 1704 <div2 id=ADEPTXBBSUSERNO> 1705 <head> 1706 ADEPTXBBSUSERNO 1707 </head> 1708 <list type=gloss> 1709 <label> 1710 Synopsis: 1711 </label> 1712 <item> 1713 <kw/ADEPTXBBSUSERNO/ <ident/<userno>/ 1714 </item> 1715 <label> 1716 Description: 1717 </label> 1718 <item> 1719 Specifyes the record number in the userfile and lastreads. 1720 </item> 1721 <label> 1722 Parameters: 1723 </label> 1724 <item> 1725 If you are not the first user in the userfile, or are sharing the 1726 messagebase with other <name/GoldED+/ users, you must either set this 1727 keyword to -1, or use a different number for each user. Each user 1728 must be defined in the userbase. 1729 </item> 1730 <label> 1731 Default: 1732 </label> 1733 <item> 1734 By default <name/GoldED+/ will use the first record in the userfile 1735 and lastreads. 1736 </item> 1737 <label> 1738 Processed by: 1739 </label> 1740 <item> 1741 Mail reader. 1742 </item> 1743 <label> 1744 See also: 1745 </label> 1746 <item> 1747 <ptr target=AREACONFIGURATION> chapter, 1748 <ref target=ADEPTXBBSPATH><kw/ADEPTXBBSPATH/</ref>, 1749 <ref target=EZYCOMUSERNO><kw/EZYCOMUSERNO/</ref>, 1750 <ref target=FIDOUSERNO><kw/FIDOUSERNO/</ref>, 1751 <ref target=GOLDBASEUSERNO><kw/GOLDBASEUSERNO/</ref>, 1752 <ref target=HUDSONUSERNO><kw/HUDSONUSERNO/</ref>, 1753 <ref target=PCBOARDUSERNO><kw/PCBOARDUSERNO/</ref>, 1754 <ref target=SQUISHUSERNO><kw/SQUISHUSERNO/</ref>, 1755 <ref target=WILDCATUSERNO><kw/WILDCATUSERNO/</ref> 1756 </item> 1757 </list> 1758 </div2> 1759 <div2 id=AKA> 1760 <head> 1761 AKA 1762 </head> 1763 <list type=gloss> 1764 <label> 1765 Synopsis: 1766 </label> 1767 <item> 1768 <kw/AKA/ 1769 <ident><zone:net/node[.point][@domain] 1770 [,pointnet]></ident> 1771 </item> 1772 <label> 1773 Description: 1774 </label> 1775 <item> 1776 Your network address, <name/FidoNet/-style. More than one address can 1777 be specified if you are member of more than one network. The keywords 1778 <ref target=ADDRESS><kw/ADDRESS/</ref> and <kw/AKA/ can be used 1779 interchangeably. 1780 </item> 1781 <label> 1782 Parameters: 1783 </label> 1784 <item> 1785 If a <ident/pointnet/ is specified with a point address, 1786 <name/GoldED+/ will use the so-called <term/3D/ addressing method in 1787 netmail msgs, otherwise the <term/4D/ method is used. The <term/3D/ 1788 method works by putting the address 1789 <ident>zone:pointnet/point.0</ident> in the msg header, instead of 1790 the <term/4D/ format <ident>zone:net/node.point</ident>. Most modern 1791 mailers and mail processors now supports the <term/4D/ format, 1792 but if you are a point, you should always consult your boss about 1793 which format to use.<lb> 1794 The optional <ident/@domain/ part can be used to specify a 1795 <term/fifth/ dimension to the <term/4D/ address. It is normally not 1796 necessary to specify a domain. Domains are never shown in the header. 1797 </item> 1798 <label> 1799 Notes: 1800 </label> 1801 <item> 1802 This keyword can be used globally and in a 1803 <ref target=RANDOMSYSTEM>Random System</ref> group. 1804 </item> 1805 <label> 1806 Processed by: 1807 </label> 1808 <item> 1809 Mail reader and nodelist compiler. 1810 </item> 1811 <label> 1812 See also: 1813 </label> 1814 <item> 1815 <ref target=ADDRESS><kw/ADDRESS/</ref>, 1816 <ref target=NETNAME><kw/NETNAME/</ref> 1817 </item> 1818 </list> 1819 </div2> 1820 <div2 id=AKAMATCH> 1821 <head> 1822 AKAMATCH 1823 </head> 1824 <list type=gloss> 1825 <label> 1826 Synopsis: 1827 </label> 1828 <item> 1829 <kw/AKAMATCH/ <ident/<pattern> <aka>/ 1830 </item> 1831 <label> 1832 Description: 1833 </label> 1834 <item> 1835 This is an enhancement of the existing aka matching logic, which in 1836 some circumstances fails to find the correct aka. 1837 </item> 1838 <label> 1839 Parameters: 1840 </label> 1841 <item> 1842 If the destination address matches <ident/pattern/ then 1843 <name/GoldED+/ will use <ident/aka/ specifyed instead of default 1844 best-match rule. All patterns are checked in the order they follow 1845 in the configuration files.<lb> 1846 Wildcards are not strictly necessary in the match <ident/pattern/, 1847 you could write f.e. <q>zone:*/*.*</q> or <q>zone:</q>, etc. 1848 </item> 1849 <label> 1850 Notes: 1851 </label> 1852 <item> 1853 When an address does not match any <kw>AKAMATCH</kw> definition, the 1854 normal aka matching logic takes over. 1855 </item> 1856 <label> 1857 Processed by: 1858 </label> 1859 <item> 1860 Mail reader. 1861 </item> 1862 <label> 1863 See also: 1864 </label> 1865 <item> 1866 <ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>, 1867 <ref target=AKAMATCHING><kw/AKAMATCHING/</ref>, 1868 <ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>, 1869 <ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref> 1870 </item> 1871 <label> 1872 Example: 1873 </label> 1874 <item><eg> 1875ADDRESS 2:236/77 ; this is primary address 1876AKA 22:33/44 ; this address valid for zones 21:, 22:, and 23 1877AKAMATCH 21:*/*.* 22:33/44 1878AKAMATCH 23: 22:33/44</eg> 1879 </item> 1880 </list> 1881 </div2> 1882 <div2 id=AKAMATCHECHO> 1883 <head> 1884 AKAMATCHECHO 1885 </head> 1886 <list type=gloss> 1887 <label> 1888 Synopsis: 1889 </label> 1890 <item> 1891 <kw/AKAMATCHECHO/ <ident><YES/NO></ident> 1892 </item> 1893 <label> 1894 Description: 1895 </label> 1896 <item> 1897 This keyword controls whether <name/GoldED+/ should do akamatching 1898 in echomail areas. 1899 </item> 1900 <label> 1901 Parameters: 1902 </label> 1903 <item> 1904 If set to <ident/YES/, <name/GoldED+/ will attempt to match one of 1905 your akas to the address of the person you are replying to in 1906 echomail areas. 1907 </item> 1908 <label> 1909 Default: 1910 </label> 1911 <item> 1912 <ident/NO/ 1913 </item> 1914 <label> 1915 Processed by: 1916 </label> 1917 <item> 1918 Mail reader. 1919 </item> 1920 <label> 1921 Notes: 1922 </label> 1923 <item> 1924 Normally it is not desirable to enable aka matching in echomail, 1925 because some echoes may be restricted to members of one particular 1926 network, and an accidental wrong aka matching may attract unwanted 1927 attention from the moderator or the compulsive flamers :-) 1928 </item> 1929 <label> 1930 See also: 1931 </label> 1932 <item> 1933 <ref target=AKAMATCH><kw/AKAMATCH/</ref>, 1934 <ref target=AKAMATCHING><kw/AKAMATCHING/</ref>, 1935 <ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>, 1936 <ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref> 1937 </item> 1938 </list> 1939 </div2> 1940 <div2 id=AKAMATCHING> 1941 <head> 1942 AKAMATCHING 1943 </head> 1944 <list type=gloss> 1945 <label> 1946 Synopsis: 1947 </label> 1948 <item> 1949 <kw/AKAMATCHING/ <ident><YES/NO></ident> 1950 </item> 1951 <label> 1952 Description: 1953 </label> 1954 <item> 1955 This keyword controls whether <name/GoldED+/ should do akamatching 1956 in areas within <ref target=RANDOMSYSTEM>Random System</ref> group it 1957 is defined. When used, it overrides any global 1958 <ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>, 1959 <ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>, or 1960 <ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref> you may have. 1961 </item> 1962 <label> 1963 Parameters: 1964 </label> 1965 <item> 1966 If set to <ident/YES/, <name/GoldED+/ will attempt to match one of 1967 your akas to the address of the person you are replying to. 1968 </item> 1969 <label> 1970 Default: 1971 </label> 1972 <item> 1973 <ident/NO/ 1974 </item> 1975 <label> 1976 Notes: 1977 </label> 1978 <item> 1979 This keyword is valid <hi/ONLY/ in a 1980 <ref target=RANDOMSYSTEM>Random System</ref> group. 1981 </item> 1982 <label> 1983 Processed by: 1984 </label> 1985 <item> 1986 Mail reader. 1987 </item> 1988 <label> 1989 See also: 1990 </label> 1991 <item> 1992 <ref target=AKAMATCH><kw/AKAMATCH/</ref>, 1993 <ref target=AKAMATCHING><kw/AKAMATCHING/</ref>, 1994 <ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>, 1995 <ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref> 1996 </item> 1997 </list> 1998 </div2> 1999 <div2 id=AKAMATCHLOCAL> 2000 <head> 2001 AKAMATCHLOCAL 2002 </head> 2003 <list type=gloss> 2004 <label> 2005 Synopsis: 2006 </label> 2007 <item> 2008 <kw/AKAMATCHLOCAL/ <ident><YES/NO></ident> 2009 </item> 2010 <label> 2011 Description: 2012 </label> 2013 <item> 2014 This keyword controls whether <name/GoldED+/ should do akamatching 2015 in local areas. 2016 </item> 2017 <label> 2018 Parameters: 2019 </label> 2020 <item> 2021 If set to <ident/YES/, <name/GoldED+/ will attempt to match one of 2022 your akas to the address of the person you are replying to in local 2023 areas. 2024 </item> 2025 <label> 2026 Default: 2027 </label> 2028 <item> 2029 <ident/NO/ 2030 </item> 2031 <label> 2032 Notes: 2033 </label> 2034 <item> 2035 It doesn't really make sense to do aka matching in local areas. The 2036 keyword is just there for completeness. 2037 </item> 2038 <label> 2039 Processed by: 2040 </label> 2041 <item> 2042 Mail reader. 2043 </item> 2044 <label> 2045 See also: 2046 </label> 2047 <item> 2048 <ref target=AKAMATCH><kw/AKAMATCH/</ref>, 2049 <ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>, 2050 <ref target=AKAMATCHING><kw/AKAMATCHING/</ref>, 2051 <ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref> 2052 </item> 2053 </list> 2054 </div2> 2055 <div2 id=AKAMATCHNET> 2056 <head> 2057 AKAMATCHNET 2058 </head> 2059 <list type=gloss> 2060 <label> 2061 Synopsis: 2062 </label> 2063 <item> 2064 <kw/AKAMATCHNET/ <ident><YES/NO></ident> 2065 </item> 2066 <label> 2067 Description: 2068 </label> 2069 <item> 2070 This keyword controls whether <name/GoldED+/ should do akamatching 2071 in netmail areas. This is especially useful if you are a member in 2072 more than one network, and therefore have more than one address. 2073 </item> 2074 <label> 2075 Parameters: 2076 </label> 2077 <item> 2078 If set to <ident/YES/, <name/GoldED+/ will attempt to match one of 2079 your akas to the address of the person you are replying to in 2080 netmail areas. 2081 </item> 2082 <label> 2083 Default: 2084 </label> 2085 <item> 2086 <ident/YES/ 2087 </item> 2088 <label> 2089 Notes: 2090 </label> 2091 <item> 2092 Normally it is not desirable to enable aka matching in echomail, 2093 because some echoes may be restricted to members of one particular 2094 network, and an accidental wrong aka matching may attract unwanted 2095 attention from the moderator or the compulsive flamers :-) 2096 </item> 2097 <label> 2098 Processed by: 2099 </label> 2100 <item> 2101 Mail reader. 2102 </item> 2103 <label> 2104 See also: 2105 </label> 2106 <item> 2107 <ref target=AKAMATCH><kw/AKAMATCH/</ref>, 2108 <ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>, 2109 <ref target=AKAMATCHING><kw/AKAMATCHING/</ref>, 2110 <ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref> 2111 </item> 2112 </list> 2113 </div2> 2114 <div2> 2115 <head> 2116 APP 2117 </head> 2118 <list type=gloss> 2119 <label> 2120 Synopsis: 2121 </label> 2122 <item> 2123 <kw/APP/ <ident><programname> [text]</ident> 2124 </item> 2125 <label> 2126 Description: 2127 </label> 2128 <item> 2129 This keyword provides a way for other programs to place configuration 2130 data in <name/GoldED+/'s configuration file. 2131 </item> 2132 <label> 2133 Parameters: 2134 </label> 2135 <item> 2136 The <ident/programname/ parameter defines name of the software which 2137 wants to read its configuration from <name/GoldED+/ configuration 2138 file. <name/GoldED+/ itself will ignore <kw/APP/ lines just like 2139 <ref target=REM/remark/ lines. 2140 </item> 2141 <label> 2142 Processed by: 2143 </label> 2144 <item> 2145 Mail reader. 2146 </item> 2147 <label> 2148 See also: 2149 </label> 2150 <item> 2151 <ref target=REM/Remarks/ 2152 </item> 2153 <label> 2154 Example: 2155 </label> 2156 <item><eg> 2157APP OtherProg REGKEY xyaxajlsaduoiweqeq 2158APP OtherProg IRQ 5</eg> 2159 </item> 2160 </list> 2161 </div2> 2162 <div2 id=AREA> 2163 <head> 2164 AREA 2165 </head> 2166 <list type=gloss> 2167 <label> 2168 Synopsis: 2169 </label> 2170 <item> 2171 <kw/AREA/ <ident><echoid> <<![ CDATA ["desc"]]>> 2172 <msgbase>[type] <location> [akano] 2173 [attrs]</ident><lb> 2174 <kw/AREA/ <ident><-FILE> <type> [path/file] 2175 [switches]</ident> 2176 </item> 2177 <label> 2178 Description: 2179 </label> 2180 <item> 2181 This <strong/obsolete/ keyword defines a mail area or external 2182 area setup. 2183 </item> 2184 <label> 2185 Parameters: 2186 </label> 2187 <item> 2188 <table rows=7 cols=2> 2189 <row> 2190 <cell> 2191 <ident/echoid/ 2192 </cell> 2193 <cell> 2194 Mail area identifier. 2195 </cell> 2196 </row> 2197 <row> 2198 <cell> 2199 <ident/desc/ 2200 </cell> 2201 <cell> 2202 Area description in (<q></q>) quotes. 2203 </cell> 2204 </row> 2205 <row> 2206 <cell> 2207 <ident/msgbase/ 2208 </cell> 2209 <cell> 2210 F, O (<name/Opus/ <code/*.msg/); 2211 S (<name/FTS-0001/ <code/*.msg/); 2212 H, R, Q (<name/Hudson/, <name/QuickBBS/, <name/RemoteAccess/); 2213 M (<name/Squish/); J (<name/JAM/); E (<name/Ezycom/); 2214 G (<name/Goldbase/); P (<name/PCBoard/); X (<name/AdeptXBBS/); 2215 W (<name/WildCat!/); Y (<name/Synchronet/) 2216 </cell> 2217 </row> 2218 <row> 2219 <cell> 2220 <ident/type/ 2221 </cell> 2222 <cell> 2223 N (Netmail), E (Echomail), L (Local). 2224 </cell> 2225 </row> 2226 <row> 2227 <cell> 2228 <ident/location/ 2229 </cell> 2230 <cell> 2231 Directory path/file or board number. 2232 </cell> 2233 </row> 2234 <row> 2235 <cell> 2236 <ident/akano/ 2237 </cell> 2238 <cell> 2239 AKA number (starting from 0) 2240 </cell> 2241 </row> 2242 <row> 2243 <cell> 2244 <ident/attrs/ 2245 </cell> 2246 <cell> 2247 <gi>R/O</gi> (Read-Only), and/or other attributes. 2248 </cell> 2249 </row> 2250 </table> 2251 </item> 2252 <label> 2253 Notes: 2254 </label> 2255 <item> 2256 It is recommended to use the newer 2257 <ref target=AREADEF><kw/AREADEF/</ref> keyword, which allows more 2258 detailed mail area setup.<lb> 2259 If more than one area defined to the same path or areatag then last 2260 definition overrides previous ones.<lb> 2261 For the <ident/-FILE/ parameters see 2262 <ref target=AREAFILE><kw/AREAFILE/</ref> keyword. 2263 </item> 2264 <label> 2265 Processed by: 2266 </label> 2267 <item> 2268 Mail reader. 2269 </item> 2270 <label> 2271 See also: 2272 </label> 2273 <item> 2274 <ptr target=MESSAGEATTRS> chapter, 2275 <ref target=AREADEF><kw/AREADEF/</ref>, 2276 <ref target=AREADESC><kw/AREADESC/</ref>, 2277 <ref target=AREAFILE><kw/AREAFILE/</ref>, 2278 <ref target=AREAEXCL><kw/AREAEXCL/</ref>, 2279 <ref target=AREAINCL><kw/AREAINCL/</ref>, 2280 <ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>, 2281 <ref target=AREAISNEWS><kw/AREAISNEWS/</ref>, 2282 <ref target=AREARENAME><kw/AREARENAME/</ref>, 2283 <ref target=AREASEP><kw/AREASEP/</ref>, 2284 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 2285 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 2286 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 2287 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 2288 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 2289 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 2290 <ref target=GOLDBASEPATH><kw/GOLDBASEPATH/</ref>, 2291 <ref target=GOLDBASESYSPATH><kw/GOLDBASESYSPATH/</ref>, 2292 <ref target=HUDSONPATH><kw/HUDSONPATH/</ref>, 2293 <ref target=HUDSONSYSPATH><kw/HUDSONSYSPATH/</ref> 2294 </item> 2295 </list> 2296 </div2> 2297 <div2 id=AREAAUTOID> 2298 <head> 2299 AREAAUTOID 2300 </head> 2301 <list type=gloss> 2302 <label> 2303 Synopsis: 2304 </label> 2305 <item> 2306 <kw/AREAAUTOID/ <ident><SHORT/VERBOSE/LONG></ident> 2307 </item> 2308 <label> 2309 Description: 2310 </label> 2311 <item> 2312 Defines how an automatically created echoid should look, when 2313 <ref target=AREAFILE><kw/AREAFILE/</ref> finds an area without an 2314 echoid. 2315 </item> 2316 <label> 2317 Parameters: 2318 </label> 2319 <item> 2320 <table rows=3 cols=2> 2321 <row> 2322 <cell> 2323 <ident>VERBOSE</ident> 2324 </cell> 2325 <cell> 2326 The echoids are given a name similar to the function of the 2327 area, such as <gi/NETMAIL/, <gi/NET_SENT/, <gi/ECHO_BAD/, 2328 <gi/ECHO_DUPES/ and so on. 2329 </cell> 2330 </row> 2331 <row> 2332 <cell> 2333 <ident>LONG</ident> 2334 </cell> 2335 <cell> 2336 The echoids are numbered sequentially like this: 2337 <gi/NETMAILxxx/, <gi/ECHOMAILxxx/ and <gi/LOCALxxx/. 2338 </cell> 2339 </row> 2340 <row> 2341 <cell> 2342 <ident>SHORT</ident> 2343 </cell> 2344 <cell> 2345 The echoids are numbered sequentially like this: <gi/NETxxx/, 2346 <gi/ECHOxxx/ and <gi/LOCALxxx/. 2347 </cell> 2348 </row> 2349 </table> 2350 </item> 2351 <label> 2352 Default: 2353 </label> 2354 <item> 2355 <ident/LONG/ 2356 </item> 2357 <label> 2358 Processed by: 2359 </label> 2360 <item> 2361 Mail reader. 2362 </item> 2363 <label> 2364 See also: 2365 </label> 2366 <item> 2367 <ref target=AREAFILE><kw/AREAFILE/</ref> 2368 </item> 2369 </list> 2370 </div2> 2371 <div2> 2372 <head> 2373 AREAAUTONEXT 2374 </head> 2375 <list type=gloss> 2376 <label> 2377 Synopsis: 2378 </label> 2379 <item> 2380 <kw/AREAAUTONEXT/ <ident><YES/NO></ident> 2381 </item> 2382 <label> 2383 Description: 2384 </label> 2385 <item> 2386 This keyword controls where to put cursor in arealist on startup 2387 and after exiting from an area you have been reading. 2388 </item> 2389 <label> 2390 Parameters: 2391 </label> 2392 <item> 2393 If enabled, <name/GoldED+/ will automatically jump to the first 2394 marked area in the arealist on startup, and the next marked area 2395 after exiting from an area you have been reading. 2396 </item> 2397 <label> 2398 Default: 2399 </label> 2400 <item> 2401 <ident/YES/ 2402 </item> 2403 <label> 2404 Processed by: 2405 </label> 2406 <item> 2407 Mail reader. 2408 </item> 2409 </list> 2410 </div2> 2411 <div2> 2412 <head> 2413 AREACATCHUPREAD 2414 </head> 2415 <list type=gloss> 2416 <label> 2417 Synopsis: 2418 </label> 2419 <item> 2420 <kw/AREACATCHUPREAD/ <ident><YES/NO></ident> 2421 </item> 2422 <label> 2423 Description: 2424 </label> 2425 <item> 2426 This keyword controls whether <!-- FIX ME!!! --><kw/AREAcatchup/ 2427 will set all skipped messages to read or not. 2428 </item> 2429 <label> 2430 Parameters: 2431 </label> 2432 <item> 2433 If enabled, <name/GoldED+/ will set all skipped messages to read when 2434 using <!-- FIX ME!!! --><kw/AREAcatchup/ in the arealist-screen. 2435 </item> 2436 <label> 2437 Default: 2438 </label> 2439 <item> 2440 <ident/YES/ 2441 </item> 2442 <label> 2443 Notes: 2444 </label> 2445 <item> 2446 This implies that 2447 <ref target=HIGHLIGHTUNREAD><kw/HIGHLIGHTUNREAD/</ref> feature is 2448 used, otherwise it has no function. 2449 </item> 2450 <label> 2451 Processed by: 2452 </label> 2453 <item> 2454 Mail reader. 2455 </item> 2456 <label> 2457 See also: 2458 </label> 2459 <item> 2460 <!-- FIX ME!!! --><kw/AREAcatchup/, 2461 <ref target=HIGHLIGHTUNREAD><kw/HIGHLIGHTUNREAD/</ref> 2462 </item> 2463 </list> 2464 </div2> 2465 <div2 id=AREACFMREPLYTO> 2466 <head> 2467 AREACFMREPLYTO 2468 </head> 2469 <list type=gloss> 2470 <label> 2471 Synopsis: 2472 </label> 2473 <item> 2474 <kw/AREACFMREPLYTO/ <ident/<echoid>/ 2475 </item> 2476 <label> 2477 Description: 2478 </label> 2479 <item> 2480 Sets the area where <name/GoldED+/ will create confirmation messages. 2481 </item> 2482 <label> 2483 Parameters: 2484 </label> 2485 <item> 2486 The destination area for the confirmation messages. 2487 </item> 2488 <label> 2489 Processed by: 2490 </label> 2491 <item> 2492 Mail reader. 2493 </item> 2494 <label> 2495 See also: 2496 </label> 2497 <item> 2498 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref> 2499 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref>, 2500 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>, 2501 <ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>, 2502 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 2503 <ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>, 2504 <ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>, 2505 <ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref> 2506 </item> 2507 </list> 2508 </div2> 2509 <div2 id=AREACOPYADDID> 2510 <head> 2511 AREACOPYADDID 2512 </head> 2513 <list type=gloss> 2514 <label> 2515 Synopsis: 2516 </label> 2517 <item> 2518 <kw/AREACOPYADDID/ <ident><YES/NO></ident> 2519 </item> 2520 <label> 2521 Description: 2522 </label> 2523 <item> 2524 It is useful if you copy echomails to some local archive areas. In 2525 this case <name/GoldED+/ can add the<eg> 2526AREA:<OriginalEchoID></eg> 2527 kludge line to inform you from where you copied the mail to. This 2528 keyword should be enabled in the destination area parameters when 2529 used in the <ref target=RANDOMSYSTEM>Random System</ref> group. 2530 </item> 2531 <label> 2532 Parameters: 2533 </label> 2534 <item> 2535 If enabled, <name>GoldED+</name> will insert the <gi/AREA/ kludge 2536 at the top of each message that is copied or moved. 2537 </item> 2538 <label> 2539 Default: 2540 </label> 2541 <item> 2542 <ident/NO/ 2543 </item> 2544 <label> 2545 Notes: 2546 </label> 2547 <item> 2548 This keyword can be used globally and in a 2549 <ref target=RANDOMSYSTEM>Random System</ref> group.<lb> 2550 Do not enable this unless you know what you doing! 2551 </item> 2552 <label> 2553 Processed by: 2554 </label> 2555 <item> 2556 Mail reader. 2557 </item> 2558 <label> 2559 See also: 2560 </label> 2561 <item> 2562 <!-- FIX ME!!! --><kw/READcopymoveforward/, 2563 <ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>, 2564 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref> 2565 </item> 2566 </list> 2567 </div2> 2568 <div2 id=AREACOPYDIRECT> 2569 <head> 2570 AREACOPYDIRECT 2571 </head> 2572 <list type=gloss> 2573 <label> 2574 Synopsis: 2575 </label> 2576 <item> 2577 <kw/AREACOPYDIRECT/ <ident><YES/NO></ident> 2578 </item> 2579 <label> 2580 Description: 2581 </label> 2582 <item> 2583 This keyword controls whether copy/move functions should bypass area 2584 selection screen. The destination area should be set with 2585 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref> keyword. 2586 </item> 2587 <label> 2588 Parameters: 2589 </label> 2590 <item> 2591 If enabled, the destination area selection list is bypassed, thereby 2592 making possible a <q/seamless/ copy/move to the default destination 2593 area. 2594 </item> 2595 <label> 2596 Default: 2597 </label> 2598 <item> 2599 <ident/NO/ 2600 </item> 2601 <label> 2602 Notes: 2603 </label> 2604 <item> 2605 This keyword can be used globally and in a 2606 <ref target=RANDOMSYSTEM>Random System</ref> group. 2607 </item> 2608 <label> 2609 Processed by: 2610 </label> 2611 <item> 2612 Mail reader. 2613 </item> 2614 <label> 2615 See also: 2616 </label> 2617 <item> 2618 <!-- FIX ME!!! --><kw/READcopymoveforward/, 2619 <ref target=AREACOPYADDID><kw/AREACOPYADDID/</ref>, 2620 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref>, 2621 <ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>, 2622 <ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>, 2623 <ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref> 2624 </item> 2625 </list> 2626 </div2> 2627 <div2 id=AREACOPYTO> 2628 <head> 2629 AREACOPYTO 2630 </head> 2631 <list type=gloss> 2632 <label> 2633 Synopsis: 2634 </label> 2635 <item> 2636 <kw/AREACOPYTO/ <ident/<echoid>/ 2637 </item> 2638 <label> 2639 Description: 2640 </label> 2641 <item> 2642 Sets the default area for the copy/move functions. Typically you 2643 could set it to a safe/permanent storage type of area. 2644 </item> 2645 <label> 2646 Parameters: 2647 </label> 2648 <item> 2649 The default destination area for the copy/move functions. 2650 </item> 2651 <label> 2652 Notes: 2653 </label> 2654 <item> 2655 This keyword can be used globally and in a 2656 <ref target=RANDOMSYSTEM>Random System</ref> group.<lb> 2657 The forward function uses the 2658 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> area instead. 2659 </item> 2660 <label> 2661 Processed by: 2662 </label> 2663 <item> 2664 Mail reader. 2665 </item> 2666 <label> 2667 See also: 2668 </label> 2669 <item> 2670 <!-- FIX ME!!! --><kw/READcopymoveforward/, 2671 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 2672 <ref target=AREACOPYADDID><kw/AREACOPYADDID/</ref>, 2673 <ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>, 2674 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref>, 2675 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>, 2676 <ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref> 2677 </item> 2678 </list> 2679 </div2> 2680 <div2 id=AREADEF> 2681 <head> 2682 AREADEF 2683 </head> 2684 <list type=gloss> 2685 <label> 2686 Synopsis: 2687 </label> 2688 <item> 2689 <kw/AREADEF/ <ident><echoid> <<![ CDATA ["desc"]]>> 2690 <group> <type> <msgbase> <path/board> 2691 <aka> <(attrs)> 2692 [<![ CDATA ["origin"]]>]</ident> 2693 </item> 2694 <label> 2695 Description: 2696 </label> 2697 <item> 2698 This keyword defines a mail area in <name>GoldED+</name>. It looks a 2699 lot like the <ref target=AREA><kw/AREA/</ref> keyword. Additional 2700 parameters are the <ident/group/, the verbose <ident/type/ and 2701 <ident/msgbase/, the fully specified <ident/aka/ address, the 2702 brackets for the attributes and the optional <ident/origin/. 2703 </item> 2704 <label> 2705 Parameters: 2706 </label> 2707 <item> 2708 <table rows=9 cols=2> 2709 <row> 2710 <cell> 2711 <ident>echoid</ident> 2712 </cell> 2713 <cell> 2714 Mail area identifier. 2715 </cell> 2716 </row> 2717 <row> 2718 <cell> 2719 <ident><![ CDATA ["desc"]]></ident> 2720 </cell> 2721 <cell> 2722 Area description in quotes. 2723 </cell> 2724 </row> 2725 <row> 2726 <cell> 2727 <ident>group</ident> 2728 </cell> 2729 <cell> 2730 Group ID uppercase letter (A-Z) or 0 if not in a group. Use 2731 #groupnumber to specify group numbers in the 1-999 range. 2732 </cell> 2733 </row> 2734 <row> 2735 <cell> 2736 <ident>type</ident> 2737 </cell> 2738 <cell> 2739 <ident/Net/, <ident/Echo/, <ident/Local/, <ident/EMail/ or 2740 <ident/News/. 2741 </cell> 2742 </row> 2743 <row> 2744 <cell> 2745 <ident>msgbase</ident> 2746 </cell> 2747 <cell> 2748 <ident/Opus/, <ident/FTS1/, <ident/Hudson/, <ident/Squish/, 2749 <ident/Ezycom/, <ident/JAM/, <ident/Goldbase/, <ident/PCBoard/, 2750 <ident/WildCat/, <ident/XBBS/, or <ident/SMB/. 2751 </cell> 2752 </row> 2753 <row> 2754 <cell> 2755 <ident>path/board</ident> 2756 </cell> 2757 <cell> 2758 Area path, board number or base filename. 2759 </cell> 2760 </row> 2761 <row> 2762 <cell> 2763 <ident>aka</ident> 2764 </cell> 2765 <cell> 2766 Address for the area, or <q>.</q> for the main address. 2767 </cell> 2768 </row> 2769 <row> 2770 <cell> 2771 <ident>(attrs)</ident> 2772 </cell> 2773 <cell> 2774 Default attributes in brackets. 2775 </cell> 2776 </row> 2777 <row> 2778 <cell> 2779 <ident><![ CDATA ["origin"]]></ident> 2780 </cell> 2781 <cell> 2782 Optional default origin in quotes. 2783 </cell> 2784 </row> 2785 </table> 2786 </item> 2787 <label> 2788 Notes: 2789 </label> 2790 <item> 2791 If more than one area defined to the same path or areatag then last 2792 definition overrides previous ones.<lb> 2793 The possibility of using <q/./ to specify the main <abbr/AKA/ and 2794 the optional default origin makes it simpler to create a common 2795 <ref target=INCLUDE><kw/INCLUDE/</ref>'able area configuration 2796 for several setups with different addresses, for example two people 2797 sharing the same msgbase.<lb> 2798 If you wish to read packed area (f.e. from CD archive) <name/GoldED+/ 2799 allows you that. You need to specify pathname <hi/with/ extension 2800 in the <ident>path/board</ident> field, set <gi/PKD/ attribute and 2801 define packer with <ref target=UNPACKER><kw/UNPACKER/</ref> keyword. 2802 This feature is not supported for <name/Hudson/ and <name/GoldBase/ 2803 messagebases. 2804 </item> 2805 <label> 2806 Processed by: 2807 </label> 2808 <item> 2809 Mail reader. 2810 </item> 2811 <label> 2812 See also: 2813 </label> 2814 <item> 2815 <ptr target=MESSAGEATTRS> chapter, 2816 <ref target=AREA><kw/AREA/</ref>, 2817 <ref target=AREADESC><kw/AREADESC/</ref>, 2818 <ref target=AREAEXCL><kw/AREAEXCL/</ref>, 2819 <ref target=AREAFILE><kw/AREAFILE/</ref>, 2820 <ref target=AREAINCL><kw/AREAINCL/</ref>, 2821 <ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>, 2822 <ref target=AREAISNEWS><kw/AREAISNEWS/</ref>, 2823 <ref target=AREARENAME><kw/AREARENAME/</ref>, 2824 <ref target=AREASEP><kw/AREASEP/</ref>, 2825 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 2826 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 2827 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 2828 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 2829 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 2830 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 2831 <ref target=GOLDBASEPATH><kw/GOLDBASEPATH/</ref>, 2832 <ref target=GOLDBASESYSPATH><kw/GOLDBASESYSPATH/</ref>, 2833 <ref target=HUDSONPATH><kw/HUDSONPATH/</ref>, 2834 <ref target=HUDSONSYSPATH><kw/HUDSONSYSPATH/</ref> 2835 </item> 2836 </list> 2837 </div2> 2838 <div2 id=AREADESC> 2839 <head> 2840 AREADESC 2841 </head> 2842 <list type=gloss> 2843 <label> 2844 Synopsis: 2845 </label> 2846 <item> 2847 <kw/AREADESC/ <ident><echoid> <<![ CDATA ["desc"]]>> 2848 [group] [aka] [(attrs)] 2849 [<![ CDATA ["origin"]]>]</ident> 2850 </item> 2851 <label> 2852 Description: 2853 </label> 2854 <item> 2855 Adds a description and optionally a group letter, <abbr>AKA</abbr>, 2856 attributes and origin to an <hi>existing</hi> (previously defined) 2857 area. This is useful if you use an areafile that does not contain 2858 descriptions, groups, akas, attributes or origins. 2859 </item> 2860 <label> 2861 Parameters: 2862 </label> 2863 <item> 2864 <table rows=6 cols=2> 2865 <row> 2866 <cell> 2867 <ident>echoid</ident> 2868 </cell> 2869 <cell> 2870 Mail area identifier. 2871 </cell> 2872 </row> 2873 <row> 2874 <cell> 2875 <ident><![ CDATA ["desc"]]></ident> 2876 </cell> 2877 <cell> 2878 Area description in quotes. 2879 </cell> 2880 </row> 2881 <row> 2882 <cell> 2883 <ident>group</ident> 2884 </cell> 2885 <cell> 2886 Optional groupid uppercase letter (A-Z) or 0 if not in a group. 2887 Use #groupnumber to specify group numbers in the 1-999 2888 range or <q>-</q> to keep the existing groupid. 2889 </cell> 2890 </row> 2891 <row> 2892 <cell> 2893 <ident>aka</ident> 2894 </cell> 2895 <cell> 2896 Optional <abbr>AKA</abbr> address for the area, or <q>.</q> for 2897 main <abbr>AKA</abbr>, or <q>-</q> to keep the existing 2898 <abbr>AKA</abbr>. 2899 </cell> 2900 </row> 2901 <row> 2902 <cell> 2903 <ident>(attrs)</ident> 2904 </cell> 2905 <cell> 2906 Optional default attributes in brackets, <q>-</q> to keep the 2907 existing attributes. Note that if they are specified, they are 2908 <hi>added</hi> to the default net/echo/local attributes. 2909 </cell> 2910 </row> 2911 <row> 2912 <cell> 2913 <ident><![ CDATA ["origin"]]></ident> 2914 </cell> 2915 <cell> 2916 Optional default origin in quotes. 2917 </cell> 2918 </row> 2919 </table> 2920 </item> 2921 <label> 2922 Notes: 2923 </label> 2924 <item> 2925 You cannot skip any of the optional parts in the middle, even if you 2926 only want to set, say, an origin. Use <q>-</q> to keep the existing 2927 value for the parts you skip. 2928 </item> 2929 <label> 2930 Processed by: 2931 </label> 2932 <item> 2933 Mail reader. 2934 </item> 2935 <label> 2936 See also: 2937 </label> 2938 <item> 2939 <ptr target=MESSAGEATTRS> chapter, 2940 <ref target=AREA><kw/AREA/</ref>, 2941 <ref target=AREADEF><kw/AREADEF/</ref>, 2942 <ref target=AREAFILE><kw/AREAFILE/</ref>, 2943 <ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>, 2944 <ref target=AREAISNEWS><kw/AREAISNEWS/</ref>, 2945 <ref target=AREARENAME><kw/AREARENAME/</ref>, 2946 <ref target=AREASEP><kw/AREASEP/</ref>, 2947 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 2948 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 2949 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 2950 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 2951 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 2952 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref> 2953 </item> 2954 </list> 2955 </div2> 2956 <div2 id=AREAEXCL> 2957 <head> 2958 AREAEXCL 2959 </head> 2960 <list type=gloss> 2961 <label> 2962 Synopsis: 2963 </label> 2964 <item> 2965 <kw/AREAEXCL/ <ident/<echoid mask>/ 2966 </item> 2967 <label> 2968 Description: 2969 </label> 2970 <item> 2971 With this keyword, you can define the echoids of areas which should 2972 be ignored by <name/GoldED+/ (thereby leaving them out of the 2973 arealist). This is normally used in connection with 2974 <ref target=AREAFILE><kw/AREAFILE/</ref>, to exclude areas you are 2975 not interested in reading. 2976 </item> 2977 <label> 2978 Parameters: 2979 </label> 2980 <item> 2981 The <ident/<echoid mask>/ may contain <name/4DOS/-style 2982 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 2983 with commas. 2984 </item> 2985 <label> 2986 Notes: 2987 </label> 2988 <item> 2989 You can use the <ref target=AREAINCL><kw/AREAINCL/</ref> keyword to 2990 reinclude areas which have been excluded with <kw/AREAEXCL/.<lb> 2991 This keyword must be placed before any of 2992 <ref target=AREA><kw/AREA/</ref>, 2993 <ref target=AREADEF><kw/AREADEF/</ref>, 2994 or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords. 2995 </item> 2996 <label> 2997 Processed by: 2998 </label> 2999 <item> 3000 Mail reader. 3001 </item> 3002 <label> 3003 See also: 3004 </label> 3005 <item> 3006 <ref target=AREA><kw/AREA/</ref>, 3007 <ref target=AREADEF><kw/AREADEF/</ref>, 3008 <ref target=AREAFILE><kw/AREAFILE/</ref>, 3009 <ref target=AREAINCL><kw/AREAINCL/</ref>, 3010 <ref target=AREARENAME><kw/AREARENAME/</ref> 3011 </item> 3012 <label> 3013 Example: 3014 </label> 3015 <item><eg> 3016AREAEXCL * ; Excludes all areas. 3017AREAEXCL *INTER* ; Excludes all areas containing INTER anywhere in the 3018 ; echoid. 3019AREAEXCL INT*.* ; Excludes all areas beginning with INT and 3020 ; containing a dot anywhere in the echoid.</eg> 3021 </item> 3022 </list> 3023 </div2> 3024 <div2 id=AREAFILE> 3025 <head> 3026 AREAFILE 3027 </head> 3028 <list type=gloss> 3029 <label> 3030 Synopsis: 3031 </label> 3032 <item> 3033 <kw/AREAFILE/ <ident><type> [path/file] 3034 [switches]</ident> 3035 </item> 3036 <label> 3037 Description: 3038 </label> 3039 <item> 3040 <name/GoldED+/ can read the area setup of many popular mailers, 3041 mail processors and <abbr/BBS/'es, thereby making it much easier 3042 and simpler to configure <name/GoldED+/ for the mail areas you 3043 receive, by eliminating the need to write area definition lines for 3044 all or most of your areas. 3045 </item> 3046 <label> 3047 Parameters: 3048 </label> 3049 <item> 3050 <table rows=3 cols=2> 3051 <row> 3052 <cell> 3053 <ident/type/ 3054 </cell> 3055 <cell> 3056 Name of the program. 3057 </cell> 3058 </row> 3059 <row> 3060 <cell> 3061 <ident>path/file</ident> 3062 </cell> 3063 <cell> 3064 Filename or path to the area setup files. 3065 </cell> 3066 </row> 3067 <row> 3068 <cell> 3069 <ident/switches/ 3070 </cell> 3071 <cell> 3072 Areafile specific switches. 3073 </cell> 3074 </row> 3075 </table> 3076 </item> 3077 <label> 3078 Notes: 3079 </label> 3080 <item> 3081 For most programs, <name>GoldED+</name> can automatically find the 3082 path or filename using environment variables. By default, 3083 <name/GoldED+/ will look for the area setup files in the 3084 <ref target=AREAPATH><kw/AREAPATH/</ref>. 3085 </item> 3086 <label> 3087 Processed by: 3088 </label> 3089 <item> 3090 Mail reader. 3091 </item> 3092 <label> 3093 See also: 3094 </label> 3095 <item> 3096 <ptr target=AREACONFIGURATION> chapter, 3097 <ref target=AREA><kw/AREA/</ref>, 3098 <ref target=AREADEF><kw/AREADEF/</ref>, 3099 <ref target=AREAEXCL><kw/AREAEXCL/</ref>, 3100 <ref target=AREAFILE><kw/AREAFILE/</ref>, 3101 <ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>, 3102 <ref target=AREAINCL><kw/AREAINCL/</ref>, 3103 <ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>, 3104 <ref target=AREAISNEWS><kw/AREAISNEWS/</ref>, 3105 <ref target=AREARENAME><kw/AREARENAME/</ref>, 3106 <ref target=AREAPATH><kw/AREAPATH/</ref>, 3107 <ref target=AREASEP><kw/AREASEP/</ref>, 3108 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 3109 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 3110 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 3111 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 3112 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 3113 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref> 3114 </item> 3115 </list> 3116 </div2> 3117 <div2 id=AREAFILEGROUPS> 3118 <head> 3119 AREAFILEGROUPS 3120 </head> 3121 <list type=gloss> 3122 <label> 3123 Synopsis: 3124 </label> 3125 <item> 3126 <kw/AREAFILEGROUPS/ <ident><YES/NO></ident> 3127 </item> 3128 <label> 3129 Description: 3130 </label> 3131 <item> 3132 In some <ref target=AREAFILE><kw/AREAFILE/</ref> setups, you can 3133 groups the areas using single letters (A-Z) or numbers (#1-999). 3134 </item> 3135 <label> 3136 Parameters: 3137 </label> 3138 <item> 3139 If this keyword is enabled, <name>GoldED+</name> will use the area 3140 groupid instead of the area echoid when gathering area specific 3141 information from the <ref target=RANDOMSYSTEM>Random System</ref> 3142 group. 3143 </item> 3144 <label> 3145 Default: 3146 </label> 3147 <item> 3148 <ident/YES/ 3149 </item> 3150 <label> 3151 Notes: 3152 </label> 3153 <item> 3154 This have only sence if you using <ref target=RANDOMSYSTEM>Random 3155 System</ref> groups. 3156 </item> 3157 <label> 3158 Processed by: 3159 </label> 3160 <item> 3161 Mail reader. 3162 </item> 3163 <label> 3164 See also: 3165 </label> 3166 <item> 3167 <ptr target=RANDOMSYSTEM> chapter 3168 </item> 3169 </list> 3170 </div2> 3171 <div2 id=AREAFORWARDDIRECT> 3172 <head> 3173 AREAFORWARDDIRECT 3174 </head> 3175 <list type=gloss> 3176 <label> 3177 Synopsis: 3178 </label> 3179 <item> 3180 <kw/AREAFORWARDDIRECT/ <ident><YES/NO></ident> 3181 </item> 3182 <label> 3183 Description: 3184 </label> 3185 <item> 3186 This keyword controls whether forward functions should bypass area 3187 selection screen. The destination area should be set with 3188 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> keyword. 3189 </item> 3190 <label> 3191 Parameters: 3192 </label> 3193 <item> 3194 If enabled, the destination area selection list is bypassed, thereby 3195 making possible a <q/seamless/ forward to the default destination 3196 area. 3197 </item> 3198 <label> 3199 Default: 3200 </label> 3201 <item> 3202 <ident/NO/ 3203 </item> 3204 <label> 3205 Notes: 3206 </label> 3207 <item> 3208 This keyword can be used globally and in a 3209 <ref target=RANDOMSYSTEM>Random System</ref> group. 3210 </item> 3211 <label> 3212 Processed by: 3213 </label> 3214 <item> 3215 Mail reader. 3216 </item> 3217 <label> 3218 See also: 3219 </label> 3220 <item> 3221 <!-- FIX ME!!! --><kw/READcopymoveforward/, 3222 <ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>, 3223 <ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>, 3224 <ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>, 3225 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> 3226 </item> 3227 </list> 3228 </div2> 3229 <div2 id=AREAFREQDIRECT> 3230 <head> 3231 AREAFREQDIRECT 3232 </head> 3233 <list type=gloss> 3234 <label> 3235 Synopsis: 3236 </label> 3237 <item> 3238 <kw/AREAFREQDIRECT/ <ident><YES/NO></ident> 3239 </item> 3240 <label> 3241 Description: 3242 </label> 3243 <item> 3244 This keyword controls whether filerequest functions should bypass 3245 area selection screen. The destination area should be set with 3246 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref> keyword. 3247 </item> 3248 <label> 3249 Parameters: 3250 </label> 3251 <item> 3252 If enabled, the destination area selection list is bypassed, thereby 3253 making possible a <q/seamless/ filerequest in the default 3254 destination area. 3255 </item> 3256 <label> 3257 Default: 3258 </label> 3259 <item> 3260 <ident/NO/ 3261 </item> 3262 <label> 3263 Notes: 3264 </label> 3265 <item> 3266 This keyword can be used globally and in a 3267 <ref target=RANDOMSYSTEM>Random System</ref> group.<lb> 3268 If you (like most) only have one mailer netmail area, you can enable 3269 this feature globally for simpler file requests. 3270 </item> 3271 <label> 3272 Processed by: 3273 </label> 3274 <item> 3275 Mail reader. 3276 </item> 3277 <label> 3278 See also: 3279 </label> 3280 <item> 3281 <!-- FIX ME!!! --><kw/READfilerequest/, 3282 <ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>, 3283 <ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>, 3284 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref>, 3285 <ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>, 3286 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 3287 <ref target=FRQEXT><kw/FRQEXT/</ref>, 3288 <ref target=FRQNODEMAP><kw/FRQNODEMAP/</ref>, 3289 <ref target=FRQOPTIONS><kw/FRQOPTIONS/</ref>, 3290 <ref target=FRQWAZOO><kw/FRQWAZOO/</ref>, 3291 <ref target=OUTBOUNDPATH><kw/OUTBOUNDPATH/</ref> 3292 </item> 3293 </list> 3294 </div2> 3295 <div2 id=AREAFREQTO> 3296 <head> 3297 AREAFREQTO 3298 </head> 3299 <list type=gloss> 3300 <label> 3301 Synopsis: 3302 </label> 3303 <item> 3304 <kw/AREAFREQTO/ <ident/<echoid>/ 3305 </item> 3306 <label> 3307 Description: 3308 </label> 3309 <item> 3310 Sets the default area for the filerequest functions. 3311 </item> 3312 <label> 3313 Parameters: 3314 </label> 3315 <item> 3316 The default destination area for the filerequest functions. 3317 </item> 3318 <label> 3319 Default: 3320 </label> 3321 <item> 3322 First netmail area. 3323 </item> 3324 <label> 3325 Notes: 3326 </label> 3327 <item> 3328 This keyword can be used globally and in a 3329 <ref target=RANDOMSYSTEM>Random System</ref> group. 3330 </item> 3331 <label> 3332 Processed by: 3333 </label> 3334 <item> 3335 Mail reader. 3336 </item> 3337 <label> 3338 See also: 3339 </label> 3340 <item> 3341 <!-- FIX ME!!! --><kw/READfilerequest/, 3342 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 3343 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref>, 3344 <ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>, 3345 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>, 3346 <ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>, 3347 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 3348 <ref target=FRQEXT><kw/FRQEXT/</ref>, 3349 <ref target=FRQNODEMAP><kw/FRQNODEMAP/</ref>, 3350 <ref target=FRQOPTIONS><kw/FRQOPTIONS/</ref>, 3351 <ref target=FRQWAZOO><kw/FRQWAZOO/</ref>, 3352 <ref target=OUTBOUNDPATH><kw/OUTBOUNDPATH/</ref> 3353 </item> 3354 </list> 3355 </div2> 3356 <div2 id=AREAINCL> 3357 <head> 3358 AREAINCL 3359 </head> 3360 <list type=gloss> 3361 <label> 3362 Synopsis: 3363 </label> 3364 <item> 3365 <kw/AREAINCL/ <ident/<echoid mask>/ 3366 </item> 3367 <label> 3368 Description: 3369 </label> 3370 <item> 3371 With this keyword, you can define the echoids of areas which should 3372 be reincluded by <name/GoldED+/, if they have been excluded with the 3373 <ref target=AREAEXCL><kw/AREAEXCL/</ref> keyword. 3374 </item> 3375 <label> 3376 Parameters: 3377 </label> 3378 <item> 3379 The <ident/<echoid mask>/ may contain <name/4DOS/-style 3380 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 3381 with commas. 3382 </item> 3383 <label> 3384 Notes: 3385 </label> 3386 <item> 3387 This keyword must be placed before any of 3388 <ref target=AREA><kw/AREA/</ref>, 3389 <ref target=AREADEF><kw/AREADEF/</ref>, 3390 or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords. 3391 </item> 3392 <label> 3393 Processed by: 3394 </label> 3395 <item> 3396 Mail reader. 3397 </item> 3398 <label> 3399 See also: 3400 </label> 3401 <item> 3402 <ref target=AREA><kw/AREA/</ref>, 3403 <ref target=AREADEF><kw/AREADEF/</ref>, 3404 <ref target=AREAFILE><kw/AREAFILE/</ref>, 3405 <ref target=AREAEXCL><kw/AREAEXCL/</ref>, 3406 <ref target=AREARENAME><kw/AREARENAME/</ref> 3407 </item> 3408 <label> 3409 Example: 3410 </label> 3411 <item><eg> 3412AREAINCL * ; Includes all areas. 3413AREAINCL *INTER* ; Includes all areas containing INTER anywhere in the 3414 ; echoid. 3415AREAINCL INT*.* ; Includes all areas beginning with INT and 3416 ; containing a dot anywhere in the echoid.</eg> 3417 </item> 3418 </list> 3419 </div2> 3420 <div2 id=AREAISEMAIL> 3421 <head> 3422 AREAISEMAIL 3423 </head> 3424 <list type=gloss> 3425 <label> 3426 Synopsis: 3427 </label> 3428 <item> 3429 <kw/AREAISEMAIL/ <ident/<echoid mask>/ 3430 </item> 3431 <label> 3432 Description: 3433 </label> 3434 <item> 3435 These keyword is designed to mark areas which are read from an 3436 <ref target=AREAFILE><kw/AREAFILE/</ref> as <name/Internet/ e-mail. 3437 This may be necessary in some cases to enable the <name/Internet/ 3438 specific features without having to manually define all 3439 <name/Internet/ areas. 3440 </item> 3441 <label> 3442 Parameters: 3443 </label> 3444 <item> 3445 The <ident/<echoid mask>/ may contain <name/4DOS/-style 3446 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 3447 with commas. 3448 </item> 3449 <label> 3450 Notes: 3451 </label> 3452 <item> 3453 This keyword must be placed before any of 3454 <ref target=AREA><kw/AREA/</ref>, 3455 <ref target=AREADEF><kw/AREADEF/</ref>, 3456 or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords. 3457 </item> 3458 <label> 3459 Processed by: 3460 </label> 3461 <item> 3462 Mail reader. 3463 </item> 3464 <label> 3465 See also: 3466 </label> 3467 <item> 3468 <ref target=AREA><kw/AREA/</ref>, 3469 <ref target=AREADEF><kw/AREADEF/</ref>, 3470 <ref target=AREAFILE><kw/AREAFILE/</ref>, 3471 <ref target=AREAISNEWS><kw/AREAISNEWS/</ref>, 3472 <ref target=AREARENAME><kw/AREARENAME/</ref> 3473 </item> 3474 <label> 3475 Example: 3476 </label> 3477 <item><eg> 3478AREAISEMAIL djgpp*, golded-plus*</eg> 3479 </item> 3480 </list> 3481 </div2> 3482 <div2 id=AREAISNEWS> 3483 <head> 3484 AREAISNEWS 3485 </head> 3486 <list type=gloss> 3487 <label> 3488 Synopsis: 3489 </label> 3490 <item> 3491 <kw/AREAISNEWS/ <ident/<echoid mask>/ 3492 </item> 3493 <label> 3494 Description: 3495 </label> 3496 <item> 3497 These keyword is designed to mark areas which are read from an 3498 <ref target=AREAFILE><kw/AREAFILE/</ref> as <name/Internet/ 3499 newsgroup. This may be necessary in some cases to enable the 3500 <name/Internet/ specific features without having to manually define 3501 all <name/Internet/ areas. 3502 </item> 3503 <label> 3504 Parameters: 3505 </label> 3506 <item> 3507 The <ident/<echoid mask>/ may contain <name/4DOS/-style 3508 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 3509 with commas. 3510 </item> 3511 <label> 3512 Notes: 3513 </label> 3514 <item> 3515 This keyword must be placed before any of 3516 <ref target=AREA><kw/AREA/</ref>, 3517 <ref target=AREADEF><kw/AREADEF/</ref>, 3518 or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords. 3519 </item> 3520 <label> 3521 Processed by: 3522 </label> 3523 <item> 3524 Mail reader. 3525 </item> 3526 <label> 3527 See also: 3528 </label> 3529 <item> 3530 <ref target=AREA><kw/AREA/</ref>, 3531 <ref target=AREADEF><kw/AREADEF/</ref>, 3532 <ref target=AREAFILE><kw/AREAFILE/</ref>, 3533 <ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>, 3534 <ref target=AREARENAME><kw/AREARENAME/</ref> 3535 </item> 3536 <label> 3537 Example: 3538 </label> 3539 <item><eg> 3540AREAISNEWS alt.*, rec.*, sci.*</eg> 3541 </item> 3542 </list> 3543 </div2> 3544 <div2 id=AREAKEEPLAST> 3545 <head> 3546 AREAKEEPLAST 3547 </head> 3548 <list type=gloss> 3549 <label> 3550 Synopsis: 3551 </label> 3552 <item> 3553 <kw/AREAKEEPLAST/ <ident><YES/NO></ident> 3554 </item> 3555 <label> 3556 Description: 3557 </label> 3558 <item> 3559 This keyword controls whether <name/GoldED+/ should write the file 3560 <code/goldlast.lst/ in the <ref target=GOLDPATH><kw/GOLDPATH/</ref> 3561 at exit and read it back when run next time. The contents of the file 3562 is a list of lastread information for each area as it was at last 3563 scan.<lb> 3564 This feature is helpful when you know that there have not been tossed 3565 new mail and don't want to wait for a full msgbase scan. Now you can 3566 just hit <ESC> at the startup screen to abort the area scan and 3567 <name/GoldED+/ will put up the lastread info from the previous 3568 session.<lb> 3569 It also makes the <q/new mail since last scan/ feature even better, 3570 because the new mail marker now shows which areas that have new mail 3571 since last session even when scanning areas at startup. 3572 </item> 3573 <label> 3574 Parameters: 3575 </label> 3576 <item> 3577 Setting this keyword to <ident/YES/ enables <code/goldlast.lst/ 3578 usage, setting to <ident/NO/ disables writes to this file. 3579 </item> 3580 <label> 3581 Default: 3582 </label> 3583 <item> 3584 <ident/YES/ 3585 </item> 3586 <label> 3587 Notes: 3588 </label> 3589 <item> 3590 <name/GoldED+/ only writes the <code/goldlast.lst/ file at exit if it 3591 survived the initial startup scan. 3592 </item> 3593 <label> 3594 Processed by: 3595 </label> 3596 <item> 3597 Mail reader. 3598 </item> 3599 <label> 3600 See also: 3601 </label> 3602 <item> 3603 <!-- FIX ME!!! --><kw/AREAscan/, 3604 <!-- FIX ME!!! --><kw/AREAscanpm/, 3605 <!-- FIX ME!!! --><kw/AREAwritegoldlast/, 3606 <ref target=AREALISTSCAN><kw/AREALISTSCAN/</ref>, 3607 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>, 3608 <ref target=AREASCAN><kw/AREASCAN/</ref> 3609 </item> 3610 </list> 3611 </div2> 3612 <div2 id=AREALISTECHOMAX> 3613 <head> 3614 AREALISTECHOMAX 3615 </head> 3616 <list type=gloss> 3617 <label> 3618 Synopsis: 3619 </label> 3620 <item> 3621 <kw/AREALISTECHOMAX/ <ident/<size>/ 3622 </item> 3623 <label> 3624 Description: 3625 </label> 3626 <item> 3627 Allows you to specify a fixed or dynamically sized width of the 3628 <gi/EchoID/ column in the arealist. 3629 </item> 3630 <label> 3631 Parameters: 3632 </label> 3633 <item> 3634 If a negative value is specified, the width will be the that of the 3635 widest echoid in the arealist plus the negative value. This might be 3636 useful if some long-name echoes have uninteresting ends, such as 3637 <gi/VERYLONGECHOID_R23.PUB/ (could benefit from a <ident/size/ of 3638 -7). There is currently no provision for long echoids with common 3639 beginning. 3640 </item> 3641 <label> 3642 Default: 3643 </label> 3644 <item> 3645 <ident/0/ 3646 </item> 3647 <label> 3648 Notes: 3649 </label> 3650 <item> 3651 The arealist can dynamically resize the <gi/EchoID/ and 3652 <gi/Description/ columns, so that long echoids are not cut off. The 3653 sizing of the <q>EchoID</q> column is done against the 3654 <gi/Description/ column, which thereby looses or gains width. 3655 </item> 3656 <label> 3657 Processed by: 3658 </label> 3659 <item> 3660 Mail reader. 3661 </item> 3662 <label> 3663 See also: 3664 </label> 3665 <item> 3666 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 3667 <ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>, 3668 <ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>, 3669 <ref target=AREALISTNOS><kw/AREALISTNOS/</ref>, 3670 <ref target=AREALISTPAGEBAR><kw/AREALISTPAGEBAR/</ref>, 3671 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref>, 3672 <ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref>, 3673 <ref target=AREASEP><kw/AREASEP/</ref>, 3674 </item> 3675 </list> 3676 </div2> 3677 <div2 id=AREALISTFORMAT> 3678 <head> 3679 AREALISTFORMAT 3680 </head> 3681 <list type=gloss> 3682 <label> 3683 Synopsis: 3684 </label> 3685 <item> 3686 <kw/AREALISTFORMAT/ <ident/<string>/ 3687 </item> 3688 <label> 3689 Description: 3690 </label> 3691 <item> 3692 The arealist column layout is configurable. This keyword allows you 3693 to change the layout to whatever you like. 3694 </item> 3695 <label> 3696 Parameters: 3697 </label> 3698 <item> 3699 The string should be composed from the following letters: 3700 <table rows=10 cols=3> 3701 <row> 3702 <cell> 3703 Letter 3704 </cell> 3705 <cell> 3706 Meaning 3707 </cell> 3708 <cell> 3709 Default width 3710 </cell> 3711 </row> 3712 <row> 3713 <cell> 3714 <ident/A/ 3715 </cell> 3716 <cell> 3717 Area number 3718 </cell> 3719 <cell> 3720 4 3721 </cell> 3722 </row> 3723 <row> 3724 <cell> 3725 <ident/M/ 3726 </cell> 3727 <cell> 3728 Marked 3729 </cell> 3730 <cell> 3731 1 3732 </cell> 3733 </row> 3734 <row> 3735 <cell> 3736 <ident/D/ 3737 </cell> 3738 <cell> 3739 Description 3740 </cell> 3741 <cell> 3742 Dynamic 3743 </cell> 3744 </row> 3745 <row> 3746 <cell> 3747 <ident/C/ 3748 </cell> 3749 <cell> 3750 Number of messages 3751 </cell> 3752 <cell> 3753 6 3754 </cell> 3755 </row> 3756 <row> 3757 <cell> 3758 <ident/P/ 3759 </cell> 3760 <cell> 3761 Personal mail mark (<q/+/) 3762 </cell> 3763 <cell> 3764 1 3765 </cell> 3766 </row> 3767 <row> 3768 <cell> 3769 <ident/U/ 3770 </cell> 3771 <cell> 3772 Number of unread/new messages 3773 </cell> 3774 <cell> 3775 6 3776 </cell> 3777 </row> 3778 <row> 3779 <cell> 3780 <ident/N/ 3781 </cell> 3782 <cell> 3783 Changed since last scan mark (<q/*/) 3784 </cell> 3785 <cell> 3786 1 3787 </cell> 3788 </row> 3789 <row> 3790 <cell> 3791 <ident/E/ 3792 </cell> 3793 <cell> 3794 Echoid 3795 </cell> 3796 <cell> 3797 <ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref> 3798 </cell> 3799 </row> 3800 <row> 3801 <cell> 3802 <ident/G/ 3803 </cell> 3804 <cell> 3805 Groupid 3806 </cell> 3807 <cell> 3808 Dynamic: 0, 1 or 3 3809 </cell> 3810 </row> 3811 </table> 3812 You can also specify widths for each or particular fields if you 3813 don't like the defaults by putting number right after the letter.<lb> 3814 If you leave out a letter, that column will not be shown. 3815 </item> 3816 <label> 3817 Default: 3818 </label> 3819 <item> 3820 <ident><![ CDATA ["AM D CPUN E G "]]></ident> 3821 </item> 3822 <label> 3823 Notes: 3824 </label> 3825 <item> 3826 Use only the defined letters. Use spaces to specify required space 3827 between columns. Use only positive numbers for widths. Failure to 3828 obey these rules may cause undocumented behaviour. 3829 </item> 3830 <label> 3831 Processed by: 3832 </label> 3833 <item> 3834 Mail reader. 3835 </item> 3836 <label> 3837 See also: 3838 </label> 3839 <item> 3840 <ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref>, 3841 <ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>, 3842 <ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>, 3843 <ref target=AREALISTNOS><kw/AREALISTNOS/</ref>, 3844 <ref target=AREALISTPAGEBAR><kw/AREALISTPAGEBAR/</ref>, 3845 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref>, 3846 <ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref>, 3847 <ref target=AREASEP><kw/AREASEP/</ref> 3848 </item> 3849 <label> 3850 Example: 3851 </label> 3852 <item><eg><![ CDATA [ 3853AREALISTFORMAT "AM D C4PU4N E G "]]></eg> 3854 </item> 3855 </list> 3856 </div2> 3857 <div2 id=AREALISTGROUPID> 3858 <head> 3859 AREALISTGROUPID 3860 </head> 3861 <list type=gloss> 3862 <label> 3863 Synopsis: 3864 </label> 3865 <item> 3866 <kw/AREALISTGROUPID/ <ident><YES/NO></ident> 3867 </item> 3868 <label> 3869 Description: 3870 </label> 3871 <item> 3872 This feature provides a way to hide group ID on the arealist screen, 3873 in a column to the right of the <gi/EchoID/ column. If a group ID is 3874 not a letter in the range A-Z (a value in the range #65-#90), 3875 the groupid is not shown anyway. 3876 </item> 3877 <label> 3878 Parameters: 3879 </label> 3880 <item> 3881 If enabled, the arealist screen will display the groupid letters, if 3882 any. 3883 </item> 3884 <label> 3885 Default: 3886 </label> 3887 <item> 3888 <ident/YES/ 3889 </item> 3890 <label> 3891 Notes: 3892 </label> 3893 <item> 3894 The same effect is achieved by skipping <ident/G/ letter in the 3895 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref> definition. 3896 </item> 3897 <label> 3898 Processed by: 3899 </label> 3900 <item> 3901 Mail reader. 3902 </item> 3903 <label> 3904 See also: 3905 </label> 3906 <item> 3907 <ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>, 3908 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 3909 <ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref> 3910 </item> 3911 </list> 3912 </div2> 3913 <div2 id=AREALISTGROUPORDER> 3914 <head> 3915 AREALISTGROUPORDER 3916 </head> 3917 <list type=gloss> 3918 <label> 3919 Synopsis: 3920 </label> 3921 <item> 3922 <kw/AREALISTGROUPORDER/ <ident/<string>/ 3923 </item> 3924 <label> 3925 Description: 3926 </label> 3927 <item> 3928 This keyword allows to change the order in which areas will be sorted 3929 when sorting by group ID is used. If some groups are not found in the 3930 <ident/string/ they will be placed below specifyed ones in 3931 alphabetical order. 3932 </item> 3933 <label> 3934 Parameters: 3935 </label> 3936 <item> 3937 The only parameter is string which specifies groups order. You may 3938 use #groupnumber to specify group numbers in the 1-999 range. 3939 </item> 3940 <label> 3941 Default: 3942 </label> 3943 <item> 3944 Empty string. 3945 </item> 3946 <label> 3947 Processed by: 3948 </label> 3949 <item> 3950 Mail reader. 3951 </item> 3952 <label> 3953 See also: 3954 </label> 3955 <item> 3956 <ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>, 3957 <ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>, 3958 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref> 3959 </item> 3960 </list> 3961 </div2> 3962 <div2 id=AREALISTNOS> 3963 <head> 3964 AREALISTNOS 3965 </head> 3966 <list type=gloss> 3967 <label> 3968 Synopsis: 3969 </label> 3970 <item> 3971 <kw/AREALISTNOS/ <ident><YES/NO></ident> 3972 </item> 3973 <label> 3974 Description: 3975 </label> 3976 <item> 3977 This keyword allows to specify whether board number or sequential 3978 area number will be displayed in the arealist. 3979 </item> 3980 <label> 3981 Parameters: 3982 </label> 3983 <item> 3984 If enabled, <name/GoldED+/ will display the board numbers of 3985 <name/Hudson/ or <name/GoldBase/ areas in the arealist instead of 3986 the default sequential numbers. 3987 </item> 3988 <label> 3989 Default: 3990 </label> 3991 <item> 3992 <ident/NO/ 3993 </item> 3994 <label> 3995 Processed by: 3996 </label> 3997 <item> 3998 Mail reader. 3999 </item> 4000 <label> 4001 See also: 4002 </label> 4003 <item> 4004 <!-- FIX ME!!! --><kw/AREAboardnos/, 4005 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 4006 <ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref>, 4007 <ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref>, 4008 <ref target=DISPAREANO><kw/DISPAREANO/</ref> 4009 </item> 4010 </list> 4011 </div2> 4012 <div2 id=AREALISTPAGEBAR> 4013 <head> 4014 AREALISTPAGEBAR 4015 </head> 4016 <list type=gloss> 4017 <label> 4018 Synopsis: 4019 </label> 4020 <item> 4021 <kw/AREALISTPAGEBAR/ <ident><YES/NO></ident> 4022 </item> 4023 <label> 4024 Description: 4025 </label> 4026 <item> 4027 Enables or disables a pagebar (scrollbar) in the arealist. 4028 </item> 4029 <label> 4030 Parameters: 4031 </label> 4032 <item> 4033 If enabled, <name/GoldED+/ will display pagebar in the arealist, if 4034 disabled - will not. 4035 </item> 4036 <label> 4037 Default: 4038 </label> 4039 <item> 4040 <ident/YES/ 4041 </item> 4042 <label> 4043 Processed by: 4044 </label> 4045 <item> 4046 Mail reader. 4047 </item> 4048 <label> 4049 See also: 4050 </label> 4051 <item> 4052 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 4053 <ref target=DISPPAGEBAR><kw/DISPPAGEBAR/</ref>, 4054 <ref target=FILELISTPAGEBAR><kw/FILELISTPAGEBAR/</ref>, 4055 <ref target=MSGLISTPAGEBAR><kw/MSGLISTPAGEBAR/</ref> 4056 </item> 4057 </list> 4058 </div2> 4059 <div2 id=AREALISTSCAN> 4060 <head> 4061 AREALISTSCAN 4062 </head> 4063 <list type=gloss> 4064 <label> 4065 Synopsis: 4066 </label> 4067 <item> 4068 <kw/AREALISTSCAN/ <ident><<![ CDATA ["L menu text"]]>> 4069 [path]<filename> [-delete]</ident> 4070 </item> 4071 <label> 4072 Description: 4073 </label> 4074 <item> 4075 This keyword allows you to define additional menu items for the 4076 arealist scanning menus (<!-- FIX ME!!! --><kw/AREAscan/ or 4077 <!-- FIX ME!!! --><kw/AREAscanpm/). 4078 </item> 4079 <label> 4080 Parameters: 4081 </label> 4082 <item> 4083 The first two characters of the menu text are the <q/hotkey/ letter 4084 that will be highlighted in the menu text, plus a space.<lb> 4085 The filename specifies a plain text file, with the echoids (wildcards 4086 allowed) of the areas you want to scan when the menu item is 4087 selected. There can be several echoids on each line in the file. If 4088 no path is given, the file is loaded from the 4089 <ref target=GOLDPATH><kw/GOLDPATH/</ref>.<lb> 4090 The <ident/-delete/ option will cause <name/GoldED+/ to delete the 4091 list file after scanning the areas in it. For example, if your mail 4092 processor generates a list of the areas that it tossed new mail to, 4093 you could add the list as a menu item on the scanning menu and use it 4094 to scan only those areas with new mail. 4095 </item> 4096 <label> 4097 Notes: 4098 </label> 4099 <item> 4100 Some mail processors automatically delete their list after using it 4101 for replylinking. You may want to do some creative stuff with 4102 batchfiles to grab a copy. 4103 </item> 4104 <label> 4105 Processed by: 4106 </label> 4107 <item> 4108 Mail reader. 4109 </item> 4110 <label> 4111 See also: 4112 </label> 4113 <item> 4114 <!-- FIX ME!!! --><kw/AREAscan/, 4115 <!-- FIX ME!!! --><kw/AREAscanpm/ 4116 </item> 4117 <label> 4118 Example: 4119 </label> 4120 <item><eg><![ CDATA [ 4121AREALISTSCAN "g Scan Newsgroups" NEWSGRPS.LST 4122AREALISTSCAN "L Scan Latest" R:\GECHO\IMPORT.ALL -delete]]></eg> 4123 <eg> 4124=== Cut, NEWSGRPS.LST === 4125ALT.*, COMP.*, MISC.*, NEWS.* 4126REC.*, SOC.*, SCI.*, TALK.* 4127=== Cut ===</eg> 4128 <eg> 4129=== Cut from an import batchfile === 4130gecho mgr toss pack -tossbad 4131if exist import.jam type import.jam >>import.all 4132if exist import.hmb type import.hmb >>import.all 4133if exist import.sdm type import.sdm >>import.all 4134mbutil link -clean 4135=== Cut ===</eg> 4136 </item> 4137 </list> 4138 </div2> 4139 <div2 id=AREALISTSORT> 4140 <head> 4141 AREALISTSORT 4142 </head> 4143 <list type=gloss> 4144 <label> 4145 Synopsis: 4146 </label> 4147 <item> 4148 <kw/AREALISTSORT/ <ident/<sortspec>/ 4149 </item> 4150 <label> 4151 Description: 4152 </label> 4153 <item> 4154 This keyword defines how the area list should be sorted. You can 4155 override the default setting from the commandline with the 4156 <code>-s</code> switch. 4157 </item> 4158 <label> 4159 Parameters: 4160 </label> 4161 <item> 4162 The <sortspec> can be composed of the following types: 4163 <table rows=16 cols=2> 4164 <row> 4165 <cell> 4166 <ident/A/ 4167 </cell> 4168 <cell> 4169 Sort by aka. 4170 </cell> 4171 </row> 4172 <row> 4173 <cell> 4174 <ident/B/ 4175 </cell> 4176 <cell> 4177 Sort by board number. 4178 </cell> 4179 </row> 4180 <row> 4181 <cell> 4182 <ident/D/ 4183 </cell> 4184 <cell> 4185 Sort by description. 4186 </cell> 4187 </row> 4188 <row> 4189 <cell> 4190 <ident/E/ 4191 </cell> 4192 <cell> 4193 Sort by echoid. 4194 </cell> 4195 </row> 4196 <row> 4197 <cell> 4198 <ident/F/ 4199 </cell> 4200 <cell> 4201 Sorts all <q/fuzzy search/ matches first. 4202 </cell> 4203 </row> 4204 <row> 4205 <cell> 4206 <ident/G/ 4207 </cell> 4208 <cell> 4209 Sort by group (if any). 4210 </cell> 4211 </row> 4212 <row> 4213 <cell> 4214 <ident/M/ 4215 </cell> 4216 <cell> 4217 Sorts all marked areas first. 4218 </cell> 4219 </row> 4220 <row> 4221 <cell> 4222 <ident/O/ 4223 </cell> 4224 <cell> 4225 Sort by original order. 4226 </cell> 4227 </row> 4228 <row> 4229 <cell> 4230 <ident/P/ 4231 </cell> 4232 <cell> 4233 Sort by personal mail count. 4234 </cell> 4235 </row> 4236 <row> 4237 <cell> 4238 <ident/p/ 4239 </cell> 4240 <cell> 4241 Sort by personal mail presence. 4242 </cell> 4243 </row> 4244 <row> 4245 <cell> 4246 <ident/S/ 4247 </cell> 4248 <cell> 4249 Sort area separators first. 4250 </cell> 4251 </row> 4252 <row> 4253 <cell> 4254 <ident/T/ 4255 </cell> 4256 <cell> 4257 Sort by type (according to 4258 <ref target=AREATYPEORDER><kw/AREATYPEORDER/</ref>). 4259 </cell> 4260 </row> 4261 <row> 4262 <cell> 4263 <ident/U/ 4264 </cell> 4265 <cell> 4266 Sort by unread messages count (try it!). 4267 </cell> 4268 </row> 4269 <row> 4270 <cell> 4271 <ident/u/ 4272 </cell> 4273 <cell> 4274 Sort by unread messages presence (try it!). 4275 </cell> 4276 </row> 4277 <row> 4278 <cell> 4279 <ident/X/ 4280 </cell> 4281 <cell> 4282 Sort by msgbase type. 4283 </cell> 4284 </row> 4285 <row> 4286 <cell> 4287 <ident/Y/ 4288 </cell> 4289 <cell> 4290 Sorts all areas with <q/new/ mail first. 4291 </cell> 4292 </row> 4293 <row> 4294 <cell> 4295 <ident/Z/ 4296 </cell> 4297 <cell> 4298 Sort by msgbase path. 4299 </cell> 4300 </row> 4301 <row> 4302 <cell> 4303 <ident/-/ 4304 </cell> 4305 <cell> 4306 Descending sort (largest first). 4307 </cell> 4308 </row> 4309 <row> 4310 <cell> 4311 <ident/+/ 4312 </cell> 4313 <cell> 4314 Ascending sort (smallest first) (default). 4315 </cell> 4316 </row> 4317 </table> 4318 </item> 4319 <label> 4320 Default: 4321 </label> 4322 <item> 4323 <ident/FYTUE/ 4324 </item> 4325 <label> 4326 Notes: 4327 </label> 4328 <item> 4329 In practice <ident/M/ and <ident/Y/ will usually give the same 4330 result, because <name/GoldED+/ automatically marks scanned areas if 4331 they contain new mail.<lb> 4332 The <ident/F/ enables fuzzy match sorting, which is very handy when 4333 looking for an echoid containing a particular word. Let's say you 4334 want a list of all <name/GoldED/ echoes. You can simply type 4335 <q/GOLDED/ and then the arealist automatically sorts itself so that 4336 all echoes with an echoid containing <q/GOLDED/ comes first.<lb> 4337 The <ident/X/ sort type sorts areas according to msgbase type, in the 4338 following order: <name/Hudson/, <name/Goldbase/, <name/JAM/, 4339 <name/Squish/, <name/Opus/ <code/*.msg/, <name/FTS-0001/ 4340 <code/*.msg/, <name/Ezycom/, <name/PCBoard/.<lb> 4341 The <ident/X/ and <ident/Z/ sort types were implemented for internal 4342 use, to optimize area scanning speed. When scanning areas, 4343 <name/GoldED+/ starts by sorting the arealist using the sortspec 4344 defined with the <ref target=AREASCANSORT><kw/AREASCANSORT/</ref> 4345 keyword. 4346 </item> 4347 <label> 4348 Processed by: 4349 </label> 4350 <item> 4351 Mail reader. 4352 </item> 4353 <label> 4354 See also: 4355 </label> 4356 <item> 4357 <ptr target=AREACONFIGURATION> chapter, 4358 <ptr target=COMMANDLINE> chapter, 4359 <ref target=AREA><kw/AREA/</ref>, 4360 <ref target=AREADEF><kw/AREADEF/</ref>, 4361 <ref target=AREAEXCL><kw/AREAEXCL/</ref>, 4362 <ref target=AREAFILE><kw/AREAFILE/</ref>, 4363 <ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>, 4364 <ref target=AREAINCL><kw/AREAINCL/</ref>, 4365 <ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>, 4366 <ref target=AREAISNEWS><kw/AREAISNEWS/</ref>, 4367 <ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>, 4368 <ref target=AREASCANSORT><kw/AREASCANSORT/</ref>, 4369 <ref target=AREASEP><kw/AREASEP/</ref>, 4370 <ref target=AREATYPEORDER><kw/AREATYPEORDER/</ref> 4371 </item> 4372 <label> 4373 Example: 4374 </label> 4375 <item><eg> 4376AREALISTSORT -U+TE</eg> 4377 </item> 4378 </list> 4379 </div2> 4380 <div2 id=AREALISTTYPE> 4381 <head> 4382 AREALISTTYPE 4383 </head> 4384 <list type=gloss> 4385 <label> 4386 Synopsis: 4387 </label> 4388 <item> 4389 <kw/AREALISTTYPE/ <ident><NEW/LAST></ident> 4390 </item> 4391 <label> 4392 Description: 4393 </label> 4394 <item> 4395 Defines the contents of the 4th column (the one after the <gi/Total/ 4396 column). 4397 </item> 4398 <label> 4399 Parameters: 4400 </label> 4401 <item> 4402 <table rows=2 cols=2> 4403 <row> 4404 <cell> 4405 <ident/NEW/ 4406 </cell> 4407 <cell> 4408 Displays the amount of new (unread) msgs (Actually number of 4409 messages after lastread mark). 4410 </cell> 4411 </row> 4412 <row> 4413 <cell> 4414 <ident/LAST/ 4415 </cell> 4416 <cell> 4417 Displays the number of the last msg read. 4418 </cell> 4419 </row> 4420 </table> 4421 </item> 4422 <label> 4423 Default: 4424 </label> 4425 <item> 4426 <ident/NEW/ 4427 </item> 4428 <label> 4429 Processed by: 4430 </label> 4431 <item> 4432 Mail reader. 4433 </item> 4434 <label> 4435 See also: 4436 </label> 4437 <item> 4438 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 4439 <ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>, 4440 <ref target=AREALISTNOS><kw/AREALISTNOS/</ref> 4441 </item> 4442 </list> 4443 </div2> 4444 <div2 id=AREAPATH> 4445 <head> 4446 AREAPATH 4447 </head> 4448 <list type=gloss> 4449 <label> 4450 Synopsis: 4451 </label> 4452 <item> 4453 <kw/AREAPATH/ <ident/<path>/ 4454 </item> 4455 <label> 4456 Description: 4457 </label> 4458 <item> 4459 This keyword defines where the area setup files are located when 4460 <ref target=AREAFILE><kw/AREAFILE/</ref> keyword is used. It is 4461 also defines default path for the semaphores. 4462 </item> 4463 <label> 4464 Parameters: 4465 </label> 4466 <item> 4467 The <ident/path/ defines the path to the area setup files. 4468 </item> 4469 <label> 4470 Notes: 4471 </label> 4472 <item> 4473 Most <ref target=AREAFILE><kw/AREAFILE/</ref> types can find the path 4474 using the environment variable(s) specific for the program(s). Such 4475 environment variables (or a path specified with the 4476 <ref target=AREAFILE><kw/AREAFILE/</ref> definition) always overrides 4477 the <ref target=AREAFILE><kw/AREAFILE/</ref>. 4478 </item> 4479 <label> 4480 Processed by: 4481 </label> 4482 <item> 4483 Mail reader. 4484 </item> 4485 <label> 4486 See also: 4487 </label> 4488 <item> 4489 <ptr target=AREACONFIGURATION> chapter, 4490 <ref target=AREAFILE><kw/AREAFILE/</ref>, 4491 <ref target=SEMAPHORE><kw/SEMAPHORE/</ref> 4492 </item> 4493 </list> 4494 </div2> 4495 <div2 id=AREAPMSCAN> 4496 <head> 4497 AREAPMSCAN 4498 </head> 4499 <list type=gloss> 4500 <label> 4501 Synopsis: 4502 </label> 4503 <item> 4504 <kw/AREAPMSCAN/ <ident/<echoid mask>/ 4505 </item> 4506 <label> 4507 Description: 4508 </label> 4509 <item> 4510 This keyword defines areas which will be automatically scanned for 4511 personal mail when starting <name/GoldED+/. 4512 </item> 4513 <label> 4514 Parameters: 4515 </label> 4516 <item> 4517 The <ident/<echoid mask>/ may contain <name/4DOS/-style 4518 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 4519 with commas. If mask started with the > (greater) character, then 4520 it represent group ID. 4521 </item> 4522 <label> 4523 Notes: 4524 </label> 4525 <item> 4526 It is recommended to have to scan all areas at startup. If you don't 4527 want to wait for the scan to complete, you can abort the scan by 4528 pressing <ESC> during startup. 4529 </item> 4530 <label> 4531 Processed by: 4532 </label> 4533 <item> 4534 Mail reader. 4535 </item> 4536 <label> 4537 See also: 4538 </label> 4539 <item> 4540 <ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>, 4541 <ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>, 4542 <ref target=AREASCAN><kw/AREASCAN/</ref>, 4543 <ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>, 4544 <ref target=AREASCANINCL><kw/AREASCANINCL/</ref> 4545 </item> 4546 <label> 4547 Example: 4548 </label> 4549 <item><eg> 4550AREAPMSCAN * ; Scan all areas. 4551AREAPMSCAN *INTER* ; Scan all areas containing INTER anywhere in the 4552 ; echoid 4553AREAPMSCAN INT*.* ; Scan all areas beginning with INT and 4554 ; containing a dot anywhere in the echoid</eg> 4555 </item> 4556 </list> 4557 </div2> 4558 <div2 id=AREAPMSCANEXCL> 4559 <head> 4560 AREAPMSCANEXCL 4561 </head> 4562 <list type=gloss> 4563 <label> 4564 Synopsis: 4565 </label> 4566 <item> 4567 <kw/AREAPMSCANEXCL/ <ident/<echoid mask>/ 4568 </item> 4569 <label> 4570 Description: 4571 </label> 4572 <item> 4573 With this keyword you can prevent areas from being scanned with 4574 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref> on startup. 4575 </item> 4576 <label> 4577 Parameters: 4578 </label> 4579 <item> 4580 The <ident/<echoid mask>/ may contain <name/4DOS/-style 4581 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 4582 with commas. If mask started with the > (greater) character, then 4583 it represent group ID. 4584 </item> 4585 <label> 4586 Notes: 4587 </label> 4588 <item> 4589 This is good if you use <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref> 4590 to scan all areas, but have some big areas which slows it down.<lb> 4591 You can use the <ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref> 4592 keyword to reinclude areas which have been excluded with 4593 <kw/AREAPMSCANEXCL/. 4594 </item> 4595 <label> 4596 Processed by: 4597 </label> 4598 <item> 4599 Mail reader. 4600 </item> 4601 <label> 4602 See also: 4603 </label> 4604 <item> 4605 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>, 4606 <ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>, 4607 <ref target=AREASCAN><kw/AREASCAN/</ref>, 4608 <ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>, 4609 <ref target=AREASCANINCL><kw/AREASCANINCL/</ref> 4610 </item> 4611 </list> 4612 </div2> 4613 <div2 id=AREAPMSCANINCL> 4614 <head> 4615 AREAPMSCANINCL 4616 </head> 4617 <list type=gloss> 4618 <label> 4619 Synopsis: 4620 </label> 4621 <item> 4622 <kw/AREAPMSCANINCL/ <ident/<echoid mask>/ 4623 </item> 4624 <label> 4625 Description: 4626 </label> 4627 <item> 4628 This keyword allows to specify areas which are to be scanned with 4629 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref> even if they were 4630 excluded with <ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>. 4631 Useful for partial reversal of wildcard specs in the excludes. 4632 </item> 4633 <label> 4634 Parameters: 4635 </label> 4636 <item> 4637 The <ident/<echoid mask>/ may contain <name/4DOS/-style 4638 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 4639 with commas. If mask started with the > (greater) character, then 4640 it represent group ID. 4641 </item> 4642 <label> 4643 Processed by: 4644 </label> 4645 <item> 4646 Mail reader. 4647 </item> 4648 <label> 4649 See also: 4650 </label> 4651 <item> 4652 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>, 4653 <ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>, 4654 <ref target=AREASCAN><kw/AREASCAN/</ref>, 4655 <ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>, 4656 <ref target=AREASCANINCL><kw/AREASCANINCL/</ref> 4657 </item> 4658 </list> 4659 </div2> 4660 <div2 id=AREAREADONLY> 4661 <head> 4662 AREAREADONLY 4663 </head> 4664 <list type=gloss> 4665 <label> 4666 Synopsis: 4667 </label> 4668 <item> 4669 <kw/AREAREADONLY/ <ident><SOFT/HARD></ident> 4670 </item> 4671 <label> 4672 Description: 4673 </label> 4674 <item> 4675 This option is designed for those who setup a system for new computer 4676 users who might be confused enough to enter a message in a read-only 4677 area despite the warning menu. 4678 </item> 4679 <label> 4680 Parameters: 4681 </label> 4682 <item> 4683 If this keyword is set to <ident/HARD/, it is no longer possible to 4684 enter/reply/change messages in areas marked read-only with the 4685 <gi>R/O</gi> area attribute. The <ident/SOFT/ setting uses a menu to 4686 ask permission as in the previous versions. 4687 </item> 4688 <label> 4689 Default: 4690 </label> 4691 <item> 4692 <ident/SOFT/ 4693 </item> 4694 <label> 4695 Processed by: 4696 </label> 4697 <item> 4698 Mail reader. 4699 </item> 4700 <label> 4701 See also: 4702 </label> 4703 <item> 4704 <ptr target=MESSAGEATTRS> chapter, 4705 <ref target=AREA><kw/AREA/</ref>, 4706 <ref target=AREADEF><kw/AREADEF/</ref>, 4707 <ref target=AREADESC><kw/AREADESC/</ref> 4708 </item> 4709 </list> 4710 </div2> 4711 <div2 id=AREARENAME> 4712 <head> 4713 AREARENAME 4714 </head> 4715 <list type=gloss> 4716 <label> 4717 Synopsis: 4718 </label> 4719 <item> 4720 <kw/AREARENAME/ <ident/<from echoid> <to echoid>/ 4721 </item> 4722 <label> 4723 Description: 4724 </label> 4725 <item> 4726 Renames one echoid to another. The feature is meant to be used in 4727 connection with <kw>AREAFILE</kw>, where some types do not store 4728 echoids with the areas (and <name>GoldED+</name> then automatically 4729 gives them unique echoids). Also you may rename areas with long 4730 echoid to the shorter one. 4731 </item> 4732 <label> 4733 Parameters: 4734 </label> 4735 <item> 4736 <ident/<From echoid>/ defines the original name for the area 4737 (given by the <name/GoldED+/ automatically) and 4738 <ident/<to echoid>/ defines echoid in the form it will be 4739 listed in the arealist. 4740 </item> 4741 <label> 4742 Processed by: 4743 </label> 4744 <item> 4745 Mail reader. 4746 </item> 4747 <label> 4748 See also: 4749 </label> 4750 <item> 4751 <ref target=AREAAUTOID><kw/AREAAUTOID/</ref>, 4752 <ref target=AREAFILE><kw/AREAFILE/</ref>, 4753 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref> 4754 </item> 4755 <label> 4756 Example: 4757 </label> 4758 <item><eg> 4759AREARENAME NET001 NETMAIL 4760AREARENAME ECHO001 BAD_MSGS 4761AREARENAME LOCAL001 BBS.USERS</eg> 4762 </item> 4763 </list> 4764 </div2> 4765 <div2 id=AREAREPLYDIRECT> 4766 <head> 4767 AREAREPLYDIRECT 4768 </head> 4769 <list type=gloss> 4770 <label> 4771 Synopsis: 4772 </label> 4773 <item> 4774 <kw/AREAREPLYDIRECT/ <ident><YES/NO></ident> 4775 </item> 4776 <label> 4777 Description: 4778 </label> 4779 <item> 4780 This keyword controls whether <!-- FIX ME!!! --><kw/READcommentmsg/, 4781 <!-- FIX ME!!! --><kw/READquotemsg/, and 4782 <!-- FIX ME!!! --><kw/READreplymsg/ functions should reply 4783 to the different area bypassing area selection screen. The 4784 destination area is choosen as follows: 4785 <list type=simple> 4786 <item> 4787 Contents of the <gi/AREA/ kludge if enabled with 4788 <ref target=USEAREA><kw/USEAREA/</ref>. 4789 </item> 4790 <item> 4791 Area set with <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> 4792 keyword. 4793 </item> 4794 <item> 4795 Current area. 4796 </item> 4797 </list> 4798 </item> 4799 <label> 4800 Parameters: 4801 </label> 4802 <item> 4803 If enabled, <name/GoldED+/ will bypass area selection screen, if 4804 disabled - will not. 4805 </item> 4806 <label> 4807 Default: 4808 </label> 4809 <item> 4810 <ident/NO/ 4811 </item> 4812 <label> 4813 Notes: 4814 </label> 4815 <item> 4816 This keyword can be used globally and in a 4817 <ref target=RANDOMSYSTEM>Random System</ref> group.<lb> 4818 It is probably not a good idea to enable this keyword globally.<lb> 4819 If you run a utility or have a mail processor which copies personal 4820 mail to a separate area and puts an <gi/AREA/ kludge at the top of 4821 the messages, you should create a random system group for the area 4822 and enable <kw>AREAREPLYDIRECT</kw> in it. 4823 </item> 4824 <label> 4825 Processed by: 4826 </label> 4827 <item> 4828 Mail reader. 4829 </item> 4830 <label> 4831 See also: 4832 </label> 4833 <item> 4834 <!-- FIX ME!!! --><kw/READcommentmsg/, 4835 <!-- FIX ME!!! --><kw/READquotemsg/, 4836 <!-- FIX ME!!! --><kw/READreplymsg/, 4837 <ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>, 4838 <ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>, 4839 <ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>, 4840 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> 4841 </item> 4842 <label> 4843 Example: 4844 </label> 4845 <item><eg> 4846GROUP ECHO_PERSONAL 4847 AREAREPLYDIRECT YES 4848ENDGROUP</eg> 4849 </item> 4850 </list> 4851 </div2> 4852 <div2 id=AREAREPLYTO> 4853 <head> 4854 AREAREPLYTO 4855 </head> 4856 <list type=gloss> 4857 <label> 4858 Synopsis: 4859 </label> 4860 <item> 4861 <kw/AREAREPLYTO/ <ident/<echoid>/ 4862 </item> 4863 <label> 4864 Description: 4865 </label> 4866 <item> 4867 Sets the default area for the reply and forward functions. Typically 4868 you could set it to a safe/permanent storage type of area. 4869 </item> 4870 <label> 4871 Parameters: 4872 </label> 4873 <item> 4874 The default destination area for the reply and forward functions. 4875 </item> 4876 <label> 4877 Default: 4878 </label> 4879 <item> 4880 First netmail area. 4881 </item> 4882 <label> 4883 Notes: 4884 </label> 4885 <item> 4886 This keyword can be used globally and in a 4887 <ref target=RANDOMSYSTEM>Random System</ref> group. 4888 </item> 4889 <label> 4890 Processed by: 4891 </label> 4892 <item> 4893 Mail reader. 4894 </item> 4895 <label> 4896 See also: 4897 </label> 4898 <item> 4899 <!-- FIX ME!!! --><kw/READcopymoveforward/, 4900 <!-- FIX ME!!! --><kw/READmovecommentmsg/, 4901 <!-- FIX ME!!! --><kw/READmovequotemsg/, 4902 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 4903 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref>, 4904 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref>, 4905 <ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>, 4906 <ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref> 4907 </item> 4908 </list> 4909 </div2> 4910 <div2 id=AREASCAN> 4911 <head> 4912 AREASCAN 4913 </head> 4914 <list type=gloss> 4915 <label> 4916 Synopsis: 4917 </label> 4918 <item> 4919 <kw/AREASCAN/ <ident/<echoid mask>/ 4920 </item> 4921 <label> 4922 Description: 4923 </label> 4924 <item> 4925 This keyword defines areas which will be automatically scanned for 4926 new mail when starting <name/GoldED+/. 4927 </item> 4928 <label> 4929 Parameters: 4930 </label> 4931 <item> 4932 The <ident/<echoid mask>/ may contain <name/4DOS/-style 4933 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 4934 with commas. If mask started with the > (greater) character, then 4935 it represent group ID. 4936 </item> 4937 <label> 4938 Notes: 4939 </label> 4940 <item> 4941 It is recommended to have to scan all areas at startup. If you don't 4942 want to wait for the scan to complete, you can abort the scan by 4943 pressing <ESC> during startup. 4944 </item> 4945 <label> 4946 Processed by: 4947 </label> 4948 <item> 4949 Mail reader. 4950 </item> 4951 <label> 4952 See also: 4953 </label> 4954 <item> 4955 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>, 4956 <ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>, 4957 <ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>, 4958 <ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>, 4959 <ref target=AREASCANINCL><kw/AREASCANINCL/</ref> 4960 </item> 4961 <label> 4962 Example: 4963 </label> 4964 <item><eg> 4965AREASCAN * ; Scan all areas. 4966AREASCAN *INTER* ; Scan all areas containing INTER anywhere in the 4967 ; echoid 4968AREASCAN INT*.* ; Scan all areas beginning with INT and 4969 ; containing a dot anywhere in the echoid</eg> 4970 </item> 4971 </list> 4972 </div2> 4973 <div2 id=AREASCANEXCL> 4974 <head> 4975 AREASCANEXCL 4976 </head> 4977 <list type=gloss> 4978 <label> 4979 Synopsis: 4980 </label> 4981 <item> 4982 <kw/AREASCANEXCL/ <ident/<echoid mask>/ 4983 </item> 4984 <label> 4985 Description: 4986 </label> 4987 <item> 4988 With this keyword you can prevent areas from being scanned with 4989 <ref target=AREASCAN><kw/AREASCAN/</ref> on startup. 4990 </item> 4991 <label> 4992 Parameters: 4993 </label> 4994 <item> 4995 The <ident/<echoid mask>/ may contain <name/4DOS/-style 4996 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 4997 with commas. If mask started with the > (greater) character, then 4998 it represent group ID. 4999 </item> 5000 <label> 5001 Notes: 5002 </label> 5003 <item> 5004 This is good if you use <ref target=AREASCAN><kw/AREASCAN/</ref> 5005 to scan all areas, but have some big areas which slows it down.<lb> 5006 You can use the <ref target=AREASCANINCL><kw/AREASCANINCL/</ref> 5007 keyword to reinclude areas which have been excluded with 5008 <kw/AREASCANEXCL/. 5009 </item> 5010 <label> 5011 Processed by: 5012 </label> 5013 <item> 5014 Mail reader. 5015 </item> 5016 <label> 5017 See also: 5018 </label> 5019 <item> 5020 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>, 5021 <ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>, 5022 <ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>, 5023 <ref target=AREASCAN><kw/AREASCAN/</ref>, 5024 <ref target=AREASCANINCL><kw/AREASCANINCL/</ref> 5025 </item> 5026 </list> 5027 </div2> 5028 <div2 id=AREASCANINCL> 5029 <head> 5030 AREASCANINCL 5031 </head> 5032 <list type=gloss> 5033 <label> 5034 Synopsis: 5035 </label> 5036 <item> 5037 <kw/AREASCANINCL/ <ident/<echoid mask>/ 5038 </item> 5039 <label> 5040 Description: 5041 </label> 5042 <item> 5043 This keyword allows to specify areas which are to be scanned with 5044 <ref target=AREASCAN><kw/AREASCAN/</ref> even if they were 5045 excluded with <ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>. 5046 Useful for partial reversal of wildcard specs in the excludes. 5047 </item> 5048 <label> 5049 Parameters: 5050 </label> 5051 <item> 5052 The <ident/<echoid mask>/ may contain <name/4DOS/-style 5053 wildcards (<q/*/ and <q/?/). You may specify multiple masks separated 5054 with commas. If mask started with the > (greater) character, then 5055 it represent group ID. 5056 </item> 5057 <label> 5058 Processed by: 5059 </label> 5060 <item> 5061 Mail reader. 5062 </item> 5063 <label> 5064 See also: 5065 </label> 5066 <item> 5067 <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>, 5068 <ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>, 5069 <ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref> 5070 <ref target=AREASCAN><kw/AREASCAN/</ref>, 5071 <ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>, 5072 </item> 5073 </list> 5074 </div2> 5075 <div2 id=AREASCANSORT> 5076 <head> 5077 AREASCANSORT 5078 </head> 5079 <list type=gloss> 5080 <label> 5081 Synopsis: 5082 </label> 5083 <item> 5084 <kw/AREASCANSORT/ <ident/<sortspec>/ 5085 </item> 5086 <label> 5087 Description: 5088 </label> 5089 <item> 5090 When scanning areas, <name/GoldED+/ can optimize area scanning 5091 speed if it first sorts the arealist in an order so that each msgbase 5092 format is scanned in sequence rather than on semi-random order. 5093 </item> 5094 <label> 5095 Parameters: 5096 </label> 5097 <item> 5098 The <sortspec> described in details in the 5099 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref> chapter. 5100 </item> 5101 <label> 5102 Default: 5103 </label> 5104 <item> 5105 <ident/XZBE/ 5106 </item> 5107 <label> 5108 Processed by: 5109 </label> 5110 <item> 5111 Mail reader. 5112 </item> 5113 <label> 5114 See also: 5115 </label> 5116 <item> 5117 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref> 5118 </item> 5119 </list> 5120 </div2> 5121 <div2 id=AREASEP> 5122 <head> 5123 AREASEP 5124 </head> 5125 <list type=gloss> 5126 <label> 5127 Synopsis: 5128 </label> 5129 <item> 5130 <kw/AREASEP/ <ident><echoid> <<![ CDATA ["desc"]]>> 5131 <group> <type> <aka></ident> 5132 </item> 5133 <label> 5134 Description: 5135 </label> 5136 <item> 5137 You can define area separation lines between groups or areatypes. 5138 </item> 5139 <label> 5140 Parameters: 5141 </label> 5142 <item> 5143 <table rows=9 cols=2> 5144 <row> 5145 <cell> 5146 <ident/echoid/ 5147 </cell> 5148 <cell> 5149 Mail area identifier. 5150 </cell> 5151 </row> 5152 <row> 5153 <cell> 5154 <ident><![ CDATA ["desc"]]></ident> 5155 </cell> 5156 <cell> 5157 Area description in quotes. 5158 </cell> 5159 </row> 5160 <row> 5161 <cell> 5162 <ident/group/ 5163 </cell> 5164 <cell> 5165 Group ID uppercase letter (A-Z) or 0 if not in a group. Use 5166 #groupnumber to specify group numbers in the 1-999 range. 5167 </cell> 5168 </row> 5169 <row> 5170 <cell> 5171 <ident/type/ 5172 </cell> 5173 <cell> 5174 <ident/Net/, <ident/Echo/, <ident/Local/, <ident/EMail/ or 5175 <ident/News/. 5176 </cell> 5177 </row> 5178 <row> 5179 <cell> 5180 <ident>aka</ident> 5181 </cell> 5182 <cell> 5183 Address for the area, or <q>.</q> for the main address. 5184 </cell> 5185 </row> 5186 </table> 5187 </item> 5188 <label> 5189 Notes: 5190 </label> 5191 <item> 5192 The area separation lines are implemented like a special kind of 5193 area, and are therefore sorted in the arealist just as if they were 5194 actual areas. This is also the reason why you can place the cursor 5195 bar on the separation lines. The fuzzy feature may be used to quickly 5196 go to an area group, that's why cursor can be placed on separation 5197 lines.<lb> 5198 When configuring area separation lines, be careful to consider the 5199 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref>, so that the lines 5200 are sorted into the positions you want. If you don't sort areas, you 5201 must make sure that the <kw/AREASEP/ definitions are placed correctly 5202 in your configuration file, that is, between/before 5203 <ref target=AREA><kw/AREA/</ref> and 5204 <ref target=AREADEF><kw/AREADEF/</ref> lines.<lb> 5205 You will note that the separation lines are not fully connected into 5206 the left and right edges. This is both by design and for practical 5207 reasons (easier to implement), not a bug.<lb> 5208 Currently the descriptions are hardcoded to the natural location in 5209 the description column. 5210 </item> 5211 <label> 5212 Processed by: 5213 </label> 5214 <item> 5215 Mail reader. 5216 </item> 5217 <label> 5218 See also: 5219 </label> 5220 <item> 5221 <ref target=AREA><kw/AREA/</ref>, 5222 <ref target=AREADEF><kw/AREADEF/</ref>, 5223 <ref target=AREAFILE><kw/AREAFILE/</ref>, 5224 <ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>, 5225 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 5226 <ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>, 5227 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref>, 5228 <ref target=AREATYPEORDER><kw/AREATYPEORDER/</ref> 5229 </item> 5230 <label> 5231 Example: 5232 </label> 5233 <item><eg><![ CDATA [ 5234; In this example areas will be separated by types 5235AREALISTSORT TYUE 5236AREASEP !NET "Netmail areas" 0 Net 5237AREASEP !EMAIL "E-mail areas" 0 EMail 5238AREASEP !ECHO "Echomail areas" 0 Echo 5239AREASEP !NEWS "Newsgroup areas" 0 News 5240AREASEP !LOCAL "Local areas" 0 Local]]></eg> 5241 <eg><![ CDATA [ 5242; And in this one areas will be separated by groups 5243AREALISTSORT GYUE 5244AREASEP !A "Group A" A Local 5245AREASEP !B "Group B" B Local 5246AREASEP !C "Group C" C Local]]></eg> 5247 </item> 5248 </list> 5249 </div2> 5250 <div2 id=AREASTART> 5251 <head> 5252 AREASTART 5253 </head> 5254 <list type=gloss> 5255 <label> 5256 Synopsis: 5257 </label> 5258 <item> 5259 <kw/AREASTART/ <ident/<echoid>/ 5260 </item> 5261 <label> 5262 Description: 5263 </label> 5264 <item> 5265 Normally <name>GoldED+</name> starts by displaying the arealist, to 5266 let you select which area you want to read. If this keyword is 5267 defined, the arealist is bypassed and <name/GoldED+/ starts directly 5268 in the configured area. You can override <kw>AREASTART</kw> with the 5269 <code>-e</code> commandline switch. 5270 </item> 5271 <label> 5272 Parameters: 5273 </label> 5274 <item> 5275 The <ident/<echoid>/ parameter specifies the echo 5276 <name/GoldED+/ should start directly in. 5277 </item> 5278 <label> 5279 Processed by: 5280 </label> 5281 <item> 5282 Mail reader. 5283 </item> 5284 <label> 5285 See also: 5286 </label> 5287 <item> 5288 <ptr target=COMMANDLINE> chapter 5289 </item> 5290 </list> 5291 </div2> 5292 <div2 id=AREATYPEORDER> 5293 <head> 5294 AREATYPEORDER 5295 </head> 5296 <list type=gloss> 5297 <label> 5298 Synopsis: 5299 </label> 5300 <item> 5301 <kw/AREATYPEORDER/ <ident><type1> <type2> <type3> 5302 <type4> <type5></ident> 5303 </item> 5304 <label> 5305 Description: 5306 </label> 5307 <item> 5308 This keyword allows you to change the ordering of the different 5309 area types when sorted by 5310 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref>. 5311 </item> 5312 <label> 5313 Parameters: 5314 </label> 5315 <item> 5316 The following types are allowed: <ident/NET/, <ident/ECHO/, 5317 <ident/LOCAL/, <ident/EMAIL/ and <ident/NEWS/. 5318 </item> 5319 <label> 5320 Default: 5321 </label> 5322 <item> 5323 <ident/NET/ <ident/EMAIL/ <ident/ECHO/ <ident/NEWS/ <ident/LOCAL/ 5324 </item> 5325 <label> 5326 Processed by: 5327 </label> 5328 <item> 5329 Mail reader. 5330 </item> 5331 <label> 5332 See also: 5333 </label> 5334 <item> 5335 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 5336 <ref target=AREALISTSORT><kw/AREALISTSORT/</ref> 5337 </item> 5338 </list> 5339 </div2> 5340 <div2 id=AREAYOUWROTETO> 5341 <head> 5342 AREAYOUWROTETO 5343 </head> 5344 <list type=gloss> 5345 <label> 5346 Synopsis: 5347 </label> 5348 <item> 5349 <kw/AREAYOUWROTETO/ <ident/<echoid>/ 5350 </item> 5351 <label> 5352 Description: 5353 </label> 5354 <item> 5355 <name/GoldED+/ automatically copies mails written by yourself to the 5356 given area when saving a new mail. <name/GoldED+/ will also add an 5357 <gi/AREA/ kludge so you can see from which area the mail originally 5358 is copied from. 5359 </item> 5360 <label> 5361 Parameters: 5362 </label> 5363 <item> 5364 The default destination area for the mails written by you. 5365 </item> 5366 <label> 5367 Notes: 5368 </label> 5369 <item> 5370 This keyword can be used globally and in a 5371 <ref target=RANDOMSYSTEM>Random System</ref> group.<lb> 5372 The mail will not be copied if you use 5373 <!-- FIX ME!!! -->READchangemsg function. 5374 </item> 5375 <label> 5376 Processed by: 5377 </label> 5378 <item> 5379 Mail reader. 5380 </item> 5381 <label> 5382 See also: 5383 </label> 5384 <item> 5385 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 5386 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref>, 5387 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref>, 5388 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> 5389 </item> 5390 </list> 5391 </div2> 5392 <div2> 5393 <head> 5394 ASKDELORIG 5395 </head> 5396 <list type=gloss> 5397 <label> 5398 Synopsis: 5399 </label> 5400 <item> 5401 <kw/ASKDELORIG/ <ident><YES/NO></ident> 5402 </item> 5403 <label> 5404 Description: 5405 </label> 5406 <item> 5407 This keyword allows to automatically delete mail in netmail and local 5408 area after replying on it. 5409 </item> 5410 <label> 5411 Parameters: 5412 </label> 5413 <item> 5414 If enabled, you will be asked if the message you just replied to 5415 should be deleted. Otherwise it is left untouched. 5416 </item> 5417 <label> 5418 Default: 5419 </label> 5420 <item> 5421 <ident/NO/ 5422 </item> 5423 <label> 5424 Notes: 5425 </label> 5426 <item> 5427 This keyword is only functional in netmail and local areas. 5428 </item> 5429 <label> 5430 Processed by: 5431 </label> 5432 <item> 5433 Mail reader. 5434 </item> 5435 <label> 5436 See also: 5437 </label> 5438 <item> 5439 <!-- FIX ME!!! --><kw/READcommentmsg/, 5440 <!-- FIX ME!!! --><kw/READmovecommentmsg/, 5441 <!-- FIX ME!!! --><kw/READmovequotemsg/, 5442 <!-- FIX ME!!! --><kw/READquotemsg/, 5443 <!-- FIX ME!!! --><kw/READreplymsg/, 5444 <ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>, 5445 <ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref>, 5446 <ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref> 5447 </item> 5448 </list> 5449 </div2> 5450 <div2 id=ATTACHPATH> 5451 <head> 5452 ATTACHPATH 5453 </head> 5454 <list type=gloss> 5455 <label> 5456 Synopsis: 5457 </label> 5458 <item> 5459 <kw/ATTACHPATH/ <ident/<path>/ 5460 </item> 5461 <label> 5462 Description: 5463 </label> 5464 <item> 5465 Defines the default path when selecting files for attachement. 5466 </item> 5467 <label> 5468 Parameters: 5469 </label> 5470 <item> 5471 The default <ident/path/ for the fileattach feature. 5472 </item> 5473 <label> 5474 Processed by: 5475 </label> 5476 <item> 5477 Mail reader. 5478 </item> 5479 <label> 5480 See also: 5481 </label> 5482 <item> 5483 <ptr target=MESSAGEATTRS> chapter, 5484 <ptr target=FILESELECTION> chapter, 5485 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5486 <ref target=EDITAUTOATTACH><kw/EDITAUTOATTACH/</ref> 5487 </item> 5488 </list> 5489 </div2> 5490 <div2 id=ATTRIBSATTACH> 5491 <head> 5492 ATTRIBSATTACH 5493 </head> 5494 <list type=gloss> 5495 <label> 5496 Synopsis: 5497 </label> 5498 <item> 5499 <kw/ATTRIBSATTACH/ <ident/<attributes>/ 5500 </item> 5501 <label> 5502 Description: 5503 </label> 5504 <item> 5505 Defines the attributes that are <hi>added</hi> to the existing 5506 attributes of a message when the file attach attribute is toggled on. 5507 </item> 5508 <label> 5509 Parameters: 5510 </label> 5511 <item> 5512 Available <ident/attributes/ are described in the 5513 <ptr target=MESSAGEATTRS> chapter. 5514 </item> 5515 <label> 5516 Default: 5517 </label> 5518 <item> 5519 <gi/LOC/ 5520 </item> 5521 <label> 5522 Processed by: 5523 </label> 5524 <item> 5525 Mail reader. 5526 </item> 5527 <label> 5528 See also: 5529 </label> 5530 <item> 5531 <ptr target=MESSAGEATTRS> chapter, 5532 <ref target=ATTACHPATH><kw/ATTACHPATH/</ref>, 5533 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 5534 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 5535 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 5536 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 5537 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 5538 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 5539 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 5540 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5541 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5542 <ref target=DISPATTACHSIZE><kw/DISPATTACHSIZE/</ref> 5543 </item> 5544 </list> 5545 </div2> 5546 <div2 id=ATTRIBSCC> 5547 <head> 5548 ATTRIBSCC 5549 </head> 5550 <list type=gloss> 5551 <label> 5552 Synopsis: 5553 </label> 5554 <item> 5555 <kw/ATTRIBSCC/ <ident/<attributes>/ 5556 </item> 5557 <label> 5558 Description: 5559 </label> 5560 <item> 5561 Defines the default attributes of carbon copy messages. <abbr/CC/ 5562 attributes are <hi/added/ to the existing attributes of the 5563 original message. Usually used to add the <gi>K/S</gi> attribute. 5564 </item> 5565 <label> 5566 Parameters: 5567 </label> 5568 <item> 5569 Available <ident/attributes/ are described in the 5570 <ptr target=MESSAGEATTRS> chapter. 5571 </item> 5572 <label> 5573 Default: 5574 </label> 5575 <item> 5576 <gi/LOC/ 5577 </item> 5578 <label> 5579 Processed by: 5580 </label> 5581 <item> 5582 Mail reader. 5583 </item> 5584 <label> 5585 See also: 5586 </label> 5587 <item> 5588 <ptr target=MESSAGEATTRS> chapter, 5589 <!-- FIX ME!!! -->Carbon Copy and Crossposting chapter, 5590 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 5591 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5592 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 5593 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 5594 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 5595 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 5596 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 5597 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 5598 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5599 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5600 <ref target=CARBONCOPYLIST><kw/CARBONCOPYLIST/</ref> 5601 </item> 5602 </list> 5603 </div2> 5604 <div2 id=ATTRIBSCFM> 5605 <head> 5606 ATTRIBSCFM 5607 </head> 5608 <list type=gloss> 5609 <label> 5610 Synopsis: 5611 </label> 5612 <item> 5613 <kw/ATTRIBSCFM/ <ident/<attributes>/ 5614 </item> 5615 <label> 5616 Description: 5617 </label> 5618 <item> 5619 Defines the default attributes of the confirmation receipt message. 5620 </item> 5621 <label> 5622 Parameters: 5623 </label> 5624 <item> 5625 Available <ident/attributes/ are described in the 5626 <ptr target=MESSAGEATTRS> chapter. 5627 </item> 5628 <label> 5629 Default: 5630 </label> 5631 <item> 5632 <gi/LOC/ 5633 </item> 5634 <label> 5635 Notes: 5636 </label> 5637 <item> 5638 Suggested attribute is: <gi/RRC/. 5639 </item> 5640 <label> 5641 Processed by: 5642 </label> 5643 <item> 5644 Mail reader. 5645 </item> 5646 <label> 5647 See also: 5648 </label> 5649 <item> 5650 <ptr target=MESSAGEATTRS> chapter, 5651 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 5652 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5653 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 5654 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 5655 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 5656 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 5657 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 5658 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 5659 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5660 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5661 <ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>, 5662 <ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>, 5663 <ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref> 5664 </item> 5665 </list> 5666 </div2> 5667 <div2 id=ATTRIBSECHO> 5668 <head> 5669 ATTRIBSECHO 5670 </head> 5671 <list type=gloss> 5672 <label> 5673 Synopsis: 5674 </label> 5675 <item> 5676 <kw/ATTRIBSECHO/ <ident/<attributes>/ 5677 </item> 5678 <label> 5679 Description: 5680 </label> 5681 <item> 5682 Defines the default attributes of messages entered in echomail areas. 5683 </item> 5684 <label> 5685 Parameters: 5686 </label> 5687 <item> 5688 Available <ident/attributes/ are described in the 5689 <ptr target=MESSAGEATTRS> chapter. 5690 </item> 5691 <label> 5692 Default: 5693 </label> 5694 <item> 5695 <gi/LOC/ 5696 </item> 5697 <label> 5698 Processed by: 5699 </label> 5700 <item> 5701 Mail reader. 5702 </item> 5703 <label> 5704 See also: 5705 </label> 5706 <item> 5707 <ptr target=MESSAGEATTRS> chapter, 5708 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 5709 <ref target=AREA><kw/AREA/</ref>, 5710 <ref target=AREADEF><kw/AREADEF/</ref>, 5711 <ref target=AREADESC><kw/AREADESC/</ref>, 5712 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5713 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 5714 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 5715 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 5716 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 5717 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 5718 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 5719 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5720 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5721 <ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref> 5722 </item> 5723 </list> 5724 </div2> 5725 <div2 id=ATTRIBSEMAIL> 5726 <head> 5727 ATTRIBSEMAIL 5728 </head> 5729 <list type=gloss> 5730 <label> 5731 Synopsis: 5732 </label> 5733 <item> 5734 <kw/ATTRIBSEMAIL/ <ident/<attributes>/ 5735 </item> 5736 <label> 5737 Description: 5738 </label> 5739 <item> 5740 Defines the default attributes of messages entered in e-mail areas. 5741 </item> 5742 <label> 5743 Parameters: 5744 </label> 5745 <item> 5746 Available <ident/attributes/ are described in the 5747 <ptr target=MESSAGEATTRS> chapter. 5748 </item> 5749 <label> 5750 Default: 5751 </label> 5752 <item> 5753 <gi/LOC/ 5754 </item> 5755 <label> 5756 Processed by: 5757 </label> 5758 <item> 5759 Mail reader. 5760 </item> 5761 <label> 5762 See also: 5763 </label> 5764 <item> 5765 <ptr target=MESSAGEATTRS> chapter, 5766 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 5767 <ref target=AREA><kw/AREA/</ref>, 5768 <ref target=AREADEF><kw/AREADEF/</ref>, 5769 <ref target=AREADESC><kw/AREADESC/</ref>, 5770 <ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>, 5771 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5772 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 5773 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 5774 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 5775 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 5776 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 5777 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 5778 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5779 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5780 <ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref> 5781 </item> 5782 </list> 5783 </div2> 5784 <div2 id=ATTRIBSFRQ> 5785 <head> 5786 ATTRIBSFRQ 5787 </head> 5788 <list type=gloss> 5789 <label> 5790 Synopsis: 5791 </label> 5792 <item> 5793 <kw/ATTRIBSFRQ/ <ident/<attributes>/ 5794 </item> 5795 <label> 5796 Description: 5797 </label> 5798 <item> 5799 Defines the attributes to use for messages generated with the file 5800 request function. 5801 </item> 5802 <label> 5803 Parameters: 5804 </label> 5805 <item> 5806 Available <ident/attributes/ are described in the 5807 <ptr target=MESSAGEATTRS> chapter. 5808 </item> 5809 <label> 5810 Default: 5811 </label> 5812 <item> 5813 <gi/FRQ/ <gi/LOC/ 5814 </item> 5815 <label> 5816 Notes: 5817 </label> 5818 <item> 5819 Suggested attributes are: <gi/PVT/ <gi>K/S</gi> <gi/CRA/. 5820 </item> 5821 <label> 5822 Processed by: 5823 </label> 5824 <item> 5825 Mail reader. 5826 </item> 5827 <label> 5828 See also: 5829 </label> 5830 <item> 5831 <ptr target=MESSAGEATTRS> chapter, 5832 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 5833 <ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>, 5834 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref>, 5835 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5836 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 5837 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 5838 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 5839 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 5840 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 5841 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 5842 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5843 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5844 <ref target=FRQEXT><kw/FRQEXT/</ref>, 5845 <ref target=FRQNODEMAP><kw/FRQNODEMAP/</ref>, 5846 <ref target=FRQOPTIONS><kw/FRQOPTIONS/</ref>, 5847 <ref target=FRQWAZOO><kw/FRQWAZOO/</ref>, 5848 <ref target=OUTBOUNDPATH><kw/OUTBOUNDPATH/</ref> 5849 </item> 5850 </list> 5851 </div2> 5852 <div2 id=ATTRIBSLOCAL> 5853 <head> 5854 ATTRIBSLOCAL 5855 </head> 5856 <list type=gloss> 5857 <label> 5858 Synopsis: 5859 </label> 5860 <item> 5861 <kw/ATTRIBSLOCAL/ <ident/<attributes>/ 5862 </item> 5863 <label> 5864 Description: 5865 </label> 5866 <item> 5867 Defines the default attributes of messages entered in local areas. 5868 </item> 5869 <label> 5870 Parameters: 5871 </label> 5872 <item> 5873 Available <ident/attributes/ are described in the 5874 <ptr target=MESSAGEATTRS> chapter. 5875 </item> 5876 <label> 5877 Default: 5878 </label> 5879 <item> 5880 <gi/LOC/ 5881 </item> 5882 <label> 5883 Processed by: 5884 </label> 5885 <item> 5886 Mail reader. 5887 </item> 5888 <label> 5889 See also: 5890 </label> 5891 <item> 5892 <ptr target=MESSAGEATTRS> chapter, 5893 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 5894 <ref target=AREA><kw/AREA/</ref>, 5895 <ref target=AREADEF><kw/AREADEF/</ref>, 5896 <ref target=AREADESC><kw/AREADESC/</ref>, 5897 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5898 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 5899 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 5900 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 5901 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 5902 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 5903 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 5904 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5905 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5906 <ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref> 5907 </item> 5908 </list> 5909 </div2> 5910 <div2 id=ATTRIBSNET> 5911 <head> 5912 ATTRIBSNET 5913 </head> 5914 <list type=gloss> 5915 <label> 5916 Synopsis: 5917 </label> 5918 <item> 5919 <kw/ATTRIBSNET/ <ident/<attributes>/ 5920 </item> 5921 <label> 5922 Description: 5923 </label> 5924 <item> 5925 Defines the default attributes of messages entered in netmail areas. 5926 </item> 5927 <label> 5928 Parameters: 5929 </label> 5930 <item> 5931 Available <ident/attributes/ are described in the 5932 <ptr target=MESSAGEATTRS> chapter. 5933 </item> 5934 <label> 5935 Default: 5936 </label> 5937 <item> 5938 <gi/LOC/ 5939 </item> 5940 <label> 5941 Processed by: 5942 </label> 5943 <item> 5944 Mail reader. 5945 </item> 5946 <label> 5947 See also: 5948 </label> 5949 <item> 5950 <ptr target=MESSAGEATTRS> chapter, 5951 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 5952 <ref target=AREA><kw/AREA/</ref>, 5953 <ref target=AREADEF><kw/AREADEF/</ref>, 5954 <ref target=AREADESC><kw/AREADESC/</ref>, 5955 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 5956 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 5957 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 5958 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 5959 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 5960 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 5961 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 5962 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 5963 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 5964 <ref target=CTRLINFONET><kw/CTRLINFONET/</ref> 5965 </item> 5966 </list> 5967 </div2> 5968 <div2 id=ATTRIBSNEWS> 5969 <head> 5970 ATTRIBSNEWS 5971 </head> 5972 <list type=gloss> 5973 <label> 5974 Synopsis: 5975 </label> 5976 <item> 5977 <kw/ATTRIBSNEWS/ <ident/<attributes>/ 5978 </item> 5979 <label> 5980 Description: 5981 </label> 5982 <item> 5983 Defines the default attributes of messages entered in news groups. 5984 </item> 5985 <label> 5986 Parameters: 5987 </label> 5988 <item> 5989 Available <ident/attributes/ are described in the 5990 <ptr target=MESSAGEATTRS> chapter. 5991 </item> 5992 <label> 5993 Default: 5994 </label> 5995 <item> 5996 <gi/LOC/ 5997 </item> 5998 <label> 5999 Processed by: 6000 </label> 6001 <item> 6002 Mail reader. 6003 </item> 6004 <label> 6005 See also: 6006 </label> 6007 <item> 6008 <ptr target=MESSAGEATTRS> chapter, 6009 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 6010 <ref target=AREA><kw/AREA/</ref>, 6011 <ref target=AREADEF><kw/AREADEF/</ref>, 6012 <ref target=AREADESC><kw/AREADESC/</ref>, 6013 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 6014 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 6015 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 6016 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 6017 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 6018 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 6019 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 6020 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 6021 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 6022 <ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref> 6023 </item> 6024 </list> 6025 </div2> 6026 <div2 id=ATTRIBUTES> 6027 <head> 6028 ATTRIBUTES 6029 </head> 6030 <list type=gloss> 6031 <label> 6032 Synopsis: 6033 </label> 6034 <item> 6035 <kw/ATTRIBUTES/ <ident/<attributes>/ 6036 </item> 6037 <label> 6038 Description: 6039 </label> 6040 <item> 6041 Defines the default attributes for area members of the current 6042 <ref target=RANDOMSYSTEM>Random System</ref> group. 6043 </item> 6044 <label> 6045 Parameters: 6046 </label> 6047 <item> 6048 Available <ident/attributes/ are described in the 6049 <ptr target=MESSAGEATTRS> chapter. 6050 </item> 6051 <label> 6052 Notes: 6053 </label> 6054 <item> 6055 This keyword is valid <hi/ONLY/ in a 6056 <ref target=RANDOMSYSTEM>Random System</ref> group. 6057 </item> 6058 <label> 6059 Processed by: 6060 </label> 6061 <item> 6062 Mail reader. 6063 </item> 6064 <label> 6065 See also: 6066 </label> 6067 <item> 6068 <ptr target=MESSAGEATTRS> chapter, 6069 <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>, 6070 <ref target=AREA><kw/AREA/</ref>, 6071 <ref target=AREADEF><kw/AREADEF/</ref>, 6072 <ref target=AREADESC><kw/AREADESC/</ref>, 6073 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 6074 <ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>, 6075 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 6076 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 6077 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 6078 <ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>, 6079 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 6080 <ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>, 6081 <ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>, 6082 <ref target=CTRLINFO><kw/CTRLINFO/</ref> 6083 </item> 6084 </list> 6085 </div2> 6086 <div2 id=BEEPCOMMENT> 6087 <head> 6088 BEEPCOMMENT 6089 </head> 6090 <list type=gloss> 6091 <label> 6092 Synopsis: 6093 </label> 6094 <item> 6095 <kw/BEEPCOMMENT/ <ident><YES/NO></ident> 6096 </item> 6097 <label> 6098 Description: 6099 </label> 6100 <item> 6101 This keyword enables or disables noise when the cursor in the 6102 internal editor is moved across a word defined with the 6103 <ref target=EDITCOMMENT><kw/EDITCOMMENT/</ref> keyword. 6104 </item> 6105 <label> 6106 Parameters: 6107 </label> 6108 <item> 6109 If enabled, <name/GoldED+/ will make a noise, otherwise will not. 6110 </item> 6111 <label> 6112 Default: 6113 </label> 6114 <item> 6115 <ident/YES/ 6116 </item> 6117 <label> 6118 Processed by: 6119 </label> 6120 <item> 6121 Mail reader. 6122 </item> 6123 <label> 6124 See also: 6125 </label> 6126 <item> 6127 <ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>, 6128 <ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>, 6129 <ref target=BEEPNOISES><kw/BEEPNOISES/</ref>, 6130 <ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>, 6131 <ref target=EDITCOMMENT><kw/EDITCOMMENT/</ref>, 6132 <ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>, 6133 <ref target=SOUNDPATH><kw/SOUNDPATH/</ref> 6134 </item> 6135 </list> 6136 </div2> 6137 <div2 id=BEEPFACTOR> 6138 <head> 6139 BEEPFACTOR 6140 </head> 6141 <list type=gloss> 6142 <label> 6143 Synopsis: 6144 </label> 6145 <item> 6146 <kw/BEEPFACTOR/ <ident/<value>/ 6147 </item> 6148 <label> 6149 Description: 6150 </label> 6151 <item> 6152 This keyword allows to change the noise speed made by the 6153 <ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>, 6154 <ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>, 6155 <ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>, 6156 <ref target=EVENT><kw/EVENT/</ref>, and 6157 <ref target=PLAY><kw/PLAY/</ref> keywords. 6158 </item> 6159 <label> 6160 Parameters: 6161 </label> 6162 <item> 6163 The <ident/value/ specifies the constant to be used in noise speed 6164 calculation. 6165 </item> 6166 <label> 6167 Default: 6168 </label> 6169 <item> 6170 <ident/1000/ 6171 </item> 6172 <label> 6173 Notes: 6174 </label> 6175 <item> 6176 This keyword is valid <hi/ONLY/ in a 6177 <ref target=RANDOMSYSTEM>Random System</ref> group. 6178 </item> 6179 <label> 6180 Processed by: 6181 </label> 6182 <item> 6183 Mail reader. 6184 </item> 6185 <label> 6186 See also: 6187 </label> 6188 <item> 6189 <ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>, 6190 <ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>, 6191 <ref target=BEEPNOISES><kw/BEEPNOISES/</ref>, 6192 <ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>, 6193 <ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref> 6194 </item> 6195 </list> 6196 </div2> 6197 <div2 id=BEEPLOCALMSG> 6198 <head> 6199 BEEPLOCALMSG 6200 </head> 6201 <list type=gloss> 6202 <label> 6203 Synopsis: 6204 </label> 6205 <item> 6206 <kw/BEEPLOCALMSG/ <ident><YES/NO></ident> 6207 </item> 6208 <label> 6209 Description: 6210 </label> 6211 <item> 6212 This keyword enables or disables noise when <name/GoldED+/ finds a 6213 message with the <gi/LOC/ attribute set. This can be useful for the 6214 sysop who wants to monitor the messages entered by users on his/her 6215 <abbr/BBS/. 6216 </item> 6217 <label> 6218 Parameters: 6219 </label> 6220 <item> 6221 If enabled, <name/GoldED+/ will make a noise, otherwise will not. 6222 </item> 6223 <label> 6224 Default: 6225 </label> 6226 <item> 6227 <ident/NO/ 6228 </item> 6229 <label> 6230 Processed by: 6231 </label> 6232 <item> 6233 Mail reader. 6234 </item> 6235 <label> 6236 See also: 6237 </label> 6238 <item> 6239 <ptr target=MESSAGEATTRS> chapter, 6240 <ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>, 6241 <ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>, 6242 <ref target=BEEPNOISES><kw/BEEPNOISES/</ref>, 6243 <ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>, 6244 <ref target=DISPLOCALHIGH><kw/DISPLOCALHIGH/</ref>, 6245 <ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>, 6246 <ref target=SOUNDPATH><kw/SOUNDPATH/</ref> 6247 </item> 6248 </list> 6249 </div2> 6250 <div2 id=BEEPNOISES> 6251 <head> 6252 BEEPNOISES 6253 </head> 6254 <list type=gloss> 6255 <label> 6256 Synopsis: 6257 </label> 6258 <item> 6259 <kw/BEEPNOISES/ <ident><YES/NO></ident> 6260 </item> 6261 <label> 6262 Description: 6263 </label> 6264 <item> 6265 This is the <hi/master switch/ for all noises in <name/GoldED+/. The 6266 <code/-m/ commandline switch overrides this option. 6267 </item> 6268 <label> 6269 Parameters: 6270 </label> 6271 <item> 6272 If enabled, <name/GoldED+/ will make a noises, otherwise will keep 6273 silence. 6274 </item> 6275 <label> 6276 Default: 6277 </label> 6278 <item> 6279 <ident/YES/ 6280 </item> 6281 <label> 6282 Processed by: 6283 </label> 6284 <item> 6285 Mail reader. 6286 </item> 6287 <label> 6288 See also: 6289 </label> 6290 <item> 6291 <ptr target=COMMANDLINE> chapter, 6292 <ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>, 6293 <ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>, 6294 <ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>, 6295 <ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>, 6296 <ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>, 6297 <ref target=SOUNDPATH><kw/SOUNDPATH/</ref> 6298 </item> 6299 </list> 6300 </div2> 6301 <div2 id=BEEPYOURMAIL> 6302 <head> 6303 BEEPYOURMAIL 6304 </head> 6305 <list type=gloss> 6306 <label> 6307 Synopsis: 6308 </label> 6309 <item> 6310 <kw/BEEPYOURMAIL/ <ident><YES/NO/ALWAYS></ident> 6311 </item> 6312 <label> 6313 Description: 6314 </label> 6315 <item> 6316 This keyword enables or disables noise when <name/GoldED+/ finds a 6317 message to one of your <ref target=USERNAME><kw/USERNAME/</ref>'s. 6318 </item> 6319 <label> 6320 Parameters: 6321 </label> 6322 <item> 6323 If set to <ident/YES/, <name/GoldED+/ will make a noise if it finds 6324 a non-received message. If set to <ident/ALWAYS/, <name/GoldED+/ will 6325 make the noise even if it has already been marked as received. 6326 </item> 6327 <label> 6328 Default: 6329 </label> 6330 <item> 6331 <ident/YES/ 6332 </item> 6333 <label> 6334 Processed by: 6335 </label> 6336 <item> 6337 Mail reader. 6338 </item> 6339 <label> 6340 See also: 6341 </label> 6342 <item> 6343 <ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>, 6344 <ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>, 6345 <ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>, 6346 <ref target=BEEPNOISES><kw/BEEPNOISES/</ref>, 6347 <ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>, 6348 <ref target=SOUNDPATH><kw/SOUNDPATH/</ref> 6349 </item> 6350 </list> 6351 </div2> 6352 <div2 id=CARBONCOPYLIST> 6353 <head> 6354 CARBONCOPYLIST 6355 </head> 6356 <list type=gloss> 6357 <label> 6358 Synopsis: 6359 </label> 6360 <item> 6361 <kw/CARBONCOPYLIST/ 6362 <ident><KEEP/NAMES/VISIBLE/HIDDEN/REMOVE></ident> 6363 </item> 6364 <label> 6365 Description: 6366 </label> 6367 <item> 6368 This keyword specifies the format of the carbon copy list, as it will 6369 look after processing. You can also change the format in the 6370 <abbr/CC/ menu before processing. 6371 </item> 6372 <label> 6373 Parameters: 6374 </label> 6375 <item> 6376 The list specification items have the following meaning: 6377 <table rows=5 cols=2> 6378 <row> 6379 <cell> 6380 <ident/KEEP/ 6381 </cell> 6382 <cell> 6383 Keep the list as entered 6384 </cell> 6385 </row> 6386 <row> 6387 <cell> 6388 <ident/NAMES/ 6389 </cell> 6390 <cell> 6391 Convert list to <q/CC: Name, Name, Name../ format 6392 </cell> 6393 </row> 6394 <row> 6395 <cell> 6396 <ident/VISIBLE/ 6397 </cell> 6398 <cell> 6399 Convert list to <q/CC: Name Address/ format 6400 </cell> 6401 </row> 6402 <row> 6403 <cell> 6404 <ident/HIDDEN/ 6405 </cell> 6406 <cell> 6407 Convert list to <q/^ACC: Name Address/ format 6408 </cell> 6409 </row> 6410 <row> 6411 <cell> 6412 <ident/REMOVE/ 6413 </cell> 6414 <cell> 6415 Remove the list completely 6416 </cell> 6417 </row> 6418 </table> 6419 </item> 6420 <label> 6421 Default: 6422 </label> 6423 <item> 6424 <ident/NAMES/ 6425 </item> 6426 <label> 6427 Processed by: 6428 </label> 6429 <item> 6430 Mail reader. 6431 </item> 6432 <label> 6433 See also: 6434 </label> 6435 <item> 6436 <!-- FIX ME!!! -->Carbon Copy and Crossposting chapter, 6437 <ref target=CROSSPOSTLIST><kw/CROSSPOSTLIST/</ref> 6438 </item> 6439 </list> 6440 </div2> 6441 <div2 id=COLOR> 6442 <head> 6443 COLOR 6444 </head> 6445 <list type=gloss> 6446 <label> 6447 Synopsis: 6448 </label> 6449 <item> 6450 <kw/COLOR/ <ident/<colorspec>/ 6451 </item> 6452 <label> 6453 Description: 6454 </label> 6455 <item> 6456 Using this keyword you can define or redefine all the colors used 6457 in <name/GoldED+/. 6458 </item> 6459 <label> 6460 Parameters: 6461 </label> 6462 <item> 6463 The detailed description for <kw/COLOR/ parameters provided in 6464 <ptr target=COLORCONFIG> chapter. 6465 </item> 6466 <label> 6467 Processed by: 6468 </label> 6469 <item> 6470 Mail reader. 6471 </item> 6472 <label> 6473 See also: 6474 </label> 6475 <item> 6476 <ptr target=COLORCONFIG> chapter, 6477 <ref target=COLORSET><kw/COLORSET/</ref> 6478 </item> 6479 </list> 6480 </div2> 6481 <div2 id=COLORSET> 6482 <head> 6483 COLORSET 6484 </head> 6485 <list type=gloss> 6486 <label> 6487 Synopsis: 6488 </label> 6489 <item> 6490 <kw/COLORSET/ <ident><NORMAL/INTENSE/MONO></ident> 6491 </item> 6492 <label> 6493 Description: 6494 </label> 6495 <item> 6496 Three color setups are built-in, and can be selected with this 6497 keyword. 6498 </item> 6499 <label> 6500 Parameters: 6501 </label> 6502 <item> 6503 The <ident/NORMAL/ scheme has all black background, with bright 6504 neon-like colors for the window frames. The <ident/INTENSE/ scheme 6505 has all bright white background (this achieved by switching off the 6506 <q/blink/ attribute, thereby enabling the use of intense (bright) 6507 colors for the background (<ident/paper/) colors as well as the 6508 foreground (<ident/ink/) colors). The <ident/MONO/ scheme is 6509 optimized for the monochrome adapters. 6510 </item> 6511 <label> 6512 Default: 6513 </label> 6514 <item> 6515 If color video adapter is detected then <ident/NORMAL/ color scheme 6516 used, otherwise <ident/MONO/ scheme. 6517 </item> 6518 <label> 6519 Processed by: 6520 </label> 6521 <item> 6522 Mail reader. 6523 </item> 6524 <label> 6525 See also: 6526 </label> 6527 <item> 6528 <ptr target=COLORCONFIG> chapter, 6529 <ref target=COLOR><kw/COLOR/</ref> 6530 </item> 6531 </list> 6532 </div2> 6533 <div2 id=CONFIRMFILE> 6534 <head> 6535 CONFIRMFILE 6536 </head> 6537 <list type=gloss> 6538 <label> 6539 Synopsis: 6540 </label> 6541 <item> 6542 <kw/CONFIRMFILE/ <ident/<filename>/ 6543 </item> 6544 <label> 6545 Description: 6546 </label> 6547 <item> 6548 <name/GoldED+/ supports the Confirmation Receipt attribute, as used 6549 in FrontDoor 2.xx with the <gi/FLAGS CFM/ kludge. If <name/GoldED+/ 6550 finds an unreceived message to one of your 6551 <ref target=USERNAME><kw/USERNAME/</ref>'s with the <gi/CFM/ (or 6552 <gi/RRQ/) attribute set, it generates an automatic response message 6553 from the content of the <kw/CONFIRMFILE/. In the file you can use 6554 many of the template tokens to personalize the automatic message. 6555 </item> 6556 <label> 6557 Parameters: 6558 </label> 6559 <item> 6560 The <ident/filename/ specifies the name of the template file used 6561 for the response message generation. 6562 </item> 6563 <label> 6564 Default: 6565 </label> 6566 <item> 6567 <code/golded.cfm/ 6568 </item> 6569 <label> 6570 Processed by: 6571 </label> 6572 <item> 6573 Mail reader. 6574 </item> 6575 <label> 6576 See also: 6577 </label> 6578 <item> 6579 <ptr target=MESSAGEATTRS> chapter, 6580 <ptr target=MESSAGETEMPLATE> chapter, 6581 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 6582 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 6583 <ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>, 6584 <ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref> 6585 </item> 6586 </list> 6587 </div2> 6588 <div2 id=CONFIRMRESPONSE> 6589 <head> 6590 CONFIRMRESPONSE 6591 </head> 6592 <list type=gloss> 6593 <label> 6594 Synopsis: 6595 </label> 6596 <item> 6597 <kw/CONFIRMRESPONSE/ <ident><YES/NO/ASK></ident> 6598 </item> 6599 <label> 6600 Description: 6601 </label> 6602 <item> 6603 An unreceived message to you with the CFM attribute set tells 6604 <name/GoldED+/ that the sender has requested a receipt that you have 6605 read the message. With this keyword you tell <name/GoldED+/ what to 6606 do when such a message is found. 6607 </item> 6608 <label> 6609 Parameters: 6610 </label> 6611 <item> 6612 <ident/YES/ tells <name/GoldED+/ to always automatically generate the 6613 receipt, <ident/NO/ cause to always ignore the requests, and if set 6614 to <ident/ASK/ you will be prompted in each case. 6615 </item> 6616 <label> 6617 Default: 6618 </label> 6619 <item> 6620 <ident/ASK/ 6621 </item> 6622 <label> 6623 Processed by: 6624 </label> 6625 <item> 6626 Mail reader. 6627 </item> 6628 <label> 6629 See also: 6630 </label> 6631 <item> 6632 <ptr target=MESSAGEATTRS> chapter, 6633 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 6634 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 6635 <ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>, 6636 <ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>, 6637 <ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref> 6638 </item> 6639 </list> 6640 </div2> 6641 <div2> 6642 <head> 6643 COOKIEPATH 6644 </head> 6645 <list type=gloss> 6646 <label> 6647 Synopsis: 6648 </label> 6649 <item> 6650 <kw/COOKIEPATH/ <ident/<path>/ 6651 </item> 6652 <label> 6653 Description: 6654 </label> 6655 <item> 6656 Defines the default path for the <!-- FIX ME!!! --><kw/@random/ 6657 template token. 6658 </item> 6659 <label> 6660 Parameters: 6661 </label> 6662 <item> 6663 The default <ident/path/ for the <!-- FIX ME!!! --><kw/@random/ 6664 template token. 6665 </item> 6666 <label> 6667 Default: 6668 </label> 6669 <item> 6670 <ref target=GOLDPATH><kw/GOLDPATH/</ref> 6671 </item> 6672 <label> 6673 Processed by: 6674 </label> 6675 <item> 6676 Mail reader. 6677 </item> 6678 <label> 6679 See also: 6680 </label> 6681 <item> 6682 <ptr target=MESSAGETEMPLATE> chapter, 6683 <ref target=GOLDPATH><kw/GOLDPATH/</ref> 6684 </item> 6685 </list> 6686 </div2> 6687 <div2 id=CROSSPOST> 6688 <head> 6689 CROSSPOST 6690 </head> 6691 <list type=gloss> 6692 <label> 6693 Synopsis: 6694 </label> 6695 <item> 6696 <kw/CROSSPOST/ <ident><YES/NO/ASK></ident> 6697 </item> 6698 <label> 6699 Description: 6700 </label> 6701 <item> 6702 This keyword configure prompt appearance when saving message which 6703 contains crosspost tokens in the body. 6704 </item> 6705 <label> 6706 Parameters: 6707 </label> 6708 <item> 6709 <ident/YES/ tells <name/GoldED+/ to always automatically process 6710 crosspost tokens, <ident/NO/ cause to always ignore them, and if set 6711 to <ident/ASK/ you will be prompted in each case. 6712 </item> 6713 <label> 6714 Default: 6715 </label> 6716 <item> 6717 <ident/ASK/ 6718 </item> 6719 <label> 6720 Processed by: 6721 </label> 6722 <item> 6723 Mail reader. 6724 </item> 6725 <label> 6726 See also: 6727 </label> 6728 <item> 6729 <ref target=CROSSPOSTLIST><kw/CROSSPOSTLIST/</ref> 6730 </item> 6731 </list> 6732 </div2> 6733 <div2 id=CROSSPOSTLIST> 6734 <head> 6735 CROSSPOSTLIST 6736 </head> 6737 <list type=gloss> 6738 <label> 6739 Synopsis: 6740 </label> 6741 <item> 6742 <kw/CROSSPOSTLIST/ 6743 <ident><RAW/VERBOSE/YES/NONE></ident> 6744 </item> 6745 <label> 6746 Description: 6747 </label> 6748 <item> 6749 This keyword specifies the format of the crosspost list, as it will 6750 look after processing. You can also change the format in the 6751 <ref target=CROSSPOST><kw/CROSSPOST/</ref> menu before processing 6752 (if menu enabled). 6753 </item> 6754 <label> 6755 Parameters: 6756 </label> 6757 <item> 6758 The list specification items have the following meaning: 6759 <table rows=4 cols=2> 6760 <row> 6761 <cell> 6762 <ident/RAW/ 6763 </cell> 6764 <cell> 6765 Keep the list as entered 6766 </cell> 6767 </row> 6768 <row> 6769 <cell> 6770 <ident/VERBOSE/ 6771 </cell> 6772 <cell> 6773 Change the list to lines of "* Crossposted in ..." 6774 </cell> 6775 </row> 6776 <row> 6777 <cell> 6778 <ident/YES/ 6779 </cell> 6780 <cell> 6781 Same as above, but expand echolist in line rather than in 6782 column 6783 </cell> 6784 </row> 6785 <row> 6786 <cell> 6787 <ident/NONE/ 6788 </cell> 6789 <cell> 6790 Crosspost without a list in the msgs 6791 </cell> 6792 </row> 6793 </table> 6794 </item> 6795 <label> 6796 Default: 6797 </label> 6798 <item> 6799 <ident/VERBOSE/ 6800 </item> 6801 <label> 6802 Processed by: 6803 </label> 6804 <item> 6805 Mail reader. 6806 </item> 6807 <label> 6808 See also: 6809 </label> 6810 <item> 6811 <!-- FIX ME!!! -->Carbon Copy and Crossposting chapter, 6812 <ref target=CARBONCOPYLIST><kw/CARBONCOPYLIST/</ref>, 6813 <ref target=CROSSPOST><kw/CROSSPOST/</ref> 6814 </item> 6815 </list> 6816 </div2> 6817 <div2 id=CTRLINFO> 6818 <head> 6819 CTRLINFO 6820 </head> 6821 <list type=gloss> 6822 <label> 6823 Synopsis: 6824 </label> 6825 <item> 6826 <kw/CTRLINFO/ <ident><YES/NO/TEARLINE,ORIGIN></ident> 6827 </item> 6828 <label> 6829 Description: 6830 </label> 6831 <item> 6832 Specifies if you want a tearline and/or origin in your messages. 6833 </item> 6834 <label> 6835 Parameters: 6836 </label> 6837 <item> 6838 The tokens have the following meaning: 6839 <table rows=4 cols=2> 6840 <row> 6841 <cell> 6842 <ident/YES/ 6843 </cell> 6844 <cell> 6845 Enable both tearline and origin 6846 </cell> 6847 </row> 6848 <row> 6849 <cell> 6850 <ident/NO/ 6851 </cell> 6852 <cell> 6853 Disable all control info 6854 </cell> 6855 </row> 6856 <row> 6857 <cell> 6858 <ident/TEARLINE/ 6859 </cell> 6860 <cell> 6861 Enable tearline, can be used with <ident/ORIGIN/ 6862 </cell> 6863 </row> 6864 <row> 6865 <cell> 6866 <ident/ORIGIN/ 6867 </cell> 6868 <cell> 6869 Enable origin, can be used with <ident/TEARLINE/ 6870 </cell> 6871 </row> 6872 </table> 6873 </item> 6874 <label> 6875 Notes: 6876 </label> 6877 <item> 6878 This keyword is valid <hi/ONLY/ in a 6879 <ref target=RANDOMSYSTEM>Random System</ref> group.<lb> 6880 This may be helpful for <abbr/QWK/ users, who can create a group for 6881 the <abbr/QWK/ areas and disable <kw/CTRLINFO/ there. 6882 </item> 6883 <label> 6884 Processed by: 6885 </label> 6886 <item> 6887 Mail reader. 6888 </item> 6889 <label> 6890 See also: 6891 </label> 6892 <item> 6893 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 6894 <ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>, 6895 <ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>, 6896 <ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>, 6897 <ref target=CTRLINFONET><kw/CTRLINFONET/</ref>, 6898 <ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>, 6899 <ref target=ORIGIN><kw/ORIGIN/</ref>, 6900 <ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>, 6901 <ref target=TEARLINE><kw/TEARLINE/</ref> 6902 </item> 6903 <label> 6904 Example: 6905 </label> 6906 <item><eg> 6907CTRLINFO YES ; Add both tearline and origin 6908CTRLINFO TEARLINE ORIGIN ; Same as above in other words 6909CTRLINFO TEARLINE ; Add only a tearline 6910CTRLINFO ORIGIN ; Add only an origin</eg> 6911 </item> 6912 </list> 6913 </div2> 6914 <div2 id=CTRLINFOECHO> 6915 <head> 6916 CTRLINFOECHO 6917 </head> 6918 <list type=gloss> 6919 <label> 6920 Synopsis: 6921 </label> 6922 <item> 6923 <kw/CTRLINFOECHO/ <ident><YES/NO/TEARLINE,ORIGIN></ident> 6924 </item> 6925 <label> 6926 Description: 6927 </label> 6928 <item> 6929 Specifies if you want a tearline and/or origin in your echomail 6930 messages. 6931 </item> 6932 <label> 6933 Parameters: 6934 </label> 6935 <item> 6936 The tokens have the following meaning: 6937 <table rows=4 cols=2> 6938 <row> 6939 <cell> 6940 <ident/YES/ 6941 </cell> 6942 <cell> 6943 Enable both tearline and origin 6944 </cell> 6945 </row> 6946 <row> 6947 <cell> 6948 <ident/NO/ 6949 </cell> 6950 <cell> 6951 Disable all control info 6952 </cell> 6953 </row> 6954 <row> 6955 <cell> 6956 <ident/TEARLINE/ 6957 </cell> 6958 <cell> 6959 Enable tearline, can be used with <ident/ORIGIN/ 6960 </cell> 6961 </row> 6962 <row> 6963 <cell> 6964 <ident/ORIGIN/ 6965 </cell> 6966 <cell> 6967 Enable origin, can be used with <ident/TEARLINE/ 6968 </cell> 6969 </row> 6970 </table> 6971 </item> 6972 <label> 6973 Default: 6974 </label> 6975 <item> 6976 <ident/YES/ 6977 </item> 6978 <label> 6979 Notes: 6980 </label> 6981 <item> 6982 Changing the default may cause unpredictable behaviour with some 6983 echomail processors so it is not recommended to change it. 6984 </item> 6985 <label> 6986 Processed by: 6987 </label> 6988 <item> 6989 Mail reader. 6990 </item> 6991 <label> 6992 See also: 6993 </label> 6994 <item> 6995 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 6996 <ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>, 6997 <ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>, 6998 <ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>, 6999 <ref target=CTRLINFONET><kw/CTRLINFONET/</ref>, 7000 <ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>, 7001 <ref target=ORIGIN><kw/ORIGIN/</ref>, 7002 <ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>, 7003 <ref target=TEARLINE><kw/TEARLINE/</ref> 7004 </item> 7005 </list> 7006 </div2> 7007 <div2 id=CTRLINFOEMAIL> 7008 <head> 7009 CTRLINFOEMAIL 7010 </head> 7011 <list type=gloss> 7012 <label> 7013 Synopsis: 7014 </label> 7015 <item> 7016 <kw/CTRLINFOEMAIL/ <ident><YES/NO/TEARLINE,ORIGIN></ident> 7017 </item> 7018 <label> 7019 Description: 7020 </label> 7021 <item> 7022 Specifies if you want a tearline and/or origin in your 7023 <name/Internet/ e-mail messages. This is not recommended. 7024 </item> 7025 <label> 7026 Parameters: 7027 </label> 7028 <item> 7029 The tokens have the following meaning: 7030 <table rows=4 cols=2> 7031 <row> 7032 <cell> 7033 <ident/YES/ 7034 </cell> 7035 <cell> 7036 Enable both tearline and origin 7037 </cell> 7038 </row> 7039 <row> 7040 <cell> 7041 <ident/NO/ 7042 </cell> 7043 <cell> 7044 Disable all control info 7045 </cell> 7046 </row> 7047 <row> 7048 <cell> 7049 <ident/TEARLINE/ 7050 </cell> 7051 <cell> 7052 Enable tearline, can be used with <ident/ORIGIN/ 7053 </cell> 7054 </row> 7055 <row> 7056 <cell> 7057 <ident/ORIGIN/ 7058 </cell> 7059 <cell> 7060 Enable origin, can be used with <ident/TEARLINE/ 7061 </cell> 7062 </row> 7063 </table> 7064 </item> 7065 <label> 7066 Default: 7067 </label> 7068 <item> 7069 <ident/NO/ 7070 </item> 7071 <label> 7072 Notes: 7073 </label> 7074 <item> 7075 Changing the default is not recommended. 7076 </item> 7077 <label> 7078 Processed by: 7079 </label> 7080 <item> 7081 Mail reader. 7082 </item> 7083 <label> 7084 See also: 7085 </label> 7086 <item> 7087 <ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>, 7088 <ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>, 7089 <ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>, 7090 <ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>, 7091 <ref target=CTRLINFONET><kw/CTRLINFONET/</ref>, 7092 <ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>, 7093 <ref target=ORIGIN><kw/ORIGIN/</ref>, 7094 <ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>, 7095 <ref target=TEARLINE><kw/TEARLINE/</ref> 7096 </item> 7097 </list> 7098 </div2> 7099 <div2 id=CTRLINFOLOCAL> 7100 <head> 7101 CTRLINFOLOCAL 7102 </head> 7103 <list type=gloss> 7104 <label> 7105 Synopsis: 7106 </label> 7107 <item> 7108 <kw/CTRLINFOLOCAL/ <ident><YES/NO/TEARLINE,ORIGIN></ident> 7109 </item> 7110 <label> 7111 Description: 7112 </label> 7113 <item> 7114 Specifies if you want tearline and origin in your messages in 7115 local areas. 7116 </item> 7117 <label> 7118 Parameters: 7119 </label> 7120 <item> 7121 The tokens have the following meaning: 7122 <table rows=4 cols=2> 7123 <row> 7124 <cell> 7125 <ident/YES/ 7126 </cell> 7127 <cell> 7128 Enable both tearline and origin 7129 </cell> 7130 </row> 7131 <row> 7132 <cell> 7133 <ident/NO/ 7134 </cell> 7135 <cell> 7136 Disable all control info 7137 </cell> 7138 </row> 7139 <row> 7140 <cell> 7141 <ident/TEARLINE/ 7142 </cell> 7143 <cell> 7144 Enable tearline, can be used with <ident/ORIGIN/ 7145 </cell> 7146 </row> 7147 <row> 7148 <cell> 7149 <ident/ORIGIN/ 7150 </cell> 7151 <cell> 7152 Enable origin, can be used with <ident/TEARLINE/ 7153 </cell> 7154 </row> 7155 </table> 7156 </item> 7157 <label> 7158 Default: 7159 </label> 7160 <item> 7161 <ident/NO/ 7162 </item> 7163 <label> 7164 Notes: 7165 </label> 7166 <item> 7167 In local areas, the tearline and origin is normally never required 7168 but can be used for cosmetic purposes. 7169 </item> 7170 <label> 7171 Processed by: 7172 </label> 7173 <item> 7174 Mail reader. 7175 </item> 7176 <label> 7177 See also: 7178 </label> 7179 <item> 7180 <ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>, 7181 <ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>, 7182 <ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>, 7183 <ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>, 7184 <ref target=CTRLINFONET><kw/CTRLINFONET/</ref>, 7185 <ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>, 7186 <ref target=ORIGIN><kw/ORIGIN/</ref>, 7187 <ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>, 7188 <ref target=TEARLINE><kw/TEARLINE/</ref> 7189 </item> 7190 </list> 7191 </div2> 7192 <div2 id=CTRLINFONET> 7193 <head> 7194 CTRLINFONET 7195 </head> 7196 <list type=gloss> 7197 <label> 7198 Synopsis: 7199 </label> 7200 <item> 7201 <kw/CTRLINFONET/ <ident><YES/NO/TEARLINE,ORIGIN></ident> 7202 </item> 7203 <label> 7204 Description: 7205 </label> 7206 <item> 7207 Specifies if you want tearline and origin in your netmail messages. 7208 </item> 7209 <label> 7210 Parameters: 7211 </label> 7212 <item> 7213 The tokens have the following meaning: 7214 <table rows=4 cols=2> 7215 <row> 7216 <cell> 7217 <ident/YES/ 7218 </cell> 7219 <cell> 7220 Enable both tearline and origin 7221 </cell> 7222 </row> 7223 <row> 7224 <cell> 7225 <ident/NO/ 7226 </cell> 7227 <cell> 7228 Disable all control info 7229 </cell> 7230 </row> 7231 <row> 7232 <cell> 7233 <ident/TEARLINE/ 7234 </cell> 7235 <cell> 7236 Enable tearline, can be used with <ident/ORIGIN/ 7237 </cell> 7238 </row> 7239 <row> 7240 <cell> 7241 <ident/ORIGIN/ 7242 </cell> 7243 <cell> 7244 Enable origin, can be used with <ident/TEARLINE/ 7245 </cell> 7246 </row> 7247 </table> 7248 </item> 7249 <label> 7250 Default: 7251 </label> 7252 <item> 7253 <ident/TEARLINE/ 7254 </item> 7255 <label> 7256 Notes: 7257 </label> 7258 <item> 7259 In netmail areas, the tearline and origin is normally never required 7260 but can be used for cosmetic purposes. Some robots reqire tearline 7261 in the message. 7262 </item> 7263 <label> 7264 Processed by: 7265 </label> 7266 <item> 7267 Mail reader. 7268 </item> 7269 <label> 7270 See also: 7271 </label> 7272 <item> 7273 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 7274 <ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>, 7275 <ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>, 7276 <ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>, 7277 <ref target=CTRLINFONET><kw/CTRLINFONET/</ref>, 7278 <ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>, 7279 <ref target=ORIGIN><kw/ORIGIN/</ref>, 7280 <ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>, 7281 <ref target=TEARLINE><kw/TEARLINE/</ref> 7282 </item> 7283 </list> 7284 </div2> 7285 <div2 id=CTRLINFONEWS> 7286 <head> 7287 CTRLINFONEWS 7288 </head> 7289 <list type=gloss> 7290 <label> 7291 Synopsis: 7292 </label> 7293 <item> 7294 <kw/CTRLINFONEWS/ <ident><YES/NO/TEARLINE,ORIGIN></ident> 7295 </item> 7296 <label> 7297 Description: 7298 </label> 7299 <item> 7300 Specifies if you want a tearline and/or origin in your 7301 <name/Internet/ news articles. 7302 </item> 7303 <label> 7304 Parameters: 7305 </label> 7306 <item> 7307 The tokens have the following meaning: 7308 <table rows=4 cols=2> 7309 <row> 7310 <cell> 7311 <ident/YES/ 7312 </cell> 7313 <cell> 7314 Enable both tearline and origin 7315 </cell> 7316 </row> 7317 <row> 7318 <cell> 7319 <ident/NO/ 7320 </cell> 7321 <cell> 7322 Disable all control info 7323 </cell> 7324 </row> 7325 <row> 7326 <cell> 7327 <ident/TEARLINE/ 7328 </cell> 7329 <cell> 7330 Enable tearline, can be used with <ident/ORIGIN/ 7331 </cell> 7332 </row> 7333 <row> 7334 <cell> 7335 <ident/ORIGIN/ 7336 </cell> 7337 <cell> 7338 Enable origin, can be used with <ident/TEARLINE/ 7339 </cell> 7340 </row> 7341 </table> 7342 </item> 7343 <label> 7344 Default: 7345 </label> 7346 <item> 7347 <ident/NO/ 7348 </item> 7349 <label> 7350 Notes: 7351 </label> 7352 <item> 7353 Changing the default is not recommended. 7354 </item> 7355 <label> 7356 Processed by: 7357 </label> 7358 <item> 7359 Mail reader. 7360 </item> 7361 <label> 7362 See also: 7363 </label> 7364 <item> 7365 <ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>, 7366 <ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>, 7367 <ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>, 7368 <ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>, 7369 <ref target=CTRLINFONET><kw/CTRLINFONET/</ref>, 7370 <ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>, 7371 <ref target=ORIGIN><kw/ORIGIN/</ref>, 7372 <ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>, 7373 <ref target=TEARLINE><kw/TEARLINE/</ref> 7374 </item> 7375 </list> 7376 </div2> 7377 <div2 id=DISPAREANO> 7378 <head> 7379 DISPAREANO 7380 </head> 7381 <list type=gloss> 7382 <label> 7383 Synopsis: 7384 </label> 7385 <item> 7386 <kw/DISPAREANO/ <ident><YES/NO/ALWAYS></ident> 7387 </item> 7388 <label> 7389 Description: 7390 </label> 7391 <item> 7392 This keyword specifies if <name/GoldED+/ should display the area 7393 number on the top line in the reader. The area number is the same as 7394 that displayed in the leftmost column in the arealist. This also 7395 means that the number displayed can be either the board number 7396 (Hudson/Goldbase/Ezycom board) or the standard sequential number. 7397 </item> 7398 <label> 7399 Parameters: 7400 </label> 7401 <item> 7402 When set to <ident/YES/ <name/GoldED+/ displays area number only if 7403 non-zero, setting to <ident/NO/ disables display at all, and 7404 <ident/ALWAYS/ forces to display the area number in any case. 7405 </item> 7406 <label> 7407 Default: 7408 </label> 7409 <item> 7410 <ident/YES/ 7411 </item> 7412 <label> 7413 Processed by: 7414 </label> 7415 <item> 7416 Mail reader. 7417 </item> 7418 <label> 7419 See also: 7420 </label> 7421 <item> 7422 <ref target=AREALISTNOS><kw/AREALISTNOS/</ref> 7423 </item> 7424 </list> 7425 </div2> 7426 <div2 id=DISPATTACHSIZE> 7427 <head> 7428 DISPATTACHSIZE 7429 </head> 7430 <list type=gloss> 7431 <label> 7432 Synopsis: 7433 </label> 7434 <item> 7435 <kw/DISPATTACHSIZE/ <ident><BYTES/KBYTES/NO></ident> 7436 </item> 7437 <label> 7438 Description: 7439 </label> 7440 <item> 7441 Controls how the size of attached files is displayed in the header. 7442 </item> 7443 <label> 7444 Parameters: 7445 </label> 7446 <item> 7447 The following options are provided: the exact size in <ident/BYTES/, 7448 the rounded size in <ident/KBYTES/, or <ident/NO/ display at all. 7449 </item> 7450 <label> 7451 Default: 7452 </label> 7453 <item> 7454 <ident/KBYTES/ 7455 </item> 7456 <label> 7457 Notes: 7458 </label> 7459 <item> 7460 If the <ident/KBYTES/ setting is chosen, the value is rounded 7461 according to the following formula: kbytes = (bytes + 512) / 1024. 7462 So a 600 bytes file is rounded up to <q/1k/, but a 500 bytes 7463 file is rounded down to <q/0k/. 7464 </item> 7465 <label> 7466 Processed by: 7467 </label> 7468 <item> 7469 Mail reader. 7470 </item> 7471 <label> 7472 See also: 7473 </label> 7474 <item> 7475 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>, 7476 <ref target=DISPMSGSIZE><kw/DISPMSGSIZE/</ref> 7477 </item> 7478 </list> 7479 </div2> 7480 <div2 id=DISPAUTONEXT> 7481 <head> 7482 DISPAUTONEXT 7483 </head> 7484 <list type=gloss> 7485 <label> 7486 Synopsis: 7487 </label> 7488 <item> 7489 <kw/DISPAUTONEXT/ <ident><YES/NO></ident> 7490 </item> 7491 <label> 7492 Description: 7493 </label> 7494 <item> 7495 Controls which message will be displayed when entering an area. 7496 </item> 7497 <label> 7498 Parameters: 7499 </label> 7500 <item> 7501 If enabled, <name/GoldED+/ will automatically jump to the next 7502 message when entering an area. Otherwise message under the lastread 7503 pointer will be displayed. 7504 </item> 7505 <label> 7506 Default: 7507 </label> 7508 <item> 7509 <ident/YES/ 7510 </item> 7511 <label> 7512 Processed by: 7513 </label> 7514 <item> 7515 Mail reader. 7516 </item> 7517 <label> 7518 See also: 7519 </label> 7520 <item> 7521 <ref target=MSGLISTFIRST><kw/MSGLISTFIRST/</ref> 7522 </item> 7523 </list> 7524 </div2> 7525 <div2 id=DISPHDRDATESET> 7526 <head> 7527 DISPHDRDATESET 7528 </head> 7529 <list type=gloss> 7530 <label> 7531 Synopsis: 7532 </label> 7533 <item> 7534 <kw/DISPHDRDATESET/ <ident/<position> <length>/ 7535 </item> 7536 <label> 7537 Description: 7538 </label> 7539 <item> 7540 Specifies the position and length of the date field in the header 7541 display. 7542 </item> 7543 <label> 7544 Parameters: 7545 </label> 7546 <item> 7547 Specifies the <ident/position/ and <ident/length/ of the date field 7548 in the header display. If a negative value is specified, that value 7549 is added to the current display width. 7550 </item> 7551 <label> 7552 Default: 7553 </label> 7554 <item> 7555 -20 20 7556 </item> 7557 <label> 7558 Processed by: 7559 </label> 7560 <item> 7561 Mail reader. 7562 </item> 7563 <label> 7564 See also: 7565 </label> 7566 <item> 7567 <ref target=DISPHDRNAMESET><kw/DISPHDRNAMESET/</ref>, 7568 <ref target=DISPHDRNODESET><kw/DISPHDRNODESET/</ref> 7569 </item> 7570 </list> 7571 </div2> 7572 <div2 id=DISPHDRNAMESET> 7573 <head> 7574 DISPHDRNAMESET 7575 </head> 7576 <list type=gloss> 7577 <label> 7578 Synopsis: 7579 </label> 7580 <item> 7581 <kw/DISPHDRNAMESET/ <ident/<position> <length>/ 7582 </item> 7583 <label> 7584 Description: 7585 </label> 7586 <item> 7587 Specifies the position and length of the from/to name field in the 7588 header display. 7589 </item> 7590 <label> 7591 Parameters: 7592 </label> 7593 <item> 7594 Specifies the <ident/position/ and <ident/length/ of the from/to name 7595 field in the header display. If a negative value is specified, that 7596 value is added to the current display width. 7597 </item> 7598 <label> 7599 Default: 7600 </label> 7601 <item> 7602 8 36 7603 </item> 7604 <label> 7605 Processed by: 7606 </label> 7607 <item> 7608 Mail reader. 7609 </item> 7610 <label> 7611 See also: 7612 </label> 7613 <item> 7614 <ref target=DISPHDRDATESET><kw/DISPHDRDATESET/</ref>, 7615 <ref target=DISPHDRNODESET><kw/DISPHDRNODESET/</ref>, 7616 <ref target=EDITHDRNAMESET><kw/EDITHDRNAMESET/</ref> 7617 </item> 7618 </list> 7619 </div2> 7620 <div2 id=DISPHDRNODESET> 7621 <head> 7622 DISPHDRNODESET 7623 </head> 7624 <list type=gloss> 7625 <label> 7626 Synopsis: 7627 </label> 7628 <item> 7629 <kw/DISPHDRNODESET/ <ident/<position> <length>/ 7630 </item> 7631 <label> 7632 Description: 7633 </label> 7634 <item> 7635 Specfies the position and length of the from/to node address field in 7636 the header display. 7637 </item> 7638 <label> 7639 Parameters: 7640 </label> 7641 <item> 7642 Specfies the <ident/position/ and <ident/length/ of the from/to node 7643 address field in the header display. If a negative value is 7644 specified, that value is added to the current display width. 7645 </item> 7646 <label> 7647 Default: 7648 </label> 7649 <item> 7650 44 16 7651 </item> 7652 <label> 7653 Notes: 7654 </label> 7655 <item> 7656 The attributes display moves along with the <kw>DISPHDRNODESET</kw> 7657 values. 7658 </item> 7659 <label> 7660 Processed by: 7661 </label> 7662 <item> 7663 Mail reader. 7664 </item> 7665 <label> 7666 See also: 7667 </label> 7668 <item> 7669 <ref target=DISPHDRDATESET><kw/DISPHDRDATESET/</ref>, 7670 <ref target=DISPHDRNAMESET><kw/DISPHDRNAMESET/</ref>, 7671 <ref target=EDITHDRNODESET><kw/EDITHDRNODESET/</ref> 7672 </item> 7673 </list> 7674 </div2> 7675 <div2 id=DISPLISTCURSOR> 7676 <head> 7677 DISPLISTCURSOR 7678 </head> 7679 <list type=gloss> 7680 <label> 7681 Synopsis: 7682 </label> 7683 <item> 7684 <kw/DISPLISTCURSOR/ 7685 <ident><TOP/NEARTOP/MIDDLE/NEARBOTTOM/BOTTOM></ident> 7686 </item> 7687 <label> 7688 Description: 7689 </label> 7690 <item> 7691 Selects the starting position of selection bar in the message list 7692 and nodelist browsers. 7693 </item> 7694 <label> 7695 Parameters: 7696 </label> 7697 <item> 7698 <table rows=5 cols=2> 7699 <row> 7700 <cell> 7701 <ident/TOP/ 7702 </cell> 7703 <cell> 7704 At the top if possible 7705 </cell> 7706 </row> 7707 <row> 7708 <cell> 7709 <ident/NEARTOP/ 7710 </cell> 7711 <cell> 7712 At top + 1/3 if possible 7713 </cell> 7714 </row> 7715 <row> 7716 <cell> 7717 <ident/MIDDLE/ 7718 </cell> 7719 <cell> 7720 At middle of possible 7721 </cell> 7722 </row> 7723 <row> 7724 <cell> 7725 <ident/NEARBOTTOM/ 7726 </cell> 7727 <cell> 7728 At bottom - 1/3 7729 </cell> 7730 </row> 7731 <row> 7732 <cell> 7733 <ident/BOTTOM/ 7734 </cell> 7735 <cell> 7736 At bottom 7737 </cell> 7738 </row> 7739 </table> 7740 </item> 7741 <label> 7742 Default: 7743 </label> 7744 <item> 7745 <ident/MIDDLE/ 7746 </item> 7747 <label> 7748 Processed by: 7749 </label> 7750 <item> 7751 Mail reader. 7752 </item> 7753 </list> 7754 </div2> 7755 <div2 id=DISPLISTWRAP> 7756 <head> 7757 DISPLISTWRAP 7758 </head> 7759 <list type=gloss> 7760 <label> 7761 Synopsis: 7762 </label> 7763 <item> 7764 <kw/DISPLISTWRAP/ <ident><YES/NO></ident> 7765 </item> 7766 <label> 7767 Description: 7768 </label> 7769 <item> 7770 Enables or disables wrap-around when the selection bar in the main 7771 list/browser windows reaches the top or bottom. 7772 </item> 7773 <label> 7774 Parameters: 7775 </label> 7776 <item> 7777 If set to <ident/YES/, <name/GoldED+/ will wrap-around when the 7778 selection bar in the main list/browser windows reaches the top or 7779 bottom. If set to <ident/NO/, the selection bar will stop at the 7780 top or bottom when reaches them. 7781 </item> 7782 <label> 7783 Default: 7784 </label> 7785 <item> 7786 <ident/NO/ 7787 </item> 7788 <label> 7789 Processed by: 7790 </label> 7791 <item> 7792 Mail reader. 7793 </item> 7794 </list> 7795 </div2> 7796 <div2 id=DISPLOCALHIGH> 7797 <head> 7798 DISPLOCALHIGH 7799 </head> 7800 <list type=gloss> 7801 <label> 7802 Synopsis: 7803 </label> 7804 <item> 7805 <kw/DISPLOCALHIGH/ <ident><YES/NO></ident> 7806 </item> 7807 <label> 7808 Description: 7809 </label> 7810 <item> 7811 This keyword controls whether <name/GoldED+/ will display the 7812 <gi/FROM/ name with the highlight color if a message has the 7813 <gi/LOC/ attribute set. 7814 </item> 7815 <label> 7816 Parameters: 7817 </label> 7818 <item> 7819 If enabled, <name/GoldED+/ will display the <gi/FROM/ name with the 7820 highlight color if a message has the <gi/LOC/ attribute set, 7821 otherwise will not. 7822 </item> 7823 <label> 7824 Default: 7825 </label> 7826 <item> 7827 <ident/YES/ 7828 </item> 7829 <label> 7830 Processed by: 7831 </label> 7832 <item> 7833 Mail reader. 7834 </item> 7835 <label> 7836 See also: 7837 </label> 7838 <item> 7839 <ptr target=MESSAGEATTRS> chapter, 7840 <ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>, 7841 <ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>, 7842 <ref target=COLOR><kw/COLOR/</ref>, 7843 <ref target=HIGHLIGHTUNREAD><kw/HIGHLIGHTUNREAD/</ref> 7844 </item> 7845 </list> 7846 </div2> 7847 <div2 id=DISPMARGIN> 7848 <head> 7849 DISPMARGIN 7850 </head> 7851 <list type=gloss> 7852 <label> 7853 Synopsis: 7854 </label> 7855 <item> 7856 <kw/DISPMARGIN/ <ident/<width>/ 7857 </item> 7858 <label> 7859 Description: 7860 </label> 7861 <item> 7862 This keyword defines the right margin (display width) used for 7863 message display. 7864 </item> 7865 <label> 7866 Parameters: 7867 </label> 7868 <item> 7869 If the <ident/width/ is 0 (zero), <name/GoldED+/ will default to the 7870 current screen width. If a negative value is specified, that value 7871 will be added to the current screen width (thereby decreasing the 7872 display width relative to the screen width). 7873 </item> 7874 <label> 7875 Default: 7876 </label> 7877 <item> 7878 0 7879 </item> 7880 <label> 7881 Notes: 7882 </label> 7883 <item> 7884 If the <ref target=DISPPAGEBAR><kw/DISPPAGEBAR/</ref> keyword is 7885 enabled, the right margin is automatically decreased by one char. 7886 </item> 7887 <label> 7888 Processed by: 7889 </label> 7890 <item> 7891 Mail reader. 7892 </item> 7893 <label> 7894 See also: 7895 </label> 7896 <item> 7897 <!-- FIX ME!!! -->READdecreasemargin, 7898 <!-- FIX ME!!! -->READincreasemargin, 7899 <ref target=DISPPAGEBAR><kw/DISPPAGEBAR/</ref>, 7900 <ref target=EDITQUOTEMARGIN><kw/EDITQUOTEMARGIN/</ref>, 7901 <ref target=PRINTMARGIN><kw/PRINTMARGIN/</ref>, 7902 <ref target=QUOTEMARGIN><kw/QUOTEMARGIN/</ref>, 7903 <ref target=SOUPEXPORTMARGIN><kw/SOUPEXPORTMARGIN/</ref> 7904 </item> 7905 </list> 7906 </div2> 7907 <div2 id=DISPMSGSIZE> 7908 <head> 7909 DISPMSGSIZE 7910 </head> 7911 <list type=gloss> 7912 <label> 7913 Synopsis: 7914 </label> 7915 <item> 7916 <kw/DISPMSGSIZE/ <ident><BYTES/KBYTES/LINES/NO></ident> 7917 </item> 7918 <label> 7919 Description: 7920 </label> 7921 <item> 7922 When enabled, this keyword displays the msgbody size in the lower 7923 left side of the header. The size displayed is for the message body 7924 text only, the header and NUL-terminator (and anything that may lurk 7925 beyond it) is excluded from the calculation. 7926 </item> 7927 <label> 7928 Parameters: 7929 </label> 7930 <item> 7931 The following options are provided: the exact size in <ident/BYTES/, 7932 the rounded size in <ident/KBYTES/, the number of <ident/LINES/, or 7933 <ident/NO/ display at all. 7934 </item> 7935 <label> 7936 Default: 7937 </label> 7938 <item> 7939 <ident/BYTES/ 7940 </item> 7941 <label> 7942 Notes: 7943 </label> 7944 <item> 7945 This feature only works when <hi/reading/ messages. While editing a 7946 message in the internal editor, this feature is disabled - however, 7947 the size will be displayed when you are in the save message menu 7948 (if <ref target=EDITSAVEMENU><kw/EDITSAVEMENU/</ref> is enabled).<lb> 7949 If the <ident/KBYTES/ setting is chosen, the value is rounded 7950 according to the following formula: kbytes = (bytes + 512) / 1024. 7951 So a 600 bytes file is rounded up to <q/1k/, but a 500 bytes 7952 file is rounded down to <q/0k/. 7953 </item> 7954 <label> 7955 Processed by: 7956 </label> 7957 <item> 7958 Mail reader. 7959 </item> 7960 <label> 7961 See also: 7962 </label> 7963 <item> 7964 <ref target=DISPATTACHSIZE><kw/DISPATTACHSIZE/</ref>, 7965 <ref target=EDITSAVEMENU><kw/EDITSAVEMENU/</ref> 7966 </item> 7967 </list> 7968 </div2> 7969 <div2 id=DISPPAGEBAR> 7970 <head> 7971 DISPPAGEBAR 7972 </head> 7973 <list type=gloss> 7974 <label> 7975 Synopsis: 7976 </label> 7977 <item> 7978 <kw/DISPPAGEBAR/ <ident><YES/NO></ident> 7979 </item> 7980 <label> 7981 Description: 7982 </label> 7983 <item> 7984 If enabled, a <q/pagebar/ (similar to the scrollbar in GUI's) will 7985 appear on the right margin, telling you about the relative size 7986 and position in the message you are reading. 7987 </item> 7988 <label> 7989 Parameters: 7990 </label> 7991 <item> 7992 If enabled, <name/GoldED+/ will display the pagebar, otherwise will 7993 not. 7994 </item> 7995 <label> 7996 Default: 7997 </label> 7998 <item> 7999 <ident/YES/ 8000 </item> 8001 <label> 8002 Notes: 8003 </label> 8004 <item> 8005 Pagebar is only displayed if a message is longer than a 8006 screenful.<lb> 8007 The pagebar automatically decreases the 8008 <ref target=DISPMARGIN><kw/DISPMARGIN/</ref> by one char. 8009 </item> 8010 <label> 8011 Processed by: 8012 </label> 8013 <item> 8014 Mail reader. 8015 </item> 8016 <label> 8017 See also: 8018 </label> 8019 <item> 8020 <ref target=AREALISTPAGEBAR><kw/AREALISTPAGEBAR/</ref>, 8021 <ref target=DISPMARGIN><kw/DISPMARGIN/</ref>, 8022 <ref target=FILELISTPAGEBAR><kw/FILELISTPAGEBAR/</ref>, 8023 <ref target=MSGLISTPAGEBAR><kw/MSGLISTPAGEBAR/</ref> 8024 </item> 8025 </list> 8026 </div2> 8027 <div2 id=DISPREALMSGNO> 8028 <head> 8029 DISPREALMSGNO 8030 </head> 8031 <list type=gloss> 8032 <label> 8033 Synopsis: 8034 </label> 8035 <item> 8036 <kw/DISPREALMSGNO/ <ident><YES/NO></ident> 8037 </item> 8038 <label> 8039 Description: 8040 </label> 8041 <item> 8042 This keyword controls how the <name/GoldED+/ displays message number 8043 in the message reader. 8044 </item> 8045 <label> 8046 Parameters: 8047 </label> 8048 <item> 8049 If set to <ident/YES/ the actual (real) message numbers will be 8050 displayed. When set to <ident/NO/, <name/GoldED+/ will display 8051 <q/relative/ numbers, which are always sequential from msg number 1. 8052 </item> 8053 <label> 8054 Default: 8055 </label> 8056 <item> 8057 <ident/NO/ 8058 </item> 8059 <label> 8060 Notes: 8061 </label> 8062 <item> 8063 Normally the relative numbers are best, because they reflect the 8064 actual number of messages in the system. 8065 </item> 8066 <label> 8067 Processed by: 8068 </label> 8069 <item> 8070 Mail reader. 8071 </item> 8072 <label> 8073 See also: 8074 </label> 8075 <item> 8076 <!-- FIX ME!!! -->READtogglerealmsgno 8077 </item> 8078 </list> 8079 </div2> 8080 <div2 id=DISPSOFTCR> 8081 <head> 8082 DISPSOFTCR 8083 </head> 8084 <list type=gloss> 8085 <label> 8086 Synopsis: 8087 </label> 8088 <item> 8089 <kw/DISPSOFTCR/ <ident><YES/NO></ident> 8090 </item> 8091 <label> 8092 Description: 8093 </label> 8094 <item> 8095 This option controls how <name/GoldED+/ will process the so-called 8096 <gi/Soft-CR/ character (<name/ASCII/ 141, hexadecimal 8Dh) when 8097 display message containing this character. 8098 </item> 8099 <label> 8100 Parameters: 8101 </label> 8102 <item> 8103 If enabled, <name/GoldED+/ will treat the <gi/Soft-CR/ character just 8104 like any other displayable character, instead of ignoring it like 8105 linefeed chars. 8106 </item> 8107 <label> 8108 Default: 8109 </label> 8110 <item> 8111 <ident/NO/ 8112 </item> 8113 <label> 8114 Notes: 8115 </label> 8116 <item> 8117 Enabling this feature is <hi/mandatory/ to make 8118 <ref target=EDITSOFTCRXLAT><kw/EDITSOFTCRXLAT/</ref> feature 8119 working.<lb> 8120 The <name/Ezycom/ message base format requires the <gi/Soft-CR/ to 8121 terminate each line. Therefore this feature is unlikely to be useful 8122 to <name/Ezycom/ sysops.<lb> 8123 The similar functionality may be obtained by defining translation 8124 table with <gi/Soft-CR/ translated to the space character. This may 8125 be useful if you need different settings for the different areas.<lb> 8126 Note that by enabling this feature, you <hi/disable/ the character 8127 translation feature that uses the <gi/Soft-CR/ as an escape character 8128 (this applies only to so-called <q/COMPOSED/ charset). 8129 </item> 8130 <label> 8131 Processed by: 8132 </label> 8133 <item> 8134 Mail reader. 8135 </item> 8136 <label> 8137 See also: 8138 </label> 8139 <item> 8140 <ref target=EDITSOFTCRXLAT><kw/EDITSOFTCRXLAT/</ref>, 8141 <ref target=XLATIMPORT><kw/XLATIMPORT/</ref> 8142 </item> 8143 </list> 8144 </div2> 8145 <div2 id=DISPSTATUSLINE> 8146 <head> 8147 DISPSTATUSLINE 8148 </head> 8149 <list type=gloss> 8150 <label> 8151 Synopsis: 8152 </label> 8153 <item> 8154 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 8155 </item> 8156 <label> 8157 Description: 8158 </label> 8159 <item> 8160 This keyword controls statusline appearance in the <name/GoldED+/. 8161 </item> 8162 <label> 8163 Parameters: 8164 </label> 8165 <item> 8166 If set to <ident/NO/, the statusline at the bottom will be disabled. 8167 </item> 8168 <label> 8169 Default: 8170 </label> 8171 <item> 8172 <ident/YES/ 8173 </item> 8174 <label> 8175 Processed by: 8176 </label> 8177 <item> 8178 Mail reader. 8179 </item> 8180 <label> 8181 See also: 8182 </label> 8183 <item> 8184 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 8185 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 8186 </item> 8187 </list> 8188 </div2> 8189 <div2 id=DISPTABSIZE> 8190 <head> 8191 DISPTABSIZE 8192 </head> 8193 <list type=gloss> 8194 <label> 8195 Synopsis: 8196 </label> 8197 <item> 8198 <kw/DISPTABSIZE/ <ident/<size>/ 8199 </item> 8200 <label> 8201 Description: 8202 </label> 8203 <item> 8204 This keyword defines the tab size (number of spaces) used when 8205 displaying the tab (<name/ASCII/ 9) character, when pressing 8206 keys assigned to <!-- FIX ME!!! -->EDITtab and 8207 <!-- FIX ME!!! -->EDITtabreverse, and when importing external data 8208 in the internal editor. 8209 </item> 8210 <label> 8211 Parameters: 8212 </label> 8213 <item> 8214 The <ident/size/ specifies tab width in the characters. 8215 </item> 8216 <label> 8217 Default: 8218 </label> 8219 <item> 8220 8 8221 </item> 8222 <label> 8223 Notes: 8224 </label> 8225 <item> 8226 If you use an external editor, you should switch it to create spaces 8227 instead of tabs, because tabs are technically not allowed in 8228 <name/FidoNet/ technology messages. 8229 </item> 8230 <label> 8231 Processed by: 8232 </label> 8233 <item> 8234 Mail reader. 8235 </item> 8236 <label> 8237 See also: 8238 </label> 8239 <item> 8240 <!-- FIX ME!!! -->EDITimportquotebuf, 8241 <!-- FIX ME!!! -->EDITimporttext, 8242 <!-- FIX ME!!! -->EDITpaste, 8243 <!-- FIX ME!!! -->EDITtab, 8244 <!-- FIX ME!!! -->EDITtabreverse 8245 </item> 8246 </list> 8247 </div2> 8248 <div2 id=DOSPROMPT> 8249 <head> 8250 DOSPROMPT 8251 </head> 8252 <list type=gloss> 8253 <label> 8254 Synopsis: 8255 </label> 8256 <item> 8257 <kw/DOSPROMPT/ <ident><YES/NO></ident> 8258 </item> 8259 <label> 8260 Description: 8261 </label> 8262 <item> 8263 Controls whether <name/GoldED+/ should add a message about itself to 8264 the operating system shell prompt when shelling out. 8265 </item> 8266 <label> 8267 Parameters: 8268 </label> 8269 <item> 8270 If set to <ident/YES/, the <name/GoldED+/ will add the message 8271 defined with <ref target=LOADLANGUAGE><kw/MS_PROMPT/</ref> keyword in 8272 the language configuration file to the system shell. 8273 </item> 8274 <label> 8275 Default: 8276 </label> 8277 <item> 8278 <ident/YES/ 8279 </item> 8280 <label> 8281 Bugs: 8282 </label> 8283 <item> 8284 This feature is known to be broken on some platforms. 8285 </item> 8286 <label> 8287 Processed by: 8288 </label> 8289 <item> 8290 Mail reader. 8291 </item> 8292 <label> 8293 See also: 8294 </label> 8295 <item> 8296 <!-- FIX ME!!! -->AREAdosshell, 8297 <!-- FIX ME!!! -->EDITdosshell, 8298 <!-- FIX ME!!! -->FILEdosshell, 8299 <!-- FIX ME!!! -->LISTdosshell, 8300 <!-- FIX ME!!! -->NODEdosshell, 8301 <!-- FIX ME!!! -->READdosshell, 8302 <ref target=EVENT><kw/EVENT/</ref>, 8303 <ref target=LOADLANGUAGE><kw/LOADLANGUAGE/</ref> 8304 </item> 8305 </list> 8306 </div2> 8307 <div2 id=EDITAUTOATTACH> 8308 <head> 8309 EDITAUTOATTACH 8310 </head> 8311 <list type=gloss> 8312 <label> 8313 Synopsis: 8314 </label> 8315 <item> 8316 <kw/EDITAUTOATTACH/ <ident><YES/NO></ident> 8317 </item> 8318 <label> 8319 Description: 8320 </label> 8321 <item> 8322 If you use drivespec (<code/C:/, <code/D:/, etc.) in the subject in 8323 a netmail message, <name/GoldED+/ can automatically turn on the file 8324 attach attribute. Autoattaching only works if the subject has been 8325 edited, so that subject files will not automatically be re-attached 8326 in replies. 8327 </item> 8328 <label> 8329 Parameters: 8330 </label> 8331 <item> 8332 If set to <ident/YES/ this feature is enabled, otherwise disabled. 8333 </item> 8334 <label> 8335 Default: 8336 </label> 8337 <item> 8338 <ident/YES/ 8339 </item> 8340 <label> 8341 Processed by: 8342 </label> 8343 <item> 8344 Mail reader. 8345 </item> 8346 <label> 8347 See also: 8348 </label> 8349 <item> 8350 <ref target=ATTACHPATH><kw/ATTACHPATH/</ref>, 8351 <ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref> 8352 </item> 8353 </list> 8354 </div2> 8355 <div2> 8356 <head> 8357 EDITAUTOSAVE 8358 </head> 8359 <list type=gloss> 8360 <label> 8361 Synopsis: 8362 </label> 8363 <item> 8364 <kw/EDITAUTOSAVE/ <ident/<seconds>/ 8365 </item> 8366 <label> 8367 Description: 8368 </label> 8369 <item> 8370 This keyword provides the way for keeping automatic backup of the 8371 message you are writing. The saved file can be restored with the 8372 <!-- FIX ME --><kw/EDITloadfile/ command. The name of the saved file 8373 is defined with the <ref target=EDITORFILE><kw/EDITORFILE/</ref> 8374 keyword.<lb> 8375 If disaster strikes (crash, lockup, power blackout, etc.) while 8376 you are writing a message in the internal editor, this feature 8377 lets you continue from the last autosaved message, which will 8378 popup automatically when you enter the internal editor again. 8379 </item> 8380 <label> 8381 Parameters: 8382 </label> 8383 <item> 8384 If a non-zero value is given, the internal editor will automatically 8385 execute the <!-- FIX ME!!! --><kw/EDITsavefile/ function with 8386 intervals of <ident/seconds/. 8387 </item> 8388 <label> 8389 Default: 8390 </label> 8391 <item> 8392 30 8393 </item> 8394 <label> 8395 Notes: 8396 </label> 8397 <item> 8398 This feature only works 100% if 8399 <ref target=KEYBMODE><kw/KEYBMODE/</ref> is set to <ident/POLL/. 8400 If <ref target=KEYBMODE><kw/KEYBMODE/</ref> is set to <ident/BLOCK/, 8401 autosave won't happen until you press a key after the interval has 8402 passed. 8403 </item> 8404 <label> 8405 Processed by: 8406 </label> 8407 <item> 8408 Mail reader. 8409 </item> 8410 <label> 8411 See also: 8412 </label> 8413 <item> 8414 <!-- FIX ME!!! --><kw/EDITloadfile/, 8415 <!-- FIX ME!!! --><kw/EDITsavefile/, 8416 <ref target=EDITORFILE><kw/EDITORFILE/</ref>, 8417 <ref target=KEYBMODE><kw/KEYBMODE/</ref> 8418 </item> 8419 </list> 8420 </div2> 8421 <div2 id=EDITCHANGEDATE> 8422 <head> 8423 EDITCHANGEDATE 8424 </head> 8425 <list type=gloss> 8426 <label> 8427 Synopsis: 8428 </label> 8429 <item> 8430 <kw/EDITCHANGEDATE/ <ident><ALWAYS/YES/NO></ident> 8431 </item> 8432 <label> 8433 Description: 8434 </label> 8435 <item> 8436 This keyword controls whether <name/GoldED+/ should change the date 8437 timestamp of the changed message. 8438 </item> 8439 <label> 8440 Parameters: 8441 </label> 8442 <item> 8443 If set to <ident/ALWAYS/, <name/GoldED+/ will always <q/touch/ the 8444 message date in the header after saving it. If set to <ident/YES/, 8445 <name/GoldED+/ will only <q/touch/ the message date in the header, 8446 if you change a message written by yourself. This is useful in cases 8447 such as when you need to edit messages written by other people 8448 which may be mis-addressed or something without messing up the date. 8449 If set to <ident/NO/, the message date is not changed when changing a 8450 message. 8451 </item> 8452 <label> 8453 Default: 8454 </label> 8455 <item> 8456 <ident/YES/ 8457 </item> 8458 <label> 8459 Processed by: 8460 </label> 8461 <item> 8462 Mail reader. 8463 </item> 8464 <label> 8465 See also: 8466 </label> 8467 <item> 8468 <!-- FIX ME!!! -->READchangemsg 8469 </item> 8470 </list> 8471 </div2> 8472 <div2 id=EDITCHARPARA> 8473 <head> 8474 EDITCHARPARA 8475 </head> 8476 <list type=gloss> 8477 <label> 8478 Synopsis: 8479 </label> 8480 <item> 8481 <kw/EDITCHARPARA/ <ident/[']<char>[']/ 8482 </item> 8483 <label> 8484 Description: 8485 </label> 8486 <item> 8487 This keyword defines the character <name/GoldED+/ will display at the 8488 end of paragraphs in the internal editor. This is where the <gi/CR/ 8489 character will be placed once the msg is saved. 8490 </item> 8491 <label> 8492 Parameters: 8493 </label> 8494 <item> 8495 The <ident/char/ defines the character <name/GoldED+/ will display at 8496 the end of paragraphs in the internal editor. The space character 8497 should be enclosed in quotes. 8498 </item> 8499 <label> 8500 Default: 8501 </label> 8502 <item> 8503 <ident/' '/ 8504 </item> 8505 <label> 8506 Notes: 8507 </label> 8508 <item> 8509 This keyword is primarily for debugging, the suggested replacement 8510 is a paragraph sign (<name/ASCII/ 20). 8511 </item> 8512 <label> 8513 Processed by: 8514 </label> 8515 <item> 8516 Mail reader. 8517 </item> 8518 <label> 8519 See also: 8520 </label> 8521 <item> 8522 <ref target=EDITCHARSPACE><kw/EDITCHARSPACE/</ref> 8523 </item> 8524 </list> 8525 </div2> 8526 <div2 id=EDITCHARSPACE> 8527 <head> 8528 EDITCHARSPACE 8529 </head> 8530 <list type=gloss> 8531 <label> 8532 Synopsis: 8533 </label> 8534 <item> 8535 <kw/EDITCHARSPACE/ <ident/[']<char>[']/ 8536 </item> 8537 <label> 8538 Description: 8539 </label> 8540 <item> 8541 This keyword defines the character <name/GoldED+/ will display 8542 instead of a space character in the internal editor. 8543 </item> 8544 <label> 8545 Parameters: 8546 </label> 8547 <item> 8548 The <ident/char/ defines the character <name/GoldED+/ will display 8549 instead of a space character in the internal editor. The space 8550 character should be enclosed in quotes. 8551 </item> 8552 <label> 8553 Default: 8554 </label> 8555 <item> 8556 <ident/' '/ 8557 </item> 8558 <label> 8559 Notes: 8560 </label> 8561 <item> 8562 This keyword is primarily for debugging, the suggested replacement 8563 is a small dot (CP437 250). 8564 </item> 8565 <label> 8566 Processed by: 8567 </label> 8568 <item> 8569 Mail reader. 8570 </item> 8571 <label> 8572 See also: 8573 </label> 8574 <item> 8575 <ref target=EDITCHARPARA><kw/EDITCHARPARA/</ref> 8576 </item> 8577 </list> 8578 </div2> 8579 <div2 id=EDITCOMMENT> 8580 <head> 8581 EDITCOMMENT 8582 </head> 8583 <list type=gloss> 8584 <label> 8585 Synopsis: 8586 </label> 8587 <item> 8588 <kw/EDITCOMMENT/ <ident><<![ CDATA ["word"]]>> 8589 <<![ CDATA ["comment"]]>></ident> 8590 </item> 8591 <label> 8592 Description: 8593 </label> 8594 <item> 8595 This feature allows you to define words which causes <name/GoldED+/ 8596 to display a comment in the statusline, when you place the cursor on 8597 the word in the internal editor. 8598 </item> 8599 <label> 8600 Parameters: 8601 </label> 8602 <item> 8603 The <ident/word/ defines the substring which should cause displaying 8604 of the <ident/comment/ in the statusline. 8605 </item> 8606 <label> 8607 Processed by: 8608 </label> 8609 <item> 8610 Mail reader. 8611 </item> 8612 <label> 8613 See also: 8614 </label> 8615 <item> 8616 <ref target=DISPSTATUSLINE><kw/DISPSTATUSLINE/</ref>, 8617 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 8618 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 8619 </item> 8620 <label> 8621 Example: 8622 </label> 8623 <item><eg><![ CDATA [ 8624EDITCOMMENT ":-(" "Don't worry, be happy!" 8625EDITCOMMENT ":-)" "Are we having fun yet?" 8626EDITCOMMENT ";-)" "Wink wink, nudge nugde..." 8627EDITCOMMENT "!!!" "Flame Warning!" 8628EDITCOMMENT "GoldED" "Great program, isn't it?" 8629EDITCOMMENT "Odin" "One more 'n' please." 8630EDITCOMMENT "Odinn" "That's right :-)"]]></eg> 8631 </item> 8632 </list> 8633 </div2> 8634 <div2> 8635 <head> 8636 EDITCOMPLETION 8637 </head> 8638 <list type=gloss> 8639 <label> 8640 Synopsis: 8641 </label> 8642 <item> 8643 <kw/EDITCOMPLETION/ <ident><<![ CDATA ["abbreviation"]]>> 8644 <<![ CDATA ["completion"]]>></ident> 8645 </item> 8646 <label> 8647 Description: 8648 </label> 8649 <item> 8650 This keyword allows you to define abbreviations which will be 8651 automatically expanded to full words or sentences when typed in 8652 the internal editor. 8653 </item> 8654 <label> 8655 Parameters: 8656 </label> 8657 <item> 8658 The <ident/abbreviation/ defines the substring which should will be 8659 automatically expanded to <ident/completion/. 8660 </item> 8661 <label> 8662 Notes: 8663 </label> 8664 <item> 8665 The abbreviation is case-sensitive. If <![ CDATA ["XX"]]> is defined 8666 as an abbreviation, completion will <b/not/ be triggered if 8667 <![ CDATA ["xx"]]> is typed. 8668 </item> 8669 <label> 8670 Processed by: 8671 </label> 8672 <item> 8673 Mail reader. 8674 </item> 8675 <label> 8676 See also: 8677 </label> 8678 <item> 8679 <!-- FIX ME!!! --><kw/Macro/, 8680 <!-- FIX ME!!! --><kw/EDITmacro/, 8681 <ref target=DISPSTATUSLINE><kw/DISPSTATUSLINE/</ref>, 8682 <ref target=EDITCOMMENT><kw/EDITCOMMENT/</ref> 8683 </item> 8684 <label> 8685 Example: 8686 </label> 8687 <item><eg><![ CDATA [ 8688EDITCOMPLETION "/Odin" "Odinn" 8689EDITCOMPLETION "/GED" "GoldED" 8690EDITCOMPLETION "/V7" "Version 7" 8691EDITCOMPLETION "/FD" "FrontDoor" 8692EDITCOMPLETION "/WfW" "Windows for Workgroups"]]></eg> 8693 </item> 8694 </list> 8695 </div2> 8696 <div2> 8697 <head> 8698 EDITCRLFTERM 8699 </head> 8700 <list type=gloss> 8701 <label> 8702 Synopsis: 8703 </label> 8704 <item> 8705 <kw/EDITCRLFTERM/ <ident><YES/NO></ident> 8706 </item> 8707 <label> 8708 Description: 8709 </label> 8710 <item> 8711 This keyword controls the format to be used for the paragraph line 8712 termination. 8713 </item> 8714 <label> 8715 Parameters: 8716 </label> 8717 <item> 8718 If set to <ident/YES/, all text paragraphs in your messages will be 8719 terminated with a <gi>CR/LF</gi> combination. If set to <ident/NO/, 8720 only a single <gi/CR/ is used. 8721 </item> 8722 <label> 8723 Default: 8724 </label> 8725 <item> 8726 <ident/NO/ 8727 </item> 8728 <label> 8729 Notes: 8730 </label> 8731 <item> 8732 This option was created to fix a problem with an older version of the 8733 <name/Dutchie/ mail processor, that apparently needed the 8734 <gi>CR/LF</gi> termination of kludge lines. 8735 </item> 8736 <label> 8737 Processed by: 8738 </label> 8739 <item> 8740 Mail reader. 8741 </item> 8742 </list> 8743 </div2> 8744 <div2> 8745 <head> 8746 EDITFIELDCLEAR 8747 </head> 8748 <list type=gloss> 8749 <label> 8750 Synopsis: 8751 </label> 8752 <item> 8753 <kw/EDITFIELDCLEAR/ <ident><YES/NO></ident> 8754 </item> 8755 <label> 8756 Description: 8757 </label> 8758 <item> 8759 This keyword controls the behaviour of the input-fields, if a 8760 non-edit key is the first key pressed. 8761 </item> 8762 <label> 8763 Parameters: 8764 </label> 8765 <item> 8766 If set to <ident/YES/, the input-fields will be automatically cleared 8767 for new entry, if a non-edit key is the first key pressed. 8768 </item> 8769 <label> 8770 Default: 8771 </label> 8772 <item> 8773 <ident/YES/ 8774 </item> 8775 <label> 8776 Processed by: 8777 </label> 8778 <item> 8779 Mail reader. 8780 </item> 8781 </list> 8782 </div2> 8783 8784 8785<!-- finished here --> 8786 8787 8788 <div2> 8789 <head> 8790 EDITHARDLINE <string> 8791 </head> 8792 <p> 8793 ("<<") 8794 </p> 8795 <p> 8796 The string is needed if you use an external editor that terminates 8797 all lines with a CR or CR/LF. The hardline string acts as a text 8798 paragraph terminator, and the normal CR's are ignored. 8799 </p> 8800 <p> 8801 The concept of "hardlines" is explained in the Hardline Feature 8802 chapter. 8803 </p> 8804 <list type=gloss> 8805 <label> 8806 Synopsis: 8807 </label> 8808 <item> 8809 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 8810 </item> 8811 <label> 8812 Description: 8813 </label> 8814 <item> 8815 This keyword controls statusline appearance in the <name/GoldED+/. 8816 </item> 8817 <label> 8818 Parameters: 8819 </label> 8820 <item> 8821 If set to <ident/NO/, the statusline at the bottom will be disabled. 8822 </item> 8823 <label> 8824 Default: 8825 </label> 8826 <item> 8827 <ident/YES/ 8828 </item> 8829 <label> 8830 Processed by: 8831 </label> 8832 <item> 8833 Mail reader. 8834 </item> 8835 <label> 8836 See also: 8837 </label> 8838 <item> 8839 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 8840 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 8841 </item> 8842 </list> 8843 </div2> 8844 <div2> 8845 <head> 8846 EDITHARDLINES <yes/no> 8847 </head> 8848 <p> 8849 (yes) 8850 </p> 8851 <p> 8852 This keyword enables the "hardline" feature. If disabled, the 8853 <kw>EDITHARDLINE</kw> string is never written to the editor message file, 8854 and the editor message file is read back exactly as entered, 8855 including terminating CR's on all lines. 8856 </p> 8857 <list type=gloss> 8858 <label> 8859 Synopsis: 8860 </label> 8861 <item> 8862 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 8863 </item> 8864 <label> 8865 Description: 8866 </label> 8867 <item> 8868 This keyword controls statusline appearance in the <name/GoldED+/. 8869 </item> 8870 <label> 8871 Parameters: 8872 </label> 8873 <item> 8874 If set to <ident/NO/, the statusline at the bottom will be disabled. 8875 </item> 8876 <label> 8877 Default: 8878 </label> 8879 <item> 8880 <ident/YES/ 8881 </item> 8882 <label> 8883 Processed by: 8884 </label> 8885 <item> 8886 Mail reader. 8887 </item> 8888 <label> 8889 See also: 8890 </label> 8891 <item> 8892 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 8893 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 8894 </item> 8895 </list> 8896 </div2> 8897 <div2 id=EDITHARDTERM> 8898 <head> 8899 EDITHARDTERM <yes/no> 8900 </head> 8901 <p> 8902 (no) 8903 </p> 8904 <p> 8905 If enabled, <name>GoldED+</name> will hard-terminate all lines in your messages 8906 at the editor margin. It is recommended to enable this keyword for 8907 Internet e-mail and newsgroups, because some user-unfriendly 8908 Internet software does not wrap long lines properly. But DON'T 8909 enable it in normal FidoNet echomail. 8910 </p> 8911 <p> 8912 This keyword can be used globally and in Random System groups. 8913 <ref target=DISPMARGIN><kw/DISPMARGIN/</ref>, 8914 <ref target=SOUPEXPORTMARGIN><kw/SOUPEXPORTMARGIN/</ref> 8915 </p> 8916 <list type=gloss> 8917 <label> 8918 Synopsis: 8919 </label> 8920 <item> 8921 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 8922 </item> 8923 <label> 8924 Description: 8925 </label> 8926 <item> 8927 This keyword controls statusline appearance in the <name/GoldED+/. 8928 </item> 8929 <label> 8930 Parameters: 8931 </label> 8932 <item> 8933 If set to <ident/NO/, the statusline at the bottom will be disabled. 8934 </item> 8935 <label> 8936 Default: 8937 </label> 8938 <item> 8939 <ident/YES/ 8940 </item> 8941 <label> 8942 Processed by: 8943 </label> 8944 <item> 8945 Mail reader. 8946 </item> 8947 <label> 8948 See also: 8949 </label> 8950 <item> 8951 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 8952 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 8953 </item> 8954 </list> 8955 </div2> 8956 <div2 id=EDITHDRNAMESET> 8957 <head> 8958 EDITHDRNAMESET <pos> <len> 8959 </head> 8960 <p> 8961 (8 36) 8962 </p> 8963 <p> 8964 Specfies the position and length of the from/to name field in the 8965 header edit display. If a negative value is specified, that value 8966 is added to the current display width. 8967 </p> 8968 </div2> 8969 <div2 id=EDITHDRNODESET> 8970 <head> 8971 EDITHDRNODESET <pos> <len> 8972 </head> 8973 <p> 8974 (44 36) 8975 </p> 8976 <p> 8977 Specfies the position and length of the from/to node address field 8978 in the header edit display. If a negative value is specified, that 8979 value is added to the current display width. 8980 </p> 8981 </div2> 8982 <div2 id=EDITHEADERATTRS> 8983 <head> 8984 EDITHEADERATTRS <yes/no> 8985 </head> 8986 <p> 8987 (yes) 8988 </p> 8989 <p> 8990 This keyword allows you to turn off the large attributes window 8991 that is shown during header edit. Even if the window is turned 8992 off, the Alt-keys are still active for toggling attributes. 8993 </p> 8994 <list type=gloss> 8995 <label> 8996 Synopsis: 8997 </label> 8998 <item> 8999 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9000 </item> 9001 <label> 9002 Description: 9003 </label> 9004 <item> 9005 This keyword controls statusline appearance in the <name/GoldED+/. 9006 </item> 9007 <label> 9008 Parameters: 9009 </label> 9010 <item> 9011 If set to <ident/NO/, the statusline at the bottom will be disabled. 9012 </item> 9013 <label> 9014 Default: 9015 </label> 9016 <item> 9017 <ident/YES/ 9018 </item> 9019 <label> 9020 Processed by: 9021 </label> 9022 <item> 9023 Mail reader. 9024 </item> 9025 <label> 9026 See also: 9027 </label> 9028 <item> 9029 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9030 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9031 </item> 9032 </list> 9033 </div2> 9034 <div2> 9035 <head> 9036 EDITHEADERFIRST <new,changes,replies,forwards,yes/no> 9037 </head> 9038 <p> 9039 (yes) 9040 </p> 9041 <p> 9042 This keyword controls the circumstances that will present you with 9043 the header editor first of all. 9044 </p> 9045 <p> 9046 New When entering a new message. 9047 Changes When changing a message 9048 Replies When making a reply. 9049 Forwards When forwarding a message. 9050 Yes Always (all of the above). 9051 No Never. 9052 </p> 9053 <p> 9054 The New, Changes, Replies and Forwards values can be combined. YES 9055 is equivalent to enabling all four of these. 9056 </p> 9057 <p> 9058 For example, we want to edit the header only when entering a new 9059 message or when changing a message: 9060 </p> 9061 <p> 9062 EDITHEADERFIRST New, Changes 9063 </p> 9064 <p> 9065 If the circumstances match the setup of this keyword, the header 9066 edit will be bypassed and you will start directly in the <kw>EDITMENU</kw> 9067 (if enabled) or in the internal or external editor. A new menu 9068 item has been added in the <kw>EDITSAVEMENU</kw>, "Edit Header", which 9069 allows you to edit the header after you have written your message, 9070 but before it is finally saved. 9071 </p> 9072 <p> 9073 If you set <kw>EDITHEADERFIRST</kw> to NO, you must either have the 9074 <kw>EDITSAVEMENU</kw> enabled, or use the internal editor, because 9075 otherwise it is not possible to edit the header at all. 9076 </p> 9077 <list type=gloss> 9078 <label> 9079 Synopsis: 9080 </label> 9081 <item> 9082 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9083 </item> 9084 <label> 9085 Description: 9086 </label> 9087 <item> 9088 This keyword controls statusline appearance in the <name/GoldED+/. 9089 </item> 9090 <label> 9091 Parameters: 9092 </label> 9093 <item> 9094 If set to <ident/NO/, the statusline at the bottom will be disabled. 9095 </item> 9096 <label> 9097 Default: 9098 </label> 9099 <item> 9100 <ident/YES/ 9101 </item> 9102 <label> 9103 Processed by: 9104 </label> 9105 <item> 9106 Mail reader. 9107 </item> 9108 <label> 9109 See also: 9110 </label> 9111 <item> 9112 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9113 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9114 </item> 9115 </list> 9116 </div2> 9117 <div2> 9118 <head> 9119 EDITINTERNAL <yes/no> 9120 </head> 9121 <p> 9122 (yes) 9123 </p> 9124 <p> 9125 Specifies if the internal editor should be the default, even if an 9126 external editor is defined. You can always change the setting in 9127 the editor menu (if <kw>EDITMENU</kw> is enabled) before you start writing 9128 your message. 9129 </p> 9130 <list type=gloss> 9131 <label> 9132 Synopsis: 9133 </label> 9134 <item> 9135 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9136 </item> 9137 <label> 9138 Description: 9139 </label> 9140 <item> 9141 This keyword controls statusline appearance in the <name/GoldED+/. 9142 </item> 9143 <label> 9144 Parameters: 9145 </label> 9146 <item> 9147 If set to <ident/NO/, the statusline at the bottom will be disabled. 9148 </item> 9149 <label> 9150 Default: 9151 </label> 9152 <item> 9153 <ident/YES/ 9154 </item> 9155 <label> 9156 Processed by: 9157 </label> 9158 <item> 9159 Mail reader. 9160 </item> 9161 <label> 9162 See also: 9163 </label> 9164 <item> 9165 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9166 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9167 </item> 9168 </list> 9169 </div2> 9170 <div2> 9171 <head> 9172 EDITMENU <yes/no> 9173 </head> 9174 <p> 9175 (yes) 9176 </p> 9177 <p> 9178 This keyword enables or disables the "Edit menu" that pops up 9179 right after you have edited the message header. If you disable the 9180 menu, you will go to the internal or external editor immediately 9181 and save a keystroke, but you will of course lose the features 9182 available from the menu, such as selection of template etc. 9183 </p> 9184 <list type=gloss> 9185 <label> 9186 Synopsis: 9187 </label> 9188 <item> 9189 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9190 </item> 9191 <label> 9192 Description: 9193 </label> 9194 <item> 9195 This keyword controls statusline appearance in the <name/GoldED+/. 9196 </item> 9197 <label> 9198 Parameters: 9199 </label> 9200 <item> 9201 If set to <ident/NO/, the statusline at the bottom will be disabled. 9202 </item> 9203 <label> 9204 Default: 9205 </label> 9206 <item> 9207 <ident/YES/ 9208 </item> 9209 <label> 9210 Processed by: 9211 </label> 9212 <item> 9213 Mail reader. 9214 </item> 9215 <label> 9216 See also: 9217 </label> 9218 <item> 9219 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9220 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9221 </item> 9222 </list> 9223 </div2> 9224 <div2 id=EDITMIXCASE> 9225 <head> 9226 EDITMIXCASE <yes/no> 9227 </head> 9228 <p> 9229 (no) 9230 </p> 9231 <p> 9232 If this keyword is enabled, <name>GoldED+</name> will automatically format the 9233 name with uppercase the first letter in words and lowercase the 9234 rest, when entering names in the header. 9235 </p> 9236 <p> 9237 Examples: 9238 </p> 9239 <p> 9240 "odinn sorensen" or "ODINN SORENSEN" 9241 </p> 9242 <p> 9243 These would be re-cased to "Odinn Sorensen". 9244 </p> 9245 <list type=gloss> 9246 <label> 9247 Synopsis: 9248 </label> 9249 <item> 9250 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9251 </item> 9252 <label> 9253 Description: 9254 </label> 9255 <item> 9256 This keyword controls statusline appearance in the <name/GoldED+/. 9257 </item> 9258 <label> 9259 Parameters: 9260 </label> 9261 <item> 9262 If set to <ident/NO/, the statusline at the bottom will be disabled. 9263 </item> 9264 <label> 9265 Default: 9266 </label> 9267 <item> 9268 <ident/YES/ 9269 </item> 9270 <label> 9271 Processed by: 9272 </label> 9273 <item> 9274 Mail reader. 9275 </item> 9276 <label> 9277 See also: 9278 </label> 9279 <item> 9280 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9281 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9282 </item> 9283 </list> 9284 </div2> 9285 <div2> 9286 <head> 9287 EDITOR <commandline> [@file] [@line] 9288 </head> 9289 <p> 9290 With <name>GoldED+</name> it is possible to use your favorite text editor or 9291 even word processor to write messages. With this keyword you 9292 specify the commandline for the editor. 9293 </p> 9294 <p> 9295 If you use a word processor, be sure to make it export clean ASCII 9296 text files without control codes. 9297 </p> 9298 <p> 9299 <commandline> Program commandline. 9300 @file Token which is replaced by the editor message 9301 filename. 9302 @line Token which is replaced by the @Position 9303 template line number. 9304 </p> 9305 <list type=gloss> 9306 <label> 9307 Synopsis: 9308 </label> 9309 <item> 9310 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9311 </item> 9312 <label> 9313 Description: 9314 </label> 9315 <item> 9316 This keyword controls statusline appearance in the <name/GoldED+/. 9317 </item> 9318 <label> 9319 Parameters: 9320 </label> 9321 <item> 9322 If set to <ident/NO/, the statusline at the bottom will be disabled. 9323 </item> 9324 <label> 9325 Default: 9326 </label> 9327 <item> 9328 <ident/YES/ 9329 </item> 9330 <label> 9331 Processed by: 9332 </label> 9333 <item> 9334 Mail reader. 9335 </item> 9336 <label> 9337 See also: 9338 </label> 9339 <item> 9340 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9341 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9342 </item> 9343 </list> 9344 </div2> 9345 <div2 id=EDITORFILE> 9346 <head> 9347 EDITORFILE <file> 9348 </head> 9349 <p> 9350 (GOLDED.MSG) 9351 </p> 9352 <p> 9353 Defines the name of the temporary editor message file. This file 9354 is written by <name>GoldED+</name> when swapping to the external editor, or when 9355 using the <kw>EDITsavefile</kw> command in the internal editor. 9356 </p> 9357 <p> 9358 The file is written in the GOLDPATH if there is no explicit path. 9359 </p> 9360 <list type=gloss> 9361 <label> 9362 Synopsis: 9363 </label> 9364 <item> 9365 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9366 </item> 9367 <label> 9368 Description: 9369 </label> 9370 <item> 9371 This keyword controls statusline appearance in the <name/GoldED+/. 9372 </item> 9373 <label> 9374 Parameters: 9375 </label> 9376 <item> 9377 If set to <ident/NO/, the statusline at the bottom will be disabled. 9378 </item> 9379 <label> 9380 Default: 9381 </label> 9382 <item> 9383 <ident/YES/ 9384 </item> 9385 <label> 9386 Processed by: 9387 </label> 9388 <item> 9389 Mail reader. 9390 </item> 9391 <label> 9392 See also: 9393 </label> 9394 <item> 9395 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9396 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9397 </item> 9398 </list> 9399 </div2> 9400 <div2 id=EDITQUOTEMARGIN> 9401 <head> 9402 EDITQUOTEMARGIN <margin> 9403 </head> 9404 <p> 9405 (75) 9406 </p> 9407 <p> 9408 Sets the right margin for editing quoted lines in the internal 9409 editor. This should be set to the same or wider than the 9410 <kw>QUOTEMARGIN</kw>. 9411 </p> 9412 <list type=gloss> 9413 <label> 9414 Synopsis: 9415 </label> 9416 <item> 9417 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9418 </item> 9419 <label> 9420 Description: 9421 </label> 9422 <item> 9423 This keyword controls statusline appearance in the <name/GoldED+/. 9424 </item> 9425 <label> 9426 Parameters: 9427 </label> 9428 <item> 9429 If set to <ident/NO/, the statusline at the bottom will be disabled. 9430 </item> 9431 <label> 9432 Default: 9433 </label> 9434 <item> 9435 <ident/YES/ 9436 </item> 9437 <label> 9438 Processed by: 9439 </label> 9440 <item> 9441 Mail reader. 9442 </item> 9443 <label> 9444 See also: 9445 </label> 9446 <item> 9447 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9448 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9449 </item> 9450 </list> 9451 </div2> 9452 <div2 id=EDITREPLYRE> 9453 <head> 9454 EDITREPLYRE <yes/no/numeric> 9455 </head> 9456 <p> 9457 (no) 9458 </p> 9459 <p> 9460 If enabled, <name>GoldED+</name> inserts the "Re:" string in front of the 9461 subject when you reply to a message. If not enabled, <name>GoldED+</name> will 9462 strip any leading "Re:" when you reply to a msg. 9463 </p> 9464 <p> 9465 The "Re:" string in subjects is an obsolete practice, and today it 9466 only slows down modern replylinking software. Do yourself and 9467 others a favor and let <name>GoldED+</name> strip the Re: in your replies. 9468 </p> 9469 <p> 9470 The "numeric" option makes <name>GoldED+</name> use numeric Re:'s, of the form 9471 "Re^n:". 9472 </p> 9473 <p> 9474 This keyword can be used globally and in Random System groups. 9475 </p> 9476 <list type=gloss> 9477 <label> 9478 Synopsis: 9479 </label> 9480 <item> 9481 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9482 </item> 9483 <label> 9484 Description: 9485 </label> 9486 <item> 9487 This keyword controls statusline appearance in the <name/GoldED+/. 9488 </item> 9489 <label> 9490 Parameters: 9491 </label> 9492 <item> 9493 If set to <ident/NO/, the statusline at the bottom will be disabled. 9494 </item> 9495 <label> 9496 Default: 9497 </label> 9498 <item> 9499 <ident/YES/ 9500 </item> 9501 <label> 9502 Processed by: 9503 </label> 9504 <item> 9505 Mail reader. 9506 </item> 9507 <label> 9508 See also: 9509 </label> 9510 <item> 9511 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9512 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9513 </item> 9514 </list> 9515 </div2> 9516 <div2 id=EDITSAVEMENU> 9517 <head> 9518 EDITSAVEMENU <yes/no> 9519 </head> 9520 <p> 9521 (yes) 9522 </p> 9523 <p> 9524 This keyword enables or disables the "Save menu" that pops up 9525 after you have edited your message in the internal or external 9526 editor. If you disable the menu, your message will be saved (or 9527 discarded if not edited) immediately and save you a keystroke, but 9528 you will also lose the features available from the menu. 9529 </p> 9530 <list type=gloss> 9531 <label> 9532 Synopsis: 9533 </label> 9534 <item> 9535 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9536 </item> 9537 <label> 9538 Description: 9539 </label> 9540 <item> 9541 This keyword controls statusline appearance in the <name/GoldED+/. 9542 </item> 9543 <label> 9544 Parameters: 9545 </label> 9546 <item> 9547 If set to <ident/NO/, the statusline at the bottom will be disabled. 9548 </item> 9549 <label> 9550 Default: 9551 </label> 9552 <item> 9553 <ident/YES/ 9554 </item> 9555 <label> 9556 Processed by: 9557 </label> 9558 <item> 9559 Mail reader. 9560 </item> 9561 <label> 9562 See also: 9563 </label> 9564 <item> 9565 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9566 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9567 </item> 9568 </list> 9569 </div2> 9570 <div2> 9571 <head> 9572 EDITSAVEUTIL <utilno> <"L menu text"> 9573 </head> 9574 <p> 9575 Defines the external utilities that will be added to the 9576 <kw>EDITSAVEMENU</kw> (if enabled). The menu text is inserted in the menu. 9577 The first two characters of the menu text are the "hotkey" letter 9578 that will be highlighted in the menu text, plus a space. Example: 9579 </p> 9580 <p> 9581 EDITSAVEUTIL 1 "S PGP Sign the msg" 9582 EDITSAVEUTIL 2 "l PGP Clear-Sign the msg" 9583 EDITSAVEUTIL 3 "E PGP Encrypt the msg" 9584 EDITSAVEUTIL 4 "p PGP Encrypt & Sign the msg" 9585 </p> 9586 <p> 9587 If you have changed the default language in this menu (in 9588 GOLDLANG.CFG), then make sure the highlight letters don't clash. 9589 </p> 9590 <p> 9591 With <kw>EDITSAVEUTIL</kw> definitions and <kw>EDITSAVEMENU</kw> enabled, you can 9592 directly call an external utility to do things like encoding or 9593 encrypting msgs before saving them. 9594 </p> 9595 <list type=gloss> 9596 <label> 9597 Synopsis: 9598 </label> 9599 <item> 9600 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9601 </item> 9602 <label> 9603 Description: 9604 </label> 9605 <item> 9606 This keyword controls statusline appearance in the <name/GoldED+/. 9607 </item> 9608 <label> 9609 Parameters: 9610 </label> 9611 <item> 9612 If set to <ident/NO/, the statusline at the bottom will be disabled. 9613 </item> 9614 <label> 9615 Default: 9616 </label> 9617 <item> 9618 <ident/YES/ 9619 </item> 9620 <label> 9621 Processed by: 9622 </label> 9623 <item> 9624 Mail reader. 9625 </item> 9626 <label> 9627 See also: 9628 </label> 9629 <item> 9630 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9631 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9632 </item> 9633 </list> 9634 </div2> 9635 <div2 id=EDITSOFTCRXLAT> 9636 <head> 9637 EDITSOFTCRXLAT <char> 9638 </head> 9639 <p> 9640 If a translation char is defined, <name>GoldED+</name> will translate the 9641 soft-cr character (ASCII 141, HEX 8D) while saving message to base. 9642 The following example translates the soft-cr to an 'H' (for use in Russia): 9643 </p> 9644 <p> 9645 EDITSOFTCRXLAT H 9646 </p> 9647 <p> 9648 You also have to enable the <kw>DISPSOFTCR</kw> keyword. 9649 </p> 9650 <list type=gloss> 9651 <label> 9652 Synopsis: 9653 </label> 9654 <item> 9655 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9656 </item> 9657 <label> 9658 Description: 9659 </label> 9660 <item> 9661 This keyword controls statusline appearance in the <name/GoldED+/. 9662 </item> 9663 <label> 9664 Parameters: 9665 </label> 9666 <item> 9667 If set to <ident/NO/, the statusline at the bottom will be disabled. 9668 </item> 9669 <label> 9670 Default: 9671 </label> 9672 <item> 9673 <ident/YES/ 9674 </item> 9675 <label> 9676 Processed by: 9677 </label> 9678 <item> 9679 Mail reader. 9680 </item> 9681 <label> 9682 See also: 9683 </label> 9684 <item> 9685 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9686 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9687 </item> 9688 </list> 9689 </div2> 9690 <div2> 9691 <head> 9692 EDITSPELLCHECK <commandline> [@file] 9693 </head> 9694 <p> 9695 While in the internal editor, you can use the <kw>EDITspellcheck</kw> 9696 command to save your message to a file and shell to external 9697 spellchecking software. When the check is completed, the corrected 9698 file is read back and you can continue editing your message. The 9699 <kw>EDITspellcheck</kw> command internally uses the <kw>EDITsavefile</kw> and 9700 <kw>EDITloadfile</kw> commands. 9701 </p> 9702 <p> 9703 <commandline> Spellchecker program commandline. 9704 [@file] Token which is replaced by the message filename 9705 (defined by the <kw>EDITORFILE</kw> keyword). 9706 </p> 9707 <list type=gloss> 9708 <label> 9709 Synopsis: 9710 </label> 9711 <item> 9712 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9713 </item> 9714 <label> 9715 Description: 9716 </label> 9717 <item> 9718 This keyword controls statusline appearance in the <name/GoldED+/. 9719 </item> 9720 <label> 9721 Parameters: 9722 </label> 9723 <item> 9724 If set to <ident/NO/, the statusline at the bottom will be disabled. 9725 </item> 9726 <label> 9727 Default: 9728 </label> 9729 <item> 9730 <ident/YES/ 9731 </item> 9732 <label> 9733 Processed by: 9734 </label> 9735 <item> 9736 Mail reader. 9737 </item> 9738 <label> 9739 See also: 9740 </label> 9741 <item> 9742 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9743 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9744 </item> 9745 </list> 9746 </div2> 9747 <div2> 9748 <head> 9749 EDITUNDELETE <lines> 9750 </head> 9751 <p> 9752 (50) 9753 </p> 9754 <p> 9755 This keyword defines the number of lines to keep in the undelete 9756 buffer between messages. 9757 </p> 9758 <list type=gloss> 9759 <label> 9760 Synopsis: 9761 </label> 9762 <item> 9763 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9764 </item> 9765 <label> 9766 Description: 9767 </label> 9768 <item> 9769 This keyword controls statusline appearance in the <name/GoldED+/. 9770 </item> 9771 <label> 9772 Parameters: 9773 </label> 9774 <item> 9775 If set to <ident/NO/, the statusline at the bottom will be disabled. 9776 </item> 9777 <label> 9778 Default: 9779 </label> 9780 <item> 9781 <ident/YES/ 9782 </item> 9783 <label> 9784 Processed by: 9785 </label> 9786 <item> 9787 Mail reader. 9788 </item> 9789 <label> 9790 See also: 9791 </label> 9792 <item> 9793 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9794 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9795 </item> 9796 </list> 9797 </div2> 9798 <div2> 9799 <head> 9800 EMPTYTEARLINE <yes/no> 9801 </head> 9802 <p> 9803 (no) 9804 </p> 9805 <p> 9806 With this keyword enabled, <name>GoldED+</name> will always strip the tearline 9807 down to just the three dashes, "---", and instead inserts the PID 9808 (Product IDentification) kludge line, which contains the same 9809 information, but in a safer form in a safer place. The PID kludge 9810 is proposed in FidoNet document FSC-0046. 9811 </p> 9812 <list type=gloss> 9813 <label> 9814 Synopsis: 9815 </label> 9816 <item> 9817 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9818 </item> 9819 <label> 9820 Description: 9821 </label> 9822 <item> 9823 This keyword controls statusline appearance in the <name/GoldED+/. 9824 </item> 9825 <label> 9826 Parameters: 9827 </label> 9828 <item> 9829 If set to <ident/NO/, the statusline at the bottom will be disabled. 9830 </item> 9831 <label> 9832 Default: 9833 </label> 9834 <item> 9835 <ident/YES/ 9836 </item> 9837 <label> 9838 Processed by: 9839 </label> 9840 <item> 9841 Mail reader. 9842 </item> 9843 <label> 9844 See also: 9845 </label> 9846 <item> 9847 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9848 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9849 </item> 9850 </list> 9851 </div2> 9852 <div2> 9853 <head> 9854 ENCODEEMAILHEADERS <yes/no> 9855 </head> 9856 <p> 9857 (yes) 9858 </p> 9859 <p> 9860 By default headers in e-mails MIME-encoded according to RFC. In 9861 Russia it is general practice not to encode headers, so you 9862 probably want to say No here if you're in Russia ;-) This keyword 9863 supported only in -asa versions. 9864 </p> 9865 <list type=gloss> 9866 <label> 9867 Synopsis: 9868 </label> 9869 <item> 9870 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9871 </item> 9872 <label> 9873 Description: 9874 </label> 9875 <item> 9876 This keyword controls statusline appearance in the <name/GoldED+/. 9877 </item> 9878 <label> 9879 Parameters: 9880 </label> 9881 <item> 9882 If set to <ident/NO/, the statusline at the bottom will be disabled. 9883 </item> 9884 <label> 9885 Default: 9886 </label> 9887 <item> 9888 <ident/YES/ 9889 </item> 9890 <label> 9891 Processed by: 9892 </label> 9893 <item> 9894 Mail reader. 9895 </item> 9896 <label> 9897 See also: 9898 </label> 9899 <item> 9900 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9901 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9902 </item> 9903 </list> 9904 </div2> 9905 <div2> 9906 <head> 9907 ENDGROUP 9908 </head> 9909 <p> 9910 Ends a Random System <kw>GROUP</kw> definition. 9911 </p> 9912 <list type=gloss> 9913 <label> 9914 Synopsis: 9915 </label> 9916 <item> 9917 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 9918 </item> 9919 <label> 9920 Description: 9921 </label> 9922 <item> 9923 This keyword controls statusline appearance in the <name/GoldED+/. 9924 </item> 9925 <label> 9926 Parameters: 9927 </label> 9928 <item> 9929 If set to <ident/NO/, the statusline at the bottom will be disabled. 9930 </item> 9931 <label> 9932 Default: 9933 </label> 9934 <item> 9935 <ident/YES/ 9936 </item> 9937 <label> 9938 Processed by: 9939 </label> 9940 <item> 9941 Mail reader. 9942 </item> 9943 <label> 9944 See also: 9945 </label> 9946 <item> 9947 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 9948 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 9949 </item> 9950 </list> 9951 </div2> 9952 <div2 id=EVENT> 9953 <head> 9954 EVENT <eventtype> <eventcommand [parameters]> 9955 </head> 9956 <p> 9957 This keyword allows you to specify which soundfile to play when a 9958 specfic event occurs. The following <eventtype>'s are defined: 9959 </p> 9960 <p> 9961 EVENTTYPE TRIGGER: 9962 </p> 9963 <p> 9964 Arealist When the arealist shows. 9965 AskYesNo Any Yes/No type prompt. 9966 Attention Warnings or information popup messages. 9967 DosShell When entering a DOS or OS/2 shell. 9968 EditComment When an editcomment is found. 9969 EndOfMsgs When there are no more msgs in the area. 9970 ErrorFatal Fatal error exit. 9971 Exit Exit from <name>GoldED+</name>. 9972 JobDone Successful completion of a job. 9973 JobFailed Unsuccessful completion of a job. 9974 MsgDeleting When deleting a msg. 9975 MsgFromYou When a msg from you is found. 9976 MsgIsLocal When a msg marked Local is found. 9977 MsgIsTwit When a msg from a Twit is found. 9978 MsgToYou When a msg to you is found. 9979 SearchFailed Search operation failed. 9980 SearchSuccess Search operation was successful. 9981 Startup When the <name>GoldED+</name> startup screen shows. 9982 </p> 9983 <p> 9984 There is currently only one <eventcommand> defined: 9985 </p> 9986 <p> 9987 PLAY <filename.ext/beepnoise>. 9988 </p> 9989 <p> 9990 The parameter to PLAY can be either a sound file or one of the 9991 following standard beepnoises: 9992 </p> 9993 <p> 9994 TheEnd A high and a low note. 9995 GotIt Two sets of low-high notes. 9996 TooBad A falling note. 9997 ToYou A rising and falling note. 9998 SayBiBi A single beep. 9999 SOS Morse S O S (...---...). 10000 </p> 10001 <p> 10002 If a sound file is specified, the sound driver must support the 10003 format. 10004 </p> 10005 <p> 10006 The DOS and 386 versions need a Goldware Sound API compatible TSR 10007 or program loader which installs an interrupt service function on 10008 the multiplex interrupt 2Dh. See the chapter about the Goldware 10009 Sound API for more details. The GCTVSAPI program loader (released 10010 separately) currently only supports the CT-VOICE.DRV driver for 10011 .VOC files. 10012 </p> 10013 <p> 10014 The OS/2 version relies on MMPM/2 (using the mciSendString API 10015 call) to play the sound files. On my system with a Sound Blaster 10016 Pro, MMPM/2 plays both .WAV and (to my surprise) .VOC files. It 10017 even plays .MID files :-) 10018 </p> 10019 <p> 10020 The Win32 version uses the Win32 API to play the sound files. It 10021 should be able to play any multimedia file that Windows knows how 10022 to handle. 10023 </p> 10024 <p> 10025 Example usages: 10026 </p> 10027 <p> 10028 EVENT MsgToYou PLAY HIMAN.VOC 10029 EVENT MsgIsTwit PLAY SHOTGUN.VOC 10030 </p> 10031 <p> 10032 You have to select the sounds carefully and probably with a lot of 10033 experimentation, unless you want to turn your mailreader into a 10034 honking, wailing and farting monster and drive your poor family or 10035 yourself nuts with a cacophony of noises... 10036 </p> 10037 <list type=gloss> 10038 <label> 10039 Synopsis: 10040 </label> 10041 <item> 10042 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 10043 </item> 10044 <label> 10045 Description: 10046 </label> 10047 <item> 10048 This keyword controls statusline appearance in the <name/GoldED+/. 10049 </item> 10050 <label> 10051 Parameters: 10052 </label> 10053 <item> 10054 If set to <ident/NO/, the statusline at the bottom will be disabled. 10055 </item> 10056 <label> 10057 Default: 10058 </label> 10059 <item> 10060 <ident/YES/ 10061 </item> 10062 <label> 10063 Processed by: 10064 </label> 10065 <item> 10066 Mail reader. 10067 </item> 10068 <label> 10069 See also: 10070 </label> 10071 <item> 10072 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 10073 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 10074 </item> 10075 </list> 10076 </div2> 10077 <div2 id=EXCLUDENODES> 10078 <head> 10079 EXCLUDENODES <addressmask> 10080 </head> 10081 <p> 10082 You can define up to 50 different addressmasks to be excluded from 10083 the compiled nodelists. Use this if you are short of space, or the 10084 nodelist compile takes very long on your system. This keyword is 10085 used by GoldNODE. 10086 </p> 10087 <p> 10088 Excluded nodes can be re-included with the <kw>INCLUDENODES</kw> keyword. 10089 </p> 10090 <list type=gloss> 10091 <label> 10092 Synopsis: 10093 </label> 10094 <item> 10095 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 10096 </item> 10097 <label> 10098 Description: 10099 </label> 10100 <item> 10101 This keyword controls statusline appearance in the <name/GoldED+/. 10102 </item> 10103 <label> 10104 Parameters: 10105 </label> 10106 <item> 10107 If set to <ident/NO/, the statusline at the bottom will be disabled. 10108 </item> 10109 <label> 10110 Default: 10111 </label> 10112 <item> 10113 <ident/YES/ 10114 </item> 10115 <label> 10116 Processed by: 10117 </label> 10118 <item> 10119 Mail reader. 10120 </item> 10121 <label> 10122 See also: 10123 </label> 10124 <item> 10125 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 10126 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 10127 </item> 10128 </list> 10129 </div2> 10130 <div2> 10131 <head> 10132 EXTERNOPTIONS <-options> 10133 </head> 10134 <p> 10135 Defines the default options for the <kw>EXTERNUTIL</kw>'s. Valid options: 10136 </p> 10137 <p> 10138 -Cls * Clear screen. 10139 -Cursor * Cursor in shell. 10140 -KeepCtrl * Keep control lines in the message. 10141 -Pause Pause for keypress before returning to <name>GoldED+</name>. 10142 -PauseOnError * Pause only if utility errorlevel is nonzero. 10143 -Reload * Reload the message file (@file). 10144 -Wipe Wipe editorfile and temporary file after use. 10145 </p> 10146 <p> 10147 Plus the reverse options with a "No" prefix, for example -NoCls. 10148 The default options are marked with an asterisk (*). 10149 </p> 10150 <p> 10151 Use -NoKeepCtrl when you want to clearsign a message. This will 10152 strip the control lines (kludges, tearline and origin) from the 10153 message before passing it to the external utility. The tearline 10154 and origin is appended to the message when reloading it. The 10155 default is to keep control lines in the message. 10156 </p> 10157 <p> 10158 Use -Wipe when you want the temporary unencrypted message files to 10159 be wiped and removed from the disk after they have been read into 10160 memory. <name>GoldED+</name> wipes a file by writing a block of 512 random bytes 10161 over the entire length of the file, then truncating it to zero 10162 bytes and finally deleting it. The default is not to wipe files. 10163 </p> 10164 <list type=gloss> 10165 <label> 10166 Synopsis: 10167 </label> 10168 <item> 10169 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 10170 </item> 10171 <label> 10172 Description: 10173 </label> 10174 <item> 10175 This keyword controls statusline appearance in the <name/GoldED+/. 10176 </item> 10177 <label> 10178 Parameters: 10179 </label> 10180 <item> 10181 If set to <ident/NO/, the statusline at the bottom will be disabled. 10182 </item> 10183 <label> 10184 Default: 10185 </label> 10186 <item> 10187 <ident/YES/ 10188 </item> 10189 <label> 10190 Processed by: 10191 </label> 10192 <item> 10193 Mail reader. 10194 </item> 10195 <label> 10196 See also: 10197 </label> 10198 <item> 10199 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 10200 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 10201 </item> 10202 </list> 10203 </div2> 10204 <div2> 10205 <head> 10206 EXTERNUTIL <utilno> [-options] <commandline> 10207 </head> 10208 <p> 10209 This new feature can be used to "filter" msgs, for example calling 10210 PGP or other encryption utilities. 10211 </p> 10212 <p> 10213 The <utilno> must be in the range 1 to 24 for utilities that will 10214 be called with key definitions (see below). Higher numbers can be 10215 used for utilities that are called from the <kw>EDITSAVEMENU</kw> (if 10216 enabled). See the <kw>EDITSAVEUTIL</kw> keyword for details. 10217 </p> 10218 <p> 10219 The default options are those specified with the <kw>EXTERNOPTIONS</kw> 10220 keyword. With [-options], you can change the those options locally 10221 for specific utils. See the <kw>EXTERNOPTIONS</kw> keyword for a list of 10222 valid options. 10223 </p> 10224 <p> 10225 The <commandline> specfies the DOS or OS/2 commandline you want to 10226 execute. This works in the same way as for the external editor and 10227 spellchecker. See the manual for details about this, especially if 10228 you want to execute batchfiles. In the <commandline> you can use 10229 @tokens to transfer information from the msg to the commandline. 10230 The @tokens are the same as for templates, and in addition you can 10231 use two other @tokens: 10232 </p> 10233 <p> 10234 @path The GOLDPATH, including a trailing backslash. 10235 @file The full filename of the message file (GOLDED.MSG) 10236 that will be written to disk before the utility is 10237 called. 10238 @tmpfile The full filename of a temporary message file 10239 (GEDTMPxx.xxx) that will be written to disk before the 10240 utility is called. 10241 </p> 10242 <p> 10243 Examples: 10244 </p> 10245 <p> 10246 EXTERNUTIL 1 c:\4dos\4dos.com /c c:\crypt\encrypt.bat @file 10247 EXTERNUTIL 2 c:\4dos\4dos.com /c c:\crypt\decrypt.bat @file 10248 </p> 10249 <p> 10250 To call a defined external utility, you must assign a key to it. 10251 There are 24 new keyboard commands you can use in GOLDKEYS.CFG for 10252 this purpose: 10253 </p> 10254 <p> 10255 ExternUtilNN 10256 </p> 10257 <p> 10258 Where NN is in the range 01 to 24 _with_ leading zero. Examples: 10259 </p> 10260 <p> 10261 F11 ExternUtil01 10262 F12 ExternUtil02 10263 </p> 10264 <p> 10265 Then if you press F11, you would call external utility number 1 10266 and so on. The <kw>ExternUtilNN</kw> keywords ONLY work in reader mode, not 10267 in the internal editor or any other place. 10268 </p> 10269 <p> 10270 HOW IT WORKS: 10271 </p> 10272 <p> 10273 1. Just before the external utility is called, <name>GoldED+</name> writes the 10274 current message text to the GOLDED.MSG file in the GOLDPATH. 10275 The file is written as a textfile with each line CR-LF 10276 terminated. The content is exactly as you see it on the 10277 screen, which means that kludges are only included if you have 10278 enabled kludge viewing. If the -NoKeepCtrl option is used, 10279 kludges, tearline and origin are stripped before the file is 10280 written. If the token @tmpfile is used, a temporary file named 10281 GEDTMPxx.xxx (where xx.xxx is something unique) is created 10282 with exactly the same content as @file. 10283 </p> 10284 <p> 10285 2. <name>GoldED+</name> clears the screen and then calls the utility. 10286 </p> 10287 <p> 10288 3. The utility can now load and process the @file and/or 10289 @tmpfile, or do anything else you want. It doesn't have to 10290 have anything to do with the current msg. You could call a 10291 spreadsheet, a game, whatever. But I think this feature will 10292 mainly be used for utilities that process the @file. If the 10293 utility processes the @file, it could write the changes back 10294 to the @file. 10295 </p> 10296 <p> 10297 4. After returning from the utility, <name>GoldED+</name> reloads the @file and 10298 displays it just as if it was the current message. For 10299 example, if your utility was a decrypter and the msg was 10300 encrypted, you would now see the decrypted msg. Neat eh? :-) 10301 </p> 10302 <p> 10303 5. If you want to make the reloaded text permanent (save it in 10304 the msg), you can use the Change Msg function and immediately 10305 choose "Save Message" from the Editing menu (if enabled with 10306 EDITMENU Yes). This is in fact the method you could use if you 10307 wanted to EN-crypt a msg (however, it is easier to use the 10308 method which involves the EDITSAVEUTIL keyword). 10309 </p> 10310 <p> 10311 The QUOTESPACING feature can interfere with encoded msgs that 10312 include the '>' character at the beginning of lines (often seen in 10313 uuencoded msgs), by automatically inserting blank lines before and 10314 after the lines with '>'. I have therefore changed the 10315 quotespacing default from YES to NO. Be sure to check if you have 10316 a different setting if you are using an older edition of the 10317 advanced configuration files. 10318 </p> 10319 <p> 10320 If the string "-----BEGIN PGP MESSAGE-----" is found as the first 10321 27 characters in a reloaded message, <name>GoldED+</name> will automatically add 10322 the FSC-0073 kludge "^aENC: PGP" to indicate that the message is 10323 encrypted. This kludge may be used by some software to set up 10324 alternative routing for encrypted mail which would otherwise be 10325 bounced if sent through normal channels. 10326 </p> 10327 <p> 10328 See the "Using PGP as an External Utility" chapter for batchfile 10329 examples and instructions on how to use this new feature with PGP. 10330 </p> 10331 <p> 10332 !!! IMPORTANT !!! From FidoNet Policy 4.07 (chapter 2.1.4): 10333 </p> 10334 <p> 10335 "[..] Therefore, encrypted and/or commercial traffic that is 10336 routed without the express permission of all the links in the 10337 delivery system constitutes annoying behavior." 10338 </p> 10339 <p> 10340 So be careful with this feature! 10341 </p> 10342 <p> 10343 TIP: You can use the EXTERNUTIL feature to setup keys to view or 10344 print an attached fax. Use something like this in GOLDED.CFG: 10345 </p> 10346 <p> 10347 EXTERNUTIL 11 c:\zfax\zfax.com pf @subject ; print fax 10348 EXTERNUTIL 12 c:\zfax\zfax.com vf @subject ; view fax 10349 </p> 10350 <p> 10351 And this in GOLDKEYS.CFG: 10352 </p> 10353 <p> 10354 @F11 ExternUtil11 ; Press Alt-F11 to print the fax 10355 @F12 ExternUtil12 ; Press Alt-F12 to view the fax 10356 </p> 10357 <p> 10358 Or choose your own key assignments and fax view/print utils. 10359 </p> 10360 <p> 10361 Note that this assumes that the fax file is listed in the subject 10362 line like an attached file. 10363 </p> 10364 <p> 10365 NOTE: If you're running <name>GoldED+</name>/386 and try to use a Win32 program 10366 as an EXTERNUTIL, you might get the error "This program cannot be 10367 run in DOS mode". You can work around this by calling the Win32 10368 program via the shell. For example if this call fails: 10369 </p> 10370 <p> 10371 EXTERNUTIL 1 c:\utl\mywin32.exe @file 10372 </p> 10373 <p> 10374 Replace it with: 10375 </p> 10376 <p> 10377 EXTERNUTIL 1 command.com /c c:\utl\mywin32.exe @file 10378 </p> 10379 <p> 10380 Then it should work. If not, try using full path to command.com. 10381 </p> 10382 <list type=gloss> 10383 <label> 10384 Synopsis: 10385 </label> 10386 <item> 10387 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 10388 </item> 10389 <label> 10390 Description: 10391 </label> 10392 <item> 10393 This keyword controls statusline appearance in the <name/GoldED+/. 10394 </item> 10395 <label> 10396 Parameters: 10397 </label> 10398 <item> 10399 If set to <ident/NO/, the statusline at the bottom will be disabled. 10400 </item> 10401 <label> 10402 Default: 10403 </label> 10404 <item> 10405 <ident/YES/ 10406 </item> 10407 <label> 10408 Processed by: 10409 </label> 10410 <item> 10411 Mail reader. 10412 </item> 10413 <label> 10414 See also: 10415 </label> 10416 <item> 10417 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 10418 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 10419 </item> 10420 </list> 10421 </div2> 10422 <div2> 10423 <head> 10424 EZYCOMMSGBASE <path> 10425 </head> 10426 <p> 10427 Defines the base path for the Ezycom msgbase. If not set, AREAFILE 10428 Ezycom will set it. 10429 </p> 10430 <list type=gloss> 10431 <label> 10432 Synopsis: 10433 </label> 10434 <item> 10435 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 10436 </item> 10437 <label> 10438 Description: 10439 </label> 10440 <item> 10441 This keyword controls statusline appearance in the <name/GoldED+/. 10442 </item> 10443 <label> 10444 Parameters: 10445 </label> 10446 <item> 10447 If set to <ident/NO/, the statusline at the bottom will be disabled. 10448 </item> 10449 <label> 10450 Default: 10451 </label> 10452 <item> 10453 <ident/YES/ 10454 </item> 10455 <label> 10456 Processed by: 10457 </label> 10458 <item> 10459 Mail reader. 10460 </item> 10461 <label> 10462 See also: 10463 </label> 10464 <item> 10465 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 10466 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 10467 </item> 10468 </list> 10469 </div2> 10470 <div2> 10471 <head> 10472 EZYCOMUSERBASE <path> 10473 </head> 10474 <p> 10475 Defines the base path for the Ezycom userbase. If not set, 10476 AREAFILE Ezycom will set it. 10477 </p> 10478 <list type=gloss> 10479 <label> 10480 Synopsis: 10481 </label> 10482 <item> 10483 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 10484 </item> 10485 <label> 10486 Description: 10487 </label> 10488 <item> 10489 This keyword controls statusline appearance in the <name/GoldED+/. 10490 </item> 10491 <label> 10492 Parameters: 10493 </label> 10494 <item> 10495 If set to <ident/NO/, the statusline at the bottom will be disabled. 10496 </item> 10497 <label> 10498 Default: 10499 </label> 10500 <item> 10501 <ident/YES/ 10502 </item> 10503 <label> 10504 Processed by: 10505 </label> 10506 <item> 10507 Mail reader. 10508 </item> 10509 <label> 10510 See also: 10511 </label> 10512 <item> 10513 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 10514 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 10515 </item> 10516 </list> 10517 </div2> 10518 <div2 id=EZYCOMUSERNO> 10519 <head> 10520 EZYCOMUSERNO <userno> 10521 </head> 10522 <p> 10523 (0) 10524 </p> 10525 <p> 10526 Defines the lastread set used in the Ezycom message base. 10527 </p> 10528 <list type=gloss> 10529 <label> 10530 Synopsis: 10531 </label> 10532 <item> 10533 <kw/DISPSTATUSLINE/ <ident><YES/NO></ident> 10534 </item> 10535 <label> 10536 Description: 10537 </label> 10538 <item> 10539 This keyword controls statusline appearance in the <name/GoldED+/. 10540 </item> 10541 <label> 10542 Parameters: 10543 </label> 10544 <item> 10545 If set to <ident/NO/, the statusline at the bottom will be disabled. 10546 </item> 10547 <label> 10548 Default: 10549 </label> 10550 <item> 10551 <ident/YES/ 10552 </item> 10553 <label> 10554 Processed by: 10555 </label> 10556 <item> 10557 Mail reader. 10558 </item> 10559 <label> 10560 See also: 10561 </label> 10562 <item> 10563 <ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>, 10564 <ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref> 10565 </item> 10566 </list> 10567 </div2> 10568 10569 10570 10571 10572 10573 10574 10575 10576 10577 10578 <div2> 10579 <head> 10580 FIDOHWMARKS <yes/no> 10581 </head> 10582 <p> 10583 (no) 10584 </p> 10585 <p> 10586 If enabled, <name>GoldED+</name> will use the echomail "highwater mark" (1.MSG) 10587 to determine if a message is "sent" or "unsent" in *.MSG areas. 10588 </p> 10589 <p> 10590 NOTE: Some older echomail processors do not update the highwater 10591 mark in a way that <name>GoldED+</name> can recognize. If all messages appear to 10592 marked "Uns", even after the mail has been scanned out, try 10593 turning off this keyword. 10594 </p> 10595 </div2> 10596 <div2> 10597 <head> 10598 FIDOLASTREAD <file> 10599 </head> 10600 <p> 10601 (LASTREAD) 10602 </p> 10603 <p> 10604 Defines the filename of the *.MSG lastread files. DO NOT specify a 10605 path. 10606 </p> 10607 </div2> 10608 <div2> 10609 <head> 10610 FIDOMSGTYPE <Opus/FTS1> 10611 </head> 10612 <p> 10613 (Opus) 10614 </p> 10615 <p> 10616 This keyword defines the default format of Fido *.MSG files. It is 10617 only used by some AREAFILE's when reading external area 10618 configuration files, where the preferred format is unknown. 10619 </p> 10620 <p> 10621 The FTS1 (FTS-0001.012 and later) format uses zone/point fields, 10622 where the Opus format uses date/time stamps. When set to Opus 10623 format, <name>GoldED+</name> interprets the date/time stamps as DOS-style 10624 bitmapped date/time. 10625 </p> 10626 </div2> 10627 <div2> 10628 <head> 10629 FIDONULLFIX <yes/no> 10630 </head> 10631 <p> 10632 (no) 10633 </p> 10634 <p> 10635 If set to YES, <name>GoldED+</name> will replace NUL chars with LF chars in the 10636 msg body when reading a Fido *.MSG file. This is slower of course, 10637 but not noticably on fast machines. 10638 </p> 10639 <p> 10640 This option was created to enable <name>GoldED+</name> users to read msgs that 10641 were created/handled by brain-dead programs (I don't have names, 10642 sorry) which are not obeying our primary technical standard: 10643 FTS-0001. FTS-1 states that a NUL terminates the msg body. But 10644 sometimes msgs are encountered which have a NUL as the first char 10645 in the msg body or perhaps in other places, thereby causing <name>GoldED+</name> 10646 to show a blank or cut-off msg. In some Pascal-based readers, such 10647 as FM, these msgs can be read anyway, because in Pascal a NUL does 10648 not terminate a string like in C/C++. 10649 </p> 10650 <p> 10651 NOTE: Even if the new FIDONULLFIX keyword is disabled, <name>GoldED+</name> will 10652 still fix a NUL if it is the _first_ character in the msg body. 10653 This probably fixes most of these buggy msgs without the overhead 10654 of checking the entire msg. 10655 </p> 10656 </div2> 10657 <div2> 10658 <head> 10659 FIDOUSERLIST <file> 10660 </head> 10661 <p> 10662 Path and filename of a FIDOUSER.LST file. 10663 </p> 10664 <p> 10665 This file is expected to be sorted in ascending alphabetical order 10666 using plain ASCII case-insensitive sort. Each line in the list is 10667 expected to be 60 characters plus a CR and a LF, or in other words 10668 records of 62 bytes each. If the list is produced by a nodelist 10669 compiler, everything should be okay, but be careful if you have 10670 edited the file manually. Note that a FIDOUSER.LST file only 10671 supports a name lookup (to get the address). 10672 </p> 10673 </div2> 10674 <div2 id=FIDOUSERNO> 10675 <head> 10676 FIDOUSERNO <userno> 10677 </head> 10678 <p> 10679 (0) 10680 </p> 10681 <p> 10682 This is an index into the FIDOLASTREAD file. Each user occupies 2 10683 bytes in the lastread file. 10684 </p> 10685 </div2> 10686 <div2> 10687 <head> 10688 FILEALIAS <alias> <filename> 10689 </head> 10690 <p> 10691 Used to define short alias names for filenames. If you regularly 10692 write msgs to different files in different paths, this feature is 10693 very useful, and reduces the risk of typing wrong. 10694 </p> 10695 <p> 10696 Example: 10697 </p> 10698 <p> 10699 FILEALIAS DKB R:\DKBBS\DKBBS 10700 </p> 10701 <p> 10702 With this file alias, you can simply write "DKB" at the filename 10703 prompt, and the long filename will be used. 10704 </p> 10705 </div2> 10706 <div2 id=FILELISTPAGEBAR> 10707 <head> 10708 FILELISTPAGEBAR <yes/no> 10709 </head> 10710 <p> 10711 (yes) 10712 </p> 10713 <p> 10714 Enables or disables a pagebar (scrollbar) in the file attach list 10715 function. 10716 </p> 10717 </div2> 10718 <div2 id=FORCETEMPLATE> 10719 <head> 10720 FORCETEMPLATE <yes/no> 10721 </head> 10722 <p> 10723 (no) 10724 </p> 10725 <p> 10726 If enabled, <name>GoldED+</name> will popup a template selection menu when you 10727 start writing a new msg or reply. If you have both TEMPLATE(s) and 10728 FORCETEMPLATE in a Random System group, you can tell <name>GoldED+</name> to use 10729 the random template(s) by hitting ESC instead of selecting from 10730 the menu. 10731 </p> 10732 <p> 10733 This keyword can be used globally and in Random System groups. 10734 </p> 10735 </div2> 10736 <div2> 10737 <head> 10738 FORMFEEDSEPARATOR <yes/no> 10739 </head> 10740 <p> 10741 (no) 10742 </p> 10743 <p> 10744 Used when saving messages to file. If enabled, it inserts a Form 10745 Feed (12d) character after each message. 10746 </p> 10747 </div2> 10748 <div2 id=FRQEXT> 10749 <head> 10750 FRQEXT <.ext> 10751 </head> 10752 <p> 10753 With this keyword you can add extra known filename extensions for 10754 the filerequest function. The following extensions are already 10755 known by default, and need not be defined (duplicate definitions 10756 are ignored): 10757 </p> 10758 <p> 10759 .ARC .ARJ .DOC .EXE .GIF .LHA .LZH .JPG .PAK .PNG .RAR .RUN .SDA 10760 .SDN .TXT .ZIP .ZOO 10761 </p> 10762 <p> 10763 Each extension _must_ have the leading dot. 10764 </p> 10765 <p> 10766 Example: FRQEXT .XYZ 10767 </p> 10768 </div2> 10769 <div2 id=FRQNODEMAP> 10770 <head> 10771 FRQNODEMAP <to-node> <from-node> 10772 </head> 10773 <p> 10774 This keyword is used for the file request feature (Ctrl-F). It 10775 allows you to define mappings from a nodenumber used in a file 10776 announcement to another nodenumber. This is useful in the cases 10777 where a multi-line system announces files using their primary 10778 nodenumber, which may be a regular V34 modem number, but they also 10779 have an ISDN number, which you would prefer to use instead. 10780 Examples: 10781 </p> 10782 <p> 10783 // change-to: from: 10784 FRQNODEMAP 2:236/99 2:236/100 10785 FRQNODEMAP 2:236/1043 2:236/43 10786 </p> 10787 <p> 10788 So, if I saw a file announcement from 2:236/100, and requested 10789 some files, the request would automatically be addressed to 10790 2:236/99. 10791 </p> 10792 </div2> 10793 <div2 id=FRQOPTIONS> 10794 <head> 10795 FRQOPTIONS <options> 10796 </head> 10797 <p> 10798 (FromTop) 10799 </p> 10800 <p> 10801 Defines options for the file request function: 10802 </p> 10803 <p> 10804 Sort Sort the list of files alphabetically. 10805 FromTop Scan the message from the top of the message. 10806 NotFromTop Scan the message from the top of the screen. 10807 NoFiles Don't list the file FILES if no files were found. 10808 NoWazooMsg Don't save the request message. 10809 Fast Bypass the header edit and save the msg immediately. 10810 </p> 10811 <p> 10812 By default, the "FromTop" option is enabled. If you often request 10813 files from very long announcement messages, you might find it very 10814 useful to set the "NotFromTop" option. 10815 </p> 10816 <p> 10817 The "NoFiles" option was added because if no filenames are found 10818 in a message, the file request function defaults to listing the 10819 magic name FILES instead of complaining that no files were found. 10820 </p> 10821 <p> 10822 If the FRQWAZOO keyword is enabled, the default behaviour is to 10823 save the request message with the FRQ attribute stripped. Use the 10824 "NoWazooMsg" option if you don't want the request message. 10825 </p> 10826 <p> 10827 Use the "Fast" option if you find that you almost never change the 10828 destination of the file request message anyway. If you enable this 10829 option, remember that you can always go over to the netmail area 10830 and change the file request message before it is sent. 10831 </p> 10832 <p> 10833 The UseFlowFile option enables a feature which was default in 10834 2.50, but which I have been informed is problematic for modern 10835 mailers in some setups. The default is now to ONLY create/update 10836 the .REQ file and NOT also touch/create a .?LO flowfile. 10837 </p> 10838 </div2> 10839 <div2 id=FRQWAZOO> 10840 <head> 10841 FRQWAZOO <yes/no> 10842 </head> 10843 <p> 10844 (no) 10845 </p> 10846 <p> 10847 If enabled, <name>GoldED+</name> will create WaZOO .REQ files instead of file 10848 request messages. You must define an OUTBOUNDPATH if you enable 10849 this feature. 10850 </p> 10851 </div2> 10852 <div2> 10853 <head> 10854 GEDHANDSHAKE <yes/no> 10855 </head> 10856 <p> 10857 (yes) 10858 </p> 10859 <p> 10860 If this switch set to yes GoldEd displays handshake char in 10861 statusline. If you annoyed with this feature you could hide this 10862 character by setting this option to no. 10863 </p> 10864 </div2> 10865 <div2> 10866 <head> 10867 GERMANKEYBOARD <yes/no> 10868 </head> 10869 <p> 10870 (autodetect) 10871 </p> 10872 <p> 10873 This option is meanful for w32 version only. Due to right Alt key 10874 required to enter some native characters in german version of 10875 Windows it could be defined to yes for this. 10876 </p> 10877 </div2> 10878 <div2 id=GOLDBASEPATH> 10879 <head> 10880 GOLDBASEPATH <path> 10881 </head> 10882 <p> 10883 Specifies the directory where <name>GoldED+</name> can find the Goldbase msgbase 10884 files. 10885 </p> 10886 </div2> 10887 <div2 id=GOLDBASESYSPATH> 10888 <head> 10889 GOLDBASESYSPATH <path> 10890 </head> 10891 <p> 10892 Specifies the directory where <name>GoldED+</name> can find the NETMAIL.DAT and 10893 ECHOMAIL.DAT files of the Goldbase msgbase. If not specified, the 10894 GOLDBASEPATH is used. 10895 </p> 10896 </div2> 10897 <div2 id=GOLDBASEUSERNO> 10898 <head> 10899 GOLDBASEUSERNO <userno> 10900 </head> 10901 <p> 10902 (0) 10903 </p> 10904 <p> 10905 Specifies the lastread set used in the Goldbase message base. 10906 </p> 10907 </div2> 10908 <div2 id=GOLDPATH> 10909 <head> 10910 GOLDPATH <path> 10911 </head> 10912 <p> 10913 This is the path where <name>GoldED+</name> finds all it's control files. It is 10914 not necessary to define this, unless you have special needs. The 10915 GOLDPATH defaults to directory where the GOLDED.CFG file was 10916 found. 10917 </p> 10918 </div2> 10919 <div2> 10920 <head> 10921 GROUP <groupname> 10922 </head> 10923 <p> 10924 Starts a Random System group. See the Random System chapter for 10925 details. 10926 </p> 10927 </div2> 10928 <div2 id=HIGHLIGHTUNREAD> 10929 <head> 10930 HIGHLIGHTUNREAD <yes/no> 10931 </head> 10932 <p> 10933 (no) 10934 </p> 10935 <p> 10936 If enabled, <name>GoldED+</name> updates (increases) the "timesread" field in 10937 each message that you read. If set to NO, it doesn't touch the 10938 message. The YES setting causes a slight performance decrease, 10939 because the header of each message has to be read, the timesread 10940 field updated and the header written back to disk. The update 10941 happens immediately after the message is displayed, so you may not 10942 notice it at all. A message is only updated if the timesread field 10943 contains the value 0 (zero). 10944 </p> 10945 <p> 10946 This keyword only works in the following msgbase formats: Fido 10947 (*.MSG), Hudson, Goldbase, JAM, Squish, Ezycom and AdeptXBBS. In 10948 Squish and Ezycom, there is no timesread field, but I have annexed 10949 a reserved message attribute (in Squish, 0x00080000, now called 10950 MSGSEEN; in Ezycom, extattr 0x80) for the purpose of marking a 10951 message as read at least once. The other formats (PCBoard, 10952 WildCat) have no timesread field, but they have reserved fields or 10953 attributes which *could* be used. 10954 </p> 10955 </div2> 10956 <div2 id=HUDSONPATH> 10957 <head> 10958 HUDSONPATH <path> 10959 </head> 10960 <p> 10961 Specifies the directory where <name>GoldED+</name> can find the Hudson msgbase 10962 files. 10963 </p> 10964 </div2> 10965 <div2> 10966 <head> 10967 HUDSONSIZEWARN <size in bytes> 10968 </head> 10969 <p> 10970 (16000000) 10971 </p> 10972 <p> 10973 When the Hudson MSGTXT.BBS file exceeds this size, <name>GoldED+</name> starts 10974 to warn that the msgbase is getting dangerously close to the 10975 structural limit (which is 16MB for the MSGTXT.BBS file). With 10976 this keyword you can raise or lower the warning size in case you 10977 think the default is too low or too high. 10978 </p> 10979 </div2> 10980 <div2 id=HUDSONSYSPATH> 10981 <head> 10982 HUDSONSYSPATH <path> 10983 </head> 10984 <p> 10985 Specifies the directory where <name>GoldED+</name> can find the NETMAIL.BBS and 10986 ECHOMAIL.BBS files of the Hudson msgbase. If not specified, the 10987 HUDSONPATH is used. 10988 </p> 10989 </div2> 10990 <div2 id=HUDSONUSERNO> 10991 <head> 10992 HUDSONUSERNO <userno> 10993 </head> 10994 <p> 10995 (0) 10996 </p> 10997 <p> 10998 Specifies the lastread set used in the Hudson message base. 10999 </p> 11000 </div2> 11001 <div2> 11002 <head> 11003 IGNORECHARSET <yes/no> 11004 </head> 11005 <p> 11006 (no) 11007 </p> 11008 <p> 11009 If set to yes then GoldEd ignores CHRS kludges in messages thus 11010 you will be able to switch codepage in messages with inappropriate 11011 charset. 11012 </p> 11013 </div2> 11014 <div2> 11015 <head> 11016 IMPORTBEGIN <text> 11017 </head> 11018 <p> 11019 ("=== Cut ===") 11020 </p> 11021 <p> 11022 This keyword, together with IMPORTEND, defines some text to add in 11023 the beginning and end of an imported text file in the internal 11024 editor. If only IMPORTBEGIN is defined, the text is also used for 11025 the IMPORTEND. The <text> may be enclosed in quotes ("") if 11026 leading or trailing spaces are needed. The quotes are stripped. 11027 </p> 11028 <p> 11029 The replacement token "@file" can be used in the <text>. It will 11030 be replaced with the import filename as entered. 11031 </p> 11032 <p> 11033 Example: 11034 </p> 11035 <p> 11036 IMPORTBEGIN === Cut Begin: @file === 11037 IMPORTEND === Cut End === 11038 </p> 11039 </div2> 11040 <div2> 11041 <head> 11042 IMPORTEND <text> 11043 </head> 11044 <p> 11045 (same as IMPORTBEGIN) 11046 </p> 11047 <p> 11048 See IMPORTBEGIN. 11049 </p> 11050 </div2> 11051 <div2> 11052 <head> 11053 INBOUNDPATH <path> 11054 </head> 11055 <p> 11056 (defaults to GOLDPATH) 11057 </p> 11058 <p> 11059 The inbound path is currently only used with the file request 11060 feature (the READfilerequest command, <Ctrl-F>). If you use this 11061 feature, <name>GoldED+</name> will put the file descriptions into a FILES.BBS in 11062 the inbound path, ready for when the requested files are moved to 11063 the correct file areas. 11064 </p> 11065 </div2> 11066 <div2 id=INCLUDE> 11067 <head> 11068 INCLUDE 11069 </head> 11070 <list type=gloss> 11071 <label> 11072 Synopsis: 11073 </label> 11074 <item> 11075 <kw/INCLUDE/ <ident/<filename>/ 11076 </item> 11077 <label> 11078 Description: 11079 </label> 11080 <item> 11081 This tells the configuration file reader to stop reading the current 11082 configuration file, and start reading the file specifyed as an 11083 extra configuration source, then resume reading the previous 11084 configuration file. <kw/INCLUDE/ files can be nested without limit. 11085 </item> 11086 <label> 11087 Parameters: 11088 </label> 11089 <item> 11090 The <ident/filename/ parameter should contain absolute path 11091 and name to the configuration file. 11092 </item> 11093 <label> 11094 Processed by: 11095 </label> 11096 <item> 11097 Mail reader and nodelist compiler. 11098 </item> 11099 </list> 11100 </div2> 11101 <div2 id=INCLUDENODES> 11102 <head> 11103 INCLUDENODES <addressmask> 11104 </head> 11105 <p> 11106 You can define up to 50 different addressmasks to be included from 11107 the compiled nodelists. This is only used in conjunction with the 11108 EXCLUDENODES keyword to include otherwise EXcluded nodes. This 11109 keyword is only used by GoldNODE. 11110 </p> 11111 </div2> 11112 <div2 id=INPUTFILE> 11113 <head> 11114 INPUTFILE <filename> 11115 </head> 11116 <p> 11117 (*) 11118 </p> 11119 <p> 11120 Defines the default name in the internal editor file import 11121 function. 11122 </p> 11123 <p> 11124 <name>GoldED+</name> can automatically uuencode and apply a base64 encoding to 11125 the files during importing them into the internal editor. 11126 </p> 11127 <p> 11128 NOTE: This is a very simple implementation of encoders. It cannot 11129 split large files over several messages. The file mode number 644 11130 is hard-coded and has nothing to do with the actual file mode. 11131 </p> 11132 <p> 11133 This keyword can be used globally and in Random System groups. 11134 </p> 11135 </div2> 11136 <div2> 11137 <head> 11138 INTENSECOLORS <yes/no> 11139 </head> 11140 <p> 11141 (no) 11142 </p> 11143 <p> 11144 <name>GoldED+</name> is capable of switching off the "blink" color, and thereby 11145 enabling the use of bright background (paper) colors. Enable this 11146 keyword, and try out one of the intense color setup examples. 11147 </p> 11148 </div2> 11149 <div2 id=INTERNETADDRESS> 11150 <head> 11151 INTERNETADDRESS <internet-address> 11152 </head> 11153 <p> 11154 Specifies your Internet address. This must be the address only, no 11155 name. The INTERNETADDRESS and USERNAME will be combined to a 11156 standard "From: internetaddresss (username)" headerline when you 11157 write e-mail or articles. 11158 </p> 11159 <p> 11160 Example: 11161 </p> 11162 <p> 11163 USERNAME Odinn Sorensen 11164 INTERNETADDRESS odinn@ibm.net 11165 </p> 11166 <p> 11167 Produces the RFC line: 11168 </p> 11169 <p> 11170 From: odinn@ibm.net (Odinn Sorensen) 11171 </p> 11172 </div2> 11173 <div2> 11174 <head> 11175 INTERNETDOMAIN <domainname> 11176 </head> 11177 <p> 11178 (username%domain.net) 11179 </p> 11180 <p> 11181 Defines the domain-part of outgouing Message-ID's. If you don't 11182 know your full domain, leave it as default, which should work just 11183 fine. 11184 </p> 11185 </div2> 11186 <div2 id=INTERNETGATE> 11187 <head> 11188 INTERNETGATE [gatename<,>]<address> 11189 </head> 11190 <p> 11191 Defines the local Internet gate you use when sending netmail to 11192 Internet users. This option is activated when you write an 11193 Internet address in the TO: field in the header display. <name>GoldED+</name> 11194 detects the Internet address by looking for the '@' character. If 11195 detected, <name>GoldED+</name> puts the gate address from INTERNETGATE in the 11196 TO: address field. If you have defined the optional gate name 11197 (typically UUCP), <name>GoldED+</name> also replaces the typed Internet address 11198 with the gate name and puts the Internet address in a TO: line in 11199 the message body. Some gate software accepts the Internet address 11200 directly in the header, while other software may need the special 11201 (UUCP) name and a separate TO: line. Examples: 11202 </p> 11203 <p> 11204 INTERNETGATE UUCP, 1:105/42 ; Standard, with gate name 11205 INTERNETGATE 2:230/9316 ; My uplink runs GIGO software 11206 </p> 11207 <p> 11208 This keyword can be used globally in GOLDED.CFG, if you only ever 11209 use one gate, or in GROUP's for specific areas in GOLDRAND.CFG if 11210 you have multiple netmail areas and regularly use more than one 11211 gate. 11212 </p> 11213 <p> 11214 NOTE: If you enable the INTERNETRFCBODY keyword, you should always 11215 use the gatename UUCP, because otherwise the gateway software may 11216 send duplicate copies (carbon copies) of your e-mails. 11217 </p> 11218 </div2> 11219 <div2> 11220 <head> 11221 INTERNETLOOKUP <yes/no> 11222 </head> 11223 <p> 11224 (no) 11225 </p> 11226 <p> 11227 If set to Yes, <name>GoldED+</name> will check the systemname in the nodelist 11228 when doing a lookup and if the systemname looks like an Internet 11229 address (contains an '@' char), the msg will be addressed to that 11230 Internet address using the INTERNETGATE name/address if defined. 11231 </p> 11232 <p> 11233 For example, let's say there was something like this in the 11234 nodelist: 11235 </p> 11236 <p> 11237 ,999,somebody@somewhere,Whereever,Some_Body,... 11238 </p> 11239 <p> 11240 And this in my GOLDED.CFG: 11241 </p> 11242 <p> 11243 INTERNETLOOKUP Yes 11244 INTERNETGATE 2:230/9316 11245 </p> 11246 <p> 11247 Then if I did a lookup of "Some Body" and selected the entry with 11248 the Internet address, <name>GoldED+</name> would make a msg looking like this: 11249 </p> 11250 <p> 11251 -------------------------------------- 11252 From : odinn@winboss.dk 2:236/77 11253 To : somebody@somewhere 2:230/9316 11254 Subj : whatever 11255 -------------------------------------- 11256 </p> 11257 <p> 11258 Or if my gate was defined as "INTERNETGATE UUCP 2:230/9316": 11259 </p> 11260 <p> 11261 -------------------------------------- 11262 From : odinn@winboss.dk 2:236/77 11263 To : UUCP 2:230/9316 11264 Subj : whatever 11265 -------------------------------------- 11266 To: somebody@somewhere 11267 </p> 11268 <p> 11269 So what's the use of all this? It allows you to make a 11270 nodelist-style list of users with Internet addresses and use it 11271 with <name>GoldED+</name> so that you can do a lookup of normal names instead of 11272 trying to remember strange Internet addresses. Of course something 11273 similar could be done using the ADDRESSMACRO's, but with the 11274 nodelist approach, you could build a "network" of users which have 11275 offline Internet access via FTN-gate software and distribute the 11276 nodelist for automatic processing. 11277 </p> 11278 </div2> 11279 <div2 id=INTERNETMSGID> 11280 <head> 11281 INTERNETMSGID <yes/no> 11282 </head> 11283 <p> 11284 (no) 11285 </p> 11286 <p> 11287 Specifies whether the FTN MSGID kludge should contain an RFC1036 11288 compatible Message-ID or the normal FTS-9 format. Note that using 11289 the RFC1036 format in MSGID breaks the FTS-9 (version 001) 11290 specification, so please don't use this feature in FidoNet netmail 11291 or echomail. As a safeguard, <name>GoldED+</name> will only use the RFC1036 11292 format in areas specifically marked as e-mail or newsgroups, using 11293 the SOUPEMAIL and SOUPNEWSRCFILE keywords or using the Email and 11294 News area types with the AREADEF keyword, even when INTERNETMSGID 11295 is set to YES globally. 11296 </p> 11297 </div2> 11298 <div2> 11299 <head> 11300 INTERNETREPLY <yes/no> 11301 </head> 11302 <p> 11303 (yes) 11304 </p> 11305 <p> 11306 When INTERNETREPLY is enabled, <name>GoldED+</name> always uses the FSC-35 11307 REPLYADDR/REPLYTO kludges to gate replies to msgs from Internet 11308 correctly. If disabled, <name>GoldED+</name> only uses the FSC-35 method if the 11309 Internet address is too large to fit in the max-35-character TO: 11310 header field. Some gate software requires that the FSC-35 method 11311 is used, while other software accepts Internet addresses directly 11312 in the header. 11313 </p> 11314 </div2> 11315 <div2 id=INTERNETRFCBODY> 11316 <head> 11317 INTERNETRFCBODY <yes/no> 11318 </head> 11319 <p> 11320 (no) 11321 </p> 11322 <p> 11323 Tells <name>GoldED+</name> whether to look for and process RFC headerlines at 11324 the top of the message body, before the first empty line. Also 11325 tells <name>GoldED+</name> to insert its own RFC headerlines at the top of the 11326 message body instead of as kludge lines. This option should only 11327 be used when receiving Internet mail as QWK packets where the RFC 11328 headerlines are usually found at the top of the messages, or when 11329 sending Internet mail via FTN packet to a gateway running GIGO. 11330 GIGO does not recognize RFC header in kludges, but it does 11331 recognize them at the top of the messages, if it is properly 11332 configured (with lines of "Allow_Xxx:" in GIGO's HEADERS.CFG, 11333 where Xxx are the RFC headerlines the gate administrator wants to 11334 allow). 11335 </p> 11336 </div2> 11337 <div2> 11338 <head> 11339 INVALIDATE <type> <"findstring"> <"replacestring"> 11340 </head> 11341 <p> 11342 This is used to invalidate (change) certain control strings in 11343 quoted text. Use this in conjunction with old versions of D'Bridge 11344 or other software that chokes on control strings in quoted text. 11345 As an added bonus feature, if the tearline or origin is 11346 invalidated to a null string (""), they will not be quoted at all. 11347 </p> 11348 <p> 11349 The <type> can be one of the following: 11350 </p> 11351 <p> 11352 Tearline Invalidate tearline ("---"). 11353 Origin Invalidate origin (" * Origin: "). 11354 Seenby Invalidate SEEN-BY's. 11355 </p> 11356 <p> 11357 By default, the following invalidations are used: 11358 </p> 11359 <p> 11360 INVALIDATE Tearline "---" "-+-" 11361 INVALIDATE Origin " * Origin: " " + Origin: " 11362 INVALIDATE Seenby "SEEN-BY" "SEEN+BY" 11363 </p> 11364 <p> 11365 If you want to disable invalidation entirely, use this: 11366 </p> 11367 <p> 11368 INVALIDATE Tearline "---" "---" 11369 INVALIDATE Origin " * Origin: " " * Origin: " 11370 INVALIDATE Seenby "SEEN-BY" "SEEN-BY" 11371 </p> 11372 <p> 11373 The defined INVALIDATEs are also used during importing a file when 11374 editing a mail in the internal message editor. 11375 </p> 11376 </div2> 11377 <div2 id=JAMHARDDELETE> 11378 <head> 11379 JAMHARDDELETE <yes/no> 11380 </head> 11381 <p> 11382 (no) 11383 </p> 11384 <p> 11385 The default setting makes <name>GoldED+</name> conform to the JAMAPI specs when 11386 deleting msgs in JAM msgbases. This means that deleted msgs are 11387 only marked as such in the message header, not in the index. As a 11388 result, <name>GoldED+</name> will find and display the deleted msgs until you 11389 run a message pack utility to physically remove the deleted msgs. 11390 </p> 11391 <p> 11392 If JAMHARDDELETE is set to Yes, <name>GoldED+</name> will zap the reference to 11393 the message in the index when deleting msgs. This way the deleted 11394 msgs will not show up again later. The drawback of this approach 11395 is that it is hard to undelete msgs, and may break other software 11396 which assume 100% to-the-letter conformance to the specs. Note 11397 however, that the hard-delete method is transparent to normal use 11398 of JAM msgbases. Probably the only software that might break are 11399 undelete utilities. 11400 </p> 11401 <p> 11402 For the techies and programmers, the hard-delete method is simply 11403 setting both UserCRC and HdrOffset in the index to 0xFFFFFFFF 11404 instead of only the UserCRC. According to the JAMAPI specs, a 11405 value of 0xFFFFFFFF in HdrOffset means that "there is no 11406 corresponding message header". Sounds remarkably like a deleted 11407 msg, right? :-) 11408 </p> 11409 </div2> 11410 <div2> 11411 <head> 11412 JAMPATH <path> 11413 </head> 11414 <p> 11415 (defaults to the HUDSONPATH) 11416 </p> 11417 <p> 11418 Defines the path where <name>GoldED+</name> can access the NETMAIL/ECHOMAIL.JAM 11419 files, which are used by mail processors to find and scan out mail 11420 written by users. 11421 </p> 11422 <p> 11423 <name>GoldED+</name> can handle enviroment variables correctly in paths 11424 specified in connection with this keyword. For example, if a path 11425 is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in 11426 AUTOEXEC.BAT (or whatever), then <name>GoldED+</name> translates the path to 11427 C:\POINT\path\name. 11428 NOTE: The translation is done at config compile time, so if you 11429 change the environment variable and haven't changed anything else 11430 that would cause <name>GoldED+</name> to recompile it's config, you must force 11431 it with the -F or -FF command parameter. 11432 </p> 11433 </div2> 11434 <div2> 11435 <head> 11436 KEYBCLEAR <yes/no> 11437 </head> 11438 <p> 11439 (no) 11440 </p> 11441 <p> 11442 Tells <name>GoldED+</name> whether or not to clear the keyboard buffer on 11443 startup. This also clears KEYBSTACK or commandline key stuffing. 11444 In older versions of <name>GoldED+</name>, it was necessary to enable this 11445 keyword if you had renamed GOLDED.EXE to DBEDIT.EXE. This version 11446 detects the .EXE renaming and automatically enables KEYBCLEAR, 11447 regardless of the configuration setting. 11448 </p> 11449 </div2> 11450 <div2> 11451 <head> 11452 KEYBDEFAULTS <yes/no> 11453 </head> 11454 <p> 11455 (yes) 11456 </p> 11457 <p> 11458 <name>GoldED+</name> defines a default keyboard configuration setup internally. 11459 The keys can be reconfigured in the GOLDKEYS.CFG file. By default, 11460 the internal keyboard setup is active always, redefinable with the 11461 definitions in GOLDKEYS.CFG. But in some cases it can be 11462 preferrable that the internal keyboard setup is turned off, so 11463 that only the keys in GOLDKEYS.CFG are active. If you want this, 11464 set KEYBDEFAULTS to NO. 11465 </p> 11466 </div2> 11467 <div2> 11468 <head> 11469 KEYBEXT <yes/no> 11470 </head> 11471 <p> 11472 (detect) 11473 </p> 11474 <p> 11475 If enabled, <name>GoldED+</name> will use extended bios calls to read the 11476 keyboard. With the extended keyboard, you can use keys like 11477 <Alt-Left>, <Alt-Home> and other extended keys. If you don't have 11478 an extended keyboard, don't despair - using a few neat tricks, I 11479 have made it possible to use some of the extended keys even with a 11480 non-extended keyboard. 11481 </p> 11482 </div2> 11483 <div2 id=KEYBMODE> 11484 <head> 11485 KEYBMODE <poll/block> 11486 </head> 11487 <p> 11488 (poll) 11489 </p> 11490 <p> 11491 If this option is set to Poll, <name>GoldED+</name> switches its keyboard 11492 handling code from "blocking" to "polling" mode. This enables 11493 <name>GoldED+</name> to provide a continuously running statusline clock, 11494 automatic internal editor autosave, timeout exit and screensaver. 11495 If set to Block, the timeout exit and screensaver are disabled, 11496 and the clock and autosave are dependent on key presses. 11497 </p> 11498 <p> 11499 In order to minimize waste of CPU resources in keyboard polling 11500 mode, <name>GoldED+</name> automatically detects DESQview, Windows and OS/2 and 11501 releases timeslices during the keyboard poll. 11502 </p> 11503 </div2> 11504<div2 id=KEYBSTACK><head>KEYBSTACK <keystring></head> 11505 <p> 11506 With this keyword, you can "stack" keys in the keyboard buffer. 11507 The KEYBSTACK can be overridden by commandline keystacking, which 11508 uses the same syntax. 11509 </p> 11510 <p> 11511 The <keystring> can be a mixture of the following: 11512 </p> 11513 <p> 11514 ^Char Ctrl-key (^Letter). 11515 ~Char Ctrl-key (~Letter). (Use this with 4DOS!). 11516 @Key Alt-key (@Number or @Letter). 11517 Char Literal character. 11518 "String" String, enclosed in double quotes. 11519 'String' String, enclosed in single quotes. 11520 Number Keyboard scan code (decimal). 11521 ! Clear keyboard buffer. 11522 </p> 11523 <p> 11524 Whitespace (space and tab) is ignored, except in quoted strings. 11525 </p> 11526 <p> 11527 See the <ptr target=MACROSANDKEYSTACKING> chapter for more info. 11528 </p> 11529 </div2> 11530 <div2> 11531 <head> 11532 KLUDGE <kludge-definition> 11533 </head> 11534 <p> 11535 The definition may optionally be enclosed in quotes. A definition 11536 must be enclosed in quotes if it contains leading or trailing 11537 spaces. The KLUDGE tells <name>GoldED+</name> which kludges it should consider 11538 as "known" in addition to the built-in known kludges. 11539 </p> 11540 <p> 11541 Here are a bunch of examples, most of which are kludges generated 11542 by the GIGO Internet gateway software: 11543 </p> 11544 <p> 11545 KLUDGE " " ; For wrapped kludges 11546 KLUDGE "Content-Type:" 11547 KLUDGE "Date:" 11548 KLUDGE "From:" 11549 KLUDGE "In-Reply-To:" 11550 KLUDGE "Message-Id:" 11551 KLUDGE "Mime-Version:" 11552 KLUDGE "Organization:" 11553 KLUDGE "Newsgroups:" 11554 KLUDGE "Received:" 11555 KLUDGE "Reply-To:" 11556 KLUDGE "Sender:" 11557 KLUDGE "Subject:" 11558 KLUDGE "To:" 11559 KLUDGE "Errors-To:" 11560 KLUDGE "FTN-From:" ; X-FTN-From: 11561 KLUDGE "ORIGREF:" ; Gated? 11562 KLUDGE "ORIGID:" ; Gated? 11563 KLUDGE "RFC-" ; Seen in NET_DEV 11564 </p> 11565 <p> 11566 The kludges defined with KLUDGE are not case-sensitive, but when 11567 <name>GoldED+</name> looks for the kludges, it matches to the exact length. This 11568 means that for example "RFC-" will match all kludges beginning 11569 with that string. 11570 </p> 11571 <p> 11572 The ASCII 1 kludge char should not be included in the definition 11573 string, but <name>GoldED+</name> can handle it if you do. 11574 </p> 11575 </div2> 11576 <div2> 11577 <head> 11578 KLUDGECHRS <yes/no> 11579 </head> 11580 <p> 11581 (yes) 11582 </p> 11583 <p> 11584 If set to YES, <name>GoldED+</name> uses the "^aCHRS" kludge instead of the 11585 "^aCHARSET" kludge when appropriate. 11586 </p> 11587 </div2> 11588 <div2 id=LOADLANGUAGE> 11589 <head> 11590 LOADLANGUAGE <file> 11591 </head> 11592 <p> 11593 If defined, this keyword will load a language definition file. 11594 </p> 11595 <p> 11596 This feature can be used to load a small set of national language 11597 definitions in national areas, an english set in international 11598 areas, etc. Typically this would be used to load the definitions 11599 of the date/time strings for use in the template and the 11600 Msg/From/To/Subj strings in the header display. 11601 </p> 11602 <p> 11603 In the ADVANCED archive, a set of GEDLNG*.CFG files are provided, 11604 which are designed for use with LOADLANGUAGE. Please note that 11605 there is also a @loadlanguage template token. This way you can 11606 choose to load a language file from the template, or by using the 11607 Random System. The template token takes precedence over the 11608 LOADLANGUAGE in the Random System, but if both are defined, both 11609 will be loaded. 11610 </p> 11611 <p> 11612 This keyword can be used globally and in Random System groups, but 11613 it is probably not very useful when used globally. 11614 </p> 11615 </div2> 11616 <div2> 11617 <head> 11618 LOGFILE <file> 11619 </head> 11620 <p> 11621 (GOLDED.LOG) 11622 </p> 11623 <p> 11624 Defines the name of the <name>GoldED+</name> logfile. You should not change the 11625 default. 11626 </p> 11627 </div2> 11628 <div2> 11629 <head> 11630 LOGFORMAT <fd,max,bink,qbbs,db> 11631 </head> 11632 <p> 11633 (fd) 11634 </p> 11635 <p> 11636 Defines the log format <name>GoldED+</name> should use when writing to the 11637 logfile. 11638 </p> 11639 </div2> 11640 <div2> 11641 <head> 11642 LOOKUPECHO <yes/no> 11643 </head> 11644 <p> 11645 (no) 11646 </p> 11647 <p> 11648 If enabled, <name>GoldED+</name> will use nodelist lookup when entering the TO: 11649 name in msgs in echomail areas. 11650 </p> 11651 <p> 11652 <name>GoldED+</name> *won't* lookup the name if it exactly matches the current 11653 WHOTO - text. This is a feature, because a lookup of "All" is not 11654 very useful. :-) 11655 </p> 11656 </div2> 11657 <div2> 11658 <head> 11659 LOOKUPLOCAL <yes/no> 11660 </head> 11661 <p> 11662 (no) 11663 </p> 11664 <p> 11665 If enabled, <name>GoldED+</name> will use nodelist lookup when entering the TO: 11666 name in msgs in local areas. 11667 </p> 11668 <p> 11669 <name>GoldED+</name> *won't* lookup the name if it exactly matches the current 11670 WHOTO - text. This is a feature, because a lookup of "All" is not 11671 very useful. :-) 11672 </p> 11673 </div2> 11674 <div2> 11675 <head> 11676 LOOKUPNET <yes/no> 11677 </head> 11678 <p> 11679 (yes) 11680 </p> 11681 <p> 11682 If enabled, <name>GoldED+</name> will use nodelist lookup when entering the TO: 11683 name in msgs in netmail areas. 11684 </p> 11685 </div2> 11686 <div2> 11687 <head> 11688 LOOKUPUSERBASE <yes/no> 11689 </head> 11690 <p> 11691 (no) 11692 </p> 11693 <p> 11694 If enabled, <name>GoldED+</name> will attempt to find a matching username in the 11695 user database if a to-name with wildcards is entered in echo or 11696 local areas. 11697 </p> 11698 <p> 11699 The userbase lookup feature is not new, but a need arose for an 11700 option to turn off the lookup. I decided to let the default be to 11701 disable the lookup. Previously the lookup was always enabled. 11702 </p> 11703 </div2> 11704 <div2 id=MAILINGLIST> 11705 <head> 11706 MAILINGLIST <echoid> <senderaddress> [contribution address] 11707 </head> 11708 <p> 11709 Defines one or more mailing lists. When importing e-mail from a 11710 SOUP packet, <name>GoldED+</name> will look at the Internet address in the 11711 "Sender" header and if it matches one of the MAILINGLIST's, the 11712 e-mail will be tossed to the defined area. Note that <name>GoldED+</name> 11713 supports only participation in, not hosting of mailing lists. The 11714 contribution address is the destination Internet address for mail 11715 you write to the mailing list - the address is typically given to 11716 you when you subscribe to a list. If the contribution address is 11717 not specified, the senderaddress is assumed. 11718 </p> 11719 </div2> 11720 <div2> 11721 <head> 11722 MAILTOSS <echoid> <contribution-address> <pattern> 11723 </head> 11724 <p> 11725 This is acutally the same as MAILINGLIST in disguise with the 11726 parameters recorded and it also enables the full set of pattern 11727 matching. The <pattern> can be written exactly as if in the prompt 11728 for the advanced search feature. 11729 </p> 11730 <p> 11731 Any number of MAILTOSS lines can be given for a particular list, 11732 if there is for some reason no single way to identify the list. 11733 </p> 11734 <p> 11735 When determining the contribution address, the first MAILTOSS 11736 (or MAILINGLIST) that matches the echoid is chosen. 11737 </p> 11738 <p> 11739 MAILTOSS and MAILINGLIST can both be used at the same time and for 11740 the same lists. MAILINGLIST is always the faster, because it looks 11741 only at specific headerlines. MAILTOSS uses much more complex 11742 pattern matching and can even match based on message body content. 11743 </p> 11744 </div2> 11745 <div2> 11746 <head> 11747 MAPPATH <server filespec> <local filespec> 11748 </head> 11749 <p> 11750 This keyword is used to map paths, for example if you have 11751 different drive letters on a server machine and a workstation. You 11752 might have your FidoNet mailer and mail processor setup to run 11753 with the server drive letter (C:), but run <name>GoldED+</name> from a 11754 workstation where that drive is mapped to a different letter (J:). 11755 If you use AREAFILE's to get the area configuration for <name>GoldED+</name>, 11756 you need to use MAPPATH to map the server drive letter to the 11757 workstation equivalent. 11758 </p> 11759 <p> 11760 Another case might be that you have a setup with DOS-style paths 11761 and want to run the Linux version with the same <name>GoldED+</name> setup. You 11762 can then use MAPPATH to map the DOS drive-based paths to Unix 11763 style paths. 11764 </p> 11765 <p> 11766 Examples: 11767 </p> 11768 <p> 11769 MAPPATH C: J: 11770 MAPPATH C:\ /mnt/dos/c/ 11771 </p> 11772 <p> 11773 NOTE: You don't have to worry about backslash/forwardslash in this 11774 case - they are always mapped automatically to the correct type 11775 for the operating system. 11776 </p> 11777 </div2> 11778 <div2 id=MEMBER> 11779 <head> 11780 MEMBER <echoid> 11781 </head> 11782 <p> 11783 Defines Random System group members. See the Random System chapter 11784 for details. 11785 </p> 11786 </div2> 11787 <div2> 11788 <head> 11789 MENUDROPMSG <yes/no> 11790 </head> 11791 <p> 11792 (no) 11793 </p> 11794 <p> 11795 Defines the default selection in the "Drop This Msg?" menu. 11796 </p> 11797 </div2> 11798 <div2> 11799 <head> 11800 MENUMARKED <marked/current/previous/default> 11801 </head> 11802 <p> 11803 (default) 11804 </p> 11805 <p> 11806 Specifies the position of the selection bar in the Marked/Current 11807 menu. 11808 </p> 11809 <p> 11810 Marked Set selector to Marked. 11811 Current Set selector to Current. 11812 Previous Set selector to previously selection. 11813 Default Set selector to Marked if there are marked msgs. 11814 </p> 11815 <p> 11816 Note that older versions (before 2.50) used the equivalent of the 11817 "previous" setting. 11818 </p> 11819 </div2> 11820 <div2> 11821 <head> 11822 MOUSE <yes/no> 11823 </head> 11824 <p> 11825 (no) 11826 </p> 11827 <p> 11828 The mouse support in <name>GoldED+</name> is currently not functional, so this 11829 keyword is ignored. 11830 </p> 11831 </div2> 11832 <div2 id=MSGLISTDATE> 11833 <head> 11834 MSGLISTDATE <written/arrived/received/no> 11835 </head> 11836 <p> 11837 (written) 11838 </p> 11839 <p> 11840 Can be used globally and in groups. This keyword specifies the 11841 default date shown in the right column in the message list. If 11842 "no" is specified, the date column is removed and the space used 11843 to widen the other columns. Personally I prefer to see the 11844 "arrived" date, which is why I implemented this feature. 11845 </p> 11846 <p> 11847 The key command LISTtoggledate (Ctrl-D) toggles between them. 11848 </p> 11849 <p> 11850 Note that the "arrived" date doubles as the "processed" date for 11851 messages that are written locally and scanned out from your 11852 messagebase. 11853 </p> 11854 <p> 11855 Not all messagebase formats supports all three dates. The table 11856 below shows which messagebase supports which dates: 11857 </p> 11858 <p> 11859 Written Arrived Received 11860 JAM X X X 11861 *.MSG X X 11862 Squish X X 11863 Ezycom X X 11864 Hudson X 11865 Goldbase X 11866 PCBoard X 11867 </p> 11868 <p> 11869 If a date is not supported, "n/a" (for "not available") is shown 11870 instead. 11871 </p> 11872 </div2> 11873 <div2 id=MSGLISTFAST> 11874 <head> 11875 MSGLISTFAST <yes/no> 11876 </head> 11877 <p> 11878 (yes) 11879 </p> 11880 <p> 11881 The message lister can operate in two ways, fast or slow. In the 11882 fast mode, only the message headers are loaded for the list 11883 information. Depending on the msgbase format and message type, 11884 some information may not be quite the same when presented in the 11885 lister because information which is gathered from kludges or other 11886 control information in the message text will be missing. Most of 11887 the time this may not be a problem, so if you want speed, chose 11888 the fast mode (default). 11889 </p> 11890 <p> 11891 The slow mode loads and fully interprets the content of each 11892 message before the message list is presented. The slowness is most 11893 noticable when entering the lister and when paging up and down. 11894 You may want to use the slow mode for areas with Internet 11895 newsgroups and e-mail, where <name>GoldED+</name> uses the "From" kludge to get 11896 the real name of the message writer. 11897 </p> 11898 <p> 11899 This keyword can be used globally and in Random System groups. 11900 </p> 11901 </div2> 11902 <div2 id=MSGLISTFIRST> 11903 <head> 11904 MSGLISTFIRST <yes/no> 11905 </head> 11906 <p> 11907 (no) 11908 </p> 11909 <p> 11910 If enabled, <name>GoldED+</name> automatically starts the message lister when 11911 entering an area. 11912 </p> 11913 <p> 11914 This keyword can be used globally and in Random System groups. 11915 </p> 11916 </div2> 11917 <div2 id=MSGLISTHEADER> 11918 <head> 11919 MSGLISTHEADER <yes/no> 11920 </head> 11921 <p> 11922 (no) 11923 </p> 11924 <p> 11925 If enabled, <name>GoldED+</name> shows the header of the current message when 11926 you scroll the bar up and down. This is how it worked in previous 11927 versions. If disabled, <name>GoldED+</name> does not show the header and instead 11928 uses the screen space to show more messages. By eliminating the 11929 header display, it is also much faster at scrolling the list. 11930 </p> 11931 <p> 11932 This keyword can be used globally and in Random System groups. 11933 </p> 11934 </div2> 11935 <div2 id=MSGLISTPAGEBAR> 11936 <head> 11937 MSGLISTPAGEBAR <yes/no> 11938 </head> 11939 <p> 11940 (yes) 11941 </p> 11942 <p> 11943 Enables or disables a pagebar (scrollbar) in the message list. 11944 </p> 11945 </div2> 11946 <div2> 11947 <head> 11948 MSGLISTVIEWSUBJ <yes/no> 11949 </head> 11950 <p> 11951 (yes) 11952 </p> 11953 <p> 11954 If enabled, <name>GoldED+</name> will display the full subject in the bottom 11955 border of the list window. Note that this feature slows down 11956 scrolling a bit. 11957 </p> 11958 </div2> 11959 <div2 id=MSGLISTWIDESUBJ> 11960 <head> 11961 MSGLISTWIDESUBJ <yes/no> 11962 </head> 11963 <p> 11964 (no) 11965 </p> 11966 <p> 11967 If enabled, the Subject column is made wider by removing the To 11968 column. This is especially useful in gated Internet newsgroups, 11969 where the To name is always "All". 11970 </p> 11971 <p> 11972 You can toggle between wide and short subject with Ctrl-B 11973 (keycommand LISTtogglewidesubj). 11974 </p> 11975 <p> 11976 This keyword can be used globally and in Random System groups. 11977 </p> 11978 </div2> 11979 <div2 id=NAMESFILE> 11980 <head> 11981 NAMESFILE <file> 11982 </head> 11983 <p> 11984 (NAMES.FD) 11985 </p> 11986 <p> 11987 <name>GoldED+</name> supports the "address macro" file supported by FrontDoor 11988 and Maximus. If no path is specified, the file is first searched 11989 for in the path from the "FD" environment variable and then the 11990 GOLDPATH, if the FD variable failed. 11991 </p> 11992 <p> 11993 The address macros are added *after* those defined with the 11994 ADDRESSMACRO keyword (if any) (see this for details on the 11995 format). 11996 </p> 11997 </div2> 11998 <div2 id=NETNAME> 11999 <head> 12000 NETNAME <q/string/ 12001 </head> 12002 <!-- 12003 This is the "netname" that is placed in the originline, after 12004 the address. 12005 12006 Example: 12007 12008 NETNAME fidonet 12009 12010 Produces: 12011 12012 * Origin: Whatever (2:236/77@fidonet) 12013 12014 This keyword can be used globally and in a Random System group. 12015 12016 NOTE: The netname is a non-standard practice with no technical 12017 merit and should not be used. It is provided for cosmetical 12018 purposes and backward compatibility only. 12019 --> 12020 <p>dummy text</p> 12021 </div2> 12022 <div2 id=NICKNAME> 12023 <head> 12024 NICKNAME <your pseudo> 12025 </head> 12026 <p> 12027 Defines the nick name (pseudo) for the current USERNAME. Can be 12028 used globally and in random system groups. 12029 12030 </p> 12031 </div2> 12032 <div2> 12033 <head> 12034 NODELIST <file> [zone/addr] 12035 </head> 12036 <p> 12037 Here you define up to 255 nodelists that are used by <name>GoldED+</name> and the 12038 companion nodelist compiler GoldNODE. The nodelists must generally 12039 be in the standard "St.Louis" nodelist format, but they can also 12040 contain FrontDoor/Version7 style Boss/Point extensions. The 12041 default zone is defined by the first ADDRESS or AKA, but can be 12042 overridden by adding the zone number or a full address after the 12043 filename. <name>GoldED+</name> currently needs it's own special index files to 12044 use the nodelists. These index files are created by GoldNODE. 12045 </p> 12046 <p> 12047 <file> Nodelist file. If the extension is .999 or a 12048 wildcard (".*"), the newest file with a numeric 12049 extension is used. 12050 [zone/addr] Default zone or address for the nodelist (if no 12051 zone info is present in the list itself). 12052 </p> 12053 <p> 12054 See also the USERLIST keyword, and the Nodelist Browsing chapter. 12055 </p> 12056 <p> 12057 NOTE: If you have nodelists with duplicate some of each others 12058 nodes, the nodelist with the newest or most correct entries should 12059 be placed LAST, and you should use the -D (remove duplicates) 12060 option with GoldNODE. 12061 </p> 12062 </div2> 12063 <div2> 12064 <head> 12065 NODELISTWARN <yes/no> 12066 </head> 12067 <p> 12068 (yes) 12069 </p> 12070 <p> 12071 If set to YES, <name>GoldED+</name> will warn you during startup if one or more 12072 nodelists are missing. Use NO to disable the warning if it bothers 12073 you or you delete/pack your nodelists when the nodelists are 12074 compiled. 12075 </p> 12076 <p> 12077 NOTE: <name>GoldED+</name> can work fine with lookups etc. without nodelists as 12078 long as it can access its own indexes (GOLDNODE.GX?). Only the 12079 extra details will be missing. 12080 </p> 12081 </div2> 12082 <div2 id=NODEPATH> 12083 <head> 12084 NODEPATH <path> 12085 </head> 12086 <p> 12087 This is where <name>GoldED+</name> and GoldNODE finds the nodelist files and 12088 indexes. 12089 </p> 12090 </div2> 12091 <div2> 12092 <head> 12093 NODEPATHFD <path> 12094 </head> 12095 <p> 12096 Path where <name>GoldED+</name> can find the FrontDoor nodelist index files. 12097 </p> 12098 </div2> 12099 <div2> 12100 <head> 12101 NODEPATHIM <path> 12102 </head> 12103 <p> 12104 Path to the InterMail nodelist index files. This is actually just 12105 an alias name of the NODEPATHFD keyword, since InterMail and 12106 FrontDoor uses the same nodelist index files. 12107 </p> 12108 </div2> 12109 <div2 id=NODEPATHV7> 12110 <head> 12111 NODEPATHV7 <path> 12112 </head> 12113 <p> 12114 Path where <name>GoldED+</name> can find the Version 7 nodelist index files. 12115 </p> 12116 <p> 12117 NOTE: For the Version 7 nodelist index support, <name>GoldED+</name> *requires* 12118 that the files SYSOP.NDX, NODEX.NDX and NODEX.DAT are present. 12119 None of these files may be missing and no other filenames are 12120 supported. Multiple sets of index files are not supported. 12121 </p> 12122 </div2> 12123 <div2> 12124 <head> 12125 NODEV7FLAGS <flag> <value> 12126 </head> 12127 <p> 12128 The Version 7 nodelist index does not by default define any 12129 nodelist flags except the CM flag. Unfortunately the V7 index does 12130 not point to the actual nodelist, it only has some bits which are 12131 marked "reserved" in the specifications. The NODEV7FLAGS keyword 12132 allows you to define the meaning of each of these bits. 12133 </p> 12134 <p> 12135 The <value> field can be a number or a bit number. Allowed numbers 12136 are: 32, 64, 128, 256, 512, 1024, 2048, 8192 and 16384. Allowed 12137 bit numbers are: b5, b6, b7, b8, b9, b10, b11, b13 and b14. 12138 </p> 12139 <p> 12140 Example: 12141 </p> 12142 <p> 12143 NODEV7FLAGS MO b5 12144 NODEV7FLAGS LO b6 12145 NODEV7FLAGS MN b7 12146 NODEV7FLAGS NC b8 12147 NODEV7FLAGS ZEC b9 12148 NODEV7FLAGS REC b10 12149 NODEV7FLAGS NEC b11 12150 NODEV7FLAGS XA b13 12151 NODEV7FLAGS XX b14 12152 </p> 12153 <p> 12154 See also the NODEV7MODEM keyword for other nodelist flags. 12155 </p> 12156 <p> 12157 The nodelist flag bits in the index files are put in by your 12158 Version 7 nodelist compiler. You must make sure that the nodelist 12159 flag definitions in your nodelist compiler setup match those in 12160 your <name>GoldED+</name> setup. 12161 </p> 12162 </div2> 12163 <div2> 12164 <head> 12165 NODEV7MODEM <type> <value> 12166 </head> 12167 <p> 12168 The Version 7 nodelist index does not by default define any 12169 nodelist modem type flags. Unfortunately the V7 index does not 12170 point to the actual nodelist, it only has some bits which are 12171 marked "reserved" in the specifications. The NODEV7MODEM keyword 12172 allows you to define the meaning of each of these bits. 12173 </p> 12174 <p> 12175 The <value> field can be a number or a bit number. Allowed numbers 12176 are: 1, 2, 4, 8, 16, 32, 64 and 128. Allowed bit numbers are: b0, 12177 b1, b2, b3, b4, b5, b6 and b7. 12178 </p> 12179 <p> 12180 Example: 12181 </p> 12182 <p> 12183 NODEV7MODEM VFC b0 12184 NODEV7MODEM HST b1 12185 NODEV7MODEM V34T b2 12186 NODEV7MODEM V32B b3 12187 NODEV7MODEM V34 b4 12188 NODEV7MODEM V42B b5 12189 NODEV7MODEM ZYX b6 12190 NODEV7MODEM ISDN b7 12191 </p> 12192 <p> 12193 See also the NODEV7FLAGS keyword for other nodelist flags. 12194 </p> 12195 <p> 12196 The modem type bits in the index files are put in by your Version 12197 7 nodelist compiler. You must make sure that the modem type 12198 definitions in your nodelist compiler setup match those in your 12199 <name>GoldED+</name> setup. 12200 </p> 12201 </div2> 12202 <div2 id=ORGANIZATION> 12203 <head> 12204 ORGANIZATION <text> 12205 </head> 12206 <p> 12207 Specifies the content of the RFC Organization header for Internet 12208 messages. 12209 </p> 12210 </div2> 12211 <div2 id=ORIGIN> 12212 <head> 12213 ORIGIN <"string"> 12214 </head> 12215 <p> 12216 You can define many different origins for use in <name>GoldED+</name>. You can 12217 select one of the defined origins from the Origin selection menu 12218 (the READchangeorigin keyword), which is also available from the 12219 EDITMENU and the EDITSAVEMENU. 12220 </p> 12221 <p> 12222 Leading and/or trailing spaces can be added by enclosing the 12223 origin string in quotes. 12224 </p> 12225 <p> 12226 This keyword can be used globally and in a Random System group. 12227 </p> 12228 <p> 12229 NOTE: Origins defined in the Random System will always override 12230 the global origins defined with this keyword, except when they are 12231 selected from the EDITSAVEMENU. 12232 </p> 12233 </div2> 12234 <div2 id=OUTBOUNDPATH> 12235 <head> 12236 OUTBOUNDPATH <path> 12237 </head> 12238 <p> 12239 Defines a Binkley-style outbound path. Currently only used for 12240 WaZOO .REQ file requests (see FRQWAZOO). This should be the name 12241 of your primary outbound without extension. 12242 </p> 12243 </div2> 12244 <div2 id=OUTPUTFILE> 12245 <head> 12246 OUTPUTFILE <file> 12247 </head> 12248 <p> 12249 This is the default name of the file written using the 12250 READwritemsg command. 12251 </p> 12252 <p> 12253 This keyword can be used globally and in a Random System group. 12254 </p> 12255 </div2> 12256 <div2> 12257 <head> 12258 PCBOARDPATH <path> 12259 </head> 12260 <p> 12261 Defines the default path where <name>GoldED+</name> should look for the PCBoard 12262 setup files if it can't find the PCBOARD environment variable. 12263 </p> 12264 </div2> 12265 <div2 id=PCBOARDUSERNO> 12266 <head> 12267 PCBOARDUSERNO <userno> 12268 </head> 12269 <p> 12270 (0) 12271 </p> 12272 <p> 12273 Specifies the lastread set used in the PCBoard message base. 12274 </p> 12275 </div2> 12276 <div2> 12277 <head> 12278 PERSONALMAIL <startup,allnames> 12279 </head> 12280 <p> 12281 Specifies options regarding the personal mail scan feature. None 12282 of them are enabled by default. 12283 </p> 12284 <p> 12285 If the "startup" option is used, <name>GoldED+</name> scans for personal mail 12286 while doing the startup mail scan. 12287 </p> 12288 <p> 12289 If the "allnames" option is used, <name>GoldED+</name> scans for mail to all the 12290 USERNAME's instead of only the first. The default is not to scan 12291 for personal mail at startup and to scan only for the first name. 12292 This is faster. 12293 </p> 12294 <p> 12295 Example: 12296 </p> 12297 <p> 12298 PERSONALMAIL Startup, AllNames 12299 </p> 12300 <p> 12301 The example makes <name>GoldED+</name> scan for personal mail to all your 12302 USERNAME's at startup. 12303 </p> 12304 </div2> 12305 <div2 id=PLAY> 12306 <head> 12307 PLAY <filename.ext/beepnoise> 12308 </head> 12309 <p> 12310 See the EVENT keyword for a definition of the PLAY parameters. 12311 You may specify <q/@/ before parameter for random noise selection. 12312 </p> 12313 <p> 12314 Bugs: At least one <kw/EVENT/ with file should be defined in order to 12315 initialize soundcard driver. Otherwise filenames specifyed for the 12316 <kw/PLAY/ will be ignored. 12317 </p> 12318 <p> 12319 This keyword can be used globally and in a Random System group. 12320 </p> 12321 </div2> 12322 <div2> 12323 <head> 12324 PRINTDEVICE <devicename> 12325 </head> 12326 <p> 12327 (PRN) 12328 </p> 12329 <p> 12330 Defines the name of the device used for printing. PRN is the 12331 default, but LPTx can also be used. Printers on COMx ports may 12332 also work, but this has not been tested. 12333 </p> 12334 <p> 12335 Devices are opened in Write-Only text mode. The function has been 12336 successfully tested to work with two popular peer-to-peer network 12337 packages. 12338 </p> 12339 <p> 12340 You should NOT use a filename as devicename. Use the filename 12341 option in the Write menu instead. 12342 </p> 12343 </div2> 12344 <div2> 12345 <head> 12346 PRINTFORMFEED <yes/no> 12347 </head> 12348 <p> 12349 (yes) 12350 </p> 12351 <p> 12352 Used when printing messages. If enabled, it prints a Form Feed 12353 (12d) character after each message. 12354 </p> 12355 </div2> 12356 <div2> 12357 <head> 12358 PRINTINIT <printstring> 12359 </head> 12360 <p> 12361 This keyword defines the command string sent to your printer to 12362 initialize it before the actual printing. 12363 </p> 12364 <p> 12365 The <printstring> can contain items like these: 12366 </p> 12367 <p> 12368 $Hex A hexadecimal string. 12369 #Decimal A decimal (integer) number. 12370 "String" Text string, enclosed in double quotes. 12371 'String' Text string, enclosed in single quotes. 12372 Other chars Ignored. 12373 </p> 12374 </div2> 12375 <div2> 12376 <head> 12377 PRINTLENGTH <lines> 12378 </head> 12379 <p> 12380 (60) 12381 </p> 12382 <p> 12383 Defines the number of lines per page for printing. A formfeed is 12384 printed when every time PRINTLENGTH lines have been printed. 12385 </p> 12386 </div2> 12387 <div2 id=PRINTMARGIN> 12388 <head> 12389 PRINTMARGIN <characters> 12390 </head> 12391 <p> 12392 (80) 12393 </p> 12394 <p> 12395 The right margin to use in printed messages. 12396 </p> 12397 </div2> 12398 <div2> 12399 <head> 12400 PRINTRESET <printstring> 12401 </head> 12402 <p> 12403 This keyword defines the command string sent to your printer to 12404 reset it after printing. 12405 </p> 12406 <p> 12407 <printstring> See the PRINTINIT keyword. 12408 </p> 12409 </div2> 12410 <div2> 12411 <head> 12412 QUOTEBLANK <yes/no> 12413 </head> 12414 <p> 12415 (no) 12416 </p> 12417 <p> 12418 If enabled, <name>GoldED+</name> will put the QUOTESTRING on blank lines in the 12419 quote. Otherwise blank lines are left blank in quotes. 12420 </p> 12421 </div2> 12422 <div2 id=QUOTEBUFFILE> 12423 <head> 12424 QUOTEBUFFILE <filename> 12425 </head> 12426 <p> 12427 If used, it sets the default filename for the quotebuffer. If no 12428 path is specified, the GOLDPATH is used. 12429 </p> 12430 <p> 12431 This keyword can be used globally and in Random System groups. 12432 </p> 12433 <p> 12434 NOTE: If this keyword is used in globally (in GOLDED.CFG), it 12435 effectively disables the automatically named quotebuffers, as 12436 described in the chapter about the QUOTEBUFMODE keyword. 12437 </p> 12438 </div2> 12439 <div2> 12440 <head> 12441 QUOTEBUFMODE <ask/append/overwrite> 12442 </head> 12443 <p> 12444 (ask) 12445 </p> 12446 <p> 12447 Specifies what <name>GoldED+</name> should do, if the quotebuffer file exists 12448 already. 12449 </p> 12450 <p> 12451 Ask A menu asks you to select append/overwrite/skip. 12452 Append Always append, no asking. 12453 Overwrite Always overwrite, no asking. 12454 </p> 12455 <p> 12456 The "always overwrite" mode is not very useful I guess, but it's 12457 there if you need it. 12458 </p> 12459 <p> 12460 The quotebuffer feature automatically creates special filenames 12461 for the buffer file, using these guidelines: 12462 </p> 12463 <p> 12464 FORMAT FILENAME LOCATION 12465 Fido GOLDED.QBF In the directory with the *.MSG's. 12466 Hudson GOLDHxxx.QBF In the HUDSONPATH. 12467 Squish filename.QBF Where the Squish area is. 12468 Ezycom GLDxxxxx.QBF In the EZYCOMMSGPATH. 12469 JAM filename.QBF Where the JAM area is. 12470 Goldbase GOLDGxxx.QBF In the GOLDBASEPATH. 12471 PCBoard filename.QBF Where the PCBoard area is. 12472 </p> 12473 <p> 12474 Note that they all have extension .QBF so that you can easily find 12475 them. 12476 </p> 12477 </div2> 12478 <div2 id=QUOTECHARS> 12479 <head> 12480 QUOTECHARS ["]<chars>["] 12481 </head> 12482 <p> 12483 Defines up to 10 chars to recognize in addition to '>' as quote 12484 string chars. This is most useful in gated Internet newsgroups, 12485 where chars such as '|', ':' and ';' are sometimes used instead of 12486 the '>'. 12487 </p> 12488 <p> 12489 This keyword can be used globally and in Random System groups. 12490 </p> 12491 <p> 12492 Example: 12493 </p> 12494 <p> 12495 Group Internet: 12496 Member alt.*, comp.*, net.email 12497 Quotechars "|:;" 12498 Username odinn@winboss.dk 12499 EndGroup 12500 </p> 12501 <p> 12502 The example is similar to the one I use myself (net.email is a 12503 local netmail area where I import my gated e-mail from 12504 winboss.dk). The username is my actual Internet address. 12505 </p> 12506 <p> 12507 Note that using additional quotechars such as '|' and ':' may 12508 cause odd results when quoting in the cases when they are actually 12509 NOT used in a message as quotechars. Consider for example quoting 12510 a smiley :-) 12511 </p> 12512 </div2> 12513 <div2 id=QUOTECTRL> 12514 <head> 12515 QUOTECTRL <Tearline,Origin,yes/no> 12516 </head> 12517 <p> 12518 Specifies if you want quote tearline and/or origin in your 12519 messages. 12520 </p> 12521 <p> 12522 This keyword can be used in random system groups. 12523 </p> 12524 </div2> 12525 <div2 id=QUOTEMARGIN> 12526 <head> 12527 QUOTEMARGIN <chars> 12528 </head> 12529 <p> 12530 (70) 12531 </p> 12532 <p> 12533 The margin to which quotes are wrapped. A negative value means 12534 that the negative value is added to the DISPMARGIN (not 12535 recommended). 12536 </p> 12537 </div2> 12538 <div2> 12539 <head> 12540 QUOTESPACING <yes/no> 12541 </head> 12542 <p> 12543 (no) 12544 </p> 12545 <p> 12546 If enabled, <name>GoldED+</name> will automatically add blank lines before and 12547 after a block of quoted text, if none are present already. This 12548 improves the readability of some messages. 12549 </p> 12550 </div2> 12551 <div2 id=QUOTESTOPS> 12552 <head> 12553 QUOTESTOPS 12554 </head> 12555 <list type=gloss> 12556 <label> 12557 Synopsis: 12558 </label> 12559 <item> 12560 <kw/QUOTESTOPS/ <ident/<string>/ 12561 </item> 12562 <label> 12563 Description: 12564 </label> 12565 <item> 12566 If one of characters defined by this keyword found before quotechar 12567 then line will be not treated as quote. 12568 </item> 12569 <label> 12570 Default: 12571 </label> 12572 <item> 12573 <![ CDATA ["<\"'-"]]> 12574 </item> 12575 </list> 12576 </div2> 12577 <div2 id=QUOTESTRING> 12578 <head> 12579 QUOTESTRING <quotespec> 12580 </head> 12581 <p> 12582 (" FL> ") 12583 </p> 12584 <p> 12585 With this keyword you define how you want the quotestring to look 12586 in your quoted replies. 12587 </p> 12588 <p> 12589 The <quotespec> can contain these characters: 12590 </p> 12591 <p> 12592 F Replaced with the first letter of the first name. 12593 M Replaced with the letters of the middle names. 12594 L Replaced with the first letter of the last name. 12595 > Required quote-char. 12596 Spaces Cosmetics. 12597 </p> 12598 <p> 12599 Other characters are allowed but *not* recommended. 12600 </p> 12601 <p> 12602 This keyword can be used globally and in Random System Groups. 12603 </p> 12604 </div2> 12605 <div2 id=QUOTEWRAPHARD> 12606 <head> 12607 QUOTEWRAPHARD <yes/no> 12608 </head> 12609 <p> 12610 (yes) 12611 </p> 12612 <p> 12613 This keyword controls behaviour of quoted text (wrap or reflow). 12614 </p> 12615 </div2> 12616 <div2> 12617 <head> 12618 QWKBADMSGS <echoid> 12619 </head> 12620 <p> 12621 Specifies the area where messages in unknown conferences are put. 12622 If you get messages tossed here by accident, you must move them 12623 manually to the correct area. If the badmsgs area is not defined, 12624 the messages will silently disappear. Messages tossed to the 12625 badmsgs area will have the control line "AREA:<bbsid>_<confno>" at 12626 the top of the message. 12627 </p> 12628 </div2> 12629 <div2> 12630 <head> 12631 QWKCONFMAP <bbsid> ["]<confname>["] <echoid> 12632 </head> 12633 <p> 12634 Defines the mapping between the BBSID and conference names in the 12635 QWK packets and the echoid name of the conference as required by 12636 <name>GoldED+</name>. You MUST define a mapping for every conference that you 12637 subscribe to. If you don't, the messages will be tossed to the 12638 area defined by QWKBADMSGS or disappear. The <bbsid> is the name 12639 listed on line 5 in CONTROL.DAT after the comma. The <confname> is 12640 the conference names listed on line 13 and on alternate lines 12641 onwards in CONTROL.DAT. If a conference name contains embedded 12642 spaces, the <confname> must be enclosed in double quotes, like 12643 this: "Main Board". The area <echoid> must be already defined 12644 either in an AREAFILE or using the AREADEF or AREA keywords. 12645 </p> 12646 </div2> 12647 <div2> 12648 <head> 12649 QWKEXPORTPATH <path> 12650 </head> 12651 <p> 12652 Path where outgoing QWK reply files (BBSID.MSG) can be placed. 12653 </p> 12654 </div2> 12655 <div2> 12656 <head> 12657 QWKIMPORTPATH <path> 12658 </head> 12659 <p> 12660 Path where incoming QWK packet files (CONTROL.DAT and 12661 MESSAGES.DAT) can be found. 12662 </p> 12663 </div2> 12664 <div2> 12665 <head> 12666 QWKOPTIONS <bbsid> <options> 12667 </head> 12668 <p> 12669 The <bbsid> is the BBSID (same as the name of the QWK packet) for 12670 which the options will be active. The <options> can be any or a 12671 combination of the following, separated by commas or spaces: 12672 </p> 12673 <p> 12674 KLUDGES/NOKLUDGES: Defaults to NOKLUDGES. Specifies whether or not 12675 to include the FidoNet-style kludges at the top of messages when 12676 exporting to QWK. NOTE: Unless you enable this option, <name>GoldED+</name> will 12677 *not* include kludges in your QWK packets. You should check if the 12678 BBS supports kludges in QWK packets. If it does, please enable 12679 this option. 12680 </p> 12681 <p> 12682 MIXCASE/NOMIXCASE: Defaults to NOMIXCASE. Specifies whether or not 12683 the BBS allows mixed upper/lower case in the QWK message headers. 12684 The default is to uppercase the TO and FROM header fields when 12685 exporting to QWK packets. 12686 </p> 12687 <p> 12688 RECEIPT/NORECEIPT: Defaults to NORECEIPT. Specifies whether or not 12689 the BBS supports return receipt requests (RRQ). If the RECEIPT 12690 option is enabled, <name>GoldED+</name> will insert "RRR" at the front of the 12691 subject field if the RRQ attribute is set on your messages, when 12692 exporting to QWK packets. 12693 </p> 12694 </div2> 12695 <div2> 12696 <head> 12697 QWKREPLYLINKER <cmd> 12698 </head> 12699 <p> 12700 Commandline for a replylinker program to call after QWK import. 12701 </p> 12702 </div2> 12703 <div2> 12704 <head> 12705 QWKTOSSLOG <file> 12706 </head> 12707 <p> 12708 Name of a file where <name>GoldED+</name> puts the echoids of each area where 12709 articles have been imported. The tosslog file is intended to be 12710 used with a replylinker. If no path is given, it defaults to the 12711 GOLDPATH. 12712 </p> 12713 </div2> 12714 <div2> 12715 <head> 12716 RA2USERSBBS <yes/no> 12717 </head> 12718 <p> 12719 (detect) 12720 </p> 12721 <p> 12722 <name>GoldED+</name> supports the two different formats of the Hudson USERS.BBS 12723 file. With this keyword you can tell <name>GoldED+</name> which format to use. 12724 </p> 12725 <p> 12726 If set to YES, the RA2 format is used. Otherwise if the it is set 12727 to NO, the Hudson format is used. 12728 </p> 12729 <p> 12730 If this keyword is NOT used, <name>GoldED+</name> tries to detect the format by 12731 looking at the size of the USERS.BBS file and comparing this to 12732 the record sizes of the RA2 and Hudson formats. 12733 </p> 12734 <p> 12735 If the size matches one and not the other, the format is detected 12736 to be of the matching type. 12737 </p> 12738 <p> 12739 If the size matches both (which is quite normal), <name>GoldED+</name> looks for 12740 the RA environment variable and if found, in the RA config files 12741 for the RA version. 12742 </p> 12743 <p> 12744 If the size does not match either of them (indicating a possibly 12745 damaged userfile), <name>GoldED+</name> exits with an error message and writes 12746 in the log with details of the problem and an advise to run a 12747 userbase packing utility. 12748 </p> 12749 <p> 12750 If used, this keyword should be placed in the configuration file 12751 _after_ any AREAFILE keyword. 12752 </p> 12753 </div2> 12754 <div2 id=RCVDISABLESCFM> 12755 <head> 12756 RCVDISABLESCFM <yes/no> 12757 </head> 12758 <p> 12759 (yes) 12760 12761 If this keyword defined to "no" then GoldEd will recognize RRq 12762 (receipt request) and/or CFM (confirmation) flag on messages with 12763 RCV (received) flag set. After that RRq and CFM flags will be 12764 resetted. It is useful if your netmail tracker sets RCV flag 12765 before you actually read messages. 12766 <ptr target=MESSAGEATTRS> chapter, 12767 <ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>, 12768 <ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>, 12769 <ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>, 12770 <ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref> 12771 </p> 12772 </div2> 12773 <div2> 12774 <head> 12775 REGISTERKEY 12776 </head> 12777 <p> 12778 </div2> 12779 <div2> 12780 <head> 12781 REGISTERNAME 12782 </head> 12783 <p> 12784 These keywords do nothing and won't do anything in the future. 12785 They were used when <name>GoldED+</name> was a Shareware product. 12786 </p> 12787 </div2> 12788 <div2> 12789 <head> 12790 REM 12791 </head> 12792 <p> 12793 This keyword ignores everything behind it. This is useful to 12794 comment a single line out. 12795 </p> 12796 </div2> 12797 <div2> 12798 <head> 12799 REPLYLINK <chain/direct> 12800 </head> 12801 <p> 12802 Defaults to "direct" for JAM and "chain" for everything else. 12803 </p> 12804 <p> 12805 If set to "direct", <name>GoldED+</name> will link your reply directly to the 12806 original message. If set to "chain", it will link to the last 12807 message in the reply chain. The default ("chain") is how <name>GoldED+</name> 12808 has done it in all previous versions. 12809 </p> 12810 <p> 12811 The advantage of the "direct" linking method is that you can 12812 easily find the the original message the reply was for. Unless of 12813 course you have later re-linked using a chain-linking replylinker 12814 utility. I can recommend the utility SQLINK by Serge Terekhov. 12815 SQLINK links Squish areas using the MSGID/REPLY kludges and makes 12816 direct links instead of chain-linking on the subject line like 12817 most other replylinkers do. There are probably also similar 12818 replylinkers for other msgbase formats, I just don't know them. 12819 </p> 12820 </div2> 12821 <div2> 12822 <head> 12823 REPLYLINKLIST <fast/full> 12824 </head> 12825 <p> 12826 (fast) 12827 </p> 12828 <p> 12829 When there is more than one reply to a msg in a JAM or Squish 12830 area, <name>GoldED+</name> pops up a list of the replies. This keyword affects 12831 the contents of the list. 12832 </p> 12833 <p> 12834 In the "fast" mode, the list data is based solely on what can be 12835 found by reading the message header, which is quite fast. 12836 Unfortunately some software does not (or cannot) fill the header 12837 with the correct origination address. In that case, set this 12838 keyword to "full", which makes <name>GoldED+</name> read and scan each message 12839 for control data to get the origination address. That can be very 12840 slow. 12841 </p> 12842 </div2> 12843 <div2 id=ROBOTNAME> 12844 <head> 12845 ROBOTNAME <name> 12846 </head> 12847 <p> 12848 A "robot" is a program on the Boss or Uplink system which responds 12849 automatically to netmail messages. Usually the robot links or 12850 unlinks echomail areas or distributed files. 12851 </p> 12852 <p> 12853 The following ROBOTNAME's are defined by default: 12854 </p> 12855 <p> 12856 AreaFix, AreaMgr, FileFix, AreaLink, AllFix, Raid, GEcho. 12857 </p> 12858 <p> 12859 If you write a netmail message where the TO: name is one of the 12860 robot names, <name>GoldED+</name> will ignore any template definition, and give 12861 you a blank msg (possibly with a tearline) to edit. 12862 </p> 12863 </div2> 12864 <div2> 12865 <head> 12866 SCREENBLANKER <seconds> [BLACK] 12867 </head> 12868 <p> 12869 (180) 12870 </p> 12871 <p> 12872 If non-zero, <name>GoldED+</name> will blank the screen after the defined number 12873 of seconds, and put a small moving window up instead. Hitting any 12874 key (including shiftkeys) will return the screen to normal. If 12875 zero, no blanking is done. 12876 </p> 12877 <p> 12878 If the additional parameter "BLACK" is given, <name>GoldED+</name> will switch 12879 the screen completely black instead of showing its own animated 12880 screenblanker. This is useful if you have a monitor with 12881 powersaving-features. 12882 </p> 12883 <p> 12884 Example: 12885 </p> 12886 <p> 12887 SCREENBLANKER 300 BLACK 12888 </p> 12889 <p> 12890 NOTE: This feature only works if KEYBMODE is set to "poll". 12891 </p> 12892 </div2> 12893 <div2> 12894 <head> 12895 SCREENMAXCOL <columns> 12896 </head> 12897 <p> 12898 (0) 12899 </p> 12900 <p> 12901 On some systems, <name>GoldED+</name> may no detect the correct display size. 12902 With this keyword you can force a specific size. If zero, 12903 autodetect is used. 12904 </p> 12905 </div2> 12906 <div2> 12907 <head> 12908 SCREENMAXROW <rows> 12909 </head> 12910 <p> 12911 (0) 12912 </p> 12913 <p> 12914 On some systems, <name>GoldED+</name> may not detect the correct display size. 12915 With this keyword you can force a specific size. If zero, 12916 autodetect is used. 12917 </p> 12918 </div2> 12919 <div2> 12920 <head> 12921 SCREENPALETTE <reg> <value> OR <reg> (red green blue) 12922 </head> 12923 <p> 12924 You can change the color palette used in <name>GoldED+</name>. The palette has 12925 16 color registers, corresponding to the 16 colors from black (0) 12926 to intense white (15). By changing the values in the palette 12927 registers, it is possible to make any of the 16 colors a 12928 completely different color. You can even make the background 12929 colors intense, without using the intense color feature. There are 12930 64 different colors to chose from. 12931 </p> 12932 <p> 12933 To configure the palette colors in <name>GoldED+</name>, the SCREENPALETTE 12934 keyword is used. There are two different syntaxes: 12935 </p> 12936 <p> 12937 SCREENPALETTE <reg> <value> 12938 SCREENPALETTE <reg> (red green blue) 12939 </p> 12940 <p> 12941 So you can either compose the color value using separate red, 12942 green, blue components, or directly use a precalculated value. The 12943 red/green/blue values can only be in the range 0-3. 12944 </p> 12945 <p> 12946 These are the original palette values: 12947 </p> 12948 <p> 12949 SCREENPALETTE 0 (0 0 0) 12950 SCREENPALETTE 1 (0 0 2) 12951 SCREENPALETTE 2 (0 2 0) 12952 SCREENPALETTE 3 (0 2 2) 12953 SCREENPALETTE 4 (2 0 0) 12954 SCREENPALETTE 5 (2 0 2) 12955 SCREENPALETTE 6 (2 2 0) 12956 SCREENPALETTE 7 (2 2 2) 12957 SCREENPALETTE 8 (1 1 1) 12958 SCREENPALETTE 9 (1 1 3) 12959 SCREENPALETTE 10 (1 3 1) 12960 SCREENPALETTE 11 (1 3 3) 12961 SCREENPALETTE 12 (3 1 1) 12962 SCREENPALETTE 13 (3 1 3) 12963 SCREENPALETTE 14 (3 3 0) 12964 SCREENPALETTE 15 (3 3 3) 12965 </p> 12966 <p> 12967 Copy these lines into your GOLDED.CFG and start experimenting! :-) 12968 </p> 12969 <p> 12970 If you have written a program to edit the palette and write a 12971 <name>GoldED+</name> palette setup file, please don't keep it a secret! :-) 12972 </p> 12973 </div2> 12974 <div2> 12975 <head> 12976 SCREENSHADOWS <yes/no> 12977 </head> 12978 <p> 12979 (yes) 12980 </p> 12981 <p> 12982 If enabled, all relevant windows and menus in <name>GoldED+</name> will have 12983 shadows. 12984 </p> 12985 </div2> 12986 <div2> 12987 <head> 12988 SCREENSIZE <mode> 12989 </head> 12990 <p> 12991 (Auto) 12992 </p> 12993 <p> 12994 Use this to force <name>GoldED+</name> to use either 25 lines, 43/50 lines on 12995 EGA/VGA, or even special videomodes supported by your SuperVGA 12996 adapter (modes like 132x44, 100x40 or 80x60). 12997 </p> 12998 <p> 12999 The <mode> can be one of the following: 13000 </p> 13001 <p> 13002 Auto Use detected size. 13003 25 Switch to 25 lines. 13004 28 Switch to 28 lines. 13005 4350 Switch to 43/50 lines. 13006 Mode <NN> Switch to videomode NN (a hexadecimal value). 13007 </p> 13008 <p> 13009 Please check your video adapter manual carefully before trying out 13010 the Mode option. SELECTING A WRONG MODE CAN DAMAGE YOUR MONITOR!!! 13011 </p> 13012 <p> 13013 The Mode option is ignored in the W32 and OS/2 version. 13014 </p> 13015 </div2> 13016 <div2> 13017 <head> 13018 SCREENUSEBIOS <yes/no> 13019 </head> 13020 <p> 13021 (no) 13022 </p> 13023 <p> 13024 If enabled, <name>GoldED+</name> will use standard BIOS calls for screen 13025 updates. This is VERY slow, and should only be used if really 13026 needed. Normally <name>GoldED+</name> uses direct screen writes. 13027 </p> 13028 <p> 13029 This feature is only interpreted in the DOS version. 13030 </p> 13031 </div2> 13032 <div2 id=SEARCHFOR> 13033 <head> 13034 SEARCHFOR ["]<string|string|..>["] 13035 </head> 13036 <p> 13037 Defines a set of search strings, separated by the '|' character. 13038 The search set defined here is the default when using the Alt-F/Z 13039 search functions or the marking system. 13040 </p> 13041 <p> 13042 The '|' character works like an OR operator. That is, the search 13043 is successful if one OR more of the strings are matched. The '&' 13044 character is used as the logical AND operator. 13045 </p> 13046 <p> 13047 Please refer to appropriate section in user's guide for more 13048 information. 13049 </p> 13050 <p> 13051 Older versions used the ';' semicolon character as a separator, 13052 but that conflicts with the config reader which treats the 13053 semicolon in a special way. The semicolon is still accepted as 13054 separator char like '|', but if semicolons are used, you MUST 13055 enclose the search strings with quotes or the config reader will 13056 treat the first semicolon as the start of a comment. 13057 </p> 13058 <p> 13059 Examples: 13060 </p> 13061 <p> 13062 SEARCHFOR string1 13063 SEARCHFOR string1|string2|stringx 13064 SEARCHFOR "string1;string2;stringx" 13065 SEARCHFOR "string 1"|string2&stringx 13066 </p> 13067 <p> 13068 This keyword can be used globally and in Random System groups. 13069 </p> 13070 </div2> 13071 <div2 id=SEMAPHORE> 13072 <head> 13073 SEMAPHORE <type> <file> 13074 </head> 13075 <p> 13076 This keyword defines "semaphore" files, for use with other mailer 13077 and/or mail processing software. 13078 </p> 13079 <p> 13080 The <type> can be one of the following: 13081 </p> 13082 <p> 13083 NETSCAN Empty netmail scan file (for D'Bridge/FD). 13084 ECHOSCAN Empty echomail scan file (for D'Bridge). 13085 EXPORTLIST Echoid-list of your new messages. 13086 IMPORTLIST Echoid-list of new imported messages. 13087 </p> 13088 <p> 13089 The semaphore files are placed in the AREAPATH, if no path is 13090 specified. 13091 </p> 13092 <p> 13093 See the example .CFG files for typical semaphore filenames. 13094 </p> 13095 <p> 13096 NOTE: You should not set SEMAPHORE EXPORTLIST to 13097 %JAMPATH%\ECHOMAIL.JAM. This is incorrect and probably may cause 13098 your mail processor to malfunction. Use the JAMPATH keyword 13099 instead. 13100 </p> 13101 <p> 13102 <name>GoldED+</name> can handle enviroment variables correctly in paths 13103 specified in connection with this keyword. For example, if a path 13104 is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in 13105 AUTOEXEC.BAT (or whatever), then <name>GoldED+</name> translates the path to 13106 C:\POINT\path\name. 13107 </p> 13108 <p> 13109 NOTE: The translation is done at config compile time, so if you 13110 change the environment variable and haven't changed anything else 13111 that would cause <name>GoldED+</name> to recompile it's config, you must force 13112 it with the -F or -FF command parameter. 13113 </p> 13114 <p> 13115 In addition, <name>GoldED+</name> itself can watch for some semaphore files and 13116 execute the appropiate function if it is in the arealist screen. 13117 This can be useful if you have a multitasking system and you want 13118 to "tell" <name>GoldED+</name> that there is new mail in some areas and <name>GoldED+</name> 13119 should update its display correctly. 13120 </p> 13121 <p> 13122 In detail, there are 13123 </p> 13124 <p> 13125 EXITNOW <file> Quit immediately. 13126 SCANALL <file> Scan all areas 13127 SCANNETMAIL <file> Scan all netmail areas 13128 SCANTHIS <file> Scan the areas listed in the file 13129 PMSCANALL <file> PM-scan all areas 13130 PMSCANNETMAIL <file> PM-scan all netmail areas 13131 PMSCANTHIS <file> PM-scan the areas listed in the file 13132 QWKIMPORT <file> Import QWK packets 13133 QWKEXPORT <file> Export to QWK 13134 SOUPIMPORT <file> Import SOUP packets 13135 SOUPEXPORT <file> Export to SOUP 13136 IDLETIME <seconds> Number of seconds between checks 13137 </p> 13138 <p> 13139 If SEMAPHORE IDLETIME is defined and non-zero, then <name>GoldED+</name> will 13140 check this list of semaphore files when the user has not pressed a 13141 key in the specified number of seconds. The semaphores are only 13142 checked when the arealist screen is active. If a semaphore file is 13143 found, the file is deleted and then the action is performed. If no 13144 path is given for the files, the GOLDPATH is assumed. 13145 </p> 13146 <p> 13147 Example: 13148 </p> 13149 <p> 13150 SEMAPHORE SCANALL SCANALL.NOW 13151 SEMAPHORE IDLETIME 30 13152 </p> 13153 <p> 13154 This causes <name>GoldED+</name> to check every 30 seconds for the SCANALL.NOW 13155 file in the GOLDPATH, and scan all areas if it's found. 13156 </p> 13157 </div2> 13158 <div2> 13159 <head> 13160 SERIALNO 13161 </head> 13162 <p> 13163 Everything mentioned above about REGISTERKEY and REGISTERNAME 13164 applied to this keyword. 13165 </p> 13166 </div2> 13167<div2 id=SHAREMODE><head>SHAREMODE <yes/no/mode#></head> 13168 <p> 13169 (yes) 13170 </p> 13171 <p> 13172 If enabled, <name>GoldED+</name> opens all files in a SHARE.EXE compatible mode. 13173 </p> 13174 <p> 13175 The default share-mode is "Share Deny None", but another may be 13176 specified directly if you give the mode number as the keyword 13177 parameter (decimal). 13178 </p> 13179 <p> 13180 It is normally not necessary to change the default. 13181 </p> 13182 </div2> 13183 <div2 id=SOUNDPATH> 13184 <head> 13185 SOUNDPATH <path> 13186 </head> 13187 <p> 13188 (defaults to the GOLDPATH) 13189 </p> 13190 <p> 13191 Tells <name>GoldED+</name> where to find the sound files for the PLAY and EVENT 13192 keywords. 13193 </p> 13194 </div2> 13195 <div2> 13196 <head> 13197 SOUPBADMSGS <echoid> 13198 </head> 13199 <p> 13200 Specifies the area where "bad messages" from SOUP packets can be 13201 tossed. It should be an echomail or newsgroup area. 13202 </p> 13203 </div2> 13204 <div2> 13205 <head> 13206 SOUPEMAIL <echoid> 13207 </head> 13208 <p> 13209 Specifies the area where Internet e-mails can be tossed. It must 13210 be a netmail or e-mail area. 13211 </p> 13212 </div2> 13213 <div2 id=SOUPEXPORTMARGIN> 13214 <head> 13215 SOUPEXPORTMARGIN <margin> 13216 </head> 13217 <p> 13218 (76) 13219 </p> 13220 <p> 13221 This is the margin that <name>GoldED+</name> will hard-wrap to when exporting to 13222 SOUP packets. If you're getting complaints that your lines are too 13223 long, you may want to set this to 70 or 60. 13224 </p> 13225 <p> 13226 NOTE: You should NOT enable EDITHARDTERM in email and newsgroups 13227 that are exported to SOUP. If you do, your messages will probably 13228 be exported with short line "droppings" after the wrapping margin. 13229 </p> 13230 </div2> 13231 <div2> 13232 <head> 13233 SOUPEXPORTPATH <path> 13234 </head> 13235 <p> 13236 Path where outgoing SOUP reply packet files (REPLIES and 13237 GOLD*.MSG) can be placed. 13238 </p> 13239 </div2> 13240 <div2> 13241 <head> 13242 SOUPIMPORTPATH <path> 13243 </head> 13244 <p> 13245 Path where the incoming SOUP packet files (AREAS and *.MSG) can be 13246 found. 13247 </p> 13248 </div2> 13249 <div2> 13250 <head> 13251 SOUPNEWSRCFILE <file> 13252 </head> 13253 <p> 13254 Name with full path of the NEWSRC file which lists the newsgroups 13255 you are connected to. <name>GoldED+</name> uses the list to mark the matching 13256 areas as newsgroups. These will then be scanned for outgoing mail 13257 when starting a SOUP export. 13258 </p> 13259 </div2> 13260 <div2> 13261 <head> 13262 SOUPREPLYLINKER <cmd> 13263 </head> 13264 <p> 13265 Commandline for a replylinker program to call after SOUP import. 13266 </p> 13267 </div2> 13268 <div2> 13269 <head> 13270 SOUPREPLYTO <internet-address> 13271 </head> 13272 <p> 13273 Internet-Address other users should use when they respond to your 13274 mails (Reply-To Headerline). 13275 </p> 13276 </div2> 13277 <div2> 13278 <head> 13279 SOUPTOSSLOG <file> 13280 </head> 13281 <p> 13282 Name of a file where <name>GoldED+</name> puts the echoids (newsgroup names) of 13283 each area where articles have been imported. The tosslog file is 13284 intended to be used with a replylinker. If no path is given, it 13285 defaults to the GOLDPATH. 13286 </p> 13287 </div2> 13288 <div2> 13289 <head> 13290 SQUISHDIRECT <yes/no> 13291 </head> 13292 <p> 13293 (no) 13294 </p> 13295 <p> 13296 If enabled, then in Squish areas, if the DIR (direct) attribute is 13297 set on a message, <name>GoldED+</name> will automatically set both the CRA 13298 (crash) and HLD (hold) attributes when saving the message. 13299 </p> 13300 <p> 13301 According to the Squish Developers Kit, this is the way to tell 13302 SquishMail that a message should be routed direct, because 13303 SquishMail does not recognize the FLAGS kludge where the DIR 13304 attribute is normally found. This keyword should probably only be 13305 used with SquishMail (the mail processor) and then only when used 13306 with Binkley or other so-called "static" mailers. DON'T use it 13307 with FrontDoor! 13308 </p> 13309 </div2> 13310 <div2> 13311 <head> 13312 SQUISHSCAN <api/quick> 13313 </head> 13314 <p> 13315 (quick) 13316 </p> 13317 <p> 13318 Specfies whether to use a quick scanning method which only looks 13319 in the .SQI files. This will normally work fine, but may fail 13320 slightly in obscure cases, especially when used with Squish 1.0x 13321 or programs using the old version of the MSGAPI. If you suspect 13322 problems, try to set this keyword to "api", which tells <name>GoldED+</name> to 13323 look in the .SQD file for an exact count of active msgs in the 13324 .SQI file. 13325 </p> 13326 <p> 13327 NOTE: <name>GoldED+</name> does NOT use the original MSGAPI by Scott Dudley. 13328 Since version 2.50, a completely rewritten implementation is used. 13329 </p> 13330 </div2> 13331 <div2 id=SQUISHUSERNO> 13332 <head> 13333 SQUISHUSERNO <index> 13334 </head> 13335 <p> 13336 (0) 13337 </p> 13338 <p> 13339 This sets the lastread index number for the Squish *.SQL lastread 13340 files. Lowest number is 0 (zero), highest is (in theory) 65534. 13341 </p> 13342 <p> 13343 If used, this disables the use of USER.BBS to find the index 13344 number, and will in effect also stop <name>GoldED+</name> from creating USER.BBS 13345 or any new entries in it (useful in a single-user point system). 13346 If a Squish msgbase is shared between several users, and you don't 13347 want to have a USER.BBS (recommended in such a case), each user 13348 must have a unique SQUISHUSERNO in their GOLDED/GOLDAREA.CFG. 13349 </p> 13350 </div2> 13351 <div2 id=SQUISHUSERPATH> 13352 <head> 13353 SQUISHUSERPATH <path>[file] 13354 </head> 13355 <p> 13356 This keyword defines the path where <name>GoldED+</name> can find and use/create 13357 your USER.BBS file, which is used in connection with the Squish 13358 area lastreads. You can also specify the exact filename if not 13359 USER.BBS. 13360 </p> 13361 <p> 13362 If this path or filename is not defined, <name>GoldED+</name> will instead take 13363 the one specified with AREAFILE Squish or AREAFILE Maximus 13364 (whichever comes first), or failing that, use the MAXIMUS or 13365 SQUISH environment variables. If even that fails, the AREAPATH or 13366 GOLDPATH is used. If AREAFILE Maximus is used, <name>GoldED+</name> gets the 13367 filename from MAX.PRM. 13368 </p> 13369 </div2> 13370 <div2 id=STATUSLINECLOCK> 13371 <head> 13372 STATUSLINECLOCK <yes/no> 13373 </head> 13374 <p> 13375 (yes) 13376 </p> 13377 <p> 13378 If enabled, <name>GoldED+</name> will display a clock in HH:MM:SS format in the 13379 right side of the statusline. 13380 </p> 13381 <p> 13382 You can redefine the clock format with the language keyword 13383 ST_STATUSLINETIMEFMT in GOLDLANG.CFG. See the Language Definition 13384 chapter to details about the date/time codes you can use. 13385 </p> 13386 <p> 13387 NOTE: The clock will only run continuously if KEYBMODE is set to 13388 "poll". 13389 </p> 13390 </div2> 13391 <div2 id=STATUSLINEHELP> 13392 <head> 13393 STATUSLINEHELP <yes/no/nologo> 13394 </head> 13395 <p> 13396 (no) 13397 </p> 13398 <p> 13399 If set to YES, <name>GoldED+</name> will replace the "logo" in the left side of 13400 the statusline with a text saying "F1 Help". This is for use in 13401 "point package" setups where the user may be a complete novice, 13402 maybe even to computers, and who needs to be guided to the help 13403 screens. The "F1 Help" text is configurable with the 13404 ST_STATUSLINEHELP language keyword (put it in GOLDLANG.CFG). 13405 </p> 13406 <p> 13407 If set to NO, <name>GoldED+</name> will display it's logo (name and version) in 13408 the left side of the statusline. 13409 </p> 13410 <p> 13411 If set to NOLOGO, <name>GoldED+</name> will not display anything in the left 13412 side. The middle part is extended to fill the space on the left 13413 side. 13414 </p> 13415 </div2> 13416 <div2> 13417 <head> 13418 STYLECODES <yes/hide/no> 13419 </head> 13420 <p> 13421 (hide) 13422 </p> 13423 <p> 13424 If enabled (yes or hide), <name>GoldED+</name> will highlight text surrounded by 13425 one of the following characters in a different color: '*' for bold 13426 text, '/' for italic text, '_' for underlined text and '#' for 13427 reversed text. These are commonly used "stylecodes" which add 13428 emphasis to the text, without making it harder to read. Examples: 13429 *This* will be shown in bold color, /this/ in italic color and 13430 _this_ in underlined color. It is also possible to combine styles, 13431 such as */this/*, in bolditalic color. 13432 </p> 13433 <p> 13434 The differ in yes and hide is that hide strips surrounding 13435 stylecodes. 13436 </p> 13437 <p> 13438 Described values are specific to -asa. Official vesions starting 13439 at 3.00beta3 has bug in implementation which causes GoldEd to 13440 ignore this keyword. Realization of this keyword in -asa versions 13441 compatible with official versions prior to 3.00beta3. 13442 </p> 13443 <p> 13444 To define the highlight colors, use COLOR STYLECODE. See the color 13445 chapter for details. 13446 </p> 13447 </div2> 13448 <div2> 13449 <head> 13450 STYLECODEPUNCT <"charlist"> 13451 </head> 13452 <p> 13453 (<q>!\"$%&()+,.:;<=>@[\]^`{|}~</q>) 13454 </div2> 13455 <div2> 13456 <head> 13457 STYLECODESTOPS <"charlist"> 13458 </head> 13459 <p> 13460 ("") 13461 </p> 13462 <p> 13463 The STYLECODEPUNCT keyword specifies all the characters that 13464 punctuates words. The stylecode line parser scans forward until it 13465 meets one of these characters and then looks back to see if it 13466 found a word with stylecodes around it. 13467 </p> 13468 <p> 13469 The STYLECODESTOPS keyword specifies characters which, if found 13470 within the word to be highlighted, causes the highlight to be 13471 cancelled. 13472 </p> 13473 <p> 13474 These keywords were added to allow users to experiment with the 13475 characters for punctuation and stop for stylecode sequences. This 13476 is mostly to illustrate the point that it is almost impossible to 13477 make stylecodes work in every case you want without getting a lot 13478 of false highlights too. Please keep in mind that stylecodes are, 13479 and always will be, a primitive and very error-prone method for 13480 adding highlights to message text. The defaults are: 13481 </p> 13482 <p> 13483 STYLECODEPUNCT <q>!\"$%&()+,.:;<=>@[\]^`{|}~</q> 13484 STYLECODESTOPS <q></q> 13485 </p> 13486 <p> 13487 Note that the double-quote (") must have the backslash (\) in 13488 front of it - the sequence (\") is translated to a single ("). 13489 </p> 13490 </div2> 13491 <div2 id=TAGLINE> 13492 <head> 13493 TAGLINE <string or filename> 13494 </head> 13495 <p> 13496 Defines one or more taglines. A tagline collection filename can be 13497 specified if prepended with an '@' character, like this: TAGLINE 13498 @TAGLINE.LST. If a tagline collection file is used, <name>GoldED+</name> will 13499 create an index file for it the first time it is used or any time 13500 the file is edited. The index file has the same name, but 13501 extension ".SDX". The index file is an array of 32-bit long 13502 integers, containing the offset of each line in the tagline 13503 collection file. 13504 </p> 13505 <p> 13506 This keyword can be used globally and in a Random System group. 13507 </p> 13508 <p> 13509 Taglines defined in the Random System *always* overrides the 13510 default global taglines defined with this keyword. 13511 </p> 13512 </div2> 13513 <div2 id=TAGLINECHAR> 13514 <head> 13515 TAGLINECHAR <char> 13516 </head> 13517 <p> 13518 ('.') 13519 </p> 13520 <p> 13521 Defines the character <name>GoldED+</name> uses when putting a tagline in your 13522 message. The default is '.'. You should not change this default. 13523 <name>GoldED+</name> itself only recognizes taglines with '.' or '_' 13524 (underscore). 13525 </p> 13526 </div2> 13527 <div2 id=TAGLINESUPPORT> 13528 <head> 13529 TAGLINESUPPORT <yes/no> 13530 </head> 13531 <p> 13532 (yes) 13533 </p> 13534 <p> 13535 Allows you to turn off the internal tagline support, in case it 13536 turns out to be too buggy or if you want to use one of the many 13537 good external tagline utilties out there instead. 13538 </p> 13539 </div2> 13540 <div2> 13541 <head> 13542 TASKTITLE <string> 13543 </head> 13544 <p> 13545 (@longpid) 13546 </p> 13547 <p> 13548 Sets window title in Win32 and OS/2 versions, ignored in other. 13549 </p> 13550 </div2> 13551 <div2 id=TEARLINE> 13552 <head> 13553 TEARLINE <string> 13554 </head> 13555 <p> 13556 (@longpid @version) 13557 </p> 13558 <p> 13559 Here you can define your default tearline. The tearline can be up 13560 to 76 chars long (excluding the leading "--- "), but beware that 13561 policies (such as FidoNet ECHOPOL1) may set a significantly lower 13562 limit (around 30). 13563 </p> 13564 <p> 13565 This keyword can be used globally and in a Random System group. 13566 </p> 13567 <p> 13568 Tearlines defined in the Random System *always* overrides the 13569 default tearline defined with this keyword. 13570 </p> 13571 <p> 13572 If your tearline does not contain at least the string "GoldED" or 13573 "GED", <name>GoldED+</name> will automatically insert it's PID kludge. See also 13574 description of USEPID keyword. 13575 </p> 13576 </div2> 13577 <div2 id=TEMPLATE> 13578 <head> 13579 TEMPLATE <file> ["desc"] [match-address] 13580 </head> 13581 <p> 13582 (GOLDED.TPL) 13583 </p> 13584 <p> 13585 You can define many different template files. The templates can be 13586 switched using the READchangetemplate (Ctrl-T) popup menu or the 13587 EDITMENU. 13588 </p> 13589 <p> 13590 The optional "desc" can be used to give the templates more 13591 meaningful names like "International template" instead of 13592 non-obvious names like "GOLDED.TPL". If a description is used, it 13593 must appear before the match-address. It must always be enclosed 13594 in quotes, even if it is only one word. 13595 </p> 13596 <p> 13597 The match-address is an address mask (wildcards allowed) which can 13598 be used to tell <name>GoldED+</name> to select that template if the destination 13599 address on a message you write matches the match-address. The 13600 matching will only take place if the TEMPLATEMATCH keyword has 13601 been enabled. 13602 </p> 13603 <p> 13604 This keyword can be used globally and in a Random System group. In 13605 Random System groups, only the <file> parameter can be used. 13606 </p> 13607 <p> 13608 Templates defined in Random System groups always override the 13609 globally defined templates, except when selected from the EDITMENU 13610 or when automatic template matching is in effect. 13611 </p> 13612 <p> 13613 To override the automatic template matching, start by selecting a 13614 template manually using the READchangetemplate (Ctrl-T) command or 13615 the EDITMENU. 13616 </p> 13617 <p> 13618 Currently only one match-address per template can be specified, 13619 but you can specify several TEMPLATE keywords for the same file. 13620 </p> 13621 <p> 13622 Example: 13623 </p> 13624 <p> 13625 // Use DANSK.TPL for messages to Danish nodes/points. 13626 TEMPLATE DANSK.TPL "Danish" 2:23/* 13627 TEMPLATE DANSK.TPL "Danish" 2:234/* 13628 TEMPLATE DANSK.TPL "Danish" 2:235/* 13629 TEMPLATE DANSK.TPL "Danish" 2:236/* 13630 TEMPLATE DANSK.TPL "Danish" 2:237/* 13631 TEMPLATE DANSK.TPL "Danish" 2:238/* 13632 </p> 13633 <p> 13634 // Use INTERNET.TPL for messages to the WinBoss gateway 13635 TEMPLATE INTERNET.TPL "Internet" 2:230/9316 13636 </p> 13637 <p> 13638 // Use ENGLISH.TPL for messages to everywhere else 13639 TEMPLATE ENGLISH.TPL "English" * 13640 </p> 13641 </div2> 13642 <div2 id=TEMPLATEMATCH> 13643 <head> 13644 TEMPLATEMATCH <yes/no> 13645 </head> 13646 <p> 13647 (no) 13648 </p> 13649 <p> 13650 If enabled, <name>GoldED+</name> will select a template which matches the 13651 destination address on messages that you write. This keyword can 13652 be used globally or in random system groups. 13653 </p> 13654 </div2> 13655 <div2> 13656 <head> 13657 TEMPLATEPATH <path> 13658 </head> 13659 <p> 13660 (defaults to the GOLDPATH) 13661 </p> 13662 <p> 13663 Defines the default path for msg templates. Use this if you want 13664 to place templates in a path separate from the GOLDPATH. 13665 </p> 13666 </div2> 13667 <div2> 13668 <head> 13669 TEMPPATH <path> 13670 </head> 13671 <p> 13672 Defines the directory where temporary files are placed by <name>GoldED+</name> 13673 and GoldNODE. 13674 </p> 13675 <p> 13676 This path should *NOT* point to a RAM disk or other volatile 13677 media! 13678 </p> 13679 <p> 13680 GoldNODE uses this path to store a temporary file which can become 13681 as large as the largest index file (GOLDNODE.GXN), so again, don't 13682 point it to a small RAM disk. If GoldNODE cannot find a TEMPPATH, 13683 it will use the NODEPATH instead. 13684 </p> 13685 </div2> 13686<div2 id=TIMEOUT><head>TIMEOUT <seconds></head> 13687 <p> 13688 (0) 13689 </p> 13690 <p> 13691 Similar to the screen blanking (SCREENBLANKER) feature, <name>GoldED+</name> can 13692 auto-exit after a specified period of time. Useful if you are in a 13693 hurry (or didn't get enough sleep last night ;-), and run <name>GoldED+</name> 13694 from your mailer shell. The timeout value can be overridden with 13695 the -T commandline option. 13696 </p> 13697 <p> 13698 NOTE: This feature only works if KEYBMODE is set to "poll". 13699 </p> 13700 </div2> 13701 <div2> 13702 <head> 13703 TIMEOUTSAVEMSG <yes/no> 13704 </head> 13705 <p> 13706 (yes) 13707 </p> 13708 <p> 13709 If set to YES, <name>GoldED+</name> behaves as usual: It saves the (perhaps 13710 partially written) msg text in the internal editor to the msgbase 13711 and exits. If set to NO, <name>GoldED+</name> will save the msg text in 13712 GOLDED.MSG just as if EDITAUTOSAVE function was in use and the 13713 power went out. Next time you started <name>GoldED+</name> and entered a msg, it 13714 would detect the "lost" msg and ask you if it should be continued. 13715 </p> 13716 </div2> 13717 <div2> 13718 <head> 13719 TITLESTATUS <yes/no> 13720 </head> 13721 <p> 13722 (yes) 13723 </p> 13724 <p> 13725 If enabled then brief status will be added to title. (Win32 and 13726 OS/2 versions only) 13727 </p> 13728 </div2> 13729 <div2 id=TWITMODE> 13730 <head> 13731 TWITMODE <mode> 13732 </head> 13733 <p> 13734 (Blank) 13735 </p> 13736 <p> 13737 In <name>GoldED+</name> you can define several "Twit" names, addresses or 13738 subjects. With this keyword you can specify the action taken when 13739 a Twit message is encountered. 13740 </p> 13741 <p> 13742 The <mode> can be one of the following: 13743 </p> 13744 <p> 13745 Show Show twit messages. 13746 Blank Blank twit messages. 13747 Skip Skip twit messages, unless to your USERNAME's. 13748 Ignore Skip twit messages, always. 13749 Kill Deletes twit messages, *without* confirmation! 13750 </p> 13751 <p> 13752 This keyword can be used globally and in a Random System group. 13753 </p> 13754 </div2> 13755 <div2> 13756 <head> 13757 TWITNAME <name/address> 13758 </head> 13759 <p> 13760 With this keyword, you can specify "Twit" names and/or addresses. 13761 When a Twit name/address is detected, the TWITMODE setting will 13762 determine the action taken. 13763 </p> 13764 </div2> 13765 <div2> 13766 <head> 13767 TWITSUBJ <"string"> 13768 </head> 13769 <p> 13770 With this keyword, you can specify "Twit" subjects. When a Twit 13771 subject is detected, the TWITMODE setting will determine the 13772 action taken. The subject string is searched in the entire subject 13773 text, so you can specify a partial twit subject. Twit subjects are 13774 limited to maximum 35 characters. 13775 </p> 13776 </div2> 13777 <div2> 13778 <head> 13779 TWITTO <yes/no> 13780 </head> 13781 <p> 13782 (no) 13783 </p> 13784 <p> 13785 If enabled, <name>GoldED+</name> will check both from- and to-names when 13786 checking for twitnames. By default only the from-names are 13787 checked. 13788 </p> 13789 <p> 13790 This is a global keyword and won't work as intended if used in a 13791 random system group. 13792 </p> 13793 </div2> 13794 <div2 id=UNPACKER> 13795 <head> 13796 UNPACKER 13797 </head> 13798 <p> 13799 Added ability to READ packed messagebases. You need to add PKD 13800 attribute to such echo definition and specify UNPACKER for the 13801 extension defined. You should pack all files from the single 13802 messagebase to the archive with the same name. For *.msg areas you 13803 should add the directory as well. When entering to the archived area 13804 UNPACKER will be executed to unpack files to TEMPPATH. On exit, all 13805 files will be deleted. 13806 13807 New UNPACKER keyword have the following syntax: 13808 13809 UNPACKER >extension< ><q/commandline/< 13810 13811 The commandline should provide the ability to extract all files from 13812 @file.<extension> to the current directory. F.e.: 13813 13814 UNPACKER zip <q/unzip @file/ 13815 13816 Note that all changes to the messagebase will be discarded. 13817 13818 This feature is not supported for Hudson and GoldBase messagebases. 13819 </p> 13820 </div2> 13821 <div2 id=USEAREA> 13822 <head> 13823 USEAREA <yes/no> 13824 </head> 13825 <p> 13826 (yes) 13827 </p> 13828 <p> 13829 If set to no then GoldEd will not recognize <gi/AREA/ kludge. 13830 </p> 13831 </div2> 13832 <div2> 13833 <head> 13834 USECHARSET <yes/no> 13835 </head> 13836 <p> 13837 (yes) 13838 </p> 13839 <p> 13840 If set to no then GoldEd will not generate @CHRS and @CHARSET 13841 kludges. 13842 </p> 13843 </div2> 13844 <div2> 13845 <head> 13846 USEFLAGS <yes/no> 13847 </head> 13848 <p> 13849 (yes) 13850 </p> 13851 <p> 13852 If enabled, <name>GoldED+</name> inserts the FLAGS kludge for certain extended 13853 attributes, as defined in FSC-0053 by Joaquim H. Homrighausen, and 13854 supported by FrontDoor, D'Bridge, IMail and other modern software. 13855 <name>GoldED+</name> uses FLAGS to emulate the Hold and Freq attributes which 13856 are not defined in the Hudson message format. 13857 </p> 13858 </div2> 13859 <div2 id=USEFWD> 13860 <head> 13861 USEFWD <yes/no/ask> 13862 </head> 13863 <p> 13864 (yes) 13865 </p> 13866 <p> 13867 If enabled, <name>GoldED+</name> inserts the FSC-0092 kludges introduced by the 13868 author of FleetStreet, Michael Hohner. These are 13869 </p> 13870 <p> 13871 FWDFROM The original From-Name 13872 FWDORIG The original From-Aka 13873 FWDTO The original TO-Field 13874 FWDDEST The original TO-aka (only in netmails) 13875 FWDSUBJ The original subject 13876 FWDAREA The original areatag 13877 FWDMSGID The original MSGID (useful for reply-linking) 13878 </p> 13879 <p> 13880 When forwarding, <name>GoldED+</name> now adds these kludges, unless the 13881 original message already contains them, in which case they are 13882 preserved. When doing a normal reply (Alt-Q or Alt-R) to a message 13883 with the FWD kludges, <name>GoldED+</name> replies to the forwarder. To reply to 13884 the from-name in the forwarded message, use the comment-reply 13885 function (Alt-G). If the message contains the FWDAREA kludge, you 13886 can reply to the forwarder in the original area (Alt-N) or reply 13887 to the from-name in the original area (Alt-B). Note that it is not 13888 possible to reply to the to-name of a message with the FWD 13889 kludges, and it is also not possible to reply to the to-name of 13890 the forwarded message (the FWDTO name). 13891 </p> 13892 </div2> 13893 <div2> 13894 <head> 13895 USEINTL <type> 13896 </head> 13897 <p> 13898 (yes) 13899 </p> 13900 <p> 13901 The INTL kludge is normally only inserted in netmail messages, if 13902 the origination zone is different from the destination zone (the 13903 "Auto" setting), but on systems with many AKA's in the mailer, it 13904 might be useful/necessary to add it ALWAYS (the "Yes" setting). 13905 The "No" option should never be used. 13906 </p> 13907 <p> 13908 The <type> can be one of the following: 13909 </p> 13910 <p> 13911 Auto Only insert in inter-zone netmail. 13912 Yes Always insert. Recommended and default. 13913 No Never insert. 13914 </p> 13915 </div2> 13916 <div2> 13917 <head> 13918 USEMSGID <yes/no> 13919 </head> 13920 <p> 13921 (yes) 13922 </p> 13923 <p> 13924 If enabled, the MSGID kludge is inserted in netmail and echomail, 13925 and the REPLY kludge is inserted when replying to a msg with a 13926 MSGID. 13927 </p> 13928 <p> 13929 The MSGID kludge is defined in FidoNet document FTS-9. 13930 </p> 13931 </div2> 13932 <div2> 13933 <head> 13934 USEPID <yes/no> 13935 </head> 13936 <p> 13937 (no if GoldEd mentioned in tearline, yes otherwise) 13938 </p> 13939 <p> 13940 If disabled then @PID kludge will not be used in your messages 13941 regardless of tearline contents. 13942 </p> 13943 </div2> 13944 <div2> 13945 <head> 13946 USERLIST <file> [zone/addr] 13947 </head> 13948 <p> 13949 In addition to normal nodelist support, <name>GoldED+</name> also supports the 13950 "FIDOUSER.LST" style userlist format. The default zone is defined 13951 by the first ADDRESS or AKA, but can be overridden by adding the 13952 zone number or a full address after the filename. 13953 </p> 13954 <p> 13955 <file> Userlist file in FIDOUSER.LST format. 13956 [zone/addr] Default address for the userlist (if no zone info 13957 is present). 13958 </p> 13959 </div2> 13960 <div2> 13961 <head> 13962 USERLISTFILE <file> 13963 </head> 13964 <p> 13965 (GOLDED.LST) 13966 </p> 13967 <p> 13968 <name>GoldED+</name> can generate a list of all users in the current area. This 13969 keyword defines the default name of the FIDOUSER.LST style 13970 userlist output file generated with the READmakeuserlist command. 13971 </p> 13972 </div2> 13973 <div2 id=USERNAME> 13974 <head> 13975 USERNAME <name>[[,]< >address] 13976 </head> 13977 <p> 13978 You can define many different names/aliases. When <name>GoldED+</name> finds an 13979 un-received message to one of your USERNAME's, it is marked as 13980 received. Useful if you use alias names in some conferences. It is 13981 possible to change the current name using the READchangeusername 13982 popup menu. 13983 </p> 13984 <p> 13985 For msgbase formats with an associated user database, <name>GoldED+</name> uses 13986 the *first* defined USERNAME to look in the user database for 13987 which lastread record to use. If your name is not found, it is 13988 added and a new lastread record created. 13989 </p> 13990 <p> 13991 Example: 13992 </p> 13993 <p> 13994 USERNAME Odinn Sorensen, 2:236/77.999 13995 </p> 13996 <p> 13997 This keyword can be used globally and in a Random System group. 13998 </p> 13999 </div2> 14000 <div2 id=USETZUTC> 14001 <head> 14002 USETZUTC <yes/no> 14003 </head> 14004 <p> 14005 (no) 14006 </p> 14007 <p> 14008 Activates usage of TZUTC kludge in your messages. You should 14009 properly setup timezone information in your OS. For example, 14010 in DOS you should set environment variable TZ to something 14011 like this: 14012 </p> 14013 <p> 14014 TZ=MSK-3MSD,M3.5.0/02:00,M10.5.0/03:00 14015 </p> 14016 <p> 14017 This line valid for Moscow, Russia. 14018 </p> 14019 <p> 14020 This option could be used in random system groups. 14021 </p> 14022 </div2> 14023 <div2> 14024 <head> 14025 UUDECODEPATH <path> 14026 </head> 14027 <p> 14028 Specifies the path where files are placed when using the uudecode 14029 feature. Files are placed in current directory if a path is not 14030 specified. 14031 </p> 14032 <p> 14033 The specified path *must* exist ! 14034 </p> 14035 </div2> 14036 <div2 id=VIEWHIDDEN> 14037 <head> 14038 VIEWHIDDEN <yes/no> 14039 </head> 14040 <p> 14041 (no) 14042 </p> 14043 <p> 14044 Hidden lines are "unknown" kludge lines. If enabled, hidden lines 14045 will be displayed (in a different color) when reading msgs. 14046 </p> 14047 <p> 14048 A hidden line is defined as a line which has the FidoNet kludge 14049 char (^a, ASCII 1) as the first char and is not on the list of 14050 internally or user defined known kludges. 14051 </p> 14052 <p> 14053 This keyword can be used globally and in a Random System group. 14054 </p> 14055 <p> 14056 IMPORTANT NOTE: 14057 </p> 14058 <p> 14059 In some conferences the hidden lines are used to give witty 14060 comment "between the lines" in the plain text, but generally it is 14061 considered a bad practice and should be avoided because it may 14062 cause severe technical problems if a witty comment in a hidden 14063 line happens to match a (perhaps experimentally) defined kludge 14064 somewhere. It should also be noted that hidden lines are not kept 14065 in their original places when used in the JAM msgbase. This is due 14066 to the way the JAM specification stores FidoNet kludges. 14067 </p> 14068 </div2> 14069 <div2 id=VIEWKLUDGE> 14070 <head> 14071 VIEWKLUDGE <yes/no> 14072 </head> 14073 <p> 14074 (no) 14075 </p> 14076 <p> 14077 If enabled, known kludge lines will be displayed (in a different 14078 color) when reading msgs. 14079 </p> 14080 <p> 14081 Known kludges are those defined internally in <name>GoldED+</name> plus those 14082 defined with the KLUDGE keyword. 14083 </p> 14084 <p> 14085 This keyword can be used globally and in a Random System group. 14086 </p> 14087 </div2> 14088 <div2 id=VIEWQUOTE> 14089 <head> 14090 VIEWQUOTE <yes/no> 14091 </head> 14092 <p> 14093 (yes) 14094 </p> 14095 <p> 14096 This is an experimental feature. It is similar to the VIEWHIDDEN 14097 and VIEWKLUDGE keywords, but for quoted text. I implemented it 14098 because I was annoyed with the excessive quoting often seen in 14099 Internet newsgroups. When this keyword is set to NO, <name>GoldED+</name> 14100 attempts to trim down the quotes so that only the first line of 14101 each quote block is shown. It is not always successful, sometimes 14102 the result is not so useful. 14103 </p> 14104 <p> 14105 A key command has been added to supplement this feature: 14106 READtogglequote. Suggested key assignment: Ctrl-V. Example: 14107 </p> 14108 <p> 14109 ^V READtogglequote 14110 </p> 14111 <p> 14112 Try it out if you are annoyed with excessive quotes. 14113 </p> 14114 <p> 14115 This keyword can be used globally and in a Random System group. 14116 </p> 14117 </div2> 14118 <div2 id=WHOTO> 14119 <head> 14120 WHOTO <name> 14121 </head> 14122 <p> 14123 This name is inserted in the TO: name field, when entering new 14124 messages (not replies) in echomail or local areas. 14125 </p> 14126 <p> 14127 This keyword can be used globally and in a Random System group. 14128 </p> 14129 </div2> 14130 <div2 id=WILDCATUSERNO> 14131 <head> 14132 WILDCATUSERNO <userno> 14133 </head> 14134 <p> 14135 Defines the lastread set used in the WildCat! 4.x message base. 14136 </p> 14137 </div2> 14138 <div2 id=WRITETEMPLATE> 14139 <head> 14140 WRITETEMPLATE 14141 </head> 14142 <p></p> 14143 </div2> 14144 <div2 id=XLATCHARSET> 14145 <head> 14146 XLATCHARSET <importid> <exportid> <file> 14147 </head> 14148 <p> 14149 This keyword defines character set translation table files. 14150 </p> 14151 <p> 14152 <importid> Charset import identifier. 14153 <exportid> Charset export identifier. 14154 <file> Charset translation table file. 14155 </p> 14156 <p> 14157 See the Character Translation chapter for details. 14158 </p> 14159 </div2> 14160 <div2 id=XLATESCSET> 14161 <head> 14162 XLATESCSET <import> <export> <escfile> 14163 </head> 14164 <p> 14165 This keyword defines escape sequence translation table files. 14166 </p> 14167 <p> 14168 <importid> Escset import identifier. 14169 <exportid> Escset export identifier. 14170 <file> Escape sequence translation table file. 14171 </p> 14172 <p> 14173 See the Character Translation chapter for details. 14174 </p> 14175 </div2> 14176 <div2 id=XLATEXPORT> 14177 <head> 14178 XLATEXPORT <charsetid> 14179 </head> 14180 <p> 14181 Defines the export charset for your messages. See the Character 14182 Translation chapter for details. 14183 </p> 14184 <p> 14185 This keyword can be used globally and in a Random System group. 14186 </p> 14187 <p> 14188 It can also be used in templates (the @xlatexport token). 14189 </p> 14190 </div2> 14191 <div2 id=XLATIMPORT> 14192 <head> 14193 XLATIMPORT <charsetid> 14194 </head> 14195 <p> 14196 (IBMPC) 14197 </p> 14198 <p> 14199 Defines the local charset for your machine. See the Character 14200 Translation chapter for details. 14201 </p> 14202 <p> 14203 This keyword can be used globally and in a Random System group. 14204 </p> 14205 </div2> 14206 <div2> 14207 <head> 14208 XLATLOCALSET <charsetid> 14209 </head> 14210 <p> 14211 (IBMPC) 14212 </p> 14213 <p> 14214 Use this keyword to specify the actual physical charset in effect 14215 for text screen display. This was previously the hardcoded value 14216 IBMPC, corresponding to the IBM codepage 437 (or the nordic 14217 edition 865). 14218 </p> 14219 <p> 14220 NOTE: All charset translation files must translate from and to the 14221 charset identified with the XLATLOCALSET keyword! 14222 </p> 14223 </div2> 14224 <div2> 14225 <head> 14226 XLATPATH <path> 14227 </head> 14228 <p> 14229 This is the path where <name>GoldED+</name> tries to find the XLATCHARSET and 14230 XLATESCSET files. 14231 </p> 14232 </div2> 14233 <div2> 14234 <head> 14235 ZONEGATING <yes/no/ask> 14236 </head> 14237 <p> 14238 (ask) 14239 </p> 14240 <p> 14241 When writing a netmail message to a destination in another zone, 14242 you can either send the message directly (No) or via the local 14243 ZoneGate (Yes). You can also be consulted each time (Ask). <name>GoldED+</name> 14244 won't ask if Cra or Hld attribute is set. 14245 </p> 14246 <p> 14247<!-- page --> 14248<!-- --------------------------------------------------------------------- --> 14249 </div2> 14250 </div1> 14251 <div1> 14252 <head> 14253 Obsolete Keywords 14254 </head> 14255 <p> 14256This is a list of keywords which were used in various older versions. 14257These keywords are now obsolete, either because they have been renamed 14258or replaced, or if they no longer have any function. Most of the 14259keywords are still active and remapped to the new names. 14260 </p> 14261 <p> 14262To check if you have obsolete keywords in your setup, run <name>GoldED+</name> with 14263the -F -D commandline parameters. Then if you get a number of "Unknown 14264keyword" warnings, you should replace the old keywords with the new 14265ones or remove them. 14266 </p> 14267 <p> 14268 Old keyword: New keyword: 14269 </p> 14270 <p> 14271 AREAAUTOFREQ AREAFREQTO 14272 AREABADMSGS SOUPBADMSGS 14273 AREASORT AREALISTSORT 14274 ASSIGNTO MEMBER 14275 AUTOATTACH EDITAUTOATTACH 14276 BLANKTIME SCREENBLANKER 14277 BOARDNOS (removed) 14278 CCATTRIB ATTRIBSCC 14279 CCLIST CARBONCOPYLIST 14280 CFMATTRIB ATTRIBSCFM 14281 CHANGEDATE EDITCHANGEDATE 14282 CHANGEPROMPT (removed) 14283 CHARSET XLATCHARSET 14284 CLEARKEYS (removed) 14285 COLOUR COLOR 14286 COMMENTNOISE BEEPCOMMENT 14287 COOKIEFILE (removed) 14288 CRLFTERM EDITCRLFTERM 14289 DELORIG ASKDELORIG 14290 DISPMSGLIST MSGLISTFIRST 14291 DISPMSGLISTFAST MSGLISTFAST 14292 DISPSTYLECODES STYLECODES 14293 DOSSWAP (removed) 14294 ECHOATTRIB ATTRIBSECHO 14295 ECHOINFO CTRLINFOECHO 14296 EDITMARGIN (removed) 14297 EDITORVERSION (removed) 14298 ELIMSNOW (removed) 14299 ESCSET XLATESCSET 14300 EXCLAREA AREAEXCL 14301 EXPORTCHARSET XLATEXPORT 14302 EXTKEYS (removed) 14303 FIDOLASTREADNO FIDOUSERNO 14304 FIELDCLEAR EDITFIELDCLEAR 14305 FILECHECK (removed) 14306 FILECHECKALL (removed) 14307 FREEAREA (removed) 14308 FREETEAR (removed) 14309 GOLDEDCFM CONFIRMFILE 14310 GOLDEDLOG LOGFILE 14311 GOLDEDLST USERLISTFILE 14312 GOLDEDMSG EDITORFILE 14313 GOLDEDNAM NAMESFILE 14314 GOLDEDPRN OUTPUTFILE 14315 GOLDHELP (no longer documented) 14316 GOLDKEYS (no longer documented) 14317 GOLDLANG (no longer documented) 14318 GOLDRAND (no longer documented) 14319 GOLDXLAT (no longer documented) 14320 HARDLINE EDITHARDLINE 14321 HARDLINES EDITHARDLINES 14322 HWMARKS (removed) 14323 INCLAREA AREAINCL 14324 INTERNALEDITOR EDITINTERNAL 14325 LASTREAD FIDOLASTREAD 14326 LASTREADUSER FIDOUSERNO 14327 LISTWRAP (removed) 14328 LOCALATTRIB ATTRIBSLOCAL 14329 LOCALCHARSET XLATIMPORT 14330 LOCALHIGHLIGHT (removed) 14331 LOCALINFO CTRLINFOLOCAL 14332 LOCALNOISE (removed) 14333 MAPDRIVE MAPPATH 14334 MATCHAKA AKAMATCH 14335 MAXCOLS SCREENMAXCOL 14336 MAXMSGSIZE (removed) 14337 EDITMSGSIZE (removed) 14338 MAXROWS SCREENMAXROW 14339 MIXCASE EDITMIXCASE 14340 MULTIQBBS (removed) 14341 NETATTRIB ATTRIBSNET 14342 NETINFO CTRLINFONET 14343 NETTEAR CTRLINFONET performs similar function 14344 NEXTAREA AREANEXT 14345 NEXTMSGS (removed) 14346 NODELISTPAGEBAR (removed) 14347 NOISEFACTOR (removed) 14348 OVERLAY (removed) 14349 OVERLAYEMS (removed) 14350 OVERLAYEXT (removed) 14351 PAGEBAR (removed) 14352 QBBSINCRESCAN (removed) 14353 QBBSPATH HUDSONPATH 14354 QBBSREBUILD (removed) 14355 QBBSSCAN (removed) 14356 QMSGPATH HUDSONPATH 14357 REALMSGNO (removed) 14358 REBUILD (removed) 14359 RENAREA AREARENAME 14360 REPLYRE EDITREPLYRE 14361 RIGHTMARGIN DISPMARGIN 14362 SAVEMENU EDITSAVEMENU 14363 SAVETIME EDITAUTOSAVE 14364 SAYBIBI (removed) 14365 SCANAREA AREASCAN 14366 SCREENELIMSNOW (removed) 14367 SCREENUSEANSI (removed) 14368 SHADOWS (removed) 14369 SHARE SHAREMODE 14370 SHOWTWITS TWITMODE 14371 SIGNALFILE SEMAPHORE 14372 SOUNDDEVICE (removed) 14373 SPACEQUOTES (removed) 14374 SPELLCHECKER EDITSPELLCHECK 14375 STACKKEYS KEYBSTACK 14376 STARTECHO AREASTART 14377 SWAPALL (removed) 14378 SYSOP USERNAME 14379 TABSIZE DISPTABSIZE 14380 TAGLINEFILE (removed) 14381 TIMESLICE (removed) 14382 TIMEZONEOFFSET USETZUTC performs similar function 14383 UNDELETELINES EDITUNDELETE 14384 USEBIOS SCREENUSEBIOS 14385 XPLIST CROSSPOSTLIST 14386 </p> 14387 <p> 14388<!-- page --> 14389<!-- --------------------------------------------------------------------- --> 14390 </div1> 14391 <div1> 14392 <head> 14393 Location Dependent Configuration Keywords 14394 </head> 14395 <p> 14396The following configuration keywords are location dependent and should 14397be placed in a particular order in the configuration file(s). Keywords 14398that are *not* listed can be placed anywhere you want. 14399 </p> 14400 <p> 14401The keywords are listed in groups of those that depend on each other. 14402They are listed in the recommended order within each group. The order 14403between the groups is not important, with one noted exception. 14404 </p> 14405 <p> 14406Name/Address/Areas: 14407 USERNAME 14408 ADDRESS 14409 AKA 14410 ATTRIBSNET Specifies default attributes for AREAFILE etc. 14411 ATTRIBSECHO As above. 14412 ATTRIBSLOCAL As above. 14413 FIDOMSGTYPE 14414 PCBOARDPATH Recommended if you use PCBoard. 14415 MAPPATH 14416 AREARENAME Rename occurs before AREAEXCL/INCL. 14417 AREAEXCL 14418 AREAINCL 14419 AREAISEMAIL 14420 AREAISNEWS 14421 AREAPATH Default path for the AREAFILE's. 14422 AREAFILE 14423 RA2USERSBBS Overrides AREAFILE RemoteAccess. 14424 AREADESC Add description and more to some AREAFILE's. 14425 AREA Overrides areas in AREAFILE's. 14426 AREADEF As above. 14427 </p> 14428 <p> 14429Paths: 14430 GOLDPATH 14431 TEMPPATH MUST be in GOLDED.CFG. Used only by GoldNODE. 14432 </p> 14433 <p> 14434Nodelists: MUST be below ADDRESS/AKA and ONLY in GOLDED.CFG! 14435 NODEPATH 14436 NODELIST 14437 USERLIST 14438 EXCLUDENODES Remember to replace "ALL" with '*'. 14439 INCLUDENODES As above. 14440 </p> 14441 <p> 14442Colors: 14443 INTENSECOLORS Selects a default intense colorset if enabled. 14444 COLORSET Selects a default colorset. 14445 COLOR 14446 </p> 14447 <p> 14448External utils: 14449 EXTERNOPTIONS 14450 EXTERNUTIL 14451 </p> 14452 <p> 14453Character translation: 14454 XLATPATH 14455 XLATCHARSET 14456 XLATESCSET 14457 </p> 14458 <p> 14459Random System: 14460 GROUP Starts a group. 14461 MEMBER Defines areas that are members of the group. 14462 <Group Items> See the Random System chapter for a list. 14463 ENDGROUP Ends a group. 14464 </p> 14465 <p> 14466<!-- page --> 14467<!-- --------------------------------------------------------------------- --> 14468 </div1> 14469<div1 id=MESSAGEATTRS><head>Message Attributes Reference</head> 14470 <p> 14471This is a list and description of all message attributes that are 14472supported by <name>GoldED+</name> in the keywords that accept attribute settings or 14473can be displayed in the header. 14474 </p> 14475 <p> 14476A/S Archive/sent. 14477ARQ Audit request. 14478ATT File attached. 14479CFM Confirmation receipt requested. 14480COV Fax cover letter. 14481CRA Crash - high priority mail. 14482DEL Deleted. 14483DIR Direct. Don't route this message. 14484FAX Fax image attached. 14485FRQ File request. 14486GRP Group message. 14487HIR Fax hi-resolution image. 14488HLD Hold for pickup. 14489HUB Host- or Hub-route message. 14490IMM Immediate - Send message NOW! 14491K/S Kill/sent. Delete message automatically after it is sent. 14492KFS Kill/file/sent. Delete attached files after they are sent. 14493LET Fax letterhead. 14494LOC Local. Message was written on your system. 14495LOK Lock. Prevents send/delete/purge/editing. 14496ORP Orphan. Could not be sent because destination node is unknown. 14497PKD Packed. Used in area definitions to unpack before using. 14498PRN Msg has been printed. Specific for Squish (bitvalue 00040000h). 14499PVT Private. Message may only be read by the addressee and author. 14500R/O Read only. Used in area definitions to prevent writing. 14501RCV Received. Read by the addressee. 14502RRC Return receipt. 14503RRQ Return receipt requested. 14504RSV FTS-1 reserved (unused) attribute. 14505SIG Fax signature. 14506SNT Sent. Message has been sent or exported from the msgbase. 14507TFS Truncate/file/sent. Truncate files to zero length when sent. 14508TRS Transit. Message passing through, not for you. 14509UNS Unsent message. 14510URQ Update file request. 14511XMA Xmail. Attach does not conform to the ARCmail 0.60 standard. 14512ZON Zonegate. Route through zonegate if possible. 14513 </p> 14514 <p> 14515<!-- page --> 14516<!-- --------------------------------------------------------------------- --> 14517 </div1> 14518<div1 id=AREACONFIGURATION><head>Area Configuration</head> 14519 <p> 14520GoldED offers a wide variety of methods for defining message areas. 14521You can define each area manually in the GOLDED.CFG file (or an 14522INCLUDE'ed GOLDAREA.CFG file), or you can tell <name>GoldED+</name> to read the area 14523setup files of many popular BBS/mailer/mail processor packages. 14524 </p> 14525 <p> 14526For manual definition of areas, use the AREA or AREADEF (recommened) 14527keywords. 14528 </p> 14529 <p> 14530For external area configuration, the general syntax for the AREAFILE 14531keyword is: 14532 </p> 14533 <p> 14534 AREAFILE <programname> [path or filename(s)] [-options] 14535 </p> 14536 <p> 14537Available options: 14538 </p> 14539 <p> 14540-S<sortspec> 14541 </p> 14542 <p> 14543 If you are *not* using the global AREALISTSORT keyword for sorting 14544 all the areas, you can sort the areas of each AREAFILE separately. 14545 See the AREALISTSORT keyword for the definition of <sortspec>. 14546 </p> 14547 <p> 14548If no path is specified, the appropriate environment variable or the 14549AREAPATH is used to find the files. 14550 </p> 14551 <p> 14552The <programname> can be one of the following: 14553 </p> 14554 <div2> 14555 <head> 14556 AdeptXBBS 14557 </head> 14558 <p> 14559 Reads the AdeptXBBS configuration files. 14560 </p> 14561 <p> 14562 Looks for the ADEPTXBBS environment variable. 14563 </p> 14564 </div2> 14565 <div2> 14566 <head> 14567 AreasBBS 14568 </head> 14569 <p> 14570 <name>GoldED+</name> is can handle a wide variety of AREAS.BBS type files. It 14571 can read and distinguish between the old CONFMAIL style with paths 14572 for *.MSG areas, the Hudson/Goldbase style with board numbers, the 14573 Squish style with "$basename" and the JAM style with "!basename". 14574 </p> 14575 <p> 14576 The disadvantage of using an AREAS.BBS is that there are no area 14577 descriptions. The echoid is used as description instead. However, 14578 <name>GoldED+</name> will use any text behind a semicolon on definition lines as 14579 description. This may or may not be compatible with mail 14580 processors, so be careful. A better solution may be to use the 14581 AREAFILE Echolist to add descriptions from a separate file. 14582 </p> 14583 <p> 14584 One or more AREAS.BBS files may be specified on the same line. 14585 </p> 14586 </div2> 14587 <div2> 14588 <head> 14589 Concord 14590 </head> 14591 <p> 14592 Support is planned but not yet implemented. 14593 </p> 14594 </div2> 14595 <div2> 14596 <head> 14597 Crashmail 14598 </head> 14599 <p> 14600 Reads the CrashMail II configuration file. 14601 </p> 14602 </div2> 14603 <div2> 14604 <head> 14605 D'Bridge 14606 </head> 14607 <p> 14608 Reads the DBRIDGE.AA1/.AA2 files (for version 1.30) or the 14609 DBRIDGE.ADF of the later versions. 14610 </p> 14611 <p> 14612 Looks for the "DBRIDGE" and "DB" environment variables. 14613 </p> 14614 </div2> 14615 <div2> 14616 <head> 14617 Dutchie 14618 </head> 14619 <p> 14620 Reads the DUTCHIE.ARE file. 14621 </p> 14622 <p> 14623 Looks for the "DUTCHIE" environment variable. 14624 </p> 14625 </div2> 14626 <div2 id=ECHOLIST> 14627 <head> 14628 Echolist 14629 </head> 14630 <p> 14631 Reads a simple ascii-text file containing an echolist in this 14632 format: 14633 </p> 14634 <p> 14635 <echoid> <description> 14636 </p> 14637 <p> 14638 or DZ-format (requires -DZ switch): 14639 </p> 14640 <p> 14641 [Status], Tag, Comment, Moderator's Name, Address,[Flags] 14642 </p> 14643 <p> 14644 This feature adds descriptions to already existing areas in 14645 <name>GoldED+</name>. Example: 14646 </p> 14647 <p> 14648 AREAFILE AreasBBS AREAS.BBS 14649 AREAFILE EchoList ECHOLIST.TXT 14650 AREAFILE EchoList echo5020.lst -dz 14651 </p> 14652 <p> 14653 Descriptions for unknown echoids are ignored. Blank lines and 14654 lines beginning with characters which are illegal in echoids (such 14655 as ';') are also ignored. 14656 </p> 14657 <p> 14658 Additional switch -SqaFix could be used to read echolist and groups 14659 from SqaFix configuration file: 14660 </p> 14661 <p> 14662 AREAFILE Squish C:\SQUISH\ 14663 AREAFILE EchoList C:\SQUISH\SQAFIX.CFG -SqaFix 14664 </p> 14665 </div2> 14666 <div2> 14667 <head> 14668 Ezycom 14669 </head> 14670 <p> 14671 Reads CONFIG.EZY and MESSAGES.EZY. Supports Ezycom 1.02 and 1.10g, 14672 but not 1.01. 14673 </p> 14674 <p> 14675 Looks for the "EZY" and "TASK" environment variables. 14676 </p> 14677 </div2> 14678 <div2> 14679 <head> 14680 FastEcho 14681 </head> 14682 <p> 14683 Reads the FASTECHO.CFG file. Supports version 1.10 up to 1.46. 14684 </p> 14685 <p> 14686 Looks for the "FASTECHO" environment variable. 14687 </p> 14688 </div2> 14689 <div2> 14690 <head> 14691 Fidoconfig 14692 </head> 14693 <p> 14694 Reads fidoconfig (used in Husky Project software). Supports 14695 version 0.15. Used parser is more powerful than original from 14696 fidoconfig, due to it strictly follows specification from proposal 14697 and implements all features from there. Additionaly it implements 14698 groups not described in proposal but used in in library. 14699 </p> 14700 <p> 14701 Looks for the "FIDOCONFIG" environment variable. 14702 </p> 14703 </div2> 14704 <div2> 14705 <head> 14706 FidoPCB 14707 </head> 14708 <p> 14709 Reads FIDOPCB.CFG. Supports version 1.x. 14710 </p> 14711 <p> 14712 Looks for the "FIDOPCB" environment variable. 14713 </p> 14714 </div2> 14715 <div2> 14716 <head> 14717 FMail 14718 </head> 14719 <p> 14720 Reads FMAIL.CFG and FMAIL.AR. Supports versions 0.92, 0.98, 1.0g, 14721 and 1.20. 14722 </p> 14723 <p> 14724 Looks for the "FMAIL" environment variable. 14725 </p> 14726 </div2> 14727 <div2> 14728 <head> 14729 FrontDoor 14730 </head> 14731 <p> 14732 Reads the SETUP.FD/FD.SYS and FOLDER.FD/FOLDER.SYS files. If you 14733 want the real echoid's attached to the areas, you will also need 14734 to supply the filename of the relevant AREAS.BBS file(s). Supports 14735 versions 1.99c and 2.xx. 14736 </p> 14737 <p> 14738 Looks for the "FD" environment variable. 14739 </p> 14740 </div2> 14741 <div2> 14742 <head> 14743 GEcho 14744 </head> 14745 <p> 14746 Reads SETUP.GE and AREAFILE.GE. Supports versions 1.00, 1.02, 14747 1.10, 1.11 and 1.20. 14748 </p> 14749 <p> 14750 Looks for the "GE" environment variable. 14751 </p> 14752 </div2> 14753 <div2> 14754 <head> 14755 IMAIL 14756 </head> 14757 <p> 14758 Reads the IMAIL.CF and IMAIL.AR files. Supports version 1.60, 14759 1.7x and 1.8x. 14760 </p> 14761 <p> 14762 Looks for the "IMAIL" environment variable. 14763 </p> 14764 </div2> 14765 <div2> 14766 <head> 14767 InterMail 14768 </head> 14769 <p> 14770 Reads the FD.SYS/IMSYS.CFG and FOLDER.CFG/IMFOLDER.CFG files. 14771 Supports version 2.26 and newer. 14772 </p> 14773 <p> 14774 Looks for the "IM" environment variable. 14775 </p> 14776 </div2> 14777 <div2> 14778 <head> 14779 LoraBBS 14780 </head> 14781 <p> 14782 Reads the CONFIG.DAT and SYSMSG.DAT files. Supports version 2.33, 14783 2.40 and possibly others. 14784 </p> 14785 <p> 14786 Looks for the "LORA" and "LORABBS" environment variables. 14787 </p> 14788 </div2> 14789 <div2> 14790 <head> 14791 Maximus 14792 </head> 14793 <p> 14794 Reads the MAX.PRM and AREA.DAT or MAREA.DAT files. Compatible (or 14795 should be) with both the old (1.xx) and (2.xx) and new (3.xx) 14796 formats. If your AREA.DAT is named differently, you must supply 14797 the correct filename. 14798 </p> 14799 <p> 14800 Looks for the "MAXIMUS" environment variable. 14801 </p> 14802 </div2> 14803 <div2> 14804 <head> 14805 ME2 14806 </head> 14807 <p> 14808 Reads the old ME2 editor AREADESC.ME2 file and AREAS.BBS file(s). 14809 You must supply the names of both files. 14810 </p> 14811 </div2> 14812 <div2> 14813 <head> 14814 Opus 14815 </head> 14816 <p> 14817 Reads the Opus 1.1x SYSTEM??.DAT files or the Opus 1.7x SYSMSG.DAT 14818 file. 14819 </p> 14820 <p> 14821 Looks for the "OPUS" environment variable. 14822 </p> 14823 </div2> 14824 <div2> 14825 <head> 14826 ParToss 14827 </head> 14828 <p> 14829 Reads the ParToss configuration file. 14830 </p> 14831 </div2> 14832 <div2> 14833 <head> 14834 PCBoard 14835 </head> 14836 <p> 14837 Reads the PCBOARD.DAT, CNAMES.@@@ and CNAMES.ADD files. Supports 14838 version 14.x and 15.x, up to and including 15.22. Note that, 14839 depending on the version, echoid's may not be read from this 14840 format. If the echoid is not available, the description is used as 14841 echoid, after conversion to uppercase and spaces to underscores. 14842 </p> 14843 <p> 14844 Looks for the "PCBOARD" environment variable. 14845 </p> 14846 </div2> 14847 <div2> 14848 <head> 14849 Portal 14850 </head> 14851 <p> 14852 Reads the PORTAL*.CFG and PORTAL.ARE files. 14853 </p> 14854 <p> 14855 Looks for the "POPCMDLINE" environment variable. 14856 </p> 14857 </div2> 14858 <div2> 14859 <head> 14860 ProBoard 14861 </head> 14862 <p> 14863 Reads MSGAREAS.PB. Supports version 2.0. 14864 </p> 14865 <p> 14866 Looks for the "PB" environment variable. 14867 </p> 14868 </div2> 14869 <div2> 14870 <head> 14871 QEcho 14872 </head> 14873 <p> 14874 Reads /etc/qecho/AreaList. Supports version patched by Eugene 14875 Sorochinsky for JAM messae base support. 14876 </p> 14877 </div2> 14878 <div2> 14879 <head> 14880 QFront 14881 </head> 14882 <p> 14883 Reads QORIGIN.DAT and QECHOS.DAT. Supports version 1.13b. 14884 </p> 14885 <p> 14886 Looks for the "QFRONT" environment variable. 14887 </p> 14888 </div2> 14889 <div2> 14890 <head> 14891 QuickBBS 14892 </head> 14893 <p> 14894 Reads the CONFIG.BBS or QUICKCFG.DAT and MSGCFG.DAT files. To get 14895 the real echoid's, you must also supply the filename of the 14896 relevant AREAS.BBS. 14897 </p> 14898 <p> 14899 Looks for the "QUICKBBS" and "QBBS" environment variables. 14900 </p> 14901 </div2> 14902 <div2> 14903 <head> 14904 RaEcho 14905 </head> 14906 <p> 14907 Reads AREAS.RAE. Supports version 1.00 and 1.01. 14908 </p> 14909 <p> 14910 Looks for the "RAECHO" environment variable. 14911 </p> 14912 </div2> 14913 <div2> 14914 <head> 14915 RemoteAccess 14916 </head> 14917 <p> 14918 Reads the MESSAGES.RA file. To get the real echoid's, you must 14919 also supply the filename of the relevant AREAS.BBS. Supports 14920 versions 0.xx, 1.xx, 2.0x and 2.5x. 14921 </p> 14922 <p> 14923 Looks for the "RA" environment variable. 14924 </p> 14925 </div2> 14926 <div2> 14927 <head> 14928 Squish 14929 </head> 14930 <p> 14931 Reads SQUISH.CFG and AREAS.BBS (if used). Supports version 1.0x 14932 and 1.1x. The "Include <filename>" feature of Squish 1.10 is also 14933 supported. 14934 </p> 14935 <p> 14936 The optional /G switch specifies the default group of the imported 14937 areas, i.e. /g=G or /g=#103. 14938 </p> 14939 <p> 14940 Looks for the "SQUISH" and "MAXIMUS" environment variables. 14941 </p> 14942 </div2> 14943 <div2> 14944 <head> 14945 SuperBBS 14946 </head> 14947 <p> 14948 Reads CONFIG.BBS, SCONFIG.BBS and BOARDS.BBS. Supports version 14949 1.16 and 1.17. 14950 </p> 14951 <p> 14952 Looks for the "SUPERBBS" and "SBBS" environment variables. 14953 </p> 14954 </div2> 14955 <div2> 14956 <head> 14957 timEd 14958 </head> 14959 <p> 14960 Reads TIMED.CFG and any included file. Also reads the 14961 configuration from other mail software defined in TIMED.CFG. 14962 </p> 14963 <p> 14964 Looks for the "TIMED" environment variable. 14965 </p> 14966 </div2> 14967 <div2> 14968 <head> 14969 Termail 14970 </head> 14971 <p> 14972 This is for the Terminate Mail system (Termail). <name>GoldED+</name> does 14973 currently only support Termail 4.00 und 5.xx style .CFG-files. 14974 </p> 14975 <p> 14976 Reads TM.CFG and any AREAFILE (an AREAS.BBS type file) defined 14977 there. 14978 </p> 14979 <p> 14980 NOTE: If you use this, you must start <name>GoldED+</name> in the Termail 14981 directory, because the standard TM configuration files use 14982 relative paths. 14983 </p> 14984 <p> 14985 Looks for the "TM" environment variable. 14986 </p> 14987 </div2> 14988 <div2> 14989 <head> 14990 TosScan 14991 </head> 14992 <p> 14993 Reads the FD.SYS/SETUP.FD and AREAFILE.FD files. Supports version 14994 1.00 and FrontDoor 1.99c and 2.xx. 14995 </p> 14996 <p> 14997 Looks for the "FD" environment variable. 14998 </p> 14999 </div2> 15000 <div2> 15001 <head> 15002 WaterGate 15003 </head> 15004 <p> 15005 Reads the WTRCFG.TDB and AREABASE.TDB files. Supports version 15006 0.93. 15007 </p> 15008 </div2> 15009 <div2> 15010 <head> 15011 WMail 15012 </head> 15013 <p> 15014 Reads the WMAIL.PRM and AREAS.PRM files. Supports version 2.2. 15015 </p> 15016 <p> 15017 Looks for the "WMAIL" environment variable. 15018 </p> 15019 </div2> 15020 <div2> 15021 <head> 15022 XMail 15023 </head> 15024 <p> 15025 Reads the AREAS.XM file. Supports version 1.00. 15026 </p> 15027 <p> 15028 Looks for the "XM" environment variable. 15029 </p> 15030<!-- page --> 15031<!-- --------------------------------------------------------------------- --> 15032 </div2> 15033 </div1> 15034<div1 id=RANDOMSYSTEM><head>The Random System</head> 15035 <p> 15036With the Random System, you can define area-specific sets of origins, 15037tearlines, templates, usernames and many other items. If 15038more than one item of each type is specified, a random one is picked - 15039a Random System. This is a very useful feature when (for example) 15040participating in conferences with different languages. 15041 </p> 15042 <p> 15043The Random System is built on the idea of "groups". A group is a 15044collection of "items", belonging to the group. You can assign one or 15045more echomail areas, designated by their echoid's to a group. Groups 15046can also be specified for just a single echo, and DOS/4DOS-style 15047wildcards can be used to simplify the assignment of echoes with common 15048strings in their name, such as *.DK, SIG.* and so on. In this way, you 15049could for example setup one group for all national echoes, another for 15050special local echoes, a third for international echoes etc. 15051 </p> 15052 <div2> 15053 <head> 15054 Defining Groups 15055 </head> 15056 <p> 15057The general syntax of a group definition is: 15058 </p> 15059 <p> 15060GROUP <id>[:] 15061 ; items go here 15062 [Member <id list>] 15063ENDGROUP 15064 </p> 15065 <p> 15066The Group <id> can be one of three things: 15067 </p> 15068 <p> 150691. A group letter or #number, matching the group letters or numbers 15070 used in the AREAFILE's of D'Bridge, GEcho, IMAIL, TosScan and many 15071 others. To use this feature, you need to enable the AREAFILEGROUPS 15072 keyword. 15073 </p> 15074 <p> 150752. An individual echoid or echoid mask (wildcards can be used). The 15076 items are then simply defined below the Group line. 15077 </p> 15078 <p> 150793. A group label, terminated by a colon (:). The group items are 15080 defined below the Group line. Echoes are assigned to the group by 15081 adding one or more Member statements. 15082 </p> 15083 <p> 15084You can't assign a group to another group. It will not harm, but it 15085also won't work :-) 15086 </p> 15087 <p> 15088The order of groups is very important. <name>GoldED+</name> scans the groups from 15089the top down. This means that the most general groups must be placed 15090at the bottom and exceptions (individual areas for example) must be 15091placed at the top. 15092 </p> 15093 </div2> 15094 <div2> 15095 <head> 15096 Defining Random Items 15097 </head> 15098 <p> 15099The random items are defined much like in the main <name>GoldED+</name> 15100configuration file. 15101 </p> 15102 <p> 15103If more than one of each item is defined within a group, those items 15104will be picked randomly (hence the name "Random System"), while <name>GoldED+</name> 15105collects items when entering an area. 15106 </p> 15107 <p> 15108 Random Item Keywords: <ref target=AKA><kw/AKA/</ref>, 15109 <ref target=AKAMATCHING><kw/AKAMATCHING/</ref>, 15110 <ref target=AREACOPYADDID><kw/AREACOPYADDID/</ref>, 15111 <ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>, 15112 <ref target=AREACOPYTO><kw/AREACOPYTO/</ref>, 15113 <ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>, 15114 <ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>, 15115 <ref target=AREAFREQTO><kw/AREAFREQTO/</ref>, 15116 <ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>, 15117 <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>, 15118 <ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>, 15119 <ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>, 15120 <ref target=CTRLINFO><kw/CTRLINFO/</ref>, 15121 <ref target=EDITHARDTERM><kw/EDITHARDTERM/</ref>, 15122 <ref target=EDITMIXCASE><kw/EDITMIXCASE/</ref>, 15123 <ref target=EDITREPLYRE><kw/EDITREPLYRE/</ref>, 15124 <ref target=FORCETEMPLATE><kw/FORCETEMPLATE/</ref>, 15125 <ref target=INPUTFILE><kw/INPUTFILE/</ref>, 15126 <ref target=INTERNETADDRESS><kw/INTERNETADDRESS/</ref>, 15127 <ref target=INTERNETGATE><kw/INTERNETGATE/</ref>, 15128 <ref target=INTERNETMSGID><kw/INTERNETMSGID/</ref>, 15129 <ref target=INTERNETRFCBODY><kw/INTERNETRFCBODY/</ref>, 15130 <ref target=LOADLANGUAGE><kw/LOADLANGUAGE/</ref>, 15131 <ref target=MEMBER><kw/MEMBER/</ref>, 15132 <ref target=MSGLISTDATE><kw/MSGLISTDATE/</ref>, 15133 <ref target=MSGLISTFAST><kw/MSGLISTFAST/</ref>, 15134 <ref target=MSGLISTFIRST><kw/MSGLISTFIRST/</ref>, 15135 <ref target=MSGLISTHEADER><kw/MSGLISTHEADER/</ref>, 15136 <ref target=MSGLISTWIDESUBJ><kw/MSGLISTWIDESUBJ/</ref>, 15137 <ref target=NICKNAME><kw/NICKNAME/</ref>, 15138 <ref target=NETNAME><kw/NETNAME/</ref>, 15139 <ref target=ORGANIZATION><kw/ORGANIZATION/</ref>, 15140 <ref target=ORIGIN><kw/ORIGIN/</ref>, 15141 <ref target=OUTPUTFILE><kw/OUTPUTFILE/</ref>, 15142 <ref target=PLAY><kw/PLAY/</ref>, 15143 <ref target=QUOTEBUFFILE><kw/QUOTEBUFFILE/</ref>, 15144 <ref target=QUOTECHARS><kw/QUOTECHARS/</ref>, 15145 <ref target=QUOTECTRL><kw/QUOTECTRL/</ref>, 15146 <ref target=QUOTESTRING><kw/QUOTESTRING/</ref>, 15147 <ref target=QUOTESTOPS><kw/QUOTESTOPS/</ref>, 15148 <ref target=QUOTEWRAPHARD><kw/QUOTEWRAPHARD/</ref>, 15149 <ref target=SEARCHFOR><kw/SEARCHFOR/</ref>, 15150 <ref target=TAGLINE><kw/TAGLINE/</ref>, 15151 <ref target=TAGLINECHAR><kw/TAGLINECHAR/</ref>, 15152 <ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>, 15153 <ref target=TEARLINE><kw/TEARLINE/</ref>, 15154 <ref target=TEMPLATE><kw/TEMPLATE/</ref>, 15155 <ref target=TEMPLATEMATCH><kw/TEMPLATEMATCH/</ref>, 15156 <ref target=TWITMODE><kw/TWITMODE/</ref>, 15157 <ref target=USEAREA><kw/USEAREA/</ref>, 15158 <ref target=USEFWD><kw/USEFWD/</ref>, 15159 <ref target=USERNAME><kw/USERNAME/</ref>, 15160 <ref target=USETZUTC><kw/USETZUTC/</ref>, 15161 <ref target=VIEWHIDDEN><kw/VIEWHIDDEN/</ref>, 15162 <ref target=VIEWKLUDGE><kw/VIEWKLUDGE/</ref>, 15163 <ref target=VIEWQUOTE><kw/VIEWQUOTE/</ref>, 15164 <ref target=WHOTO><kw/WHOTO/</ref>, 15165 <ref target=WRITETEMPLATE><kw/WRITETEMPLATE/</ref>, 15166 <ref target=XLATEXPORT><kw/XLATEXPORT/</ref>, 15167 <ref target=XLATIMPORT><kw/XLATIMPORT/</ref>. 15168 </p> 15169 <p> 15170See the Configuration Keyword Reference chapter for details about each 15171keyword. 15172 </p> 15173 </div2> 15174 <div2> 15175 <head> 15176 Random System Example 15177 </head> 15178 <p> 15179Below is an example of how a Random System could be setup. Note how 15180the letter group 'D' goes first, followed by the explicit group 15181definitions for the NERDS and FOO echoes. Then comes the more general 15182groups (those with Label:'s), where the echoes are assigned with one 15183or more Member statements. At last there is the catch-all "Group *", 15184which works as the default group. 15185 </p> 15186 <p> 15187=== Cut, GOLDRAND.CFG === 15188 </p> 15189 <p> 15190Group NERDS ; For the NERDS echo. 15191 Origin "I am a Nerd. Take me to your Loser!" 15192 </p> 15193 <p> 15194Group FOO ; This group is *only* for the FOO echo. 15195 Tearline FooED @rev 15196 Origin "Foo-ing my day away" 15197 </p> 15198 <p> 15199Group FooEchoes: 15200 Member *FOO* ; Use wildcards to catch any other foo echo. 15201 Tearline FooED @rev 15202 Origin "This is a Foo-lish origin" 15203 </p> 15204 <p> 15205Group FidoNet: 15206 Member NET_DEV, WORLDPOL, INTERCOOK 15207 Member GREEN.029, C_ECHO, C_PLUSPLUS 15208 Origin "Fight-O-Net? Good name..." 15209 Template FIDONET.TPL 15210 Whoto Everyone 15211 </p> 15212 <p> 15213Group SigNet: 15214 Member SIG.* ; The wildcard is VERY handy here ;-) 15215 Origin "To SIG or not to SIG..." 15216 Template SIGNET.TPL 15217 </p> 15218 <p> 15219Group D ; Letter D for Danish echoes. 15220 Template DANSK.TPL 15221 </p> 15222 <p> 15223Group * ; This is default group 15224 Origin "Yet another forgotten echo" 15225 </p> 15226 <p> 15227=== Uncut === 15228 </p> 15229 <p> 15230See the example GOLDRAND.CFG in the ADVANCED archive for a real-life 15231setup similar to the one I use myself. 15232 </p> 15233<!-- page --> 15234<!-- --------------------------------------------------------------------- --> 15235 </div2> 15236 </div1> 15237 <div1 id=COLORCONFIG> 15238 <head> 15239 The Color Configuration 15240 </head> 15241 <p> 15242Color configuration in <name>GoldED+</name> is a bit complicated, and you probably 15243have to experiment quite a bit, if you want make your own setup. For 15244your convenience, I have added a number of example color setups, 15245provided by some of my many good users. I suggest you try them all and 15246use the one that suits you best, perhaps tuning it a bit to your 15247taste. 15248 </p> 15249 <p> 15250The COLOR keyword uses the following syntax: 15251 </p> 15252 <div2> 15253 <head> 15254 COLOR <window> <part> <colors> 15255 </head> 15256 <p> 15257 <window> AREA, ASK, BACKGROUND, BRAG, HEADER, HELP, INFO, MENU, 15258 READER, SHADOW, STATUS. 15259 </p> 15260 <p> 15261 <part> BLOCK, BORDER, BTYPE, EDIT, HIDDEN, HIGHLIGHT, INPUT, 15262 KLUDGE, NOSELECT, ORIGIN, QUOTE, SELECTOR, TEARLINE, 15263 TITLE, WINDOW. 15264 </p> 15265 <p> 15266The <colors> are composed of [blinking] <ink> [on <paper>]. 15267 </p> 15268 <p> 15269 <ink> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey, 15270 DGrey, LBlue, LGreen, LCyan, LRed, LMagenta, Yellow, 15271 White. 15272 </p> 15273 <p> 15274 <paper> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey. 15275 </p> 15276 <p> 15277For monochrome setups we instead have: 15278 </p> 15279 <p> 15280 <ink> Normal, Highlight, Reverse, Underline. 15281 </p> 15282 <p> 15283The SHADOW color does not need a <part>, because it is global. 15284 </p> 15285 <p> 15286The paper color always defaults to Black if not specified. 15287 </p> 15288 <p> 15289If <part> is "BTYPE", the <color> is a value in the range 0-3, which 15290defines the type of lines used when drawing menus and windows: 15291 </p> 15292 <p> 15293BTYPE 0 is single horizontal and single vertical lines. 15294BTYPE 1 is double horizontal and double vertical lines. 15295BTYPE 2 is single horizontal and double vertical lines. 15296BTYPE 3 is double horizontal and single vertical lines. 15297 </p> 15298 <p> 15299The default border type is always BTYPE 0. 15300 </p> 15301 <p> 15302The following is a description of the different window parts: 15303 </p> 15304 </div2> 15305 <div2> 15306 <head> 15307 Various general color items 15308 </head> 15309 <p> 15310 SHADOW Shadow below windows and menus. 15311 STATUS WINDOW Status line at the bottom. 15312 BACKGROUND WINDOW Background for the startup window. 15313 BACKGROUND BORDER Overscan color (currently DOS only). 15314 </p> 15315 <p> 15316 <anything> PAGEBAR Pagebar (scrollbar). 15317 </p> 15318 <p> 15319 The PAGEBAR color specifially sets the color of the pagebars 15320 (scrollbars) in <name>GoldED+</name>. A pagebar color can currently be set for 15321 AREA, READER and MENU. Note that BORDER will set both the BORDER and 15322 PAGEBAR colors, so remember to place the PAGEBAR color below the 15323 BORDER color. 15324 </p> 15325 </div2> 15326 <div2> 15327 <head> 15328 Startup screen / logo window 15329 </head> 15330 <p> 15331 BRAG WINDOW The Copyright window. 15332 BRAG BORDER Lines around the Copyright window. 15333 BRAG TITLE The logo text. 15334 BRAG HIGHLIGHT The inner logo lines. 15335 BRAG BLOCK The outer logo lines. 15336 BRAG BTYPE Copyright window border type. 15337 </p> 15338 </div2> 15339 <div2> 15340 <head> 15341 Area Selection Menu 15342 </head> 15343 <p> 15344 AREA WINDOW Descriptions, the top line (inc. search). 15345 AREA BORDER Lines. 15346 AREA TITLE Titles on the border. 15347 AREA SELECTOR Selection bar. 15348 AREA HIGHLIGHT The color for the area marks. 15349 AREA BTYPE Window border type. 15350 </p> 15351 </div2> 15352 <div2> 15353 <head> 15354 Message Header 15355 </head> 15356 <p> 15357 HEADER WINDOW Header text. 15358 HEADER BORDER Lines. 15359 HEADER TITLE Titles on the border. 15360 HEADER INPUT Message number input field. 15361 HEADER EDIT Header input fields. 15362 HEADER HIGHLIGHT Marks. 15363 HEADER BTYPE Window border type. 15364 HEADER FROM Header From field. 15365 HEADER TO Header To field. 15366 HEADER SUBJECT Header Subject field. 15367 </p> 15368 <p> 15369 The FROM/TO/SUBJECT colors supplement the HEADER WINDOW color. Note 15370 that WINDOW will also set the FROM/TO/SUBJECT colors, so remember to 15371 place the new colors below it. 15372 </p> 15373 </div2> 15374 <div2> 15375 <head> 15376 Message Text 15377 </head> 15378 <p> 15379 READER WINDOW Normal message text. 15380 READER BORDER The Pagebar. 15381 READER QUOTE (Odd) Quoted lines. 15382 READER QUOTE2 (Even) Quoted lines. 15383 READER CURSOR Character at cursor pos. (int. editor). 15384 READER KLUDHIDD Kludges and hidden lines. 15385 READER TEARORIG Tearline and Origin. 15386 READER BLOCK Block color (internal editor). 15387 READER BTYPE Window border type. 15388 READER HIGHLIGHT Search highlight in the message text. 15389 READER KLUDGE Known kludges. 15390 READER HIDDEN Hidden lines. (Unknown kludges). 15391 READER SIGNATURE Internet-Style signatures ("-- "). 15392 READER TAGLINE Taglines. (Only the one just above tearline). 15393 READER TEARLINE Tearline. 15394 READER ORIGIN Origin. 15395 </p> 15396 <p> 15397 The KLUDGE/HIDDEN colors replaces the old KLUDHIDD color. Note that 15398 KLUDHIDD will set both the KLUDGE and HIDDEN colors, so remember to 15399 place the new colors below it if you keep the old definition. 15400 </p> 15401 <p> 15402 The TAGLINE color is the color of taglines. <name>GoldED+</name> detects a tagline 15403 if it starts with "..." or "___" and is just above the tearline or 15404 origin. 15405 </p> 15406 <p> 15407 The TEARLINE/ORIGIN colors replaces the old TEARORIG color. Note 15408 that TEARORIG will set both the TEARLINE and ORIGIN colors, so 15409 remember to place the new colors below it if you keep the old 15410 definition. 15411 </p> 15412 </div2> 15413 <div2> 15414 <head> 15415 Miscellaneous Smaller Menus 15416 </head> 15417 <p> 15418 ASK WINDOW Menu items. 15419 ASK BORDER Lines. 15420 ASK TITLE Menu title. 15421 ASK SELECTOR Selection bar. 15422 ASK NOSELECT Non-selectable menu items. 15423 ASK HIGHLIGHT Hotkeys. 15424 ASK BTYPE Window border type. 15425 </p> 15426 </div2> 15427 <div2> 15428 <head> 15429 Miscellaneous Larger Menus (Browser Windows) 15430 </head> 15431 <p> 15432 MENU WINDOW Menu items. 15433 MENU BORDER Lines. 15434 MENU TITLE Menu title. 15435 MENU SELECTOR Selection bar. 15436 MENU NOSELECT Non-selectable menu items. 15437 MENU HIGHLIGHT Hotkeys/marks. 15438 MENU UNREAD When a msg is unread. 15439 MENU UNREADHIGH Additional highlight of to/from. 15440 MENU UNSENT When a msg is unsent. 15441 MENU UNSENTHIGH Additional highlight of to/from. 15442 </p> 15443 </div2> 15444 <div2> 15445 <head> 15446 Help Screens 15447 </head> 15448 <p> 15449 HELP WINDOW Help text. 15450 HELP BORDER Lines. 15451 HELP SELECTOR Current keyword. 15452 HELP HIGHLIGHT Other keywords. 15453 HELP BTYPE Window border type. 15454 </p> 15455 </div2> 15456 <div2> 15457 <head> 15458 Pop Up Information Windows 15459 </head> 15460 <p> 15461 INFO WINDOW Window text. 15462 INFO BORDER Lines. 15463 INFO TITLE Info title. 15464 INFO BTYPE Window border type. 15465 </p> 15466 </div2> 15467 <div2> 15468 <head> 15469 Stylecodes 15470 </head> 15471 <p> 15472 STYLECODE ALL All stylecodes at once. 15473 STYLECODE B *Bold* 15474 STYLECODE I /Italic/ 15475 STYLECODE BI /*BoldItalic*/ 15476 STYLECODE U _Underline_ 15477 STYLECODE BU _*BoldUnderline*_ 15478 STYLECODE IU /_ItalicUnderline_/ 15479 STYLECODE BIU _/*BoldItalicUnderline*/_ 15480 STYLECODE R #Reverse# 15481 STYLECODE RB *#ReverseBold#* 15482 STYLECODE RI /#ReverseItalic#/ 15483 STYLECODE RBI /*#ReverseBoldItalic#*/ 15484 STYLECODE RU _#ReverseUnderline_# 15485 STYLECODE RBU _*#ReverseBoldUnderline#*_ 15486 STYLECODE RIU _/#ReverseItalicUnderline#/_ 15487 STYLECODE RBIU _/*#ReverseItalicUnderline#*/_ 15488 </p> 15489 <p> 15490 Note that stylecode color definitions must be placed below COLOR 15491 READER WINDOW, because it overrides the COLOR STYLECODE definitions. 15492 </p> 15493 <p> 15494See the GEDCOL*.CFG and GEDMON*.CFG files for examples of color 15495configuration. 15496 </p> 15497<!-- page --> 15498<!-- --------------------------------------------------------------------- --> 15499 </div2> 15500 </div1> 15501 <div1 id=MESSAGETEMPLATE> 15502 <head> 15503 The Message Template 15504 </head> 15505 <p> 15506The message template gives you a ready-made skeleton for writing your 15507messages in the editor. The template is one of <name>GoldED+</name>'s many strong 15508features. With this, you can eliminate the tedious typing of greetings 15509etc etc. <name>GoldED+</name> also provides a number of replacement strings, 15510"tokens", to dynamically add message specific information to the 15511template. 15512 </p> 15513 <p> 15514As in the configuration file, a semicolon (;) first on the line makes 15515the line a comment. Any other line is put into the editor file, after 15516token expansion. Tokens are not case sensitive. 15517 </p> 15518 <p> 15519The following is a list of the tokens available: 15520 </p> 15521 <div2> 15522 <head> 15523 Conditional tokens 15524 </head> 15525 <p> 15526 (these are replaced with a null string) 15527 </p> 15528 <p> 15529@changed Line is only inserted in Changed msgs (from others). 15530@comment Line is only inserted in Reply-Comments. 15531@echo Line is only inserted in Echomail. 15532@forward Line is only inserted in Forwarded messages. 15533@local Line is only inserted in Local messages. 15534@moderator Line is only inserted if substring "moderator" appeared in 15535 from line. 15536@moved Line is only inserted in Reply-Moved messages. 15537@net Line is only inserted in Netmail. 15538@new Line is only inserted in New messages (not replies). 15539@position Specifies the starting line for the editor cursor. 15540@quotebuf Line is only inserted in Quotebuffered msgs. 15541@quoted Line is only inserted in Quoted replies. 15542@reply Line is only inserted in Non-Quoted Replies. 15543 </p> 15544 </div2> 15545 <div2> 15546 <head> 15547 Insert tokens 15548 </head> 15549 <p> 15550 (anything else on the line is ignored) 15551 </p> 15552 <p> 15553@attrib <attributes> - Adds specific message attributes. 15554@include <filename> - Inserts the file. 15555@forcefrom <"from"> - sets message FROM: field, even if non-empty 15556 (see @setfrom) 15557@forcesubj <"subject"> - sets message SUBJ: field, even if non-empty 15558 (see @setsubj) 15559@forceto <"to"> - sets message TO: field, even if non-empty 15560 (see @setto) 15561@loadlanguage Loads a partial language config file. 15562@message Inserts the original message (in Forward & Change). 15563@quote Inserts a quote of the original message. 15564@random [random.txt] - Inserts random text. 15565@setfrom <"from"> - Sets the message FROM: field. 15566@setsubj <"subject"> - Sets the message SUBJ: field. 15567@setto <"to"> - Sets the message TO: field. 15568@xlatexport <charset> - Sets the export charset. 15569 </p> 15570 </div2> 15571 <div2> 15572 <head> 15573 Replacement tokens 15574 </head> 15575 <p> 15576 (replaced with message specific data): 15577 </p> 15578 <p> 15579@c3daddr Current user 3D (boss) address. 15580@caddr Current user address. 15581@cdate Current date. 15582@cdesc Current area description. 15583@cecho Current echoid. 15584@cfname Current user first name. 15585@clname Current user last name. 15586@cname Current user name. 15587@cpseudo Current pseudonym given by NICKNAME keyword, or @cfname. 15588@ctime Current time. 15589@ctzoffset Current timezone offset (if available and enabled). 15590@d3daddr Destination 3D (boss) address. 15591@daddr Destination address. 15592@dfname Destination first name. 15593@dlname Destination last name. 15594@dname Destination name. 15595@dpseudo Destination pseudonym (see addressbook), or @dfname. 15596@f3daddr Current from 3D (boss) address. 15597@faddr Current from address. 15598@ffname Current from first name. 15599@flname Current from last name. 15600@fname Current from name. 15601@fpseudo Current from pseudonym (see addressbook), or @ffname. 15602@longpid Long program id. "GoldED", "GoldED/2" or "GoldED/386". 15603@o3daddr Original 3D (boss) address. 15604@oaddr Original address. 15605@odate Original date. 15606@odesc Original area description if moved, else current. 15607@oecho Original echoid if moved, otherwise current. 15608@ofname Original first name. 15609@ofrom Original RFC "From" headerline. 15610@olname Original last name. 15611@omessageid Original RFC "Message-ID" headerline. 15612@omsgid Original MSGID kludge content. 15613@oname Original name. 15614@opseudo Original pseudonym (see addressbook), or @ofname. 15615@origin The current global or Random System origin. 15616@os2slash "/2" if running <name>GoldED+</name>/2. Empty otherwise. 15617@osslash same as above. 15618@otime Original time. 15619@otzoffset Original timezone offset (if available and enabled). 15620@oto Original RFC "To" headerline. 15621@pid Short program id. "GED", "GED/2" or "GED386". 15622@pseudo pseudonym (see addressbook), or @tfname. 15623@rev The revision number (in the form mmdd). 15624@serialno Emptiness. 15625@subject The message subject line. 15626@t3daddr Destination to 3D (boss) address. 15627@taddr Destination to address. 15628@tagline The current global or Random System tagline. 15629@tearline The current global or Random System tearline. 15630@tfname Destination to first name. 15631@tlname Destination to last name. 15632@tname Destination to name. 15633@tpseudo Destination to pseudonym (see addressbook), or @tfname. 15634@ver The simple version number (in the form x.yy) 15635@version The complete release version number of <name>GoldED+</name>. 15636@_caddr Current user address (fixed width: 19 chars). 15637@_cname Current user name (fixed width: 34 chars). 15638@_daddr Destination address (fixed width: 19 chars). 15639@_dname Destination name (fixed width: 34 chars). 15640@_oaddr Original address (fixed width: 19 chars). 15641@_oname Original name (fixed width: 34 chars). 15642@_taddr Destination to address (fixed width: 19 chars). 15643@_tname Destination to name (fixed width: 34 chars). 15644 </p> 15645 <p> 15646Tokens dealing with names may optionally have two parameters (each 15647parameter enclosed in curve brackets): your name and opponent name, 15648destination name additionally accepts third parameter - WhoTo name. 15649Here is example on how this feature could be used: 15650 </p> 15651 <p> 15652 @oname{I}{You} wrote to @dname{me}{you}{everyone}: 15653 </p> 15654 <p> 15655The template text begins at the first non-comment line. 15656 </p> 15657 <p> 15658See the included GOLDED.TPL for example usage. 15659 </p> 15660 <p> 15661If you need to put some text which contains one of these tokens into a 15662template file, use an extra '@' in front of the token. 15663 </p> 15664 <p> 15665Example: 15666 </p> 15667 <p> 15668 Internet: somebody@veryhot.com 15669 </p> 15670 <p> 15671would produce 15672 </p> 15673 <p> 15674 Internet: somebody2.51yhot.com (because @ver is a token) 15675 </p> 15676 <p> 15677so write it like this instead: 15678 </p> 15679 <p> 15680 Internet: somebody@@veryhot.com 15681 </p> 15682 <p> 15683The double '@' will then be translated to a single, and token 15684translation skips past the @token. 15685 </p> 15686<!-- page --> 15687<!-- --------------------------------------------------------------------- --> 15688 </div2> 15689 </div1> 15690 <div1> 15691 <head> 15692 The Online Help System 15693 </head> 15694 <p> 15695GoldED has a built-in context sensitive help system, tied to the <F1> 15696key (one of the very few keys that cannot be reconfigured). It 15697contains a complete keyboard reference and help for most situations. 15698It is current not as complete or sophisticated as I'd like it myself, 15699but this may be improved in future versions. 15700 </p> 15701 <p> 15702You can completely redefine the help screens if you wish - the 15703GOLDHELP.CFG file is a plain ASCII text file which contains all help 15704definitions. The help file is split into several help categories. Here 15705is an example of a couple of defined help categories: 15706 </p> 15707 <p> 15708 *B 1,Help Category 1 15709 help text help text help text 15710 help text help text help text 15711 *P 15712 help text help text help text 15713 help text help text help text 15714 *E 15715 </p> 15716 <p> 15717 *B 2,Help Category 2 15718 help text help text help text 15719 help text help text help text 15720 *P 15721 help text help text help text 15722 help text help text help text 15723 See also: ^Help Category 1^ 15724 *E 15725 </p> 15726 <p> 15727The "*B" indicator specifies the beginning of a help category. The 15728format is "*B helpcatnumber[,helpcatname]". In <name>GoldED+</name> the help 15729categories are numbered 1000-9999, split into more or less logical 15730groups. See the help file for assignments. There should be only one 15731space between the "*B" and the help category number. The help category 15732name is only required for cross-references. If there are no 15733cross-references to that help category, then you can leave the 15734helpcatname parameter out. 15735 </p> 15736 <p> 15737The "*P" indicator specifies a page break and is optional. You may 15738have as many page breaks as you'd like. The "*E" indicator specifies 15739the end of the help category. The "*B", "*P", and "*E" indicators must 15740all begin in the first column. These indicators and the help category 15741name are case insensitive (can be in lowercase, uppercase, or mixed). 15742 </p> 15743 <p> 15744In the definition of Help Category 2, you will notice the 15745crossreference to Help Category 1. All cross-referencing is done by 15746embedding the cross- reference category name (not number) inside 15747carats (^). If you need to display a carat inside the help file, use a 15748double carat (^^). 15749 </p> 15750 <p> 15751Any text contained outside of the "*B" and "*E" is treated as 15752comments. If an "*E" is not found, then the end-of-file will be 15753treated as an "*E". 15754 </p> 15755 <p> 15756Not all of the help categories in this help file are actually used in 15757the current version of <name>GoldED+</name>. The ones not used are empty, except for 15758a two-line "header". 15759 </p> 15760 <p> 15761The usable dimensions of the help window are 60 columns by 16 lines. 15762In the help file there is a model of the actual window. 15763 </p> 15764<!-- page --> 15765<!-- --------------------------------------------------------------------- --> 15766 </div1> 15767 <div1> 15768 <head> 15769 Character Translation 15770 </head> 15771 <p> 15772GoldED implements several different proposals for character 15773translation in imported and exported messages: 15774 </p> 15775 <div2> 15776 <head> 15777 FSC-0050 "Charset Identifier" 15778 </head> 15779 <p> 15780 by Thomas Sundblom. 15781 </div2> 15782 <div2> 15783 <head> 15784 FSC-0051 "I51" 15785 </head> 15786 <p> 15787 by Thomas Gradin. 15788 </div2> 15789 <div2> 15790 <head> 15791 FSC-0054 "CHARSET proposal" 15792 </head> 15793 <p> 15794 by Duncan McNutt. 15795 </div2> 15796 <div2> 15797 <head> 15798 No FSC "Composed Characters" 15799 </head> 15800 <p> 15801 by Andre van de Wijdeven. 15802 </p> 15803 <p> 15804FSC-0050 is currently known to be implemented in the OPMED 3.xx 15805message editor, and in Opus 1.7x. It uses the same identifier as 15806FSC-0054 (a ^aCHARSET kludge), but is a lot simpler (but not 15807necessarily better). 15808 </p> 15809 <p> 15810The "I51" and "CHARSET" proposals are in the process of being merged 15811to one proposal, which should combine the advantages of both. They are 15812both based on using the LATIN-1 (also known as ISO 8859-1) character 15813set for extended ASCII. The LATIN-1 set is the same set used by 15814Windows 3.xx, Amiga and many other non-PC computers. In addition to 15815LATIN-1, I51 defines a set of so-called escape sequences for 15816characters not found in the LATIN-1 set. 15817 </p> 15818 <p> 15819"Composed Characters" became quite popular in Holland, but the author 15820decided to drop his proposal because it relied on escape sequences 15821using the so called "soft-cr" (141d, 8Dh) character. <name>GoldED+</name> will 15822continue to support Composed as long as it seems necessary. 15823 </p> 15824 <p> 15825If you want to know more about the details, I suggest you read the 15826proposals or contact the authors. 15827 </p> 15828 <p> 15829GoldED currently supports two types of translation tables, the *.ESC 15830files and the *.CHS files. 15831 </p> 15832 </div2> 15833 <div2> 15834 <head> 15835 The ESC translation tables 15836 </head> 15837 <p> 15838The *.ESC files are used for import translation of the escape 15839sequences defined in I51 and Composed Characters. 15840 </p> 15841 <p> 15842In the ESC files, the semicolon is used for comments. The *first* 15843non-comment line defines the charset the escape code are mapped TO. 15844This is normally IBMPC, and should not be changed. Any other 15845non-comment line is treated as an escape sequence definition with this 15846syntax: 15847 </p> 15848 <p> 15849 <esc1><esc2><space><map chars>[; comment/description] 15850 </p> 15851 <p> 15852Leading spaces are *not* allowed in ESC files. <esc1> and <esc2> are 15853the two characters that define the escape sequence. <space> is ignored 15854and can be used to make the table look better. <map chars> defines the 15855local representation of the escape sequence, up to three characters. 15856Normally you would only map to one extended ascii character. The map 15857chars can be either the characters themselves, or decimal or 15858hexadecimal numbers of the form "\d<dec>" or "\x<hex>" (like in the C 15859programming language). 15860 </p> 15861 </div2> 15862 <div2> 15863 <head> 15864 The CHS translation tables 15865 </head> 15866 <p> 15867The *.CHS files are used for import and export translation of the 15868CHARSET type character sets, and export of I51 and Composed escape 15869sequences. 15870 </p> 15871 <p> 15872The CHS files uses the format of the raw text files provided in the 15873CHARSET3.ZIP example implementation of FSC-0054. Study some of the 15874files provided if you want to know how to define them. 15875 </p> 15876 <p> 15877The two keywords XLATESCSET and XLATCHARSET are used to define which 15878files belong to what import and export set. You can define more than 15879one import and export set for each file. 15880 </p> 15881 <p> 15882The keyword XLATIMPORT defines which charset you have on your own 15883machine - this would normally be "IBMPC". It can be useful to change 15884this (using the Random System) in areas where another character set 15885than IBMPC is the dominant (like Amiga or MacIntosh, whatever). 15886 </p> 15887 <p> 15888The keyword XLATEXPORT defines the charset your messages should be 15889exported to, if any. 15890 </p> 15891 <p> 15892Confused? Yeah, I know - this is a confusing subject, and my 15893implementation and documentation is not perfect. Normally you will not 15894have to worry about it. Turn it off completely if you don't understand 15895it. 15896 </p> 15897<!-- page --> 15898<!-- --------------------------------------------------------------------- --> 15899 </div2> 15900 </div1> 15901 <div1> 15902 <head> 15903 Keyboard Command Reference 15904 </head> 15905 <p> 15906Most of the <name>GoldED+</name> keyboard commands can be reached with just one 15907keystroke. To ease operation for experienced users of other message 15908editors, <name>GoldED+</name> comes with several sets of keys for each of the 15909keyboard commands - direct non-shifted keys, Alt/Ctrl-keys and 15910function keys. Many of these key assignments will be familiar for 15911users of Msged, Msged/Q, ME2 and FM. 15912 </p> 15913 <p> 15914The following is a list of all keyboard commands, sorted by type and 15915alphabetically, using the format 15916 </p> 15917 <p> 15918 <command> <short description> 15919 </p> 15920 <p> 15921This list is also available in the context-sensitive help system on 15922the <F1> key. 15923 </p> 15924 <p> 15925It is possible to almost completely redefine the keyboard - this in 15926done in the GOLDKEYS.CFG file, which also handles macro definition 15927(see later). 15928 </p> 15929 <div2> 15930 <head> 15931 Arealist Commands 15932 </head> 15933 <p> 15934AREAabort Abort the arealist. 15935AREAaskexit Exit <name>GoldED+</name>, prompt for final decision. 15936AREAboardnos Toggle sequential areas vs. board numbers. 15937AREAcatchup Point the lastread pointer to the last message 15938 in the current area. 15939AREAdosshell Shell to DOS. 15940AREAdropmsgmarks Unmark all msgs in selected areas. 15941AREAgotofirst Move selection bar to first area. 15942AREAgotolast Move selection bar to last area. 15943AREAgotonext Move selection bar to next area. 15944AREAgotoprev Move selection bar to previous area. 15945AREAheat Heat highwatermarks. 15946AREAjump Move selection bar to next marked area. 15947AREAjumpnextmatch Move selection bar to next matching area. 15948AREAquitnow Exit immediately, no questions asked. 15949AREAscan Scan areas. 15950AREAscanpm Scan areas for personal mail. 15951AREAselect Enter the reader for the selected area. 15952AREAselectmarks Select which set of area marks should be used. 15953AREAsoundkill Stops currently played sound file. 15954AREAtoggle Toggle mark on the selected area. 15955AREAtouchnetscan Touches the SEMAPHORE NETSCAN file. 15956AREAwritegoldlast Write a fresh copy of GOLDLAST.LST 15957AREAzap Zap highwatermarks. 15958 </p> 15959 </div2> 15960 <div2> 15961 <head> 15962 Internal Editor Commands 15963 </head> 15964 <p> 15965EDITabort Abort editing this message - ask first. 15966EDITanchor Set a block "anchor" on the current line. 15967EDITaskexit Exit from <name>GoldED+</name> - ask first. 15968EDITblockdown Extend block area one line down. 15969EDITblockend Extend block area to the end of line. 15970EDITblockhome Extend block area to the beginning of line. 15971EDITblockleft Extend block area one character left. 15972EDITblockpgup Extend block area one screen up. 15973EDITblockpgdn Extend block area one screen down. 15974EDITblockright Extend block area one character right. 15975EDITblockup Extend block area one line up. 15976EDITcleardeletebuf Clears the undelete buffer. 15977EDITclearpastebuf Clears the cut'n'paste buffer. 15978EDITcopy Copies the block to the cut'n'paste buffer. 15979EDITcopyabovechar Inserts character same as in the same position 15980 in previous line. 15981EDITcut Cut the block to the cut'n'paste buffer. 15982EDITdelchar Delete the char at the cursor position. 15983EDITdelete Delete the block. 15984EDITdeleteeol Delete from cursor position to end of line. 15985EDITdelleft Delete the char to the left of the cursor. 15986EDITdelline Delete the current line. (Copied to the 15987EDITdelltword Delete the word to the left of the cursor. 15988EDITdelrtword Delete the word to the right of the cursor. 15989EDITdosshell Shell to DOS. 15990EDITdupline Duplicates the current line. 15991EDITexitmsg Drop this message - NO ASKING! DANGEROUS! 15992EDITexporttext Exports the current block to a file. 15993EDITgobegline Move cursor to beginning of line. 15994EDITgobotline Move cursor to the bottom line in the display. 15995EDITgobotmsg Move cursor to the last line in the message. 15996EDITgodown Move cursor down to next line. 15997EDITgoeol Move cursor to the end of the line. 15998EDITgoleft Move cursor one position left. 15999EDITgopgdn Move cursor one page of lines down. 16000EDITgopgup Move cursor one page of lines up. 16001EDITgoright Move cursor one position right. 16002EDITgotopline Move cursor to the top line in the display. 16003EDITgotopmsg Move cursor to the first line in the message. 16004EDITgoup Move cursor up to the previous line. 16005EDITgowordleft Move cursor to the previous word. 16006EDITgowordright Move cursor to the next word. 16007EDITheader Edit the message header, attributes etc. 16008EDITimportquotebuf Imports the current quote buffer. 16009EDITimporttext Import text file into this message. 16010EDITkillquotes (ignored) 16011EDITloadfile Load the message file saved with EDITsavefile. 16012EDITlookupcursor Lookup name/node at cursor position. 16013EDITlookupdest Lookup TO: node. 16014EDITlookuporig Lookup FROM: node. 16015EDITnewline Terminate paragraph and/or add a new line. 16016EDITpaste Paste a previously cut block at the cursor. 16017EDITquitnow Quit <name>GoldED+</name> immediately - no asking. 16018EDITreflow Reflows the current text or quote paragraph. 16019EDITsavefile Saves the current message as a file. 16020EDITsavemsg Save this message. 16021EDITsoundkill Stops currently played sound flie. 16022EDITspellcheck Calls an external spell checker for the msg. 16023EDITtab Add spaces to the next tab-stop. 16024EDITtabreverse Remove spaces to the prev tab-stop. 16025EDITtogglecase Toggle the case of the cursor character. 16026EDITtoggleinsert Toggle insert mode. 16027EDITtolower Change the cursor character to lowercase. 16028EDITtoupper Change the cursor character to uppercase. 16029EDITundelete Undelete previously deleted lines. 16030EDITzapquotebelow Deletes quotes below. 16031 </p> 16032 </div2> 16033 <div2 id=FILESELECTION> 16034 <head> 16035 File Selection Commands 16036 </head> 16037 <p> 16038FILEabort Abort file selection. 16039FILEaskexit Exit <name>GoldED+</name> - ask first. 16040FILEdosshell Shell to DOS. 16041FILEgotofirst Go to first file. 16042FILEgotolast Go to last file. 16043FILEgotonext Go to next file. 16044FILEgotoprev Go to previous file. 16045FILEmark Mark file. 16046FILEmarkall Mark all files. 16047FILEquitnow Quit <name>GoldED+</name> immediately. 16048FILEselect Select the marked file(s). 16049FILEtogglemark Toggle file mark. 16050FILEunmark Unmark file. 16051FILEunmarkall Unmark all files. 16052 </p> 16053 </div2> 16054 <div2> 16055 <head> 16056 Message Lister Commands 16057 </head> 16058 <p> 16059LISTabort Abort message lister. 16060LISTaskexit Exit <name>GoldED+</name> - ask first. 16061LISTdosshell Shell to DOS. 16062LISTgotobookmark Go to BookMark message. 16063LISTgotofirst Go to first message. 16064LISTgotolast Go to last message. 16065LISTgotonext Go to next message. 16066LISTgotoprev Go to previous message. 16067LISTmarkingoptions Marking menu. 16068LISTquitnow Quit <name>GoldED+</name> immediately. 16069LISTselect Go to reader at the selected message. 16070LISTtogglebookmark Toggle BookMark on the selected message. 16071LISTtoggledate Toggle date column content. 16072LISTtogglemark Toggle Mark on the selected message. 16073LISTtogglewidesubj Toggle between wide and short subject. 16074 </p> 16075 </div2> 16076 <div2> 16077 <head> 16078 Nodelist Browser Commands 16079 </head> 16080 <p> 16081NODEabort Abort nodelist browsing. 16082NODEaskexit Exit <name>GoldED+</name> - ask first. 16083NODEdosshell Shell to DOS. 16084NODEgotofirst Go to first node. 16085NODEgotolast Go to last node. 16086NODEgotonext Go to next node. 16087NODEgotoprev Go to previous node. 16088NODEquitnow Quit <name>GoldED+</name> immediately. 16089NODEselect Select node. 16090 </p> 16091 </div2> 16092 <div2> 16093 <head> 16094 Message Reader Commands 16095 </head> 16096 <p> 16097READaddressbookadd Add current/marked mail writer(s) to 16098 addressbook. Ask first. 16099READaskexit Exit <name>GoldED+</name>, prompt for final decision. 16100READchangeaka Change default AKA address for current area. 16101READchangeattrs Change the attributes of the current message. 16102READchangemsg Change current message. 16103READchangeorigin Change default origin for the current area. 16104READchangetagline Change default tagline. 16105READchangetemplate Change default template. 16106READchangeusername Change default username. 16107READchangexlatimport Change default import charset. 16108READcommentmsg Comment-Reply to message. (Reply to TO name). 16109READcopymoveforward Enter the Copy/Move/Forward function menu. 16110READdecreasemargin Decrease message margin. For test purposes. 16111READdeletemsg Delete current/marked message(s). Ask first. 16112READdosshell Shell to DOS. 16113READfidorenumber Renumber Fido/Opus *.MSG files. 16114READfilerequest Generate a filerequest from the current msg. 16115READfindall Find string(s) in message header and text. 16116READfindheader Find string(s) in message header. 16117READgotobookmark Go to the "BookMark" message. 16118READgotofirstmsg Go to the first message in the area. 16119READgotolastmsg Go to the last message in the area. 16120READgotomsgno Go to a specific message number. 16121READgotonextarea Go directly to the next area. 16122READgotonextmsg Go to the next message. 16123READgotonextunread Go to the next unread message. 16124READgotoprevarea Go directly to the previous area. 16125READgotoprevmsg Go to the previous message. 16126READgotoprevunread Go to the previous unread message. 16127READgotoreplies Choose from the next messages in the replylink. 16128READgotoreply1st Go to the first reply to this message. 16129READgotoreplynext Go to the next reply to this message. 16130READgotoreplyprev Go to the parent message in the replylink. 16131READincreasemargin Increase message margin. For test purposes. 16132READlookupdest Lookup TO: node. 16133READlookuporig Lookup FROM: node. 16134READmakeuserlist Generate FIDOUSER.LST of users in the area. 16135READmakepathreport Added "path report" feature. The output file 16136 can be processed by a RDDT (Route Diagram 16137 Drawing Tool) utility. 16138READmarkingoptions Enter the marking menu. 16139READmessagelist Enter the message lister. 16140READmovecommentmsg Comment-Reply in another area. 16141READmovequotemsg Quote-Reply in another area. 16142READmsgcontinue Page down or go to next message. 16143READmsgend Display last part of current message. 16144READmsghome Display first part of current message. 16145READmsglinedown Scroll message display. 16146READmsglineup Scroll message display. 16147READmsgpgdn Page message display. 16148READmsgpgup Page message display. 16149READnewarea Enter the area selection screen. 16150READnewmsg Start a new message. 16151READquitnow Exit <name>GoldED+</name> immediately, no questions asked. 16152READquotebuf Append quote of the msg to the quotebuffer. 16153READquotemsg Quote-Reply to message. (Reply to FROM name). 16154READreplymsg Reply to the current message, without quoting. 16155READsearch Launches the search engine. 16156READsoundkill Stops currently played sound file. 16157READthreadtree Enter the Message Threading lister. 16158READtogglebookmark Toggle a "BookMark" on the current message. 16159READtogglehexdump Toggle hexdump mode. For debugging purposes. 16160READtogglehiddklud Toggle display of Hidden and Kludge lines. 16161READtogglehidden Toggle display of Hidden lines. 16162READtogglekludge Toggle display of Kludge lines. 16163READtogglemark Toggle a message mark on the current message. 16164READtogglemarkread Toggle "Read Marked" mode. 16165READtogglepagebar Toggle the "PageBar" feature. 16166READtogglequote Toggle display of quoted lines. Experimental. 16167READtogglerot13 Toggle ROT13 encryption for the current msg. 16168READtogglerealmsgno Toggle between seq. or real message numbers. 16169READtogglestyles Toggle Disable/Show/Show+Strip of STYLECODES. 16170READtoggletwits Toggle Twit display - Show/Blank/Skip/Ignore. 16171READtouchnetscan Touches the SEMAPHORE NETSCAN file. 16172READtouchsemaphore Popup touch a manually entered semaphore file. 16173READuserbase Launches the addressbook. 16174READuudecode UUdecodes the current message. 16175READwritemsg Write message(s) to file or printer. 16176 </p> 16177 </div2> 16178 <div2> 16179 <head> 16180 Key Undefine Commands 16181 </head> 16182 <p> 16183AREAundefine 16184EDITundefine 16185FILEundefine 16186LISTundefine 16187NODEundefine 16188READundefine 16189 </p> 16190 <p> 16191The undefine commands can used to undefine any of the built-in default 16192keyboard definitions. 16193 </p> 16194 <p> 16195See the Key Reference below for a list of the key symbols you can use 16196in keyboard redefinition. 16197 </p> 16198<!-- page --> 16199<!-- --------------------------------------------------------------------- --> 16200 </div2> 16201 </div1> 16202<div1 id=MACROSANDKEYSTACKING><head>Macros and Keystacking</head> 16203 <p> 16204GoldED has a simple keyboard macro facility, which you can use to 16205automate certain common operations. In addition, a "keystacking" 16206facility allows you to create simple automatic macros on the fly. 16207 </p> 16208 <p> 16209The macro definition syntax is modelled after the syntax used in the 16210QEdit text editor: 16211 </p> 16212 <p> 16213 <assignment-key> Macro <commands or keys> 16214 <assignment-key> AreaMacro <commands or keys> 16215 <assignment-key> EditMacro <commands or keys> 16216 <assignment-key> FileMacro <commands or keys> 16217 <assignment-key> ListMacro <commands or keys> 16218 <assignment-key> NodeMacro <commands or keys> 16219 <assignment-key> ReadMacro <commands or keys> 16220 </p> 16221 <p> 16222Macros are defined in the GOLDKEYS.CFG file, where you can also find 16223several examples. 16224 </p> 16225 <p> 16226By using the word "Auto" as <assignment-key>, you can even define a 16227special macro which will be automatically executed when you start 16228GoldED. 16229 </p> 16230 <p> 16231Keystacking is a special form of auto-macros. You simply specify a 16232bunch of keys to be "stacked" in the (special internal) keyboard 16233buffer for sequential execution. 16234 </p> 16235 <p> 16236You can either specify a default set of keystacking in the .CFG 16237configuration file, or override any default keystacking by typing the 16238keystack definitions at the <name>GoldED+</name> commandline or the GEDCMD 16239environment variable. 16240 </p> 16241 <p> 16242See the Key Reference chapter for a list of the key symbols you can 16243use in macros and keystacking. 16244 </p> 16245 <p> 16246<!-- page --> 16247<!-- --------------------------------------------------------------------- --> 16248 </div1> 16249 <div1> 16250 <head> 16251 Key Reference 16252 </head> 16253 <p> 16254Below is the list of key symbols recognized by <name>GoldED+</name> for 16255keyboard/macro definition and keystacking. 16256 </p> 16257 <p> 16258Unshifted function keys 16259 </p> 16260 <p> 16261 F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 16262 </p> 16263 <p> 16264Shift-function keys 16265 </p> 16266 <p> 16267 #F1 #F2 #F3 #F4 #F5 #F6 #F7 #F8 #F9 #F10 #F11 #F12 16268 </p> 16269 <p> 16270Alt-function keys 16271 </p> 16272 <p> 16273 @F1 @F2 @F3 @F4 @F5 @F6 @F7 @F8 @F9 @F10 @F11 @F12 16274 </p> 16275 <p> 16276Ctrl-function keys 16277 </p> 16278 <p> 16279 ^F1 ^F2 ^F3 ^F4 ^F5 ^F6 ^F7 ^F8 ^F9 ^F10 ^F11 ^F12 16280 </p> 16281 <p> 16282Alt-Numbers 16283 </p> 16284 <p> 16285 @0 @1 @2 @3 @4 @5 @6 @7 @8 @9 16286 </p> 16287 <p> 16288Alt-Letters 16289 </p> 16290 <p> 16291 @A @B @C @D @E @F @G @H @I @J @K @L @M 16292 @N @O @P @Q @R @S @T @U @V @W @X @Y @Z 16293 </p> 16294 <p> 16295Ctrl-Letters 16296 </p> 16297 <p> 16298 ^A ^B ^C ^D ^E ^F ^G ^H ^I ^J ^K ^L ^M 16299 ^N ^O ^P ^Q ^R ^S ^T ^U ^V ^W ^X ^Y ^Z 16300 </p> 16301 <p> 16302Insert/Delete 16303 </p> 16304 <p> 16305 Ins ^Ins @Ins 16306 Del ^Del @Del 16307 </p> 16308 <p> 16309Home/End 16310 </p> 16311 <p> 16312 Home ^Home @Home 16313 End ^End @End 16314 </p> 16315 <p> 16316Page up/down 16317 </p> 16318 <p> 16319 PgUp ^PgUp @PgUp 16320 PgDn ^PgDn @PgDn 16321 </p> 16322 <p> 16323Cursor left/right 16324 </p> 16325 <p> 16326 Left ^Left @Left 16327 Right ^Right @Right 16328 </p> 16329 <p> 16330Cursor up/down 16331 </p> 16332 <p> 16333 Up ^Up @Up 16334 Down ^Down @Down 16335 </p> 16336 <p> 16337Misc other keys 16338 </p> 16339 <p> 16340 Esc ^Grey* Key5 Space Tab #Tab @Tab BackSpace ^BackSpace 16341 @BackSpace Enter ^Enter @Enter 16342 </p> 16343 <p> 16344Note that some of the Alt-keys, especially the cursor-related keys and 16345the F11/F12 keys, are "extended" keys normally only available on 16346systems with an extended keyboard bios. However, <name>GoldED+</name> uses a few 16347tricks to make some the extended keys available on non-extended 16348systems. 16349 </p> 16350<!-- page --> 16351<!-- --------------------------------------------------------------------- --> 16352 </div1> 16353 <div1> 16354 <head> 16355 Language Definition 16356 </head> 16357 <p> 16358GoldED allows you to almost completely redefine the language dependent 16359text in the program. 16360 </p> 16361 <p> 16362The language dependent text in <name>GoldED+</name> is defined in the plain ASCII 16363text GOLDLANG.CFG file. 16364 </p> 16365 <p> 16366See the example language file for the actual method and format of 16367language redefinition. 16368 </p> 16369 <p> 16370If you are planning to translate the text in <name>GoldED+</name>, you should also 16371look into the definition of the help screens. 16372 </p> 16373 <p> 16374You do not need permission from the author before announcing or 16375distributing your own modified language files. 16376 </p> 16377 <div2> 16378 <head> 16379 Date/Time Substitution Codes 16380 </head> 16381 <p> 16382A few of the language texts can contain special date/time substitution 16383codes. The keywords for those are: MS_DateTimeFmt, MS_DateFmt, 16384MS_TimeFmt and ST_StatuslineTimeFmt. 16385 </p> 16386 <p> 16387Here are the valid substitution codes: 16388 </p> 16389 <p> 16390 %a Abbreviated weekday name (Mon, Tue, Wed, ...). 16391 %A Full weekday name (Monday, Tuesday, Wednesday, ...). 16392 %b Abbreviated month name (Jan, Feb, Mar, ...). 16393 %B Full month name (January, February, March, ...). 16394 %d Day of month (01-31). 16395 %e Day of month, with leading space for single digits (1-31). 16396 %E Day of month (1-31). 16397 %H Hour (00-23) (24-hour clock). 16398 %I Hour (01-12) (12-hour clock). 16399 %j Day of the year (001-366). 16400 %m Month (01-12). 16401 %M Minute (00-59). 16402 %p AM or PM according to 12-hour clock. 16403 %S Second (00-59). 16404 %U Week number (00-52) where sunday is first day of the week. 16405 %w Weekday (0-6) where 0 is sunday. 16406 %W Week number (01-53) where monday is first day of the week. 16407 %y Year without century (00-99). 16408 %Y Year with century. 16409 %% Character '%'. 16410 </p> 16411 <p> 16412The %a, %A, %b and %B codes substitute to the current language setup 16413loaded using the LOADLANGUAGE keyword. 16414 </p> 16415 <p> 16416*** NOTE *** 16417 </p> 16418 <p> 16419In the continuing development of <name>GoldED+</name>, it is impossible to 16420completely maintain backward compatibility of the language format or 16421the text defined there. New features may add and/or obsolete some 16422definitions, or may change the format of others. 16423 </p> 16424 <p> 16425The existing language file may contain definitions which are already 16426obsolete, but which I haven't had time to search for and remove, as 16427well as there may be some texts in <name>GoldED+</name> which are not yet definable. 16428All this will of course be corrected in future versions. If you find 16429inconsistencies, please report them, because I may have overlooked 16430them. 16431 </p> 16432<!-- page --> 16433<!-- --------------------------------------------------------------------- --> 16434 </div2> 16435 </div1> 16436 <div1> 16437 <head> 16438 Message Kludge Lines 16439 </head> 16440 <p> 16441Kludge lines are special control lines, that begin with a ^a (ASCII 1) 16442as the first character of the line, followed by a unique identifying 16443name and the relevant control information. 16444 </p> 16445 <p> 16446GoldED is aware of a lot of these kludges, and supports a number of 16447them, if you want to have them inserted in your messages. 16448 </p> 16449 <p> 16450Some kludges are useless junk and more or less commercials for this 16451and that software, but a few are useful for miscellaneous purposes. In 16452the following, I will list (some of) the known and supported kludges, 16453and a short description of what they are used for. 16454 </p> 16455 <div2> 16456 <head> 16457 ACUPDATE: 16458 </head> 16459 <p> 16460 This kludge is a feature of Squish 1.10: Message Broadcast 16461 Modify/Delete. Read the docs for Squish 1.10 for details. 16462 </p> 16463 </div2> 16464 <div2> 16465 <head> 16466 AREA:<echoname> 16467 </head> 16468 <p> 16469 This is not really a kludge, and it doesn't begin with a ^a, but I 16470 included it on the kludge list because it sometimes turned up in 16471 echomail areas where it should have been stripped off by the mail 16472 tosser. 16473 </p> 16474 </div2> 16475 <div2> 16476 <head> 16477 CC: <name> <address> 16478 </head> 16479 <p> 16480 When <name>GoldED+</name> produces carbon copies, it adds to each message a full 16481 list of the persons who get a copy. One version of this list is 16482 hidden behind the CC: kludge. 16483 </p> 16484 </div2> 16485 <div2> 16486 <head> 16487 CHARSET:<charset identifier> 16488 </head> 16489 <p> 16490 Proposed in FSC-0050 and FSC-0054, this kludge is an attempt to 16491 find a solution to the problem of the high-bit characters (like 16492 the IBM PC vs Amiga vs Mac etc. national chars) in messages. 16493 <name>GoldED+</name> can recognize, use and generate this kludge. 16494 </p> 16495 </div2> 16496 <div2> 16497 <head> 16498 CHRC:<font change id> 16499 </head> 16500 <p> 16501 Proposed in FSC-0054, this is a kludge for changing fonts, 16502 underlining and other stuff. 16503 </p> 16504 </div2> 16505 <div2> 16506 <head> 16507 CHRS:<charset identifier> 16508 </head> 16509 <p> 16510 Alternative FSC-0054 version of the CHARSET kludge. 16511 </p> 16512 </div2> 16513 <div2> 16514 <head> 16515 DESTADDR:<destaddress> 16516 </head> 16517 <p> 16518 This one is not proposed anywhere, but it looks like it gives the 16519 address of the intended recipient. <name>GoldED+</name> takes the address for 16520 the dest field. 16521 </p> 16522 </div2> 16523 <div2> 16524 <head> 16525 DOMAIN <destdomain> <destaddress> <origdomain> <origaddress> 16526 </head> 16527 <p> 16528 Proposed in FSC-0038, this tries to solve the problem of mail 16529 crossing domain boundaries. <name>GoldED+</name> takes both addresses. 16530 </p> 16531 </div2> 16532 <div2> 16533 <head> 16534 EID:<crc16> <stamp> [replycrc16] <replystamp> 16535 </head> 16536 <p> 16537 Proposed in FSC-0031, this is used for dupe checking and reply 16538 linking. The EID is today generally considered as garbage, but a 16539 lot of older mail processors such as QMail still generate it. 16540 </p> 16541 </div2> 16542 <div2> 16543 <head> 16544 ENC: 16545 </head> 16546 <p> 16547 Signifies that the message contains encrypted data. <name>GoldED+</name> will 16548 add this kludge if it detects that the message has been encrypted 16549 with PGP. 16550 </p> 16551 </div2> 16552 <div2> 16553 <head> 16554 EOT: 16555 </head> 16556 <p> 16557 End Of Text. See SOT. 16558 </p> 16559 </div2> 16560 <div2> 16561 <head> 16562 FLAGS <special attributes> 16563 </head> 16564 <p> 16565 Proposed in FSC-0053, this is a special netmail kludge used by the 16566 FrontDoor and D'Bridge mailers and the IMail mail processor. It 16567 provides extra attributes not found among the standard attributes 16568 in the normal message/packet headers. <name>GoldED+</name> uses and generates 16569 this kludge, if you set the attributes. 16570 </p> 16571 </div2> 16572 <div2> 16573 <head> 16574 FMPT <from point> 16575 </head> 16576 <p> 16577 Defined in <name>FTS-0001</name>, this tells the point number of the 16578 originator. Netmail only. <name>GoldED+</name> can generate this line. 16579 </p> 16580 </div2> 16581 <div2> 16582 <head> 16583 FWDAREA <original area> 16584 </head> 16585 <p> 16586 <name>FSC-0092</name>: The original area in forwards. See 16587 <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed 16588 description. 16589 </p> 16590 </div2> 16591 <div2> 16592 <head> 16593 FWDDEST <aka> 16594 </head> 16595 <p> 16596 <name>FSC-0092</name>: The original <gi>To:</gi> address in forwards. 16597 See <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed 16598 description. 16599 </p> 16600 </div2> 16601 <div2> 16602 <head> 16603 FWDFROM <name> 16604 </head> 16605 <p> 16606 <name>FSC-0092</name>: The original <gi>From:</gi> name in forwards. 16607 See <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed 16608 description. 16609 </p> 16610 </div2> 16611 <div2> 16612 <head> 16613 FWDMSGID <aka serial#> 16614 </head> 16615 <p> 16616 <name>FSC-0092</name>: The original <gi>MSGID</gi> in forwards. 16617 See <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed 16618 description. 16619 </p> 16620 </div2> 16621 <div2> 16622 <head> 16623 FWDORIG <aka> 16624 </head> 16625 <p> 16626 <name>FSC-0092</name>: The original from-aka in forwards. See 16627 <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed 16628 description. 16629 </p> 16630 </div2> 16631 <div2> 16632 <head> 16633 FWDSUBJ <original subject> 16634 </head> 16635 <p> 16636 <name>FSC-0092</name>: The original subject in forwards. See 16637 <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed 16638 description. 16639 </p> 16640 </div2> 16641 <div2> 16642 <head> 16643 FWDTO <name> 16644 </head> 16645 <p> 16646 <name>FSC-0092</name>: The original <q>To:</q> field in forwards. See 16647 <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed 16648 description. 16649 </p> 16650 </div2> 16651 <div2> 16652 <head> 16653 GATECHK:<???> 16654 </head> 16655 <p> 16656 Some sort of gating kludge? Don't know what it's for. 16657 </p> 16658 </div2> 16659 <div2> 16660 <head> 16661 GIF:<filename> 16662 </head> 16663 <p> 16664 Invented by <name>Henk Wever</name> and used in his 16665 <name>Dutchie</name> software. The filename (which does not have an 16666 extension) indicates a <abbr>GIF</abbr> picture of the author of the 16667 message. 16668 </p> 16669 </div2> 16670 <div2> 16671 <head> 16672 GROUP:<echoname> 16673 </head> 16674 <p> 16675 I think this one comes from stray Groupmail messages. Similar to the 16676 <gi>AREA</gi> kludge. 16677 </p> 16678 </div2> 16679 <div2> 16680 <head> 16681 I51 (no parameters) 16682 </head> 16683 <p> 16684 Proposed in <name>FSC-0051</name>, this indicates that the message text 16685 conforms to the <name>ISO-8859-1</name> (<name>LATIN-1</name>) 16686 character set, and may contain certain escape codes. The 16687 <name>ISO-8859-1</name> set is used in <name>Amiga</name> and 16688 <name>Windows</name> 3.xx. <name>GoldED+</name> can recognize, use and 16689 generate this kludge. 16690 </p> 16691 </div2> 16692 <div2> 16693 <head> 16694 INTL <destaddress> <origaddress> 16695 </head> 16696 <p> 16697 Defined in <name>FTS-0001</name>, this one solves the problem of 16698 crossing zone boundaries. Netmail only. <name>GoldED+</name> can 16699 generate this line. 16700 </p> 16701 </div2> 16702 <div2> 16703 <head> 16704 MSGID: <origaddress> <serialno> 16705 </head> 16706 <p> 16707 Defined in <name>FTS-0009</name>, this is a method for unique 16708 identification of a message. It can be used for dupe checking and 16709 replylinking. <name>GoldED+</name> can generate this line. 16710 </p> 16711 </div2> 16712 <div2> 16713 <head> 16714 MSGTO: <destaddress> 16715 </head> 16716 <p> 16717 This one is not proposed anywhere, but it looks like it gives the 16718 address of the intended recipient. <name>GoldED+</name> takes the 16719 address for the dest field. 16720 </p> 16721 </div2> 16722 <div2> 16723 <head> 16724 Original: <Carbon copy, original name> 16725 </head> 16726 <p> 16727 Generated by the <name>FrontDoor</name> <name>FM</name> editor when it 16728 produces carbon copies. 16729 </p> 16730 </div2> 16731 <div2> 16732 <head> 16733 PATH: <list of nodes> 16734 </head> 16735 <p> 16736 Defined in <name>FTS-0004</name>, this is a valuable tool for finding 16737 dupe links and other structural faults in the net structures. 16738 Unfortunately the list of nodes is 2D (net/node), and this creates 16739 problems when exporting echomail across zones. 16740 </p> 16741 </div2> 16742 <div2> 16743 <head> 16744 PTH: <list of nodes> 16745 </head> 16746 <p> 16747 Not yet a <name>FSC</name> (or is it?), this is a 5D-version of the 16748 <gi>PATH</gi> kludge, which sticks to the top of the msg. 16749 </p> 16750 </div2> 16751 <div2> 16752 <head> 16753 PID: <identifier> <version> [serialno] 16754 </head> 16755 <p> 16756 Proposed in <name>FSC-0046</name>, this takes a stab at the tearline 16757 abuse, and puts <q>safe</q> information about the first mail processing 16758 software in the line. This could be message editors, mail scanners and 16759 other stuff. 16760 </p> 16761 </div2> 16762 <div2> 16763 <head> 16764 Realname: <Name> 16765 </head> 16766 <p> 16767 This kludge was probably born in Russia because of some software was 16768 not able to properly handle non-<abbr>ASCII</abbr> characters in 16769 the header lines. Name should be written in national codepage. 16770 Otherwise I don't see any reason for this kludge. I don't know any 16771 software that generate this kludge. 16772 </p> 16773 </div2> 16774 <div2> 16775 <head> 16776 RFD: <id> 16777 </head> 16778 <p> 16779 Received For Distribution. A kludge inserted by one of the file 16780 announcement programs. 16781 </p> 16782 </div2> 16783 <div2> 16784 <head> 16785 REPLY: <replyaddress> <replyserialno> 16786 </head> 16787 <p> 16788 Defined in <name>FTS-0009</name>, this is the <gi>MSGID</gi> 16789 counterpart. When replying to a message with a <gi>MSGID</gi>, the 16790 <gi>MSGID</gi> of the original is renamed to <gi>REPLY</gi>. 16791 </p> 16792 </div2> 16793 <div2> 16794 <head> 16795 RID:<stuff> 16796 </head> 16797 <p> 16798 Unknown kludge which looks suspiciously like the <gi>EID</gi>. 16799 </p> 16800 </div2> 16801 <div2> 16802 <head> 16803 ROUTE <list of nodes and points> 16804 </head> 16805 <p> 16806 Specifies route path. Currently supported by <name>Unimail</name> and 16807 <name>S\Tosser</name>. 16808 </p> 16809 </div2> 16810 <div2> 16811 <head> 16812 SEEN-BY: <list of nodes> 16813 </head> 16814 <p> 16815 Defined in <name>FTS-0004</name>, this is a tool for finding dupe links 16816 and other structural faults in the net structures. Depending on the 16817 mail tosser, the seen-by's may or may not have a preceding ^a 16818 character. Unfortunately the list of nodes is 2D (net/node), and this 16819 can create problems when exporting echomail across zones. 16820 </p> 16821 </div2> 16822 <div2> 16823 <head> 16824 SN:<serialno> 16825 </head> 16826 <p> 16827 Serial number inserted by the <name>Dutchie</name> message editor. 16828 </p> 16829 </div2> 16830 <div2> 16831 <head> 16832 SOT: 16833 </head> 16834 <p> 16835 Start Of Text. See <gi>EOT</gi>. 16836 </p> 16837 </div2> 16838 <div2> 16839 <head> 16840 SPLIT: 16841 </head> 16842 <p> 16843 Defined in <name>FSC-0047</name>. A method for splitting large msgs so 16844 that some mail processors don't choke on them. 16845 </p> 16846 </div2> 16847 <div2> 16848 <head> 16849 TCL1:, TCL2: <long hex string> 16850 </head> 16851 <p> 16852 Old obsolete swedish dupecheck/replylink kludge. 16853 </p> 16854 </div2> 16855 <div2> 16856 <head> 16857 TID: 16858 </head> 16859 <p> 16860 Tosser <abbr>ID</abbr>. Similar to the <gi>PID</gi>, but specifically 16861 for mail processors. 16862 </p> 16863 </div2> 16864 <div2> 16865 <head> 16866 TOPT <to point> 16867 </head> 16868 <p> 16869 Defined in <name>FTS-0001</name>, this tells the point number of the 16870 destination. Netmail only. <name>GoldED+</name> can generate this line. 16871 </p> 16872 </div2> 16873 <div2> 16874 <head> 16875 TZ <offset from UTC> 16876 </head> 16877 <p> 16878 Specifies the time to <hi>add</hi> to the header time to get the 16879 <abbr>UTC</abbr> (Universal Time Coordinated) time. Generated by newer 16880 versions of the <name>TrackMail</name> netmail processor. 16881 </p> 16882 </div2> 16883 <div2> 16884 <head> 16885 TZUTC 16886 </head> 16887 <p> 16888 See <gi>TZ</gi>. <name>GoldED+</name> can generate this line. 16889 </p> 16890 </div2> 16891 <div2> 16892 <head> 16893 Via: <netmail tossing info> 16894 </head> 16895 <p> 16896 Routed netmail messages usually gets a <gi>Via</gi> line for each node 16897 it passes through. This can be used for tracing faults in the netmail 16898 routing structure. 16899 </p> 16900 </div2> 16901 <div2> 16902 <head> 16903 XID:<stuff> 16904 </head> 16905 <p> 16906 Unknown kludge which looks suspiciously like the EID. 16907 </p> 16908 </div2> 16909 </div1> 16910<!-- --------------------------------------------------------------------- --> 16911 </body> 16912<!-- --------------------------------------------------------------------- --> 16913 </text> 16914<!-- --------------------------------------------------------------------- --> 16915</TEI.2> 16916