home *** CD-ROM | disk | FTP | other *** search
Text File | 1993-03-07 | 228.9 KB | 6,540 lines |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ────────────────────────────────────────────────
-
-
- ┌┐ ┌┐ ┌┐
- ││ ││ ││
- ││ ││ ││
- ││ ││ ││
- ┌┬──┬┐ ┌┬──┬┐ ││ ┌┬──┤│ ┌┬──┬┐ ┌┬──┤│
- ││ ││ ││ ││ ││ ││ ││ ││ ││ ││ ││
- ││ ││ ││ ││ ││ ││ ││ ││ ││ ││ ││
- ││ ││ ││ ││ ││ ││ ││ │├──┴┘ ││ ││
- ││ ││ ││ ││ ││ ││ ││ ││ ││ ││
- ││ ││ ││ ││ ││ ││ ││ ││ ┌┐ ││ ││
- └┴──┤│ └┴──┴┘ └┘ └┴──┴┘ └┴──┴┘ └┴──┴┘
- ││
- ││
- ┌┐ ││ GoldED Version 2.40
- └┴──────┴┘ ───────────────────
-
-
- ────────────────────────────────────────────────
-
-
-
- Released March 31, 1992
-
-
- Reference manual
-
-
- Program and manual written by Odinn Sorensen
-
-
- Copyright (C) 1990-1992 by Odinn Sorensen. All Rights Reserved
-
-
- ──────────────────────────────────────────────────────────────────────
- 0. TABLE OF CONTENTS
- ──────────────────────────────────────────────────────────────────────
-
-
- 0. TABLE OF CONTENTS . . . . . . . . . . . . . . . . . . . . . i
-
- 1. FEATURES . . . . . . . . . . . . . . . . . . . . . . . . . . 1
-
- 2. REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . 2
-
- 3. THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . 3
-
- 4. LEGAL STUFF . . . . . . . . . . . . . . . . . . . . . . . . 4
-
- 5. QUICK INSTALLATION . . . . . . . . . . . . . . . . . . . . . 5
- Simple configuration . . . . . . . . . . . . . . . . . . . . 5
- Advanced configuration . . . . . . . . . . . . . . . . . . . 5
-
- 6. COMMANDLINE USAGE . . . . . . . . . . . . . . . . . . . . . 6
- Commandline options . . . . . . . . . . . . . . . . . . . . 6
- Commandline keystacking . . . . . . . . . . . . . . . . . . 7
-
- 7. ENVIRONMENT VARIABLES . . . . . . . . . . . . . . . . . . . 8
- GoldED specific environment variables . . . . . . . . . . . 8
- Other environment variables . . . . . . . . . . . . . . . . 8
-
- 8. ERRORLEVELS . . . . . . . . . . . . . . . . . . . . . . . . 9
-
- 9. LOGFILE . . . . . . . . . . . . . . . . . . . . . . . . . . 10
-
- 10. NODELISTS AND USERLISTS . . . . . . . . . . . . . . . . . . 11
-
- 11. CONFIGURATION KEYWORD REFERENCE . . . . . . . . . . . . . . 12
- ADDRESS <zone:net/node[.point][@domain][, pointnet]> . . . . 12
- ADDRESSMACRO <macro>,<name>,<address>[,subject] . . . . . . 13
- AKA <zone:net/node[.point][@domain][, pointnet]> . . . . . . 13
- AKAMATCHECHO <yes/no> (no) . . . . . . . . . . . . . . . . 13
- AKAMATCHNET <yes/no> (yes) . . . . . . . . . . . . . . . . 13
- AKAMATCHLOCAL <yes/no> (no) . . . . . . . . . . . . . . . . 14
- AREA <echoid> <"desc"> <msgbase>[type] <loc> [akano] [attrs] 14
- AREAAUTONEXT <yes/no> (yes) . . . . . . . . . . . . . . . . 14
- AREAEXCL <echoid mask> . . . . . . . . . . . . . . . . . . . 14
- AREAFILE <type> [path/file] [switches] . . . . . . . . . . . 15
- AREAFILEGROUPS <yes/no> (no) . . . . . . . . . . . . . . . 15
- AREAINCL <echoid mask> . . . . . . . . . . . . . . . . . . . 15
- AREALISTNOS <yes/no> (no) . . . . . . . . . . . . . . . . . 15
- AREALISTSORT <sortspec> . . . . . . . . . . . . . . . . . . 16
- AREALISTTYPE <new/last> (new) . . . . . . . . . . . . . . . 16
- AREAPATH <path> . . . . . . . . . . . . . . . . . . . . . . 16
- AREARENAME <from echoid> <to echoid> . . . . . . . . . . . . 17
- AREASCAN <echoid mask> . . . . . . . . . . . . . . . . . . . 17
- AREASTART <echoid> . . . . . . . . . . . . . . . . . . . . . 17
- ASKDELORIG <yes/no> (yes) . . . . . . . . . . . . . . . . . 17
- ATTRIBSCC <attributes> . . . . . . . . . . . . . . . . . . . 17
- ATTRIBSCFM <attributes> . . . . . . . . . . . . . . . . . . 18
- ATTRIBSECHO <attributes> . . . . . . . . . . . . . . . . . . 18
-
-
- ──────────────────────────────────────────────────────────────────────
- TABLE OF CONTENTS GoldED Manual, Page i
-
-
- ATTRIBSLOCAL <attributes> . . . . . . . . . . . . . . . . . 18
- ATTRIBSNET <attributes> . . . . . . . . . . . . . . . . . . 18
- BEEPCOMMENT <yes/no> (yes) . . . . . . . . . . . . . . . . 18
- BEEPFACTOR <value> (5) . . . . . . . . . . . . . . . . . . 18
- BEEPLOCALMSG <yes/no> (yes) . . . . . . . . . . . . . . . . 18
- BEEPNOISES <yes/no> (yes) . . . . . . . . . . . . . . . . . 18
- BEEPYOURMAIL <yes/no/always> (yes) . . . . . . . . . . . . 19
- CARBONCOPYLIST <listspec> (Names) . . . . . . . . . . . . . 19
- COLOR <colorspec> . . . . . . . . . . . . . . . . . . . . . 19
- COLORSET <Normal/Intense/Mono> (Normal or Mono) . . . . . . 19
- CONFIRMFILE <filename> (GOLDED.CFM) . . . . . . . . . . . . 20
- CROSSPOSTLIST <listspec> (Verbose) . . . . . . . . . . . . 20
- CTRLINFOECHO <Tearline,Origin,yes/no> (Tearline Origin) . . 20
- CTRLINFOLOCAL <Tearline,Origin,yes/no> (Tearline Origin) . 20
- CTRLINFONET <Tearline,Origin,yes/no> (Tearline) . . . . . . 21
- DISPAUTONEXT <yes/no> (yes) . . . . . . . . . . . . . . . . 21
- DISPLISTWRAP <yes/no> (yes) . . . . . . . . . . . . . . . . 21
- DISPLOCALHIGH <yes/no> (yes) . . . . . . . . . . . . . . . 21
- DISPMARGIN <width> (0) . . . . . . . . . . . . . . . . . . 21
- DISPPAGEBAR <yes/no> (yes) . . . . . . . . . . . . . . . . 21
- DISPREALMSGNO <yes/no> (no) . . . . . . . . . . . . . . . . 22
- DISPREPLIESMODE <yes/no> (yes) . . . . . . . . . . . . . . 22
- DISPTABSIZE <chars> (8) . . . . . . . . . . . . . . . . . . 22
- DOSPROMPT (yes/no) (yes) . . . . . . . . . . . . . . . . . 22
- DOSSWAP <yes/no,xms,ems,disk,hide,checknet,noprealloc> (no) 23
- EDITAUTOATTACH <yes/no> (yes) . . . . . . . . . . . . . . . 23
- EDITAUTOSAVE <seconds> (30) . . . . . . . . . . . . . . . . 23
- EDITCHANGEDATE <yes/no> (yes) . . . . . . . . . . . . . . . 24
- EDITCOMMENT <"word"> <"comment"> . . . . . . . . . . . . . . 24
- EDITCRLFTERM <yes/no> (yes) . . . . . . . . . . . . . . . . 24
- EDITFIELDCLEAR <yes/no> (yes) . . . . . . . . . . . . . . . 24
- EDITHARDLINE <string> ("<<") . . . . . . . . . . . . . . . 24
- EDITHARDLINES <yes/no> (yes) . . . . . . . . . . . . . . . 24
- EDITINTERNAL <yes/no> (yes) . . . . . . . . . . . . . . . . 25
- EDITMENU <yes/no> (yes) . . . . . . . . . . . . . . . . . . 25
- EDITMIXCASE <yes/no> (yes) . . . . . . . . . . . . . . . . 25
- EDITMSGSIZE <bytes> (65530) . . . . . . . . . . . . . . . . 25
- EDITOR <commandline> [@file] [@line] . . . . . . . . . . . . 25
- EDITORFILE <file> (GOLDED.MSG) . . . . . . . . . . . . . . 26
- EDITREPLYRE <yes/no> (no) . . . . . . . . . . . . . . . . . 26
- EDITSAVEMENU <yes/no> (yes) . . . . . . . . . . . . . . . . 26
- EDITSPELLCHECK <commandline> [@file] . . . . . . . . . . . . 26
- EDITUNDELETE <lines> (50) . . . . . . . . . . . . . . . . . 26
- EMPTYTEARLINE <yes,no> (no) . . . . . . . . . . . . . . . . 26
- EXCLUDENODES <addressmask> . . . . . . . . . . . . . . . . . 27
- FIDOHWMARKS <yes/no> (no) . . . . . . . . . . . . . . . . . 27
- FIDOLASTREAD <file> (LASTREAD.) . . . . . . . . . . . . . . 27
- FIDOLASTREADNO <userno> (0) . . . . . . . . . . . . . . . . 27
- FILEALIAS <alias> <filename> . . . . . . . . . . . . . . . . 27
- FREETEAR <echoid> (MAGNA) . . . . . . . . . . . . . . . . . 27
- GOLDHELP <file> (GOLDHELP.CFG) . . . . . . . . . . . . . . 28
- GOLDKEYS <file> (GOLDKEYS.CFG) . . . . . . . . . . . . . . 28
- GOLDLANG <file> (GOLDLANG.CFG) . . . . . . . . . . . . . . 28
- GOLDPATH <path> . . . . . . . . . . . . . . . . . . . . . . 28
- GOLDRAND <file> (GOLDRAND.CFG) . . . . . . . . . . . . . . 28
- GOLDXLAT <file> (GOLDXLAT.CFG) . . . . . . . . . . . . . . 28
- IGNORE . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
-
-
- ──────────────────────────────────────────────────────────────────────
- TABLE OF CONTENTS GoldED Manual, Page ii
-
-
- INBOUNDPATH <path> (defaults to GOLDPATH) . . . . . . . . . 28
- INCLUDE <file> . . . . . . . . . . . . . . . . . . . . . . . 28
- INCLUDENODES <addressmask> . . . . . . . . . . . . . . . . . 29
- INTENSECOLORS <yes/no> (no) . . . . . . . . . . . . . . . . 29
- INVALIDATE <type> <"findstring"> <"replacestring"> . . . . . 29
- KEYBCLEAR <yes/no> (no) . . . . . . . . . . . . . . . . . . 29
- KEYBEXT <yes/no> (no) . . . . . . . . . . . . . . . . . . . 29
- KEYBSTACK <keystring> . . . . . . . . . . . . . . . . . . . 30
- LOGFILE <file> (GOLDED.LOG) . . . . . . . . . . . . . . . . 30
- LOOKUPECHO <yes/no> (no) . . . . . . . . . . . . . . . . . 30
- LOOKUPLOCAL <yes/no> (no) . . . . . . . . . . . . . . . . . 30
- LOOKUPNET <yes/no> (yes) . . . . . . . . . . . . . . . . . 30
- MAPDRIVE <server driveletter> <local driveletter> . . . . . 30
- MOUSE <yes/no> (no) . . . . . . . . . . . . . . . . . . . . 31
- NAMESFILE <file> (NAMES.FD) . . . . . . . . . . . . . . . . 31
- NETNAME <"string"> . . . . . . . . . . . . . . . . . . . . . 31
- NODELIST <file> [zone/addr] . . . . . . . . . . . . . . . . 31
- NODEPATH <path> . . . . . . . . . . . . . . . . . . . . . . 32
- ORIGIN <"string"> . . . . . . . . . . . . . . . . . . . . . 32
- OUTBOUNDPATH <path> . . . . . . . . . . . . . . . . . . . . 32
- OUTPUTFILE <file> . . . . . . . . . . . . . . . . . . . . . 32
- OVERLAY <ems/ext/disk> (disk) . . . . . . . . . . . . . . . 32
- PRINTDEVICE <devicename> (PRN) . . . . . . . . . . . . . . 32
- PRINTFORMFEED <yes/no> (yes) . . . . . . . . . . . . . . . 32
- PRINTINIT <printstring> . . . . . . . . . . . . . . . . . . 33
- PRINTLENGTH <lines> (65) . . . . . . . . . . . . . . . . . 33
- PRINTMARGIN <characters> (80) . . . . . . . . . . . . . . . 33
- PRINTRESET <printstring> . . . . . . . . . . . . . . . . . . 33
- QBBSINCRESCAN <yes/no> (yes) . . . . . . . . . . . . . . . 33
- QBBSPATH <path> . . . . . . . . . . . . . . . . . . . . . . 33
- QBBSREBUILD <yes/no> (no) . . . . . . . . . . . . . . . . . 33
- QUOTEBLANK <yes/no> (no) . . . . . . . . . . . . . . . . . 34
- QUOTEMARGIN <chars> (-5) . . . . . . . . . . . . . . . . . 34
- QUOTESPACING <yes/no> (yes) . . . . . . . . . . . . . . . . 34
- QUOTESTRING <quotespec> (" FML> ") . . . . . . . . . . . . 34
- REGISTERKEY <keycode> . . . . . . . . . . . . . . . . . . . 34
- REGISTERNAME <keyname> . . . . . . . . . . . . . . . . . . . 34
- ROBOTNAME <name> . . . . . . . . . . . . . . . . . . . . . . 34
- SCREENBLANKER <seconds> (180) . . . . . . . . . . . . . . . 35
- SCREENELIMSNOW <yes/no> (no) . . . . . . . . . . . . . . . 35
- SCREENMAXCOL <columns> (0) . . . . . . . . . . . . . . . . 35
- SCREENMAXROW <rows> (0) . . . . . . . . . . . . . . . . . . 35
- SCREENSHADOWS <yes/no> (yes) . . . . . . . . . . . . . . . 35
- SCREENSIZE <mode> (Auto) . . . . . . . . . . . . . . . . . 35
- SCREENUSEBIOS <yes/no> (no) . . . . . . . . . . . . . . . . 35
- SEMAPHORE <type> <file> . . . . . . . . . . . . . . . . . . 36
- SHAREMODE <yes/no/mode#> (yes) . . . . . . . . . . . . . . 36
- SQUISHSCAN <api/quick> (quick) . . . . . . . . . . . . . . 36
- SQUISHUSERNO <index> . . . . . . . . . . . . . . . . . . . . 36
- SQUISHUSERPATH <path> . . . . . . . . . . . . . . . . . . . 37
- SWAPPATH <path> (defaults to TEMPPATH) . . . . . . . . . . 37
- TEARLINE <string> (GoldED @version) . . . . . . . . . . . . 37
- TEMPLATE <file> ["desc"] (GOLDED.TPL) . . . . . . . . . . . 37
- TEMPPATH <path> . . . . . . . . . . . . . . . . . . . . . . 37
- TIMEOUT <seconds> (360) . . . . . . . . . . . . . . . . . . 38
- TIMESLICE <type> (none) . . . . . . . . . . . . . . . . . . 38
- TWITMODE <mode> (Show) . . . . . . . . . . . . . . . . . . 38
-
-
- ──────────────────────────────────────────────────────────────────────
- TABLE OF CONTENTS GoldED Manual, Page iii
-
-
- TWITNAME <name/addressmask> . . . . . . . . . . . . . . . . 38
- TWITSUBJ <"string"> . . . . . . . . . . . . . . . . . . . . 38
- USEFLAGS <yes/no> (yes) . . . . . . . . . . . . . . . . . . 39
- USEINTL <type> (Auto) . . . . . . . . . . . . . . . . . . . 39
- USEMSGID <yes/no> (yes) . . . . . . . . . . . . . . . . . . 39
- USERLIST <file> [zone/addr] . . . . . . . . . . . . . . . . 39
- USERLISTFILE <file> (GOLDED.LST) . . . . . . . . . . . . . 39
- USERNAME <name>[,address] . . . . . . . . . . . . . . . . . 40
- VIEWHIDDEN <yes/no> (yes) . . . . . . . . . . . . . . . . . 40
- VIEWKLUDGE <yes/no> (no) . . . . . . . . . . . . . . . . . 40
- WHOTO <name> . . . . . . . . . . . . . . . . . . . . . . . . 40
- XLATCHARSET <importid> <exportid> <file> . . . . . . . . . . 40
- XLATESCSET <import> <export> <escfile> . . . . . . . . . . . 40
- XLATEXPORT <charsetid> . . . . . . . . . . . . . . . . . . . 40
- XLATIMPORT <charsetid> (IBMPC) . . . . . . . . . . . . . . 41
- XLATPATH <path> . . . . . . . . . . . . . . . . . . . . . . 41
- ZONEGATING <yes/no/ask> (ask) . . . . . . . . . . . . . . . 41
-
- 12. THE OLD CONFIGURATION KEYWORDS . . . . . . . . . . . . . . . 42
- Old keyword New keyword . . . . . . . . . . . . . . . . . 42
-
- 13. AREA CONFIGURATION . . . . . . . . . . . . . . . . . . . . . 44
- Syntax for manually defined areas . . . . . . . . . . . . . 44
- Syntax for external area configuration . . . . . . . . . . . 44
-
- 14. COLOR CONFIGURATION . . . . . . . . . . . . . . . . . . . . 46
- Various general color items . . . . . . . . . . . . . . . . 46
- Startup screen / logo window . . . . . . . . . . . . . . . . 47
- Area Selection Menu . . . . . . . . . . . . . . . . . . . . 47
- Message Header . . . . . . . . . . . . . . . . . . . . . . . 47
- Message Text . . . . . . . . . . . . . . . . . . . . . . . . 47
- Miscellaneous Smaller Menus . . . . . . . . . . . . . . . . 47
- Miscellaneous Larger Menus (Browser Windows) . . . . . . . . 48
- Help Screens . . . . . . . . . . . . . . . . . . . . . . . . 48
- Pop Up Information Windows . . . . . . . . . . . . . . . . . 48
-
- 15. THE RANDOM SYSTEM . . . . . . . . . . . . . . . . . . . . . 49
- Defining Groups . . . . . . . . . . . . . . . . . . . . . . 49
- Defining Random Items . . . . . . . . . . . . . . . . . . . 50
- ATTRIBUTES <attributes> . . . . . . . . . . . . . . . . 50
- LOADLANGUAGE <file> . . . . . . . . . . . . . . . . . . 50
- NETNAME <"string"> . . . . . . . . . . . . . . . . . . 50
- ORIGIN <"string"> . . . . . . . . . . . . . . . . . . . 50
- OUTPUTFILE <file> . . . . . . . . . . . . . . . . . . . 50
- SEARCHFOR <string;string;..> . . . . . . . . . . . . . 51
- TEARLINE <string> . . . . . . . . . . . . . . . . . . . 51
- TEMPLATE <file> . . . . . . . . . . . . . . . . . . . . 51
- TWITMODE <mode> . . . . . . . . . . . . . . . . . . . . 51
- USERNAME <name>[,addr] . . . . . . . . . . . . . . . . 51
- VIEWHIDDEN <yes/no> . . . . . . . . . . . . . . . . . . 51
- VIEWKLUDGE <yes/no> . . . . . . . . . . . . . . . . . . 51
- WHOTO <name> . . . . . . . . . . . . . . . . . . . . . 51
- XLATEXPORT <charsetid> . . . . . . . . . . . . . . . . 51
- XLATIMPORT <charsetid> . . . . . . . . . . . . . . . . 51
- Random System Example . . . . . . . . . . . . . . . . . . . 52
-
- 16. THE MESSAGE TEMPLATE . . . . . . . . . . . . . . . . . . . . 54
-
-
- ──────────────────────────────────────────────────────────────────────
- TABLE OF CONTENTS GoldED Manual, Page iv
-
-
- Conditional tokens . . . . . . . . . . . . . . . . . . . . . 54
- Insert tokens . . . . . . . . . . . . . . . . . . . . . . . 54
- Replacement tokens . . . . . . . . . . . . . . . . . . . . . 54
-
- 17. HELP SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . 56
-
- 18. CHARACTER TRANSLATION . . . . . . . . . . . . . . . . . . . 58
- The *.ESC files . . . . . . . . . . . . . . . . . . . . . . 58
- The *.CHS files . . . . . . . . . . . . . . . . . . . . . . 59
-
- 19. KEYBOARD COMMAND REFERENCE . . . . . . . . . . . . . . . . . 60
- Arealist commands . . . . . . . . . . . . . . . . . . . . . 60
- Internal editor commands . . . . . . . . . . . . . . . . . . 61
- File selection commands . . . . . . . . . . . . . . . . . . 62
- Message lister commands . . . . . . . . . . . . . . . . . . 62
- Nodelist browser commands . . . . . . . . . . . . . . . . . 62
- Message reader commands . . . . . . . . . . . . . . . . . . 63
-
- 20. MACROS AND KEYSTACKING . . . . . . . . . . . . . . . . . . . 65
- Macro definition . . . . . . . . . . . . . . . . . . . . . . 65
- Keystacking . . . . . . . . . . . . . . . . . . . . . . . . 65
-
- 21. KEY REFERENCE . . . . . . . . . . . . . . . . . . . . . . . 66
- Unshifted function keys . . . . . . . . . . . . . . . . . . 66
- Shift-function keys . . . . . . . . . . . . . . . . . . . . 66
- Alt-function keys . . . . . . . . . . . . . . . . . . . . . 66
- Ctrl-function keys . . . . . . . . . . . . . . . . . . . . . 66
- Alt-Numbers . . . . . . . . . . . . . . . . . . . . . . . . 66
- Alt-Letters . . . . . . . . . . . . . . . . . . . . . . . . 66
- Ctrl-Letters . . . . . . . . . . . . . . . . . . . . . . . . 66
- Insert/Delete . . . . . . . . . . . . . . . . . . . . . . . 67
- Home/End . . . . . . . . . . . . . . . . . . . . . . . . . . 67
- Page up/down . . . . . . . . . . . . . . . . . . . . . . . . 67
- Cursor left/right . . . . . . . . . . . . . . . . . . . . . 67
- Cursor up/down . . . . . . . . . . . . . . . . . . . . . . . 67
- Misc other keys . . . . . . . . . . . . . . . . . . . . . . 67
-
- 22. LANGUAGE DEFINITION . . . . . . . . . . . . . . . . . . . . 68
- NOTES . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
-
- 23. THE MSGBASE FORMATS . . . . . . . . . . . . . . . . . . . . 69
- Fido/Opus/FTSC *.MSG . . . . . . . . . . . . . . . . . . . . 69
- QBBS (Hudson) MSG*.BBS . . . . . . . . . . . . . . . . . . . 70
- Squish *.SQ* . . . . . . . . . . . . . . . . . . . . . . . . 71
-
- 24. ENTERING MESSAGES . . . . . . . . . . . . . . . . . . . . . 72
-
- 25. THE "HARDLINE" FEATURE . . . . . . . . . . . . . . . . . . . 73
-
- 26. QUOTE REFLOW . . . . . . . . . . . . . . . . . . . . . . . . 75
-
- 27. CARBON COPY AND CROSSPOSTING . . . . . . . . . . . . . . . . 76
- Carbon Copying . . . . . . . . . . . . . . . . . . . . . . . 76
- Crossposting . . . . . . . . . . . . . . . . . . . . . . . . 77
-
- 28. ENCRYPTING MESSAGES . . . . . . . . . . . . . . . . . . . . 78
-
-
-
- ──────────────────────────────────────────────────────────────────────
- TABLE OF CONTENTS GoldED Manual, Page v
-
-
- 29. NODELIST BROWSE AND LOOKUPS . . . . . . . . . . . . . . . . 79
- Nodelist browser . . . . . . . . . . . . . . . . . . . . . . 79
- Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . 80
-
- 30. USER DATABASE LOOKUP . . . . . . . . . . . . . . . . . . . . 81
-
- 31. MARKING MESSAGES . . . . . . . . . . . . . . . . . . . . . . 82
-
- 32. THE FILE REQUEST FEATURE . . . . . . . . . . . . . . . . . . 83
-
- 33. KLUDGE LINES . . . . . . . . . . . . . . . . . . . . . . . . 84
- AREA:<echoname> . . . . . . . . . . . . . . . . . . . . . . 84
- CC: <name> <address> . . . . . . . . . . . . . . . . . . . . 84
- CHARSET:<charset identifier> . . . . . . . . . . . . . . . . 84
- CHRC:<font change id> . . . . . . . . . . . . . . . . . . . 84
- CHRS:<charset identifier> . . . . . . . . . . . . . . . . . 84
- DESTADDR:<destaddress> . . . . . . . . . . . . . . . . . . . 84
- DOMAIN <destdomain> <destaddress> <origdomain> <origaddress> 84
- EID:<crc16> <stamp> [replycrc16] <replystamp> . . . . . . . 85
- FLAGS <special attributes> . . . . . . . . . . . . . . . . . 85
- FMPT <from point> . . . . . . . . . . . . . . . . . . . . . 85
- GATECHK:<???> . . . . . . . . . . . . . . . . . . . . . . . 85
- GROUP:<echoname> . . . . . . . . . . . . . . . . . . . . . . 85
- I51 (no parameters) . . . . . . . . . . . . . . . . . . . . 85
- INTL <destaddress> <origaddress> . . . . . . . . . . . . . . 85
- MSGID: <origaddress> <serialno> . . . . . . . . . . . . . . 85
- MSGTO: <destaddress> . . . . . . . . . . . . . . . . . . . . 85
- Original: <Carbon copy, original name> . . . . . . . . . . . 86
- PATH: <list of nodes> . . . . . . . . . . . . . . . . . . . 86
- PTH: <list of nodes> . . . . . . . . . . . . . . . . . . . . 86
- PID: <identifier> <version> [serialno] . . . . . . . . . . . 86
- RFD: <id> . . . . . . . . . . . . . . . . . . . . . . . . . 86
- REPLY: <replyaddress> <replyserialno> . . . . . . . . . . . 86
- RID:<stuff> . . . . . . . . . . . . . . . . . . . . . . . . 86
- SEEN-BY: <list of nodes> . . . . . . . . . . . . . . . . . . 86
- SN:<serialno> . . . . . . . . . . . . . . . . . . . . . . . 86
- TCL1:, TCL2: <long hex string> . . . . . . . . . . . . . . . 86
- TOPT <to point> . . . . . . . . . . . . . . . . . . . . . . 87
- TZ <offset from UTC> . . . . . . . . . . . . . . . . . . . . 87
- VIA: <netmail tossing info> . . . . . . . . . . . . . . . . 87
- XID:<stuff> . . . . . . . . . . . . . . . . . . . . . . . . 87
-
- 34. KNOWN BUGS . . . . . . . . . . . . . . . . . . . . . . . . . 88
- Internal editor . . . . . . . . . . . . . . . . . . . . . . 88
- Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . 88
- Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . 88
-
- 35. RESTRICTED FEATURES . . . . . . . . . . . . . . . . . . . . 89
-
- 36. FUTURE PLANS . . . . . . . . . . . . . . . . . . . . . . . . 90
-
- 37. DISTRIBUTION AND REGISTRATION SITES . . . . . . . . . . . . 91
-
- 38. SUPPORT CONFERENCES . . . . . . . . . . . . . . . . . . . . 92
-
- 39. ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . . 93
-
-
-
- ──────────────────────────────────────────────────────────────────────
- TABLE OF CONTENTS GoldED Manual, Page vi
-
-
- 40. THE AUTHOR . . . . . . . . . . . . . . . . . . . . . . . . . 94
-
- APPENDIX A - Attributes . . . . . . . . . . . . . . . . . . . . . 95
-
- APPENDIX B - Address masks . . . . . . . . . . . . . . . . . . . 96
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- TABLE OF CONTENTS GoldED Manual, Page vii
-
-
- ──────────────────────────────────────────────────────────────────────
- 1. FEATURES
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED is a very advanced FidoNet-compatible offline reader/editor for
- SysOps and Points.
-
- The following are a few highlights of the main features:
-
- ■ Supports three of the most popular msgbase formats: Fido *.MSG,
- QuickBBS and Squish.
- ■ Supports the area configuration setups of 15+ of the most popular
- BBS'es, mailers and mail processors, greatly easing area setup.
- ■ Can use your favorite external text editor/word processor or the
- internal editor for writing messages.
- ■ Extremely configurable, using plain ascii text files.
- ■ Language, keyboard, colors, help, all fully configurable!
- ■ Message templates.
- ■ Advanced file requesting directly from SDS/SDN/whatever postings!
- ■ File selection for file attaching.
- ■ Nodelist lookup and browsing.
- ■ Advanced "Random System" for area-specific origins, templates and
- lots of other things!
- ■ Keyboard macros and keystacking from the commandline.
- ■ Carbon copies and crossposting.
- ■ Support for external spellchecking software!
- ■ Bulk message marking and copy/move/printing.
- ■ Forward or move replies to other conferences!
- ■ Character translations using the CHARSET kludge.
- ■ Twitting of names and subjects.
- ■ Countless other features!
- ■ More than 500+ registered users worldwide!
- ■ Constantly being further developed by a dedicated author.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- FEATURES GoldED Manual, Page 1
-
-
- ──────────────────────────────────────────────────────────────────────
- 2. REQUIREMENTS
- ──────────────────────────────────────────────────────────────────────
-
-
- ■ Any IBM PC compatible computer with at least 512K memory.
- ■ MS-DOS (or compatible) 3.30 or later. (Earlier might also work).
- ■ Diskspace for the GoldED files + msgbase files.
- ■ At least FILES=30 in CONFIG.SYS.
- ■ Any Fido/Opus (*.MSG), Squish or QBBS compatible msgbase.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- REQUIREMENTS GoldED Manual, Page 2
-
-
- ──────────────────────────────────────────────────────────────────────
- 3. THIS MANUAL
- ──────────────────────────────────────────────────────────────────────
-
-
- As you will see, this is mainly a technical reference manual for the
- configuration of GoldED. You will also find a number of chapters
- detailing some of the many features, but there are still some that
- remain undescribed at the time of writing. I find myself pressed for
- time, so I hope you will examine this manual carefully - the "clues"
- are all in here, even if the actual feature is not described.
-
- You are highly recommended to read the NOTES.DOC file - it contains a
- complete collection of all release notes since version 2.30, and
- provides many important clues and information about the features and
- inner workings of GoldED. It is often very technical in nature, but I
- think you will find it worthwhile anyway.
-
- A more general introduction to the wonderful world of electronic mail
- is outside the scope of this manual. Good texts on the subject can be
- found in the manuals of most popular BBS/Mailers/Mail processors.
-
- GoldED is designed to be configurable to the extreme, and unfortunate-
- ly this makes things (even more) difficult for the inexperienced point
- or sysop. I hope that I have made life a bit easier by providing the
- simpler configuration examples, and including a special "advanced"
- package for when you feel more confident with the operation of GoldED.
-
- I hope you will like and enjoy what you see, and join the thousands of
- other GoldED users, and - hopefully - The Few, The Proud, The
- Registered! :-)
-
- Have a nice day!
-
- Odinn Sorensen, Author of GoldED.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THIS MANUAL GoldED Manual, Page 3
-
-
- ──────────────────────────────────────────────────────────────────────
- 4. LEGAL STUFF
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED is provided as is, with no warranty of any kind, either expres-
- sed or implied. GoldED is only guaranteed to occupy disk space. You
- are free to copy and distribute the GoldED archive freely, provided no
- changes or additions are made to the package.
-
- Odinn Sorensen (The Author) shall in no event be held liable to you or
- anyone else for any damages of ANY kind, incidental or consequential,
- arising from the use or inability to use this program.
-
- All products by Odinn Sorensen are trademarks and are Copyright by
- Odinn Sorensen. Other products and brand names are trademarks and
- Copyright by the respective holders.
-
- Please read the REGISTER.DOC file for more information about the legal
- uses of this program.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- LEGAL STUFF GoldED Manual, Page 4
-
-
- ──────────────────────────────────────────────────────────────────────
- 5. QUICK INSTALLATION
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED is a very complex program with many options meant for experi-
- enced users. If you have been using GoldED before, or consider your-
- self a configuration wizard, go ahead and use the advanced con-
- figuration provided. It contains just about *all* the possible con-
- figuration options available, and has been known to be hard nut to
- crack even for experienced users ;-)
-
- For new and/or inexperienced users, a relatively simple standard setup
- has been provided to get you going fairly painlessly.
-
- All configuration is done in flat ASCII files, so you need a good text
- editor. I use QEdit - what else :-)
-
- This following is a step-by-step procedure for quick installation.
-
- ■ Make a new directory. The GoldED setup is composed of many dif-
- ferent files, and it is a good idea to keep them in a place for
- themselves.
- ■ Move all the files in the distribution archive to the new direc-
- tory.
- ■ Check if you have the GOLDED environment variable, and
- remove/change it if needed. (see the section about environment
- variables later).
-
-
- Simple configuration
- ──────────────────────────────────────────────────────────────────────
-
- 1. Edit GOLDED.CFG to match your setup. (Use the AREAFILE's!)
- 2. Run GOLDNODE.EXE if you want nodelist lookup.
- 3. Run GOLDED.EXE.
-
- And that's it! However, as soon as you are familiar with the simple
- configuration, you should take a look at the advanced stuff, because
- there are many interesting and useful things there!
-
-
- Advanced configuration
- ──────────────────────────────────────────────────────────────────────
-
- 1. Unpack ADVANCED.ARJ & XLAT.ARJ. Rename ADVANCED.CFG to GOLDED.CFG.
- 2. Edit GOLDED.CFG and GOLDAREA.CFG to match your setup.
- 3. Run GOLDNODE.EXE if you want nodelist lookup.
- 4. Run GOLDED.EXE.
- 5. Repeat 2. through 4. until it works ;-)
-
- Good luck!
-
- Remember, if you have having trouble with your setup, you can always
- ask in the international GOLDED echo, or a corresponding local echo.
- There are bound to be other GoldED usere who will be glad to help!
-
-
-
- ──────────────────────────────────────────────────────────────────────
- QUICK INSTALLATION GoldED Manual, Page 5
-
-
- ──────────────────────────────────────────────────────────────────────
- 6. COMMANDLINE USAGE
- ──────────────────────────────────────────────────────────────────────
-
-
- For extra flexibility, GoldED has a set of commandline options for
- various purposes.
-
- Commandline syntax: GOLDED [options] [keystacking]
-
-
- Commandline options
- ──────────────────────────────────────────────────────────────────────
-
- -C<configname> Specifies another configuration file than
- GOLDED.CFG.
-
- -D(isable) Disable old configuration keywords. Used when up-
- grading your old setup to use the new configuration
- keywords.
-
- -E<echoid> If specified, GoldED starts directly in that echo,
- bypassing the arealist screen. See the AREASTART
- configuration keyword for more info.
-
- -F(orce) Force complete re-compile of all configuration
- files, regardless of whether they are up-to-date or
- not. This is equivalent to deleting all the *.GED
- files (or GOLDED.DAT etc. in the old 2.3x setups).
-
- -N(oshare) If used, this prevents GoldED from using SHARE
- compatible file-open calls, which are used by
- default. Works only until the SHAREMODE keyword is
- used in GOLDED.CFG. This keyword is normally not
- useful, but may be used to debug your setup or
- something.
-
- -O<ovlsize> Specifies the overlay size for GoldED (the default
- is approximately 64K). Higher values (up to about
- 300K) causes GoldED to run faster, and use more
- memory. Lower values (down to about 30K) makes it
- run slower, in less memory. Check the "memory
- meter" on the right side of the statusline to see
- how much memory is free at any given time. The
- memory meter value should be *minimum* 50-100k or
- more for best performance and insurance against
- "out of memory" errors. The lower memory meter
- value, the higher risk of out of memory errors...
-
- -Q(uiet) Turns off verbose config compile. On by default.
- This could be used on the commandline to disable
- a -V(erbose) option in the GEDCMD environment
- variable.
-
- -S<sortspec> Sort all areas according to <sortspec>. (see the
- AREALISTSORT config keyword).
-
-
-
- ──────────────────────────────────────────────────────────────────────
- COMMANDLINE USAGE GoldED Manual, Page 6
-
-
- -T<seconds> Set the timeout value. A value of zero (0) means
- never timeout. (see the TIMEOUT config keyword).
-
- -V(erbose) Turns on verbose config compile. When used, GoldED
- will display the full filename of each main config
- file it compiles. This can be useful for debugging
- your setup, and see if it accesses the files
- (especially the AREAFILE's) it is supposed to. You
- can also use the expanded syntax "-VV", which makes
- GoldED display all the lines while compiling. This
- could be used to find the exact spot if it crashes
- or stops while compiling.
-
-
- Commandline keystacking
- ──────────────────────────────────────────────────────────────────────
-
- Any non-option characters on the commandline are stuffed into the
- keyboard buffer. See the chapter on keyboard definition and the
- KEYBSTACK keyword for more info.
-
- Example: GOLDED @S A
-
- Makes GoldED go to the area scanning menu <Alt-S>, and select scanning
- of <A> all areas.
-
- See the Macros and Keystacking section, page 65, for more info.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- COMMANDLINE USAGE GoldED Manual, Page 7
-
-
- ──────────────────────────────────────────────────────────────────────
- 7. ENVIRONMENT VARIABLES
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED recognizes and uses several environment variables.
-
-
- GoldED specific environment variables
- ──────────────────────────────────────────────────────────────────────
-
- These are specifically for GoldED, no other program uses them.
-
- GOLDED Path to the GOLDED.CFG file. It is recommended to set
- this variable, but don't forget to change it if you move
- your GoldED setup to a different directory!
-
- GEDCMD Specifies additional commandline options. Use this if
- you want to specify options, but need to run GoldED
- without them (for example when renaming GOLDED.EXE to
- DBEDIT.EXE in older versions of D'Bridge). You can over-
- ride the environment options with commandline options.
-
- GOLDNODE The path where GoldNODE can find a GOLDED.CFG to use.
-
-
- Other environment variables
- ──────────────────────────────────────────────────────────────────────
-
- When reading areas from other program setups with the AREAFILE con-
- figuration keyword, GoldED can use these environment variables to find
- the location of the setup files.
-
- DB Path to the D'Bridge system files.
- DBRIDGE Path to the D'Bridge system files.
- DUTCHIE Path to the Dutchie system files.
- FASTECHO Path to the FastEcho system files.
- FD Path to the FrontDoor/TosScan system files.
- GE Path to the GEcho system files.
- IMAIL Path to the Imail system files.
- MAXIMUS Path to the Maximus and Squish system files.
- OPUS Path to the Opus system files.
- QBBS Path to the QuickBBS system files.
- RA Path to the RemoteAccess system files.
- RAECHO Path to the RA-Echo system files.
- SQUISH Path to the Squish system files.
- WMAIL Path to the Window Mail (WMAIL) system files.
-
- Please read the Area Configuration section for specific details of
- each supported AREAFILE type.
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- ENVIRONMENT VARIABLES GoldED Manual, Page 8
-
-
- ──────────────────────────────────────────────────────────────────────
- 8. ERRORLEVELS
- ──────────────────────────────────────────────────────────────────────
-
-
- To ease operation in batch files, GoldED operates with a set of
- errorlevel values.
-
- 100 QBBS Index errors. (See the QBBSREBUILD keyword).
- 004 Echomail entered.
- 002 Netmail entered.
- 001 Local mail entered.
- 000 Exit okay. No mail entered.
-
- Other values: Some other sort of error.
-
- Add values together to find the combined error levels. For example,
- error level 6 is returned if netmail (2) and echomail (4) was entered.
-
- In the distribution archive (inside ADVANCED.ARJ), there is a sample
- RUNGOLD.BAT, which provides a useful skeleton for automated operation
- using the errorlevels.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- ERRORLEVELS GoldED Manual, Page 9
-
-
- ──────────────────────────────────────────────────────────────────────
- 9. LOGFILE
- ──────────────────────────────────────────────────────────────────────
-
-
- If GoldED exits with an error, a GOLDED.LOG file is generated,
- specifying some debugging detail about the error situation. Please
- send cuttings from this log if you report bugs that causes a log to be
- generated.
-
- The log file is in the format used by the FrontDoor mailer, and the
- filename is defined with the LOGFILE keyword.
-
- Please note that the log contents may not make much sense to you, but
- it can provide me with important information about exactly where the
- error occurred and why. The error logging feature is current not as
- complete or "smart" as I'd like it, but hey, I need something to do in
- the future too :-)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- LOGFILE GoldED Manual, Page 10
-
-
- ──────────────────────────────────────────────────────────────────────
- 10. NODELISTS AND USERLISTS
- ──────────────────────────────────────────────────────────────────────
-
-
- In order to enable nodelist/userlist lookup and browsing, GoldED needs
- to use a set of special nodelist index files. This is taken care of
- with the GoldED nodelist compiler, GoldNODE.
-
- You may think - "Oh No! Not ANOTHER Nodelist Compiler!!!". Yes, unfor-
- tunately, and I'm very sorry about this, none of the existing types of
- nodelist indexes were sufficiently useful or documented, so I had to
- create my own format, and a compiler for it. My index is "moderately"
- sized, a bit smaller than the nodelist itself. We can only hope that
- some day there will be a binary nodelist format which can be used by
- most or all of the FidoNet developers, but that day has yet to come.
-
- GoldED normally uses and displays information from the nodelist when
- browsing, but it doesn't really need the nodelist for anything. The
- index files contains sufficient information for lookup and browsing of
- names or addresses. This means that you can delete or pack away the
- nodelists and/or userlists after compiling with GoldNODE, if you want
- to save space and you don't need them for anything else.
-
-
- Command line syntax: GOLDNODE [-options] [configfile]
-
- The [-options] are:
-
- -C Conditional compile.
- -D Remove duplicate nodes from index.
- -F Forced compile.
- -M<nodes> Compile max <nodes> nodes (maximum is 32767).
- -NE Disable the use of EMS memory.
- -NX Disable the use of XMS memory.
- -S<size> Set the max size of names. Normally not used.
- -U<file> Create sorted FIDOUSER.LST userlist file.
-
- The [configfile] is the path AND filename of the GOLDED.CFG confi-
- guration file to read. If no filename is given, the path specified
- with the GOLDNODE or GOLDED environment variables are used.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- NODELISTS AND USERLISTS GoldED Manual, Page 11
-
-
- ──────────────────────────────────────────────────────────────────────
- 11. CONFIGURATION KEYWORD REFERENCE
- ──────────────────────────────────────────────────────────────────────
-
-
- This is an alphabetical list of all the configuration keywords used in
- the main GoldED configuration file.
-
- The following special symbols are used in the keyword parameter lists:
-
- () Default value.
- [] Optional parameter.
- <> Required parameter, not optional.
- "" Parameter must be inclosed in quotes ("").
- / Separates mutually exclusive values.
- , Separates possible values for the keyword.
-
-
- ADDRESS <zone:net/node[.point][@domain][, pointnet]>
- ──────────────────────────────────────────────────────────────────────
- Your network address, FidoNet-style. More than one address can be
- specified if you are member of more than one network.
-
- If a pointnet is specified with a point address, GoldED will use
- the so-called "3D" addressing method in netmail msgs, otherwise
- the "4D" method is used. The 3D method works by putting the
- address ZONE:POINTNET/POINT.0 in the msg header, instead of the 4D
- format ZONE:NET/NODE.POINT. Most modern mailers and mail proces-
- sors now supports the 4D format, but if you are a point, you
- should always consult your Boss about which format to use.
-
- The optional @domain part can be used to specify a "fifth" dimen-
- sion to the 4D address. It is normally not necessary to specify a
- domain.
-
- NOTE: Because of design limitations of the msg header display,
- GoldED currently doesn't support domains as well as it should. If
- the combined length of the address + domain exceeds the address
- field width, GoldED will chop off characters at the end of the
- domain name..
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 12
-
-
- ADDRESSMACRO <macro>,<name>,<address>[,subject]
- ──────────────────────────────────────────────────────────────────────
- Defines a short name for often used addresses. Typical uses are
- for your uplink, boss, points or others you write to often. To use
- a defined address macro, you just type it where you would normally
- type the name or an address to lookup.
-
- Examples:
-
- af116,AreaFix,2:231/116,password
- ff116,FileFix,2:231/116,password
- odin,Odinn Sorensen,2:231/77,GoldED - What else? :-)
-
- A special format is supported for UUCP or INTERNET gateways. The
- special format is indicated with a (@) as the first character in
- the <name>.
-
- jfu,@fallesen@diku.dk,2:310/33
- dn,@INTERNET/david@csource.oz.au,2:241/999
-
- In the first example, GoldED would put "UUCP" (the default gateway
- name) in the TO: msg header field and "TO: fallesen@diku.dk" on
- the first line of the message text.
-
- In the second example, GoldED would put "INTERNET" in the TO:
- field, and "TO: david@csource.oz.au" in the message. The forward
- slash (/) separates the gateway name from the receiver address.
- Any gateway name may be used.
-
- The address macros can also be specified in an external file, like
- the NAMES.FD file supported by the FrontDoor mailer/editor. See
- the keyword NAMESFILE for details.
-
- AKA <zone:net/node[.point][@domain][, pointnet]>
- ──────────────────────────────────────────────────────────────────────
- See ADDRESS. AKA is simply another name for the ADDRESS keyword.
-
- AKA is short for Also Known As.
-
- AKAMATCHECHO <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will attempt to match one of your akas to the
- address of the person you are replying to in echomail areas.
-
- Normally it is not desirable to enable aka matching in echomail,
- because some echoes may be restricted to members of one particular
- network, and an accidental wrong aka matching may attract unwanted
- attention from the moderator or the compulsive flamers :-)
-
- AKAMATCHNET <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will attempt to match one of your akas to the
- address of the person you are replying to in netmail areas.
-
- This is especially useful if you are a member in more than one
- network, and therefore have more than one address.
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 13
-
-
- AKAMATCHLOCAL <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will attempt to match one of your akas to the
- address of the person you are replying to in local areas.
-
- It doesn't really make sense to do aka matching in local areas.
- The keyword is just there for completeness, if nothing else.
-
- AREA <echoid> <"desc"> <msgbase>[type] <loc> [akano] [attrs]
- ──────────────────────────────────────────────────────────────────────
- This keyword defines a mail area in GoldED. You need to define at
- least one mail area to run GoldED, or use the AREAFILE keyword to
- read the area setup of your mailer, mail processor or BBS.
-
- <echoid> Area id string, for example C_ECHO, INTERUSER, etc.
- <"desc"> Verbose description of the area.
- <msgbase> Msgbase type used for the area.
- [type] Echomail, Netmail or Local area.
- <loc> Location of msgbase. A path, file or board number.
- [akano] Aka number to use.
- [attrs] Attributes for the area.
-
- This keyword is explained in greater detail in the Area Configura-
- tion section, page 44.
-
- AREAAUTONEXT <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will automatically jump to the first marked
- area in the arealist on startup, and the next marked area after
- exiting from an area you have been reading.
-
- AREAEXCL <echoid mask>
- ──────────────────────────────────────────────────────────────────────
- With this keyword, you can define the echoids of areas which
- should be ignored by GoldED (thereby leaving them out of the
- arealist). This is normally used in connection with AREAFILE, to
- exclude areas you are not interested in reading. DOS/4DOS-style
- wildcards (* and ?) can be used in the echoid mask.
-
- Examples:
-
- AREAEXCL * Excludes all areas.
- AREAEXCL *INTER* Excludes all areas containing "INTER"
- anywhere in the echoid.
- AREAEXCL INT*.* Excludes all areas beginning with
- "INT" and containing a '.' anywhere
- in the echoid.
-
- You can use the AREAINCL keyword to re-include areas which have
- been excluded with AREAEXCL.
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 14
-
-
- AREAFILE <type> [path/file] [switches]
- ──────────────────────────────────────────────────────────────────────
- GoldED can read the area setup of many popular mailers, mail
- processors and BBS'es, thereby making it much easier and simpler
- to configure GoldED for the mail areas you receive, by eliminating
- the need to write AREA lines for all or most of your areas.
-
- <type> Name of the program.
- [path/file] Filename or path to the area setup files.
- [switches] Msgbase specific switches.
-
- For most programs, GoldED can automatically find the path or
- filename using environment variables. By default, GoldED will look
- for the area setup files in the AREAPATH.
-
- There are switches for sorting the areas, and for turning off an
- update-check when GoldED starts up.
-
- This keyword is explained in greater detail in the Area Configura-
- tion section, page 44.
-
- AREAFILEGROUPS <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- In some AREAFILE setups, you can groups the areas using single
- letters (A-Z). If this keyword is enabled, GoldED will use the
- area groupid letter instead of the area echoid when gathering area
- specific information from the Random System.
-
- If this keyword is enabled, you should setup matching GROUP's in
- GOLDRAND.CFG. See the Random System section page 49, for details.
-
- AREAINCL <echoid mask>
- ──────────────────────────────────────────────────────────────────────
- With this keyword, you can define the echoids of areas which
- should be re-included by GoldED, if they have been excluded with
- the AREAEXCL keyword. DOS/4DOS-style wildcards (* and ?) can be
- used in the echoid mask.
-
- Examples:
-
- AREAINCL * Includes all areas.
- AREAINCL *INTER* Includes all areas containing "INTER"
- anywhere in the echoid.
- AREAINCL INT*.* INcludes all areas beginning with
- "INT" and containing a '.' anywhere
- in the echoid.
-
- AREALISTNOS <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will display the board numbers of QBBS-type
- areas in the arealist instead of the default sequential numbers.
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 15
-
-
- AREALISTSORT <sortspec>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines how the area list should be sorted. You can
- override the default setting from the commandline with the -S
- switch.
-
- The <sortspec> can be composed of the following types:
-
- A Sort by aka.
- B Sort by board number.
- D Sort by description.
- E Sort by echoid.
- G Sort by group (if any).
- O Sort by original order.
- T Sort by type (in the order net, echo, local).
- U Sort by unread messages (try it!).
- - Descending sort (largest first).
- + Ascending sort (smallest first) (default).
-
- Example:
-
- AREALISTSORT T-U+E
-
- This sorts ascending by Type, descending by Unread (that is, areas
- with the most unread messages comes first) and ascending by Echoid
- (in case two areas have the same number of unread msgs).
-
- By default no sorting is done, and all areas are listed in the
- order they were found (unless sorting was specified with an
- AREAFILE keyword). However, the configuration examples all make
- use of the Unread sorting type. This is a very useful way of
- sorting areas, because it keeps all the areas with mail together.
-
- AREALISTTYPE <new/last> (new)
- ──────────────────────────────────────────────────────────────────────
- Defines the contents of the 4th column (the one after the "Total"
- column).
-
- New Displays the amount of new (unread) msgs.
- Last Displays the number of the last msg read.
-
- AREAPATH <path>
- ──────────────────────────────────────────────────────────────────────
- If you use the AREAFILE keyword, GoldED will need to know where
- the area setup files are located. This keyword specifies where
- they are found, if not current directory.
-
- NOTE: Some AREAFILE types can find the path using the environment
- variable(s) specific for the program(s). Such environment
- variables (or a path specified with the AREAFILE definition)
- always overrides the AREAPATH.
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 16
-
-
- AREARENAME <from echoid> <to echoid>
- ──────────────────────────────────────────────────────────────────────
- Renames one echoid to another. The feature is meant to be used in
- connection with AREAFILE, where some types do not store echoids
- with the areas (and GoldED then automatically gives them unique
- echoids).
-
- Examples:
-
- AREARENAME LOCAL001 BBS.USERS
- AREARENAME NETMAIL001 NETMAIL
- AREARENAME ECHOMAIL001 BAD_MSGS
-
- AREASCAN <echoid mask>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines areas which will be automatically scanned
- when starting GoldED. DOS/4DOS-style wildcards (* and ?) can be
- used in the echoid mask.
-
- Examples:
-
- AREASCAN * Scan all areas.
- AREASCAN *INTER* Scan all areas containing "INTER"
- anywhere in the echoid.
- AREASCAN INT*.* Scan all areas beginning with "INT"
- and containing a '.' anywhere in the
- echoid.
-
- AREASCAN only works for areas in the Squish or *.MSG flavors.
- Areas in the QBBS flavor are always automatically scanned in any
- case.
-
- AREASTART <echoid>
- ──────────────────────────────────────────────────────────────────────
- Normally GoldED starts by displaying the arealist, to let you
- select which area you want to read. If this keyword is defined,
- the arealist is bypassed and GoldED starts directly in the con-
- figured area. You can override AREASTART with the -E commandline
- switch.
-
- ASKDELORIG <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, you will be asked if the message you just replied to
- should be deleted. Otherwise it is left untouched.
-
- This keyword is only functional in netmail and local areas.
-
- ATTRIBSCC <attributes>
- ──────────────────────────────────────────────────────────────────────
- Defines the default attributes of Carbon Copy messages. CC at-
- tributes are *added* to the existing attributes of the original
- message. Usually used to add the Kill/Sent attribute.
-
- See appendix A for valid attributes.
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 17
-
-
- ATTRIBSCFM <attributes>
- ──────────────────────────────────────────────────────────────────────
- Defines the default attributes of the Confirmation Receipt mes-
- sage.
-
- See appendix A for valid attributes.
-
- ATTRIBSECHO <attributes>
- ──────────────────────────────────────────────────────────────────────
- Defines the default attributes of msgs entered in echomail areas.
-
- See appendix A for valid attributes.
-
- ATTRIBSLOCAL <attributes>
- ──────────────────────────────────────────────────────────────────────
- Defines the default attributes of msgs entered in local areas.
-
- See appendix A for valid attributes.
-
- ATTRIBSNET <attributes>
- ──────────────────────────────────────────────────────────────────────
- Defines the default attributes of msgs entered in netmail areas.
-
- See appendix A for valid attributes.
-
- BEEPCOMMENT <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will make a noise when the cursor in the
- internal editor is moved across a word defined with the EDITCOM-
- MENT keyword.
-
- BEEPFACTOR <value> (5)
- ──────────────────────────────────────────────────────────────────────
- The value changes the "gwynk" noise made by the BEEPCOMMENT,
- BEEPLOCALMSG and BEEPYOURMAIL keywords.
-
- The "gwynk" noise is dependent on speed of the computer, so a low
- value is best for XT's and AT's, while larger values may be better
- for 386's and 486's. Experiment with different values until you
- find a good one.
-
- BEEPLOCALMSG <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will make a noise if it finds a msg with the
- "Local" (LOC) attributes set. This can be useful for the sysop who
- wants to monitor the msgs entered by users on his/her BBS.
-
- A related keyword is DISPLOCALHIGH.
-
- BEEPNOISES <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED makes appropriate noises (beeps, "gwynks" or
- small melodies) when it wants attention.
-
- NOTE: This is the "master switch" for all noises in GoldED.
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 18
-
-
- BEEPYOURMAIL <yes/no/always> (yes)
- ──────────────────────────────────────────────────────────────────────
- If set to "yes", GoldED will make a noise if it finds a non-
- received message to one of your USERNAME's. If set to "always",
- GoldED will make the noise even if it has already been marked as
- received.
-
- CARBONCOPYLIST <listspec> (Names)
- ──────────────────────────────────────────────────────────────────────
- This specifies the format of the Carbon Copy list, as it will look
- after processing. You can also change the format in the CC menu
- before processing.
-
- The <listspec> can be one of the following:
-
- Keep Keep the list as entered.
- Names Convert list to "CC: Name, Name, Name.." format.
- Visible Convert list to "CC: Name Address" format.
- Hidden Convert list to "^aCC: Name Address" format.
- Remove Remove the list completely.
-
- More details can be found in the Carbon Copy and Crossposting
- section, page 76.
-
- COLOR <colorspec>
- ──────────────────────────────────────────────────────────────────────
- Using this keyword you can define or redefine all the colors used
- in GoldED.
-
- The Color Configuration section, page 46, has the details.
-
- A complete color setup consists of a quite a lot of COLOR key-
- words, and it is normal practice to put them in a separate .CFG
- file and use the INCLUDE keyword to read it. The COLORS.ARJ
- archive contains a number of example color/mono setups. Try them
- out if you think the default colors stink :-)
-
- COLORSET <Normal/Intense/Mono> (Normal or Mono)
- ──────────────────────────────────────────────────────────────────────
- Three color setups are built-in, and can be selected with this
- keyword.
-
- The Normal set is the default when a color display adapter is
- detected. The Normal set has all black background, with bright
- colors for the window frames. Some hate it, some love it :-)
-
- The Intense set switches off the "blink" attribute, thereby
- enabling the use of intense (bright) colors for the background
- ("paper") colors as well as the foreground ("ink") colors. This is
- used in the Intense set to make a bright white background, sort of
- like the standard Windows 3.0 setup.
-
- The Mono set is the default for monochrome adapters.
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 19
-
-
- CONFIRMFILE <filename> (GOLDED.CFM)
- ──────────────────────────────────────────────────────────────────────
- GoldED supports the Confirmation Receipt attribute, as used in
- FrontDoor 2.xx with the FLAGS CFM kludge. If GoldED finds an
- unreceived message to one of your USERNAME's with the CFM (or the
- RRQ Return Receipt Request) attribute set, it generates an auto-
- matic response message from the content of the CONFIRMFILE. In the
- file you can use many of the template tokens to personalize the
- automatic message. You can specify the default attributes for the
- message with the ATTRIBSCFM keyword.
-
- Tokens are explained in the Message Template section, page 54.
-
- CROSSPOSTLIST <listspec> (Verbose)
- ──────────────────────────────────────────────────────────────────────
- This specifies the format of the Crosspost list, as it will look
- after processing.
-
- The <listspec> can be one of the following:
-
- None Crosspost without a list in the msgs.
- Verbose Change the list to lines of "* Crossposted in ..."
- Raw Keep the crosspost list as you entered it.
-
- More details can be found in the Carbon Copy and Crossposting
- section, page 76.
-
- CTRLINFOECHO <Tearline,Origin,yes/no> (Tearline Origin)
- ──────────────────────────────────────────────────────────────────────
- Specifies if you want tearline and origin in your echomail mes-
- sages. They will be added by your echomail processor, if you
- disable them here.
-
- Examples:
-
- CTRLINFOECHO Tearline Origin ; Add both tearline and origin.
- CTRLINFOECHO Tearline ; Add only a tearline.
- CTRLINFOECHO Origin ; Add only an origin.
-
- Note that if you use the last example, your mail processor may get
- confused. However, most modern mail processors *can* handle msgs
- without a tearline.
-
- CTRLINFOLOCAL <Tearline,Origin,yes/no> (Tearline Origin)
- ──────────────────────────────────────────────────────────────────────
- Specifies if you want tearline and origin in your messages in
- local areas. In local areas, the tearline and origin is normally
- never required, and can be used for cosmetic purposes if nothing
- else.
-
- Examples:
-
- CTRLINFOLOCAL Tearline Origin ; Add both tearline and origin.
- CTRLINFOLOCAL Tearline ; Add only a tearline.
- CTRLINFOLOCAL Origin ; Add only an origin.
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 20
-
-
- CTRLINFONET <Tearline,Origin,yes/no> (Tearline)
- ──────────────────────────────────────────────────────────────────────
- Specifies if you want tearline and origin in your netmail mes-
- sages. In netmail areas, the tearline and origin is normally never
- required, and can be used for cosmetic purposes if nothing else.
-
- Examples:
-
- CTRLINFONET Tearline Origin ; Add both tearline and origin.
- CTRLINFONET Tearline ; Add only a tearline.
- CTRLINFONET Origin ; Add only an origin.
-
- DISPAUTONEXT <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will automatically jump to the next message
- when entering an area.
-
- DISPLISTWRAP <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- Enables/disables wrap-round when the selection bar in the main
- list/browser windows reaches the top or bottom.
-
- DISPLOCALHIGH <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will display the FROM name with the highlight
- color, if a message has the Local (LOC) attribute set.
-
- A related keyword is BEEPLOCALMSG.
-
- DISPMARGIN <width> (0)
- ──────────────────────────────────────────────────────────────────────
- This is the right margin (display width) used for message display.
- If the value is 0 (zero), GoldED will default to the current
- screen width. If a negative value is specified, that value will be
- added to the current screen width (thereby decreasing the display
- width relative to the screen width).
-
- If the DISPPAGEBAR keyword is enabled, the right margin is auto-
- matically decreased by one char.
-
- DISPPAGEBAR <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, a "pagebar" (sort of like the scrollbar in GUI's) will
- appear on the right margin, telling you about the relative size
- and position in the message you are reading.
-
- The pagebar decreases the DISPMARGIN by one char.
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 21
-
-
- DISPREALMSGNO <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- GoldED can display the message numbers in two ways:
-
- 1. As the actual (real) msg numbers.
- 2. As "relative" numbers, which are always sequential.
-
- Normally the relative numbers are best, because they reflect the
- actual number of msgs in the system.
-
- DISPREPLIESMODE <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- * Reserved for future implementation! *
-
- DISPTABSIZE <chars> (8)
- ──────────────────────────────────────────────────────────────────────
- The tab size (number of spaces) used when displaying the tab
- (ASCII 9) character, and when pressing <Tab> in the internal
- editor.
-
- If you use an external editor, you should switch it to create
- spaces instead of tabs, because tabs are technically not allowed
- in FidoNet technology messages.
-
- DOSPROMPT (yes/no) (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will add a message about itself to the DOS
- prompt when shelling out.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 22
-
-
- DOSSWAP <yes/no,xms,ems,disk,hide,checknet,noprealloc> (no)
- ──────────────────────────────────────────────────────────────────────
- With this keyword you can specify what storage devices the swapper
- should try or use, and what order to try them in.
-
- The YES parameter tells the swapper to try XMS, EMS, DISK in that
- order, and NO tells it not to swap at all (this will leave the
- main part of GoldED in memory, and give you little room in the DOS
- shell).
-
- You can specify your own order, such as "DOSSWAP EMS, XMS, DISK",
- which makes it try it in that order, or "DOSSWAP EMS, DISK", which
- makes it ignore XMS.
-
- If disk swapping is used, the swap file will be placed in the
- SWAPPATH.
-
- These parameters modify the disk swapping behaviour:
-
- HIDE Hides the swapfile, if diskswapping is used.
- CHECKNET For some reason, disk swapping is slower if running
- on a (Novell) network without this.
- NOPREALLOC Use this if you are always running on a network
- (instead of enabling CHECKNET).
-
- IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT
-
- Some programs use extended memory in ways that may conflict
- with the XMS extended memory driver, causing inexplicable
- crashes. If you have problems, you should first try turning
- off the OVERLAY keyword, and if it still fails, turn off
- DOSSWAP (or stop using those other programs :-)
-
- EDITAUTOATTACH <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, and you use drivespec (C:, D:, etc.) in the subject in
- a netmail message, GoldED will automatically turn on the file
- attach attribute. Autoattaching only works if the subject has been
- edited, so that subject files will not automatically be re-at-
- tached in replies.
-
- EDITAUTOSAVE <seconds> (30)
- ──────────────────────────────────────────────────────────────────────
- If a non-zero value is given, the internal editor will automati-
- cally execute the EDITsavefile function with intervals of
- <seconds>. Good for keeping automatic backup of the message you
- are writing. The saved file can be restored with the EDITloadfile
- command. The name of the saved file is defined with the EDITORFILE
- keyword.
-
- If disaster strikes (power blackout, etc.) while you are writing a
- message in the internal editor, this feature lets you continue
- from the last autosaved message, which will popup automatically
- when you enter the internal editor again.
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 23
-
-
- EDITCHANGEDATE <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will always "touch" the message date in the
- header, if you change a message after saving it.
-
- You should always have this enabled.
-
- EDITCOMMENT <"word"> <"comment">
- ──────────────────────────────────────────────────────────────────────
- This feature has no serious use at all :-)
-
- It allows you to define words which causes GoldED to display a
- comment in the statusline, when you place the cursor on the word
- in the internal editor.
-
- Example:
-
- EDITCOMMENT ";-)" "Wink wink, nudge nudge!"
- EDITCOMMENT "!!!" "!!! Flame Warning !!!"
-
- Have fun with it!
-
- EDITCRLFTERM <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, all text paragraphs in your messages will be ter-
- minated with a CR/LF combination. If disabled, only a single CR is
- used. This option was created to fix a problem with an older
- version of the Dutchie mail processor, that apparently needed the
- CR/LF termination of kludge lines.
-
- EDITFIELDCLEAR <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, the input-fields will be automatically cleared for new
- entry, if a non-edit key is the first key pressed.
-
- EDITHARDLINE <string> ("<<")
- ──────────────────────────────────────────────────────────────────────
- The string is needed if you use an external editor that terminates
- all lines with a CR or CR/LF. The hardline string acts as a text
- paragraph terminator, and the normal CR's are ignored.
-
- The concept of "hardlines" is explained in the Hardline Feature
- section, page 73.
-
- EDITHARDLINES <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- This keyword enables the "hardline" feature. If disabled, the
- EDITHARDLINE string is never written to the editor message file,
- and the editor message file is read back exactly as entered,
- including terminating CR's on all lines.
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 24
-
-
- EDITINTERNAL <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- Specifies if the internal editor should be the default, even if an
- external editor is defined. You can always change the setting in
- the editor menu (if EDITMENU is enabled) before you start writing
- your message.
-
- EDITMENU <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- This keyword enables or disables the "Edit menu" that pops up
- right after you have edited the message header. If you disable the
- menu, you will go to the internal or external editor immediately
- and save a keystroke, but you will of course lose the features
- available from the menu.
-
- EDITMIXCASE <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If this keyword is enabled, GoldED will automatically format the
- name with uppercase the first letter in words and lowercase the
- rest, when entering names in the header.
-
- Example:
-
- "odinn sorensen" or "ODINN SORENSEN"
-
- .. is re-cased to "Odinn Sorensen".
-
- EDITMSGSIZE <bytes> (65530)
- ──────────────────────────────────────────────────────────────────────
- This lets you limit the size of loaded msgs. GoldED currently
- cannot handle msgs larger than 64k. This keyword ensures that the
- system will not get confused and possibly crash or exit, if a
- message was encountered that was larger than 64k.
-
- EDITOR <commandline> [@file] [@line]
- ──────────────────────────────────────────────────────────────────────
- With GoldED it is possible to use your favorite text editor or
- even word processor to write messages. With this keyword you
- specify the commandline for the editor.
-
- If you use a word processor, be sure to make it export clean ASCII
- text files without control codes. You may also need to enable the
- DOSSWAP keyword, if the editor or word processor requires a lot of
- free memory to run.
-
- <commandline> Program commandline.
- @file Token which is replaced by the editor message file-
- name.
- @line Token which is replaced by the @Position template
- line number.
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 25
-
-
- EDITORFILE <file> (GOLDED.MSG)
- ──────────────────────────────────────────────────────────────────────
- Defines the name of the temporary editor message file. This file
- is written by GoldED when swapping to the external editor, or when
- using the EDITsavefile command in the internal editor.
-
- If no path is specified, the TEMPPATH is used.
-
- EDITREPLYRE <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED inserts the "RE:" string in front of the
- subject when you reply to a message. If not enabled, GoldED will
- strip any leading "RE:" when you reply to a msg.
-
- The "RE:" string in subjects is an obsolete practice, and today
- only slows down modern replylinking software. Do yourself and
- others a favor and let GoldED strip the RE: in your replies.
-
- EDITSAVEMENU <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- This keyword enables or disables the "Save menu" that pops up
- after you have edited your message in the internal or external
- editor. If you disable the menu, your message will be saved (or
- discarded if not edited) immediately and save you a keystroke, but
- you will also lose the features available from the menu.
-
- EDITSPELLCHECK <commandline> [@file]
- ──────────────────────────────────────────────────────────────────────
- While in the internal editor, you can use the EDITspellcheck
- command to save your message to a file and shell to external
- spellchecking software. When the check is completed, the corrected
- file is read back and you can continue editing your message. The
- EDITspellcheck command internally uses the EDITsavefile and
- EDITloadfile commands.
-
- <commandline> Spellchecker program commandline.
- [@file] Token which is replaced by the message filename
- (defined by the EDITORFILE keyword).
-
- EDITUNDELETE <lines> (50)
- ──────────────────────────────────────────────────────────────────────
- This keyword defines the number of lines to keep in the undelete
- buffer between messages.
-
- EMPTYTEARLINE <yes,no> (no)
- ──────────────────────────────────────────────────────────────────────
- With this keyword enabled, GoldED will always strip the tearline
- down to just the three dashes, "---", and instead inserts the PID
- (Product IDentification) kludge line, which contains the same
- information, but in a safer form in a safer place. The PID kludge
- is proposed in FidoNet document FSC-0046.
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 26
-
-
- EXCLUDENODES <addressmask>
- ──────────────────────────────────────────────────────────────────────
- You can define up to 50 different addressmasks to be excluded from
- the compiled nodelists. Use this if you are short of space, or the
- nodelist compile takes very long on your system. This keyword is
- used by GoldNODE, and must be present in the main GOLDED.CFG file
- (not in INCLUDE'ed .CFG's).
-
- <addressmask> See Appendix B for valid addressmasks.
-
- Excluded nodes can be re-included with the INCLUDENODES keyword.
-
- FIDOHWMARKS <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will use the echomail "highwater mark" (1.MSG)
- to determine if a message is "sent" or "unsent".
-
- NOTE: Some older echomail processors do not update the highwater
- mark in a way that GoldED can recognize. If all messages appear to
- marked "Uns", even after the mail has been scanned out, try
- turning off this keyword.
-
- This keyword only works in echomail areas of the *.MSG flavor.
-
- FIDOLASTREAD <file> (LASTREAD.)
- ──────────────────────────────────────────────────────────────────────
- Defines the filename of the lastread files. DO NOT specify a path.
-
- This keyword only works in areas of the *.MSG flavor.
-
- FIDOLASTREADNO <userno> (0)
- ──────────────────────────────────────────────────────────────────────
- This is an index into the FIDOLASTREAD file. Each user occupies 4
- bytes in the lastread file.
-
- This keyword only works in areas of the *.MSG flavor.
-
- FILEALIAS <alias> <filename>
- ──────────────────────────────────────────────────────────────────────
- Used to define short alias names for filenames. If you regularly
- write msgs to different files in different paths, this feature is
- very useful, and reduces the risk of typing wrong.
-
- Example:
-
- FILEALIAS DKB R:\DKBBS\DKBBS
-
- With this file alias, I can simply write "DKB" at the filename
- prompt, and the long filename will be used.
-
- FREETEAR <echoid> (MAGNA)
- ──────────────────────────────────────────────────────────────────────
- This keyword only works for UN-registered users. It defines one
- area in which you are allowed to have a userdefined (with the
- TEARLINE keyword) or a random tearline (using the Random System).
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 27
-
-
- GOLDHELP <file> (GOLDHELP.CFG)
- ──────────────────────────────────────────────────────────────────────
- Defines the name of the help system definition file.
-
- GOLDKEYS <file> (GOLDKEYS.CFG)
- ──────────────────────────────────────────────────────────────────────
- Defines the name of the keyboard configuration file.
-
- GOLDLANG <file> (GOLDLANG.CFG)
- ──────────────────────────────────────────────────────────────────────
- Defines the name of the language definition file.
-
- GOLDPATH <path>
- ──────────────────────────────────────────────────────────────────────
- This is the path where GoldED finds all it's control files. It is
- not necessary to define this, unless you have special needs. The
- GOLDPATH defaults to directory where the GOLDED.CFG file was
- found.
-
- GOLDRAND <file> (GOLDRAND.CFG)
- ──────────────────────────────────────────────────────────────────────
- Defines the name of the Random System configuration file.
-
- GOLDXLAT <file> (GOLDXLAT.CFG)
- ──────────────────────────────────────────────────────────────────────
- * Reserved for future use! *
-
- IGNORE
- ──────────────────────────────────────────────────────────────────────
- This tells the configuration file reader to ignore all subsequent
- lines until another IGNORE keyword is encountered. Useful for
- testing and quickly switching portions of configuration.
-
- INBOUNDPATH <path> (defaults to GOLDPATH)
- ──────────────────────────────────────────────────────────────────────
- The inbound path is currently only used in connection with the
- file request feature (the READfilerequest command, <Ctrl-F>). If
- you use this feature, GoldED will put the file descriptions into a
- FILES.BBS in the inbound path, ready for when the requested files
- are moved to the correct file areas.
-
- INCLUDE <file>
- ──────────────────────────────────────────────────────────────────────
- This tells the configuration file reader to stop reading the
- current .CFG file, and start reading the <file> as an extra
- configuration file, then resume reading the previous .CFG. The
- INCLUDE filenames are stored and their timestamps are checked when
- GoldED is started. INCLUDE files can be nested without any (fo-
- rmal) limit.
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 28
-
-
- INCLUDENODES <addressmask>
- ──────────────────────────────────────────────────────────────────────
- You can define up to 50 different addressmasks to be included from
- the compiled nodelists. This is only used in conjunction with the
- EXCLUDENODES keyword to include otherwise EXcluded nodes. This
- keyword is only used by GoldNODE, and must be present in the main
- .CFG file (not in INCLUDE'ed .CFG's).
-
- <addressmask> See Appendix B for valid masks.
-
- INTENSECOLORS <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- GoldED is capable of switching off the "blink" color, and thereby
- enabling the use of bright background (paper) colors. Enable this
- keyword, and try out one of the intense color setup examples.
-
- INVALIDATE <type> <"findstring"> <"replacestring">
- ──────────────────────────────────────────────────────────────────────
- This is used to invalidate (change) certain control strings in
- quoted text. Use this in conjunction with D'Bridge or other
- software that chokes on control strings in quoted text. As an
- added bonus feature, if the tearline or origin is invalidated to a
- null string (""), they will not be quoted at all.
-
- The <type> can be one of the following:
-
- Tearline Invalidate tearline ("---").
- Origin Invalidate origin (" * Origin: ").
- Seenby Invalidate SEEN-BY's.
-
- By default, the following invalidations are used:
-
- "---" "-+-"
- " * Origin: " " + Origin: "
- "SEEN-BY" "SEEN+BY"
-
- KEYBCLEAR <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- Tells GoldED whether or not to clear the keyboard buffer on
- startup. This also clears KEYBSTACK or commandline key stuffing.
- In older versions of GoldED, it was necessary to enable this
- keyword if you had renamed GOLDED.EXE to DBEDIT.EXE. This version
- detects the .EXE renaming and automatically enables KEYBCLEAR,
- regardless of the configuration setting.
-
- KEYBEXT <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will use extended bios calls to read the
- keyboard. With the extended keyboard, you can use keys like
- <Alt-Left>, <Alt-Home> and other extended keys. If you don't have
- an extended keyboard, don't despair - using a few neat tricks, I
- have made it possible to use the extended keys even with a non-
- extended keyboard.
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 29
-
-
- KEYBSTACK <keystring>
- ──────────────────────────────────────────────────────────────────────
- With this keyword, you can "stack" keys in the keyboard buffer.
- The KEYBSTACK can be overridden by commandline keystacking, which
- uses the same syntax.
-
- The <keystring> can be a mixture of the following:
-
- ^Char Ctrl-key (^Letter).
- ~Char Ctrl-key (~Letter). (Use this with 4DOS!).
- @Key Alt-key (@Number or @Letter).
- Char Literal character.
- "String" String, enclosed in double quotes.
- 'String' String, enclosed in single quotes.
- Number Keyboard scan code (decimal).
- ! Clear keyboard buffer.
-
- Whitespace (space and tab) is ignored, except in quoted strings.
-
- See the Macros and Keystacking section, page 65, for more info.
-
- LOGFILE <file> (GOLDED.LOG)
- ──────────────────────────────────────────────────────────────────────
- Defines the name of the GoldED logfile. The logfile uses the
- FrontDoor format, and is currently only generated/appended if
- GoldED exits with an error.
-
- LOOKUPECHO <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will use nodelist lookup when entering the TO:
- name in msgs in echomail areas.
-
- LOOKUPLOCAL <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will use nodelist lookup when entering the TO:
- name in msgs in local areas.
-
- LOOKUPNET <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will use nodelist lookup when entering the TO:
- name in msgs in netmail areas.
-
- MAPDRIVE <server driveletter> <local driveletter>
- ──────────────────────────────────────────────────────────────────────
- If your system is running on a network, you might have your
- mailer, mail processor and other software running on the server,
- while GoldED is running locally on another machine on the network.
- In such a case, the drive specification (C: etc) on the server
- will probably not match those of the local machine. If you are
- file attaching or reading area config from the mailer or mail
- processor on the server with AREAFILE, the drives would be all
- wrong. This problem is solved by using MAPDRIVE to remap the drive
- letters in GoldED.
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 30
-
-
- MOUSE <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- The mouse support in GoldED is only partially functional, so this
- keyword is a bit of a joke...
-
- NAMESFILE <file> (NAMES.FD)
- ──────────────────────────────────────────────────────────────────────
- GoldED supports the "address macro" file supported by FrontDoor
- 1.99c and above. If no path is specified, the file is first
- searched for in the path from the "FD" environment variable and
- then the GOLDPATH, if the FD variable failed.
-
- The address macros are added *after* those defined with the
- ADDRESSMACRO keyword (if any) (see this for details on the for-
- mat).
-
- NETNAME <"string">
- ──────────────────────────────────────────────────────────────────────
- This is the "netname" that is placed in the originline, in front
- of the address.
-
- Example:
-
- NETNAME "FidoNet"
-
- Produces:
-
- * Origin: Whatever (FidoNet 2:231/77)
-
- NOTE: The netname is a non-standard practice and should not be
- used. The option is provided for use only in certain restricted
- conferences where being naughty with the tearline/origin is
- considered great fun :-)
-
- NODELIST <file> [zone/addr]
- ──────────────────────────────────────────────────────────────────────
- Here you define the nodelists that are used by GoldED and the
- companion nodelist compiler GoldNODE. The nodelists must generally
- be in the standard "St.Louis" nodelist format, but they can also
- contain FrontDoor/Version7 style Boss/Point extensions. The
- default zone is defined by the first ADDRESS or AKA, but can be
- overridden by adding the zone number or a full address after the
- filename. GoldED currently needs it's own special index files to
- use the nodelists. These index files are created by GoldNODE.
-
- <file> Nodelist file. If extension is numeric, the newest
- file with numeric extension is used.
- [zone/addr] Default zone or address for the nodelist (if no
- zone info is present in the list itself).
-
- See also the USERLIST keyword, and the Nodelist Browsing section,
- page 79.
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 31
-
-
- NODEPATH <path>
- ──────────────────────────────────────────────────────────────────────
- This is where GoldED and GoldNODE finds the nodelist files and
- indexes.
-
- ORIGIN <"string">
- ──────────────────────────────────────────────────────────────────────
- You can define many different origins for use in GoldED. You can
- select one of the defined origins from the Origin selection menu
- (the READchangeorigin keyword), which is also available from the
- EDITMENU and the EDITSAVEMENU.
-
- Leading and/or trailing spaces can be added by enclosing the
- origin string in quotes.
-
- NOTE: Origins defined in the Random System will always override
- the default origins defined with this keyword, except when select-
- ed from the EDITSAVEMENU menu.
-
- OUTBOUNDPATH <path>
- ──────────────────────────────────────────────────────────────────────
- * Reserved for future use! *
-
- OUTPUTFILE <file>
- ──────────────────────────────────────────────────────────────────────
- This is the default name of the file written using the
- READwritemsg command.
-
- OVERLAY <ems/ext/disk> (disk)
- ──────────────────────────────────────────────────────────────────────
- This keyword controls where GoldED places the overlay swap blocks.
- GoldED uses the Borland VROOMM dynamic overlays to decrease the
- resident executable code.
-
- See the DOSSWAP keyword for a warning note!
-
- PRINTDEVICE <devicename> (PRN)
- ──────────────────────────────────────────────────────────────────────
- Defines the name of the device used for printing. PRN is the
- default, but LPTx can also be used. Printers on COMx ports may
- also work, but this has not been tested.
-
- Devices are opened in Write-Only text mode. The function has been
- successfully tested to work with two popular peer-to-peer network
- packages.
-
- You should NOT use a filename as devicename. Use the filename
- option in the Write menu instead.
-
- PRINTFORMFEED <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- Used when printing messages. If enabled, it prints a Form Feed
- (12d) character after each message.
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 32
-
-
- PRINTINIT <printstring>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines the command string sent to your printer to
- initialize it before the actual printing.
-
- The <printstring> can contain items like these:
-
- $Hex A hexadecimal string.
- #Decimal A decimal (integer) number.
- "String" Text string, enclosed in double quotes.
- 'String' Text string, enclosed in single quotes.
- Other chars Ignored.
-
- PRINTLENGTH <lines> (65)
- ──────────────────────────────────────────────────────────────────────
- Defines the number of lines per page for printing. A formfeed is
- printed when every time PRINTLENGTH lines have been printed.
-
- PRINTMARGIN <characters> (80)
- ──────────────────────────────────────────────────────────────────────
- The right margin to use in printed messages.
-
- PRINTRESET <printstring>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines the command string sent to your printer to
- reset it after printing.
-
- <printstring> See the PRINTINIT keyword.
-
- QBBSINCRESCAN <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will regularly check the QBBS msgbase files,
- and incrementally rescan it if a change was detected (new msgs
- arrived).
-
- This keyword is only used with the QBBS msg flavor.
-
- QBBSPATH <path>
- ──────────────────────────────────────────────────────────────────────
- Specifies the directory where GoldED can find the QBBS-style mes-
- sage base files (MSG*.BBS, USERS.BBS, LASTREAD.BBS etc.).
-
- This keyword is only used with the QBBS msg flavor.
-
- QBBSREBUILD <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will rebuild the QBBS msgbase index files, if
- fatal errors were detected. If disabled, GoldED will exit with a
- specific errorlevel and log the cause.
-
- Fatal errors are mainly mismatched sizes of the MSGHDR/IDX/TOIDX
- files.
-
- This keyword is only used with the QBBS msg flavor.
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 33
-
-
- QUOTEBLANK <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will put the QUOTESTRING on blank lines in the
- quote. Otherwise blank lines are left blank in quotes.
-
- QUOTEMARGIN <chars> (-5)
- ──────────────────────────────────────────────────────────────────────
- The margin to which quotes are wrapped. A negative value means
- that the negative value is added to the DISPMARGIN.
-
- QUOTESPACING <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will automatically add blank lines before and
- after a block of quoted text, if none are present already. This
- usually improves the readability of some messages.
-
- QUOTESTRING <quotespec> (" FML> ")
- ──────────────────────────────────────────────────────────────────────
- With this keyword you define how you want the quotestring to look
- in your quoted replies.
-
- The <quotespec> can contain these characters:
-
- F Replaced with the first letter of the first name.
- M Replaced with the letters of the middle names.
- L Replaced with the first letter of the last name.
- > Required quote-char.
- ... As well as spaces.
-
- Other characters are allowed but *not* recommended.
-
- REGISTERKEY <keycode>
- ──────────────────────────────────────────────────────────────────────
- This keyword is only used in registered setups.
-
- REGISTERNAME <keyname>
- ──────────────────────────────────────────────────────────────────────
- This keyword is only used in registered setups.
-
- ROBOTNAME <name>
- ──────────────────────────────────────────────────────────────────────
- A "robot" is a program that responds automatically to netmail mes-
- sages - usually the robot links or unlinks echomail areas or
- distributed files.
-
- Examples of robot names are: AreaFix, AreaMgr, AreaLink, FileFix,
- GEcho, Raid, ImlaList, etc etc etc.
-
- If you write a netmail message where the TO: name is one of the
- robot names, GoldED will ignore any template definition, and give
- you a blank msg (possibly with a tearline) to edit.
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 34
-
-
- SCREENBLANKER <seconds> (180)
- ──────────────────────────────────────────────────────────────────────
- If non-zero, GoldED will blank the screen after the defined number
- of seconds, and put a small moving window up instead. Hitting any
- key (including shiftkeys) will return the screen to normal. If
- zero, no blanking is done.
-
- SCREENELIMSNOW <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- By default GoldED writes directly to the screen memory, but un-
- fortunately on older CGA display adapters, direct screen writes
- can produce harmless, but annoying "snow". If you can't live with
- that, enable this keyword. Note however, that this also slows down
- the screen updating drastically.
-
- SCREENMAXCOL <columns> (0)
- ──────────────────────────────────────────────────────────────────────
- On some systems, GoldED cannot detect the correct display size.
- With this keyword you can force a specific size. If zero, auto-
- detect is used.
-
- SCREENMAXROW <rows> (0)
- ──────────────────────────────────────────────────────────────────────
- On some systems, GoldED cannot detect the correct display size.
- With this keyword you can force a specific size. If zero, auto-
- detect is used.
-
- SCREENSHADOWS <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, all relevant windows and menus in GoldED will have
- shadows.
-
- SCREENSIZE <mode> (Auto)
- ──────────────────────────────────────────────────────────────────────
- Use this to force GoldED to use either 25 lines, 43/50 lines on
- EGA/VGA, or even special videomodes supported by your SuperVGA
- adapter (modes like 132x44 or 80x60).
-
- The <mode> can be one of the following:
-
- Auto Use detected size.
- 25 Switch to 25 lines.
- 4350 Switch to 43/50 lines.
- Mode <NN> Switch to videomode NN (hex).
-
- Please check your video adapter manual carefully before trying out
- the Mode option. SELECTING A WRONG MODE CAN DAMAGE YOUR MONITOR!!!
-
- SCREENUSEBIOS <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will use standard BIOS calls for screen up-
- dates. This is VERY slow, and should only be used if really
- needed. Normally GoldED uses direct screen writes.
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 35
-
-
- SEMAPHORE <type> <file>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines "semaphore" files, for use with other mailer
- and/or mail processing software.
-
- The <type> can be one of the following:
-
- QNETSCAN QBBS-style netmail scanning index file.
- QECHOSCAN QBBS-style echomail scanning index file.
- NETSCAN Empty netmail scan file (for D'Bridge/FD).
- ECHOSCAN Empty echomail scan file (for D'Bridge).
- EXPORTLIST Echoid-list of your new messages.
- IMPORTLIST Echoid-list of new imported messages.
-
- The semaphore files are placed in the AREAPATH, if no path is
- specified.
-
- See the example .CFG files for typical semaphore filenames.
-
- SHAREMODE <yes/no/mode#> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED opens all files in a SHARE.EXE compatible mode.
-
- The default share-mode is "Share, Deny none", but another may be
- specified directly if you give the mode number as the keyword
- parameter (decimal).
-
- You normally only need to enable this keyword if you are running
- GoldED in a network/multitasking environment with a BBS or other
- users accessing the same msgbase files.
-
- GoldED is compatible with the QBBS-msgbase sharing methods used by
- RemoteAccess, SuperBBS and probably most other modern QBBS-com-
- patible BBS software.
-
- SQUISHSCAN <api/quick> (quick)
- ──────────────────────────────────────────────────────────────────────
- GoldED currently supports the Squish msgbase through the MSGAPI
- provided by the Squish/Maximus author, Scott Dudley. However, the
- API method of scanning a Squish area is a bit slow. Therefore this
- keyword allows you to switch to a significantly quicker scanning
- method. The quick method is fully compatible with the API method.
-
- SQUISHUSERNO <index>
- ──────────────────────────────────────────────────────────────────────
- This sets the lastread index number for the Squish *.SQL lastread
- files. Lowest number is 0 (zero), highest is (in theory) 65534.
-
- If used, this disables the use of USER.BBS to find the index
- number, and will in effect also stop GoldED from creating USER.BBS
- or any new entries in it (useful in a single-user point system).
-
- If a Squish msgbase is shared between several users, and you don't
- want to have a USER.BBS (recommended in such a case), each user
- must have a unique SQUISHUSERNO in their GOLDED/GOLDAREA.CFG.
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 36
-
-
- SQUISHUSERPATH <path>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines the path where GoldED can find and use/create
- your USER.BBS file, which is used in connection with the Squish
- area lastreads.
-
- If this path is not defined, GoldED will instead take the one
- specified with AREAFILE Squish or AREAFILE Maximus (whichever
- comes first), or failing that, use the MAXIMUS or SQUISH environ-
- ment variables. If even that fails, the AREAPATH or GOLDPATH is
- used.
-
- SWAPPATH <path> (defaults to TEMPPATH)
- ──────────────────────────────────────────────────────────────────────
- Defines where the swap file will be placed in case of disk swap-
- ping in DOS shells. It is recommended that this points to a RAM
- disk, if available. GoldED needs 3-500k free disk space for the
- swapfile, depending on the overlay buffer size specified with
- the -O commandline switch.
-
- TEARLINE <string> (GoldED @version)
- ──────────────────────────────────────────────────────────────────────
- Here you can define your default tearline. The tearline can be up
- to 76 chars long (excluding the leading "--- "), but beware that
- policies (such as FidoNet ECHOPOL1) may set a significantly lower
- limit (around 30).
-
- Tearlines defined in the Random System *always* overrides the
- default tearline defined with this keyword.
-
- If your tearline does not contain at least the string "GoldED" or
- "GED", GoldED will automatically insert it's PID kludge.
-
- NOTE: The tearline redefinition feature is only fully functional
- for registered users. Unregistered users are only be able to
- define their own tearline in one area, defined with the FREETEAR
- keyword.
-
- TEMPLATE <file> ["desc"] (GOLDED.TPL)
- ──────────────────────────────────────────────────────────────────────
- You can define many different template files. The templates can be
- switched using the READchangetemplate popup menu or the EDITMENU.
- The Random System always overrides the default templates, except
- when selected from the EDITMENU.
-
- The optional "desc" can be used to give the templates more
- meaningful names like "International template" instead of just
- plain "G:\GOLDED.TPL".
-
- TEMPPATH <path>
- ──────────────────────────────────────────────────────────────────────
- Defines the directory where temporary files are placed.
-
- NOTE: This path should *NOT* point to a RAM disk or other volatile
- media! The editor autosave file is placed here, and will almost
- certainly be lost if a RAM disk is used...
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 37
-
-
- TIMEOUT <seconds> (360)
- ──────────────────────────────────────────────────────────────────────
- Similar to the screen blanking (SCREENBLANKER) feature, GoldED can
- auto-exit after a specified period of time. Useful if you are in a
- hurry (or didn't get enough sleep last night ;-), and run GoldED
- from your mailer shell. The timeout value can be overridden with
- the -T commandline option.
-
- TIMESLICE <type> (none)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED will release timeslices, when GoldED has
- nothing to do, such as when it is waiting for keyboard input.
-
- Available <type>'s are:
-
- DesqView (Int 15, AX=1000h)
- Windows (Int 2F, AX=1680h)
- OS/2 (Int 2F, AX=1680h)
- MultiLink (Int 7F, AX=0200h)
- T-View (Int 15, AX=1000h)
- PC-MOS (Int 38, AX=0703h, BX=3, CX=DX=0)
- DoubleDOS (Int F4)
- Detect Try to detect one of these (don't rely on it!)
- None Do not release any timeslices (calls Int 28).
-
- Only the DesqView type has been tested by the Author, but the rest
- of them were found in the Binkley 2.50 source, so...
-
- TWITMODE <mode> (Show)
- ──────────────────────────────────────────────────────────────────────
- In GoldED you can define several "Twit" names or subject. With
- this keyword you can specify the action taken when a Twit message
- is encountered.
-
- The <mode> can be one of the following:
-
- Show Show twit messages.
- Blank Blank twit messages.
- Skip Skip twit messages, unless to your USERNAME's.
- Ignore Skip twit messages, always.
-
- TWITNAME <name/addressmask>
- ──────────────────────────────────────────────────────────────────────
- With this keyword, you can specify "Twit" names and/or address-
- masks. When a Twit name/address is detected, the TWITMODE setting
- will determine the action taken.
-
- <addressmask> See Appendix B for valid addressmasks.
-
- TWITSUBJ <"string">
- ──────────────────────────────────────────────────────────────────────
- With this keyword, you can specify "Twit" subjects. When a Twit
- subject is detected, the TWITMODE setting will determine the
- action taken. The subject string is searched in the whole subject,
- so you can specify a partial twit subject. Twit subjects are
- limited to maximum 35 characters.
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 38
-
-
- USEFLAGS <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, GoldED inserts the FLAGS kludge for certain extended
- attributes, as defined in FSC-0053 by Joaquim H. Homrighausen, and
- supported by FrontDoor, D'Bridge, IMail and other modern software.
- GoldED uses FLAGS to emulate the Hold and Freq attributes which
- are not defined in the QBBS message format.
-
- USEINTL <type> (Auto)
- ──────────────────────────────────────────────────────────────────────
- The INTL kludge is normally only inserted in netmail messages, if
- the origination zone is different from the destination zone (the
- "Auto" setting), but on systems with many AKA's in the mailer, it
- might be useful/necessary to add it ALWAYS (the "Yes" setting).
- The "No" option should never be used.
-
- The <type> can be one of the following:
-
- Auto Only insert in inter-zone netmail.
- Yes Always insert.
- No Never insert.
-
- NOTE: Some older netmail processors can be confused by the INTL
- line, if it contains the same orig/dest zone, especially in
- conjunction with points and the FMPT/TOPT kludges.
-
- USEMSGID <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- If enabled, the MSGID kludge is inserted in netmail and echomail,
- and the REPLY kludge is inserted when replying to a msg with a
- MSGID.
-
- The MSGID kludge is defined in FidoNet document FTS-0009.
-
- USERLIST <file> [zone/addr]
- ──────────────────────────────────────────────────────────────────────
- In addition to normal nodelist support, GoldED also supports the
- "FIDOUSER.LST" style userlist format. The default zone is defined
- by the first ADDRESS or AKA, but can be overridden by adding the
- zone number or a full address after the filename.
-
- <file> Userlist file in FIDOUSER.LST format.
- [zone/addr] Default address for the userlist (if no zone info
- is present).
-
- USERLISTFILE <file> (GOLDED.LST)
- ──────────────────────────────────────────────────────────────────────
- GoldED can generate a list of all users in the current area. This
- keyword defines the default name of the FIDOUSER.LST style user-
- list output file generated with the READmakeuserlist command.
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 39
-
-
- USERNAME <name>[,address]
- ──────────────────────────────────────────────────────────────────────
- You can define many different names/aliases. When GoldED finds an
- un-received message to one of your USERNAME's, it is marked as
- received. Useful if you use alias names in some conferences. It is
- possible to change the current name using the READchangeusername
- popup menu.
-
- If you run a QBBS style message base, the *first* USERNAME is used
- to identify which lastread record to use. This is done by looking
- in the USERS.BBS file. If the name is not found in USERS.BBS, a
- new set of LASTREAD.BBS and USERS.BBS records are added auto-
- matically.
-
- VIEWHIDDEN <yes/no> (yes)
- ──────────────────────────────────────────────────────────────────────
- Hidden lines are "unknown" kludge lines. If enabled, hidden lines
- will be displayed when reading msgs.
-
- VIEWKLUDGE <yes/no> (no)
- ──────────────────────────────────────────────────────────────────────
- If enabled, known kludge lines will be displayed when reading
- msgs.
-
- WHOTO <name>
- ──────────────────────────────────────────────────────────────────────
- This name is inserted in the TO: name field, when entering new
- messages (not replies) in echomail or local areas. The setting of
- this keyword can be overridden with a definition in the Random
- System.
-
- XLATCHARSET <importid> <exportid> <file>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines character set translation table files.
-
- <importid> Charset import identifier.
- <exportid> Charset export identifier.
- <file> Charset translation table file.
-
- See the Character Translation section, page 58, for details.
-
- XLATESCSET <import> <export> <escfile>
- ──────────────────────────────────────────────────────────────────────
- This keyword defines escape sequence translation table files.
-
- <importid> Escset import identifier.
- <exportid> Escset export identifier.
- <file> Escape sequence translation table file.
-
- See the Character Translation section, page 58, for details.
-
- XLATEXPORT <charsetid>
- ──────────────────────────────────────────────────────────────────────
- Defines the export charset for your messages.
-
- See the Character Translation section, page 58, for details.
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 40
-
-
- XLATIMPORT <charsetid> (IBMPC)
- ──────────────────────────────────────────────────────────────────────
- Defines the local charset for your machine.
-
- See the Character Translation section, page 58, for details.
-
- XLATPATH <path>
- ──────────────────────────────────────────────────────────────────────
- This is the path where GoldED tries to find the XLATCHARSET and
- XLATESCSET files.
-
- ZONEGATING <yes/no/ask> (ask)
- ──────────────────────────────────────────────────────────────────────
- When writing a netmail message to a destination in another zone,
- you can either send the message directly (No) or via the local
- ZoneGate (Yes). You can also be consulted each time (Ask).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CONFIGURATION KEYWORD REFERENCE GoldED Manual, Page 41
-
-
- ──────────────────────────────────────────────────────────────────────
- 12. THE OLD CONFIGURATION KEYWORDS
- ──────────────────────────────────────────────────────────────────────
-
-
- This section is only relevant for users of the previous versions
- (including the older versions in the recent 2.32 beta series).
-
- In this version, many of the configuration keywords have been renamed
- to a more consistent naming scheme. The old keywords will still be
- supported for a couple of versions, but you should change to the new
- ones as soon as possible.
-
- To aid the conversion process, the commandline switch -D is provided
- to turn off the support of the old keywords. This will make GoldED
- report all the lines containing old keywords. Redirect this report to
- a printer or file, and start editing your configuration files.
-
- Below is a list of all the old keywords, and the corresponding new
- keyword, where applicable:
-
-
- Old keyword New keyword
- ──────────────────────────────────────────────────────────────────────
- AREASORT AREALISTSORT
- AUTOATTACH EDITAUTOATTACH
- BLANKTIME SCREENBLANKER
- BOARDNOS AREALISTNOS
- CCATTRIB ATTRIBSCC
- CCLIST CARBONCOPYLIST
- CFMATTRIB ATTRIBSCFM
- CHANGEDATE EDITCHANGEDATE
- CHANGEPROMPT DOSPROMPT
- CHARSET XLATCHARSET
- CLEARKEYS KEYBCLEAR
- COLOUR COLOR
- COMMENTNOISE BEEPCOMMENT
- CRLFTERM EDITCRLFTERM
- DELORIG ASKDELORIG
- ECHOATTRIB ATTRIBSECHO
- ECHOINFO CTRLINFOECHO
- ELIMSNOW SCREENELIMSNOW
- ESCSET XLATESCSET
- EXCLAREA AREAEXCL
- EXPORTCHARSET XLATEXPORT
- EXTKEYS KEYBEXT
- FIELDCLEAR EDITFIELDCLEAR
- GOLDEDCFM CONFIRMFILE
- GOLDEDLOG LOGFILE
- GOLDEDLST USERLISTFILE
- GOLDEDMSG EDITORFILE
- GOLDEDNAM NAMESFILE
- GOLDEDPRN OUTPUTFILE
- HARDLINE EDITHARDLINE
- HARDLINES EDITHARDLINES
- HWMARKS FIDOHWMARKS
- INCLAREA AREAINCL
-
-
- ──────────────────────────────────────────────────────────────────────
- THE OLD CONFIGURATION KEYWORDS GoldED Manual, Page 42
-
-
- INTERNALEDITOR EDITINTERNAL
- LASTREAD FIDOLASTREAD
- LASTREADUSER FIDOLASTREADNO
- LISTWRAP DISPLISTWRAP
- LOCALATTRIB ATTRIBSLOCAL
- LOCALCHARSET XLATIMPORT
- LOCALHIGHLIGHT DISPLOCALHIGH
- LOCALINFO CTRLINFOLOCAL
- LOCALNOISE BEEPLOCALMSG
- MATCHAKA AKAMATCHNET
- MAXCOLS SCREENMAXCOL
- MAXMSGSIZE EDITMSGSIZE
- MAXROWS SCREENMAXROW
- MIXCASE EDITMIXCASE
- MULTIQBBS QBBSINCRESCAN
- NETATTRIB ATTRIBSNET
- NETINFO CTRLINFONET
- NETTEAR CTRLINFONET
- NEXTAREA AREAAUTONEXT
- NEXTMSGS DISPAUTONEXT
- NOISEFACTOR BEEPFACTOR
- OVERLAYEMS OVERLAY
- OVERLAYEXT OVERLAY
- PAGEBAR DISPPAGEBAR
- QMSGPATH QBBSPATH
- REALMSGNO DISPREALMSGNO
- REBUILD QBBSREBUILD
- RENAREA AREARENAME
- REPLYRE EDITREPLYRE
- RIGHTMARGIN DISPMARGIN
- SAVEMENU EDITSAVEMENU
- SAVETIME EDITAUTOSAVE
- SAYBIBI BEEPNOISES
- SCANAREA AREASCAN
- SHADOWS SCREENSHADOWS
- SHARE SHAREMODE
- SHOWTWITS TWITMODE
- SIGNALFILE SEMAPHORE
- SPACEQUOTES QUOTESPACING
- SPELLCHECKER EDITSPELLCHECK
- STACKKEYS KEYBSTACK
- STARTECHO AREASTART
- SWAPALL DOSSWAP
- SYSOP USERNAME
- TABSIZE DISPTABSIZE
- UNDELETELINES EDITUNDELETE
- USEBIOS SCREENUSEBIOS
- XPLIST CROSSPOSTLIST
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE OLD CONFIGURATION KEYWORDS GoldED Manual, Page 43
-
-
- ──────────────────────────────────────────────────────────────────────
- 13. AREA CONFIGURATION
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED offers a wide variety of methods for defining message areas.
- You can define each area manually in the GOLDED.CFG file (or an
- INCLUDE'ed GOLDAREA.CFG file), or you can tell GoldED to read the area
- setup files of many popular BBS/mailer/mail processor packages.
-
- Syntax for manually defined areas
- ──────────────────────────────────────────────────────────────────────
-
- AREA <echoid> <"desc"> <msgbase>[type] <loc> [aka] [attrs]
-
- <echoid> Echomail area identifier.
- <"desc"> Area description in ("") quotes.
- <msgbase> O(Opus *.MSG), F(Fido *.MSG), S(FTS-0001 *.MSG),
- Q(QuickBBS), R(RemoteAccess), M(Squish).
- [type] N(Netmail), E(Echomail), L(Local).
- <location> Directory path/file or QBBS board number.
- [aka] AKA number (starting from 0)
- [attrs] R/O(Read-Only), and/or other attributes.
-
- "O(Opus)" and "F(Fido)" are synonyms (*.MSG files).
- "S(FTS-0001)" are *.MSG files, but with zone/point header fields.
- "Q(QuickBBS)" and "R(RemoteAccess)" are synonyms (MSG*.BBS files).
- "M(Squish) is the Squish format (*.SQ* files).
-
- See the GOLDED.CFG and GOLDAREA.CFG files for examples.
-
-
- Syntax for external area configuration
- ──────────────────────────────────────────────────────────────────────
-
- The general syntax for the AREAFILE keyword is:
-
- AREAFILE <programname> [path or filename(s)] [-options]
-
- The <programname> can be one of the following:
-
- AreasBBS GoldED is equipped to read a wide variety of AREAS.BBS
- type files. It can read and distinguish between the old
- CONFMAIL style with paths for *.MSG areas, the QBBS
- style with board numbers and finally the new Squish
- style AREAS.BBS.
-
- D'Bridge Reads the DBRIDGE.AA1/.AA2 files (for version 1.30) or
- the DBRIDGE.ADF of the later versions (1.31 beta and
- later).
-
- Dutchie Reads the DUTCHIE.ARE file.
-
- FastEcho Reads the FASTECHO.CFG file.
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- AREA CONFIGURATION GoldED Manual, Page 44
-
-
- FrontDoor Reads the SETUP.FD/FD.SYS and FOLDER.FD/FOLDER.SYS
- files. If you want the real echoid's attached to the
- areas, you will also need to supply the filename of the
- relevant AREAS.BBS file(s).
-
- GEcho Reads SETUP.GE/GECHO.SYS and AREAFILE.GE.
-
- IMail Reads the IMAIL.CF and IMAIL.AR files. At the time of
- writing, GoldED supports both the old IMail 1.00-1.10
- format and the new 1.20+ format. New versions will be
- supported when they become available.
-
- Maximus Reads the AREA.DAT file. Compatible with both the old
- (1.xx) and new (2.xx) formats. If your AREA.DAT is named
- differently, you must supply the correct filename.
-
- ME2 Reads the old ME2 editor AREADESC.ME2 file and AREAS.BBS
- files. You must supply the names of both files.
-
- Opus Reads the Opus 1.1x SYSTEM??.DAT files or the Opus 1.7x
- SYSMSG.DAT file.
-
- QuickBBS Reads the CONFIG.BBS file. To get the real echoid's, you
- must also supply the filename of the relevant AREAS.BBS.
-
- RaEcho Reads AREAS.RAE.
-
- RemoteAccess Reads the MESSAGES.RA file. To get the real echoid's,
- you must also supply the filename of the relevant
- AREAS.BBS.
-
- Squish Reads SQUISH.CFG and AREAS.BBS (if any).
-
- TosScan Reads the FD.SYS/SETUP.FD and AREAFILE.FD files.
-
- WMail Reads the WMAIL.PRM and AREAS.PRM files.
-
-
- The [-options] are:
-
- -NOCHK Normally GoldED will check the areafile timestamps when
- starting up, and recompile the configuration if a file
- was changed. If this option is given for any AREAFILE,
- those areafiles will not be checked. This can be useful
- in cases like TosScan, GEcho, IMail and several others
- which "touch" their files every time they run.
-
- -S<sortspec> If you are *not* using the global AREALISTSORT keyword
- for sorting all the areas, you can sort the areas of
- each AREAFILE separately. See the AREASORT keyword for
- the definition of <sortspec>.
-
- If no path is specified, the AREAPATH or the appropriate environment
- variable is used to find the files.
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- AREA CONFIGURATION GoldED Manual, Page 45
-
-
- ──────────────────────────────────────────────────────────────────────
- 14. COLOR CONFIGURATION
- ──────────────────────────────────────────────────────────────────────
-
-
- Color configuration in GoldED is a bit complicated, and you probably
- have to experiment quite a bit, if you want make your own setup. For
- your convenience, I have added a number of example color setups,
- provided by some of my many good users. I suggest you try them all and
- use the one that suits you best, perhaps tuning it a bit to your
- taste.
-
- The COLOR keyword uses the following syntax:
-
- COLOR <window> <part> <colors>.
-
- <window> AREA, ASK, BACKGROUND, BRAG, HEADER, HELP, INFO, MENU,
- READER, SHADOW, STATUS.
-
- <part> BLOCK, BORDER, BTYPE, EDIT, HIDDEN, HIGHLIGHT, INPUT,
- KLUDGE, NOSELECT, ORIGIN, QUOTE, SELECTOR, TEARLINE,
- TITLE, WINDOW.
-
- The <colors> are composed of [blinking] <ink> [on <paper>].
-
- <ink> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey,
- DGrey, LBlue, LGreen, LCyan, LRed, LMagenta, Yellow,
- White.
-
- (For monochrome setups we instead have:)
- Normal, Highlight, Reverse, Underline.
-
- <paper> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey.
-
- The SHADOW color does not need a <part>, it is global.
-
- The paper color always defaults to Black if not specified.
-
- If <part> is "BTYPE", the <color> is a value in the range 0-3, which
- defines the type of lines used when drawing menus and windows:
-
- BTYPE 0 is single horizontal and single vertical lines.
- BTYPE 1 is double horizontal and double vertical lines.
- BTYPE 2 is single horizontal and double vertical lines.
- BTYPE 3 is double horizontal and single vertical lines.
-
- The default border type is always BTYPE 0.
-
- The following is a description of the different window parts:
-
-
- Various general color items
- ──────────────────────────────────────────────────────────────────────
- SHADOW Shadow below windows and menus.
- STATUS WINDOW Status line at the bottom.
- BACKGROUND WINDOW Background for the startup window.
-
-
-
- ──────────────────────────────────────────────────────────────────────
- COLOR CONFIGURATION GoldED Manual, Page 46
-
-
- Startup screen / logo window
- ──────────────────────────────────────────────────────────────────────
- BRAG WINDOW The Copyright window.
- BRAG BORDER Lines around the Copyright window.
- BRAG TITLE The logo text.
- BRAG HIGHLIGHT The inner logo lines.
- BRAG BLOCK The outer logo lines.
- BRAG BTYPE Copyright window border type.
-
- Area Selection Menu
- ──────────────────────────────────────────────────────────────────────
- AREA WINDOW Descriptions, the top line (inc. search).
- AREA BORDER Lines.
- AREA TITLE Titles on the border.
- AREA SELECTOR Selection bar.
- AREA HIGHLIGHT The color for the area marks.
- AREA BTYPE Window border type.
-
- Message Header
- ──────────────────────────────────────────────────────────────────────
- HEADER WINDOW Header text.
- HEADER BORDER Lines.
- HEADER TITLE Titles on the border.
- HEADER INPUT Message number input field.
- HEADER EDIT Header input fields.
- HEADER HIGHLIGHT Marks.
- HEADER BTYPE Window border type.
-
- Message Text
- ──────────────────────────────────────────────────────────────────────
- READER WINDOW Normal message text.
- READER BORDER The Pagebar.
- READER QUOTE Quoted lines.
- READER CURSOR Character at cursor pos. (int. editor).
- READER KLUDHIDD Kludges and hidden lines.
- READER TEARORIG Tearline and Origin.
- READER BLOCK Block color (internal editor).
- READER BTYPE Window border type.
-
- Miscellaneous Smaller Menus
- ──────────────────────────────────────────────────────────────────────
- ASK WINDOW Menu items.
- ASK BORDER Lines.
- ASK TITLE Menu title.
- ASK SELECTOR Selection bar.
- ASK NOSELECT Non-selectable menu items.
- ASK HIGHLIGHT Hotkeys.
- ASK BTYPE Window border type.
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- COLOR CONFIGURATION GoldED Manual, Page 47
-
-
- Miscellaneous Larger Menus (Browser Windows)
- ──────────────────────────────────────────────────────────────────────
- MENU WINDOW Menu items.
- MENU BORDER Lines.
- MENU TITLE Menu title.
- MENU SELECTOR Selection bar.
- MENU NOSELECT Non-selectable menu items.
- MENU HIGHLIGHT Hotkeys/marks.
-
- Help Screens
- ──────────────────────────────────────────────────────────────────────
- HELP WINDOW Help text.
- HELP BORDER Lines.
- HELP SELECTOR Current keyword.
- HELP HIGHLIGHT Other keywords.
- HELP BTYPE Window border type.
-
- Pop Up Information Windows
- ──────────────────────────────────────────────────────────────────────
- INFO WINDOW Window text.
- INFO BORDER Lines.
- INFO TITLE Info title.
- INFO BTYPE Window border type.
-
-
- See the GEDCOL*.CFG and GEDMON*.CFG files for examples of color
- configuration.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- COLOR CONFIGURATION GoldED Manual, Page 48
-
-
- ──────────────────────────────────────────────────────────────────────
- 15. THE RANDOM SYSTEM
- ──────────────────────────────────────────────────────────────────────
-
-
- With the Random System, you can define area-specific sets of origins,
- netnames, tearlines, templates, usernames and many other items. If
- more than one item of each type is specified, a random one is picked -
- a Random System. This is a very useful feature when (for example)
- participating in conferences with different languages.
-
- The Random System is built on the idea of "groups". A group is a
- collection of "items", belonging to the group. You can assign one or
- more echomail areas, designated by their echoid's to a group. Groups
- can also be specified for just a single echo, and DOS/4DOS-style
- wildcards can be used to simplify the assignment of echoes with common
- strings in their name, such as *.DK, SIG.* and so on. In this way, you
- could for example setup one group for all national echoes, another for
- special local echoes, a third for international echoes etc.
-
-
- Defining Groups
- ──────────────────────────────────────────────────────────────────────
-
- The general syntax of a group definition is:
-
- GROUP <id>[:]
- ; items go here
- [ASSIGNTO <id list>]
-
- The GROUP <id> can be one of three things:
-
- 1. A group letter, matching the group letters used in the AREAFILE's
- of D'Bridge, GEcho, IMail, TosScan and possibly others. To use
- this feature, you need to enable the AREAFILEGROUPS keyword, and
- the letter groups must be defined before any other group types.
-
- 2. An echoid or echoid mask (wildcards can be used). The items are
- simply defined below the GROUP line.
-
- 3. A group label, terminated by a colon (:). The group items are
- defined below the GROUP line. Echoes are assigned to the group by
- adding one or more ASSIGNTO statements after the group items.
-
- You can't assign a group to another group. It will not harm, but it
- also won't work :-)
-
- Groups must defined with the most explicit groups first. GoldED simply
- scans from beginning to end, and stops at the first group with a
- matching <id> or ASSIGNTO list.
-
- In the previous version of the random system, there was a "Default:"
- group in the beginning of the file. In the new system, this is done by
- adding a "GROUP *" as the last group. This works as a "catch-all" for
- any echoes that didn't belong to an explicit group definition.
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE RANDOM SYSTEM GoldED Manual, Page 49
-
-
- Defining Random Items
- ──────────────────────────────────────────────────────────────────────
-
- The random items are defined much like in the main GoldED configura-
- tion file. Below is a list of the random item keywords available in
- this version.
-
- If more than one of each item is defined within a group, those items
- will be picked randomly (hence the name "Random System"), as GoldED
- collects items when entering an area.
-
- Most of the following keywords are described in more detail in the
- regular keyword reference. See this if in doubt.
-
-
- ATTRIBUTES <attributes>
- ──────────────────────────────────────────────────────────────────────
- Defines the attributes to use in the group area(s).
-
- LOADLANGUAGE <file>
- ──────────────────────────────────────────────────────────────────────
- If defined, this keyword will load a language definition file when
- entering the group area(s).
-
- This feature can be used to load a small set of national language
- definitions in national areas, an english set in international,
- etc. Typically this would be used to load the definitions of the
- date/time strings for use in the template.
-
- In the ADVANCED archive, a set of GEDLNG*.CFG files are provided,
- which are designed for use with LOADLANGUAGE. Please note that
- there is also a @LoadLanguage template token. This way you can
- choose to load a language file from the template, or by using the
- Random System. The template token takes precedence over the
- LOADLANGUAGE in the Random System, but if both are defined, both
- will be loaded.
-
- NETNAME <"string">
- ──────────────────────────────────────────────────────────────────────
- Defines one or more netnames.
-
- ORIGIN <"string">
- ──────────────────────────────────────────────────────────────────────
- Defines one or more origins
-
- OUTPUTFILE <file>
- ──────────────────────────────────────────────────────────────────────
- Defines an output file.
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE RANDOM SYSTEM GoldED Manual, Page 50
-
-
- SEARCHFOR <string;string;..>
- ──────────────────────────────────────────────────────────────────────
- Defines a set of search strings, separated by semicolons. The
- search set defined here is the default when using the Alt-F/Z
- search functions or the marking system.
-
- The semicolon works like an OR operator. That is, the search is
- successful if one or more of the strings are matched.
-
- TEARLINE <string>
- ──────────────────────────────────────────────────────────────────────
- Defines one or more tearlines.
-
- TEMPLATE <file>
- ──────────────────────────────────────────────────────────────────────
- Defines one or more templates.
-
- TWITMODE <mode>
- ──────────────────────────────────────────────────────────────────────
- Defines the twitmode.
-
- USERNAME <name>[,addr]
- ──────────────────────────────────────────────────────────────────────
- Defines one or more usernames
-
- VIEWHIDDEN <yes/no>
- ──────────────────────────────────────────────────────────────────────
- Defines if we want to see hidden lines.
-
- VIEWKLUDGE <yes/no>
- ──────────────────────────────────────────────────────────────────────
- Defines if we want to see kludge lines.
-
- WHOTO <name>
- ──────────────────────────────────────────────────────────────────────
- Defines one or more TO: names.
-
- XLATEXPORT <charsetid>
- ──────────────────────────────────────────────────────────────────────
- Defines the export charset.
-
- XLATIMPORT <charsetid>
- ──────────────────────────────────────────────────────────────────────
- Defines the import charset.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE RANDOM SYSTEM GoldED Manual, Page 51
-
-
- Random System Example
- ──────────────────────────────────────────────────────────────────────
-
- This is an example of how a Random System could be setup. Note how the
- letter group 'D' goes first, followed by the explicit group defini-
- tions for the NERDS and FOO echoes. Then comes the more general groups
- (those with Label:'s), where the echoes are assigned with one or more
- ASSIGNTO statements. At last there is the catch-all "GROUP *", which
- works as the default group.
-
-
- === Cut, GOLDRAND.CFG ===
-
-
- GROUP D ; I'm using group letter D for my danish echoes in
- GEcho.
- TEMPLATE DANSK.TPL
-
-
- GROUP NERDS
- ORIGIN "I am a Nerd. Take me to your Loser!"
-
-
- GROUP FOO ; This group is *only* for the FOO echo.
- TEARLINE FooED @rev
- ORIGIN "Foo-ing my day away"
-
-
- GROUP FooEchoes:
- TEARLINE FooED @rev
- ORIGIN "This is a Foo-lish origin"
- ASSIGNTO *FOO* ; Use wildcards to catch any other foo echo.
-
-
- GROUP FidoNet:
- ORIGIN "Fight-O-Net? Good name..."
- TEMPLATE FIDONET.TPL
- WHOTO Everyone
- ASSIGNTO NET_DEV, WORLDPOL, INTERCOOK
- ASSIGNTO GREEN.029, C_ECHO, C_PLUSPLUS
-
-
- GROUP SigNet:
- ORIGIN "To SIG or not to SIG..."
- TEMPLATE SIGNET.TPL
- ASSIGNTO SIG.* ; The wildcard is VERY handy here ;-)
-
-
- GROUP * ; This is default group
- ORIGIN "Ding-Dong!!! Another new echo we forgot about! :-)"
-
-
- === Uncut ===
-
-
- See the example GOLDRAND.CFG in the ADVANCED archive for a real-life
- setup similar to the one I use myself.
-
-
- ──────────────────────────────────────────────────────────────────────
- THE RANDOM SYSTEM GoldED Manual, Page 52
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE RANDOM SYSTEM GoldED Manual, Page 53
-
-
- ──────────────────────────────────────────────────────────────────────
- 16. THE MESSAGE TEMPLATE
- ──────────────────────────────────────────────────────────────────────
-
-
- The message template gives you a ready-made skeleton for writing your
- messages in the editor. The template is one of GoldED's many strong
- features. With this, you can eliminate the tedious typing of greetings
- etc etc. GoldED also provides a number of replacement strings,
- "tokens", to dynamically add message specific information to the
- template.
-
- As in the configuration file, a semicolon (;) first on the line makes
- the line a comment. Any other line is put into the editor file, after
- token expansion. Tokens are not case sensitive.
-
- The following is a list of the tokens available:
-
- Conditional tokens
- ──────────────────────────────────────────────────────────────────────
- (These are replaced with a null string)
-
- @Changed Line is only inserted in Changed msgs (from others).
- @Comment Line is only inserted in Reply-Comments.
- @Echo Line is only inserted in Echomail.
- @Forward Line is only inserted in Forwarded messages.
- @Local Line is only inserted in Local messages.
- @Moved Line is only inserted in Reply-Moved messages.
- @Net Line is only inserted in Netmail.
- @New Line is only inserted in New messages (not replies).
- @Position Specifies the starting line for the editor cursor.
- @Quoted Line is only inserted in Quoted replies.
- @Reply Line is only inserted in Non-Quoted Replies.
-
- Insert tokens
- ──────────────────────────────────────────────────────────────────────
- (Anything else on the line is ignored)
-
- @Attrib <attributes> - Adds specific message attributes.
- @LoadLanguage Loads a partial language config file.
- @Message Inserts the original message (in Forward & Change).
- @Quote Inserts a quote of the original message.
- @Quotebuf Reserved for future use...
- @Random [random.txt [random.idx]] - Inserts random text.
- @SetSubj <"subject"> - Sets the message subject, if empty.
-
- Replacement tokens
- ──────────────────────────────────────────────────────────────────────
- (Replaced with message specific data)
-
- @CAddr Current user address.
- @CDate Current date.
- @CDesc Current area description.
- @CEcho Current echoid.
- @CFName Current user first name.
- @CLName Current user last name.
- @CName Current user name.
-
-
- ──────────────────────────────────────────────────────────────────────
- THE MESSAGE TEMPLATE GoldED Manual, Page 54
-
-
- @CTime Current time.
- @DAddr Destination address.
- @DFName Destination first name.
- @DLName Destination last name.
- @DName Destination name.
- @OAddr Original address.
- @ODate Original date.
- @ODesc Original area description if moved, else current.
- @OEcho Original echoid if moved, otherwise current.
- @OFName Original first name.
- @OLName Original last name.
- @OName Original name.
- @OTime Original time.
- @Rev The revision number (in the form mmdd).
- @Serialno For registered users: The registraion serial number.
- @Subject The message subject line.
- @TAddr Destination to address.
- @TFName Destination to first name.
- @TLName Destination to last name.
- @TName Destination to name.
- @Ver The simple version number (in the form x.yy)
- @Version The complete release version number of GoldED.
- @_CAddr Current user address (fixed width: 19 chars).
- @_CName Current user name (fixed width: 34 chars).
- @_DAddr Destination address (fixed width: 19 chars).
- @_DName Destination name (fixed width: 34 chars).
- @_OAddr Original address (fixed width: 19 chars).
- @_OName Original name (fixed width: 34 chars).
- @_TAddr Destination to address (fixed width: 19 chars).
- @_TName Destination to name (fixed width: 34 chars).
-
- The template text begins at the first non-comment line.
-
- See the included GOLDED.TPL for example usage.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE MESSAGE TEMPLATE GoldED Manual, Page 55
-
-
- ──────────────────────────────────────────────────────────────────────
- 17. HELP SYSTEM
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED has a built-in context sensitive help system, tied to the <F1>
- key (one of the very few keys that cannot be reconfigured). It con-
- tains a complete keyboard reference and help for most situations. It
- is current not as complete or sophisticated as I'd like it myself, but
- this may be improved in future versions.
-
- You can completely redefine the help screens if you wish - the
- GOLDHELP.CFG file is a plain ASCII text file which contains all help
- definitions. The help file is split into several help categories. Here
- is an example of a couple of defined help categories:
-
- *B 1,Help Category 1
- help text help text help text
- help text help text help text
- help text help text help text
- *P
- help text help text help text
- help text help text help text
- help text help text help text
- *E
-
- *B 2,Help Category 2
- help text help text help text
- help text help text help text
- help text help text help text
- *P
- help text help text help text
- help text help text help text
- help text help text help text
- See also: ^Help Category 1^
- *E
-
- The "*B" indicator specifies the beginning of a help category. The
- format is "*B helpcatnumber[,helpcatname]". In GoldED the help cate-
- gories are numbered 1000-9999, split into more or less logical groups.
- See the help file for assignments. There should be only one space
- between the "*B" and the help category number. The help category name
- is only required for cross-references. If there are no cross-referen-
- ces to that help category, then you can leave the helpcatname para-
- meter out.
-
- The "*P" indicator specifies a page break and is optional. You may
- have as many page breaks as you'd like. The "*E" indicator specifies
- the end of the help category. The "*B", "*P", and "*E" indicators must
- all begin in the first column. These indicators and the help category
- name are case insensitive (can be in lowercase, uppercase, or mixed).
-
- In the definition of Help Category 2, you will notice the cross-
- reference to Help Category 1. All cross-referencing is done by embed-
- ding the cross- reference category name (not number) inside carats
- (^). If you need to display a carat inside the help file, use a double
- carat (^^).
-
-
- ──────────────────────────────────────────────────────────────────────
- HELP SYSTEM GoldED Manual, Page 56
-
-
- Any text contained outside of the "*B" and "*E" will be treated as
- comments. If an "*E" is not found, then the end-of-file will be
- treated as an "*E".
-
- Not all of the help categories in this help file are actually used in
- the current version of GoldED. The ones not used are empty, except for
- a two-line "header".
-
- The usable dimensions of the help window are 60 columns by 16 lines.
- In the help file there is a model of the actual window.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- HELP SYSTEM GoldED Manual, Page 57
-
-
- ──────────────────────────────────────────────────────────────────────
- 18. CHARACTER TRANSLATION
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED implements several different proposals for character trans-
- lation in imported and exported messages:
-
- FSC-0050 "Charset Identifier" Thomas Sundblom (2:201/114).
- FSC-0051 "I51" Thomas Gradin (2:200/108).
- FSC-0054 "CHARSET proposal" Duncan McNutt (2:243/100).
- No FSC "Composed Characters" Andre van de Wijdeven (2:500/131).
-
- FSC-0050 is currently known to be implemented in the OPMED 3.xx
- message editor, and in Opus 1.7x. It uses the same identifier as
- FSC-0054 (a ^aCHARSET kludge), but is a lot simpler (but not neces-
- sarily better).
-
- The "I51" and "CHARSET" proposals are in the process of being merged
- to one proposal, which should combine the advantages of both. They are
- both based on using the LATIN-1 (also known as ISO 8859-1) character
- set for extended ASCII. The LATIN-1 set is the set used by Windows 3,
- Amiga and many other non-PC computers. In addition to LATIN-1, I51
- defines a set of so-called escape sequences for characters not found
- in the LATIN-1 set.
-
- "Composed Characters" became quite popular in Holland, but the author
- decided to drop his proposal because it relied on escape sequences
- using the so called "soft-cr" (141d, 8Dh) character. GoldED will
- continue to support Composed as long as it seems necessary.
-
- If you want to know more about the details, I suggest you read the
- proposals or contact the authors.
-
- GoldED currently supports two types of translation tables:
-
-
- The *.ESC files
- ──────────────────────────────────────────────────────────────────────
-
- These files are used for import translation of the escape sequences
- defined in I51 and Composed Characters.
-
- In the ESC files, the semicolon is used for comments. The *first* non-
- comment line defines the charset the escape code are mapped TO. This
- is normally IBMPC, and should not be changed. Any other non-comment
- line is treated as an escape sequence definition with this syntax:
-
- <esc1><esc2><space><map chars>[; comment/description]
-
- Leading spaces are *not* allowed in ESC files. <esc1> and <esc2> are
- the two characters that define the escape sequence. <space> is ignored
- and can be used to make the table look better. <map chars> defines the
- local representation of the escape sequence, up to three characters.
- Normally you would only map to one extended ascii character. The map
- chars can be either the characters themselves, or decimal or hexa-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CHARACTER TRANSLATION GoldED Manual, Page 58
-
-
- decimal numbers of the form "\d<dec>" or "\x<hex>" (like in the C
- programming language).
-
-
- The *.CHS files
- ──────────────────────────────────────────────────────────────────────
-
- These files are used for import and export translation of the CHARSET
- type character sets, and export of I51 and Composed escape sequences.
-
- The CHS files uses the format of the raw text files provided in the
- CHARSET3.ZIP example implementation of FSC-0054.003. Study some of the
- files provided if you want to know how to define them.
-
- The two keywords XLATESCSET and XLATCHARSET are used to define which
- files belong to what import and export set. You can define more than
- one import and export set for each file.
-
- The keyword XLATIMPORT defines which charset you have on your own
- machine - this would normally be "IBMPC". It can be useful to change
- this (using the Random System) in areas where another character set
- than IBMPC is the dominant (like Amiga or MacIntosh, whatever).
-
- The keyword XLATEXPORT defines the charset your messages should be
- exported to, if any.
-
- Confused? Yeah, I know - this is a confusing subject, and my implemen-
- tation and documentation is not perfect. Normally you will not have to
- worry about it. Turn it off completely if you don't understand it :-)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CHARACTER TRANSLATION GoldED Manual, Page 59
-
-
- ──────────────────────────────────────────────────────────────────────
- 19. KEYBOARD COMMAND REFERENCE
- ──────────────────────────────────────────────────────────────────────
-
-
- Most of the GoldED keyboard commands can be reached with just one key-
- stroke. To ease operation for experienced users of other message
- editors, GoldED comes with several sets of keys for each of the
- keyboard commands - direct non-shifted keys, Alt/Ctrl-keys and func-
- tion keys. Many of these key assignments will be familiar for users of
- Msged, Msged/Q, ME2 and FM.
-
- The following is a list of all keyboard commands, sorted by type and
- alphabetically, using the format
-
- <command> <short description>
-
- This list is also available in the context-sensitive help system on
- the <F1> key.
-
- It is possible to almost completely redefine the keyboard - this in
- done in the GOLDKEYS.CFG file, which also handles macro definition
- (see later).
-
- Arealist commands
- ──────────────────────────────────────────────────────────────────────
-
- AREAabort Abort the arealist.
- AREAaskexit Exit GoldED, prompt for final decision.
- AREAboardnos Toggle sequential areas vs. q-board numbers.
- AREAdosshell Shell to DOS.
- AREAheat Heat highwatermarks.
- AREAgotofirst Move selection bar to first area.
- AREAgotolast Move selection bar to last area.
- AREAgotonext Move selection bar to next area.
- AREAgotoprev Move selection bar to previous area.
- AREAjump Move selection bar to next marked area.
- AREAquitnow Exit immediately, no questions asked.
- AREAscan Scan areas - all or marked.
- AREAselect Enter the reader for the selected area.
- AREAtoggle Toggle mark on the selected area.
- AREAzap Zap highwatermarks.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KEYBOARD COMMAND REFERENCE GoldED Manual, Page 60
-
-
- Internal editor commands
- ──────────────────────────────────────────────────────────────────────
-
- EDITabort Abort editing this message - ask first.
- EDITanchor Set a block "anchor" on the current line.
- EDITaskexit Exit from GoldED - ask first.
- EDITcut "Cut" the block to the Cut'n'Paste buffer.
- EDITdelchar Delete the character at the cursor position.
- EDITdeleteeol Delete from cursor position to end of line.
- EDITdelleft Delete the character to the left of the cursor.
- EDITdelline Delete the curr. line. (Copied to the killbuf).
- EDITdelltword Delete the word to the left of the cursor.
- EDITdelrtword Delete the word to the right of the cursor.
- EDITdosshell Shell to DOS.
- EDITdupline Duplicates the current line.
- EDITexitmsg Drop this message - NO ASKING! DANGEROUS!
- EDITexporttext Exports the current block to a file.
- EDITgobegline Move cursor to beginning of line.
- EDITgobotline Move cursor to the bottom line in the display.
- EDITgobotmsg Move cursor to the last line in the message.
- EDITgodown Move cursor down to next line.
- EDITgoeol Move cursor to the end of the line.
- EDITgoleft Move cursor one position left.
- EDITgopgdn Move cursor one page of lines down.
- EDITgopgup Move cursor one page of lines up.
- EDITgoright Move cursor one position right.
- EDITgotopline Move cursor to the top line in the display.
- EDITgotopmsg Move cursor to the first line in the message.
- EDITgoup Move cursor up to the previous line.
- EDITgowordleft Move cursor to the previous word.
- EDITgowordright Move cursor to the next word.
- EDITheader Edit the message header, attributes etc.
- EDITimporttext Import text file into this message.
- EDITloadfile Loads the message file saved with EDITsavefile.
- EDITlookupcursor Lookup name/node at cursor position.
- EDITlookupdest Lookup TO: node.
- EDITlookuporig Lookup FROM: node.
- EDITnewline Terminate paragraph and/or add a new line.
- EDITpaste "Paste" a previously "Cut" block at the cursor.
- EDITquitnow Quit GoldED immediately - no asking.
- EDITsavefile Saves the current message as a file.
- EDITsavemsg Save this message.
- EDITspellcheck Calls an external spell checker for the msg.
- EDITtab Add spaces to the next tab-stop.
- EDITtogglecase Toggle the case of the cursor character.
- EDITtoggleinsert Toggle insert mode.
- EDITtolower Change the cursor character to lowercase.
- EDITtoupper Change the cursor character to uppercase.
- EDITundelete Undelete previously deleted lines.
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KEYBOARD COMMAND REFERENCE GoldED Manual, Page 61
-
-
- File selection commands
- ──────────────────────────────────────────────────────────────────────
-
- FILEabort Abort file selection.
- FILEaskexit Exit GoldED - ask first.
- FILEdosshell Shell to DOS.
- FILEgotofirst Go to first file.
- FILEgotolast Go to last file.
- FILEgotonext Go to next file.
- FILEgotoprev Go to previous file.
- FILEmark Mark file.
- FILEmarkall Mark all files.
- FILEquitnow Quit GoldED immediately.
- FILEselect Select the marked file(s).
- FILEtogglemark Toggle file mark.
- FILEunmark Unmark file.
- FILEunmarkall Unmark all files.
-
-
- Message lister commands
- ──────────────────────────────────────────────────────────────────────
-
- LISTabort Abort message lister.
- LISTaskexit Exit GoldED - ask first.
- LISTdosshell Shell to DOS.
- LISTgotobookmark Go to BookMark message.
- LISTgotofirst Go to first message.
- LISTgotolast Go to last message.
- LISTgotonext Go to next message.
- LISTgotoprev Go to previous message.
- LISTmarkingoptions Marking menu.
- LISTquitnow Quit GoldED immediately.
- LISTselect Go to reader at the selected message.
- LISTtogglebookmark Toggle BookMark on the selected message.
- LISTtogglemark Toggle Mark on the selected message.
-
-
- Nodelist browser commands
- ──────────────────────────────────────────────────────────────────────
-
- NODEabort Abort nodelist browsing.
- NODEaskexit Exit GoldED - ask first.
- NODEdosshell Shell to DOS.
- NODEgotofirst Go to first node.
- NODEgotolast Go to last node.
- NODEgotonext Go to next node.
- NODEgotoprev Go to previous node.
- NODEquitnow Quit GoldED immediately.
- NODEselect Select node.
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KEYBOARD COMMAND REFERENCE GoldED Manual, Page 62
-
-
- Message reader commands
- ──────────────────────────────────────────────────────────────────────
-
- READaskexit Exit GoldED, prompt for final decision.
- READchangeaka Change default AKA address for current area.
- READchangeattrs Change the attributes of the current message.
- READchangemsg Change current message.
- READchangeorigin Change default origin for the current area.
- READchangetemplate Change default template.
- READchangeusername Change default username.
- READcommentmsg Comment-Reply to message. (Reply to TO name).
- READcopymoveforward Enter the Copy/Move/Forward function menu.
- READdecreasemargin Decrease message margin. For test purposes.
- READdeletemsg Delete current/marked message(s). Ask first.
- READdosshell Shell to DOS.
- READfidorenumber Renumber Fido/Opus *.MSG files.
- READfilerequest Generate a filerequest from the current msg.
- READfindall Find string(s) in message header and text.
- READfindheader Find string(s) in message header.
- READgotobookmark Go to the "BookMark" message.
- READgotodownlink Go to the previous message in the replylink.
- READgotofirstmsg Go to the first message in the area.
- READgotolastmsg Go to the last message in the area.
- READgotomsgno Go to a specific message number.
- READgotonextarea Go directly to the next area.
- READgotonextmsg Go to the next message.
- READgotoprevarea Go directly to the previous area.
- READgotoprevmsg Go to the previous message.
- READgotouplink Go to the next message in the replylink.
- READincreasemargin Increase message margin. For test purposes.
- READlookupdest Lookup TO: node.
- READlookuporig Lookup FROM: node.
- READmakeuserlist Generate FIDOUSER.LST of all users in the area.
- READmarkingoptions Enter the marking menu.
- READmessagelist Enter the message lister.
- READmovequotemsg Quote-Reply in another area.
- READmsgcontinue Page down or go to next message.
- READmsgend Display last part of current message.
- READmsghome Display first part of current message.
- READmsglinedown Scroll message display.
- READmsglineup Scroll message display.
- READmsgpgdn Page message display.
- READmsgpgup Page message display.
- READnewarea Enter the area selection screen.
- READnewmsg Start a new message.
- READquitnow Exit GoldED immediately, no questions asked.
- READquotemsg Quote-Reply to message. (Reply to FROM name).
- READreplymsg Reply to the current message, without quoting.
- READtogglebookmark Toggle a "BookMark" on the current message.
- READtogglehexdump Toggle hexdump mode. For debugging purposes.
- READtogglehiddklud Toggle display of Hidden and Kludge lines.
- READtogglehidden Toggle display of Hidden lines.
- READtogglekludge Toggle display of Kludge lines.
- READtogglemark Toggle a message mark on the current message.
- READtogglemarkread Toggle "Read Marked" mode.
- READtogglepagebar Toggle the "PageBar" feature.
- READtogglerot13 Toggle ROT13 encryption for the current msg.
-
-
- ──────────────────────────────────────────────────────────────────────
- KEYBOARD COMMAND REFERENCE GoldED Manual, Page 63
-
-
- READtogglerealmsgno Toggle between seq. or real message numbers.
- READtoggletwits Toggle Twit display - Show/Blank/Skip/Ignore.
- READwritemsg Write message(s) to file or printer.
-
-
- See the Key Reference below for a list of the key symbols you can use
- in keyboard redefinition.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KEYBOARD COMMAND REFERENCE GoldED Manual, Page 64
-
-
- ──────────────────────────────────────────────────────────────────────
- 20. MACROS AND KEYSTACKING
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED has a fairly simple keyboard macro facility, which you can use
- to automate certain common operations. In addition, a "keystacking"
- facility allows you to create simple automatic macros on the fly.
-
- Macro definition
- ──────────────────────────────────────────────────────────────────────
-
- The macro definition syntax is modelled after the syntax used in the
- QEdit text editor:
-
- <assignment-key> Macro <commands or keys>
-
- Macros are defined in the GOLDKEYS.CFG file, where you can also find
- several examples.
-
- By using the word "Auto" as <assignment-key>, you can even define a
- special macro which will be automatically executed when you start
- GoldED.
-
-
- Keystacking
- ──────────────────────────────────────────────────────────────────────
-
- Keystacking is a special form of auto-macros. You simply specify a
- bunch of keys to be "stacked" in the (special internal) keyboard
- buffer for sequential execution.
-
- You can either specify a default set of keystacking in the .CFG
- configuration file, or override any default keystacking by typing the
- keystack definitions at the GoldED commandline or the GEDCMD environ-
- ment variable.
-
- See the Key Reference below for a list of the key symbols you can use
- in macros and keystacking.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- MACROS AND KEYSTACKING GoldED Manual, Page 65
-
-
- ──────────────────────────────────────────────────────────────────────
- 21. KEY REFERENCE
- ──────────────────────────────────────────────────────────────────────
-
-
- Below is the list of key symbols recognized by GoldED for key-
- board/macro definition and keystacking.
-
-
- Unshifted function keys
- ──────────────────────────────────────────────────────────────────────
-
- F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12
-
-
- Shift-function keys
- ──────────────────────────────────────────────────────────────────────
-
- #F1 #F2 #F3 #F4 #F5 #F6 #F7 #F8 #F9 #F10 #F11 #F12
-
-
- Alt-function keys
- ──────────────────────────────────────────────────────────────────────
-
- @F1 @F2 @F3 @F4 @F5 @F6 @F7 @F8 @F9 @F10 @F11 @F12
-
-
- Ctrl-function keys
- ──────────────────────────────────────────────────────────────────────
-
- ^F1 ^F2 ^F3 ^F4 ^F5 ^F6 ^F7 ^F8 ^F9 ^F10 ^F11 ^F12
-
-
- Alt-Numbers
- ──────────────────────────────────────────────────────────────────────
-
- @0 @1 @2 @3 @4 @5 @6 @7 @8 @9
-
-
- Alt-Letters
- ──────────────────────────────────────────────────────────────────────
-
- @A @B @C @D @E @F @G @H @I @J @K @L @M @N @O @P @Q @R
- @S @T @U @V @W @X @Y @Z
-
-
- Ctrl-Letters
- ──────────────────────────────────────────────────────────────────────
-
- ^A ^B ^C ^D ^E ^F ^G ^H ^I ^J ^K ^L ^M ^N ^O ^P ^Q ^R
- ^S ^T ^U ^V ^W ^X ^Y ^Z
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KEY REFERENCE GoldED Manual, Page 66
-
-
- Insert/Delete
- ──────────────────────────────────────────────────────────────────────
-
- Ins ^Ins @Ins
- Del ^Del @Del
-
-
- Home/End
- ──────────────────────────────────────────────────────────────────────
-
- Home ^Home @Home
- End ^End @End
-
-
- Page up/down
- ──────────────────────────────────────────────────────────────────────
-
- PgUp ^PgUp @PgUp
- PgDn ^PgDn @PgDn
-
-
- Cursor left/right
- ──────────────────────────────────────────────────────────────────────
-
- Left ^Left @Left
- Right ^Right @Right
-
-
- Cursor up/down
- ──────────────────────────────────────────────────────────────────────
-
- Up ^Up @Up
- Down ^Down @Down
-
-
- Misc other keys
- ──────────────────────────────────────────────────────────────────────
-
- Esc ^Grey* Key5 Space Tab #Tab @Tab BackSpace ^BackSpace
- @BackSpace Enter ^Enter @Enter
-
- Note that some of the Alt-keys, especially the cursor-related keys and
- the F11/F12 keys, are "extended" keys normally only available on
- systems with an extended keyboard bios. However, GoldED uses a few
- tricks to make some the extended keys available on non-extended
- systems.
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KEY REFERENCE GoldED Manual, Page 67
-
-
- ──────────────────────────────────────────────────────────────────────
- 22. LANGUAGE DEFINITION
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED allows the user to almost completely redefine the language
- dependent text in the program.
-
- The language dependent text in GoldED is defined in the plain ASCII
- text GOLDLANG.CFG file.
-
- See the example language file for the actual method and format of lan-
- guage redefinition.
-
- If you are planning to translate the text in GoldED, you should also
- look into the definition of the help screens.
-
- If you think you have made a good set of translated files, you should
- contact the nearest registration or support site for official distri-
- bution of your files with future versions and/or with disk registra-
- tions.
-
- You do not need permission from the author before announcing or
- distributing your own modified language files.
-
-
- NOTES
- ──────────────────────────────────────────────────────────────────────
-
- In the continuing development of GoldED, it is impossible to com-
- pletely maintain backward compatibility of the language format or the
- text defined there. New features may add and/or obsolete some defini-
- tions, or may change the format of others.
-
- The existing language file may contain definitions which are already
- obsolete, but which I haven't had time to search for and remove, as
- well as there may be some texts in GoldED which are not yet definable.
- All this will of course be corrected in future versions. If you find
- inconsistencies, please report them, because I may have forgotten
- them.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- LANGUAGE DEFINITION GoldED Manual, Page 68
-
-
- ──────────────────────────────────────────────────────────────────────
- 23. THE MSGBASE FORMATS
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED currently supports several different message database formats.
- The following is a list of them all, with notes about their charac-
- teristics and what special quirks to look out for with each of them.
-
-
- Fido/Opus/FTSC *.MSG
- ──────────────────────────────────────────────────────────────────────
- These are three variants of the same type of msgbase. It works by
- using one physical file per message (1.MSG, 2.MSG etc.), collecting
- them in a directory for each area. Depending on the clustersize on the
- harddisk, this can be a very wasteful and slow way to store messages.
- With a clustersize of about 512 bytes, the waste is acceptable, but
- the access speed can be dramatically slow if there are many *.MSG
- files. I'm told caches and BUFFERS adjustments can improve it, but
- there are limits.
-
- In echomail areas, this format has a special quirk: The first message
- (1.MSG) is normally used to store the so-called "highwatermark". The
- highwatermark tells the echomail processor where it should start
- scanning for new messages entered by users. By deleting (Zapping) the
- highwatermark, you can make the echomail processor re-scan the whole
- area again. This may cause messages to be sent out as "dupes", so this
- should be used sparingly and carefully, if at all! The highwatermark
- can also be "Heated" - which means that it is set to the last msg in
- the area. This prevents the echomail processor from finding newly
- entered unscanned msgs. Use with care.
-
- The variants: The "Fido" format was historically one of the first in
- FidoNet, and it is still used in many setups. The "Opus" format is a
- later variant, used in the Opus BBS system. It put some Fido un-
- documented(?) fields to use as date/time stamps. GoldED treats Fido
- and Opus as the same type, using date/time stamps. The "FTSC" format
- is yet another variant, where the undocumented fields instead are used
- to set the zone/point information for the msg. To the authors know-
- ledge, the Fido/Opus variant is the dominant, and the FTSC variant is
- doomed to oblivion.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE MSGBASE FORMATS GoldED Manual, Page 69
-
-
- QBBS (Hudson) MSG*.BBS
- ──────────────────────────────────────────────────────────────────────
- This msgbase format was invented by Adam Hudson, and was first used in
- his QuickBBS package. Later several other BBS'es were cloned from
- QuickBBS (like RemoteAccess and SuperBBS), which now use the same
- format.
-
- The basic format is built around 7 files:
-
- MSGTXT.BBS This contains the message text of all msgs in all areas.
- MSGHDR.BBS The headers for all the msgs in MSGTXT.BBS.
- MSGIDX.BBS A small index for MSGHDR.BBS.
- MSGINFO.BBS Tells how many msgs there are in each area.
- MSGTOIDX.BBS Index that contains all the TO names.
- LASTREAD.BBS Lastreads for all areas for each user in USERS.BBS.
- USERS.BBS Contains a record for each user. Make lastreads work.
-
- The format limits the total size of MSGTXT.BBS to a max of 16MB, which
- translates to about 16000 msgs of "average" length. GoldED automati-
- cally warns you if the limit is close to being reached, and advises
- you to pack the msgbase.
-
- The first incarnations of QuickBBS did not support "sharing" of the
- msgbase. This became more and more important in later years as multi-
- taskers and networks got cheaper. RemoteAccess BBS was the first to
- implement a useful method, and later a better method was evolved
- (known as "RA 1.01 or RA 1.1x"), which is now the standard for all
- modern software that supports msgbase sharing. GoldED fully supports
- the new standard of course.
-
- The main virtue of this format is that it is very fast to access the
- msgbase.
-
- The main disadvantage is that it is very sensitive to disk problems,
- and it is a common (horror) story that people loose their entire
- msgbase because the disk developed bad clusters or some program went
- berserk and messed up the msgbase files.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE MSGBASE FORMATS GoldED Manual, Page 70
-
-
- Squish *.SQ*
- ──────────────────────────────────────────────────────────────────────
- The Squish format is relatively new. It is invented by Maximus BBS
- author Scott Dudley in 1991, and was first used in Maximus CBCS v2.00.
- Soon after, GoldED was among the first message editors to support this
- new format (although it took quite a while to get it right, as my
- brave betatesters can testify ;-)
-
- This format is sort of a cross between the two first. It uses three
- files per area: A header/message text file (*.SQD), an index file
- (*.SQI) and a lastread file (*.SQL). The Squish echomail processor
- uses a fourth (*.SQB) to hold a dup-database.
-
- The uses of a database for each area - instead of one file per msg, or
- all msgs in one big database - makes this format fast, very safe and
- resistant to disk problems. Even if something messed up a Squish area,
- it can almost always be fixed and recovered, using the SQFIX utility
- that comes with the Squish echomail processor.
-
- A special feature of Squish areas is that they can be self-main-
- taining. You can "tell" a Squish area that it may only contain a
- maximum of so-and-so many msgs, and then it will automatically re-use
- old msgs when the limit is reached, and so it will practically stop
- growing. It will still need packing, but not nearly as often as a QBBS
- msgbase has to.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE MSGBASE FORMATS GoldED Manual, Page 71
-
-
- ──────────────────────────────────────────────────────────────────────
- 24. ENTERING MESSAGES
- ──────────────────────────────────────────────────────────────────────
-
-
- The process of entering a message deserves some description, because
- there a number of steps that may be a bit hard to figure out directly.
-
- You start a message by using one the following commands:
-
- READnewmsg Start a blank new message.
- READquotemsg Quote-reply the current msg (FROM person).
- READcommentmsg Quote-reply the current msg (TO person).
- READmovequotemsg Quote-reply in another area.
- READreplymsg Reply to current msg, but don't quote.
-
- The first thing that happens is that the header display comes to life,
- and allows you to change the names and addresses of destination and
- origination. In netmail areas, the userlist lookup feature is in
- effect for the destination name field. You move around in the header
- with the arrowkeys. Pressing <Tab> or <Enter> moves to the next field.
- Pressing <Enter> in the subject field or <Ctrl-Enter> anywhere, ends
- the header editing. Pressing <Esc> drops the message. While editing
- the header, you can use the Alt-keys to toggle message attributes.
-
- After the header editing is done, a menu appears, allowing you to
- change the message attributes, origin, template, start the internal or
- external editor or quit it.
-
- When you select to start the editor, the template is processed and
- prepared for use.
-
- Safely back from the editor, you are presented with a menu where you
- can select to save the message, drop the message, continue editing,
- view the message, change origin or ROT13 crypt it (the latter only if
- you are a registered user).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- ENTERING MESSAGES GoldED Manual, Page 72
-
-
- ──────────────────────────────────────────────────────────────────────
- 25. THE "HARDLINE" FEATURE
- ──────────────────────────────────────────────────────────────────────
-
-
- This section relates only to the use of an *external* editor.
-
- Like all message editors that allows the use of external text editors
- for writing messages, GoldED must deal with the problem of free-
- flowing text paragraphs versus hard-cr-terminated lines.
-
- Most text editors terminate *all* lines with a carriage return (CR,
- 13d, 0Dh). Unless you use a fairly short right margin in the text
- editor, those lines can be very annoying to quote if the quotemargin
- is shorter. This usually results in "ragged" quotes, with a long
- quoteline alternating with a short leftover. This looks bad, and
- requires a lot of work to edit to a respectable shape.
-
- To solve this problem, GoldED treats the file from the text just as if
- text blocks doesn't have any hard-cr's in them - it "reflows" the
- text. Of course, this immediately creates another problem: If you
- include a clipping from a log file, source code, table or other stuff
- that *requires* the text block to be aligned with itself. Those blocks
- would become scrambled and unreadable.
-
- GoldED recognizes a special control string, that tells the reflowing
- code to put hard-cr's on single lines or groups of lines. You define
- the string with the keyword "Hardline" in the configuration file. Here
- is an example of the use of the hardline string (in the example "<<"):
-
- <<
- ==== Log Cut ====
- ---------- Sat 21 Mar 92
- + 22.24.31 Event 0-@
- - 22.24.42 Preparing outbound mail
- = 22.58.47 RING
- = 22.58.55 CONNECT 2400
- + 22.59.02 Incoming call at 2400 baud
- 22.59.03 Sending text in BANNER.TXT
- ==== Log Cut ====
- <<
-
- In this example, the hardline string on the lines before and after the
- cutting tells the reflow code, that all those lines must the hard-cr
- terminated. The hardline string must be the only characters on the
- line, and it must be placed on the *first* position. The reflow code
- looks for <string><cr>. The hardline string works as a "toggle".
-
- The hardline string also has another use: If you put the string as the
- last characters on a line, that line will also be hard-cr terminated.
- Example:
-
- Greetings...<<
- Odinn Sorensen<<
-
- The last << in this example was not really necessary, because a blank
- line always ends the preceding line or paragraph with a hard-cr. In
-
-
- ──────────────────────────────────────────────────────────────────────
- THE HARDLINE FEATURE GoldED Manual, Page 73
-
-
- any case, the hardline string is stripped off before the message is
- saved.
-
- Some lines are by definition always hard-cr terminated, and does not
- need hardline strings. Those lines are quoted lines and control lines
- like kludges, tearlines and originlines. In addition, three identical
- characters at the beginning of a line also terminates the preceding
- paragraph.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE HARDLINE FEATURE GoldED Manual, Page 74
-
-
- ──────────────────────────────────────────────────────────────────────
- 26. QUOTE REFLOW
- ──────────────────────────────────────────────────────────────────────
-
-
- When you quote a message that already contains quoted lines, those
- lines may be too long for your quotemargin. Most message editors would
- then just cut a bit off the end and put it on a line below. GoldED
- does it differently - it determines the quotestring of the line, and
- then "reflows" all the following lines with the same quotestring and
- puts the quotestring back on the reflowed lines. This usually works
- great and looks good. It can also fail miserably in a few cases.
-
- The reflowing is in effect in both the message displaying and in
- quoting. If you want to observe the effects, try executing the
- READdecreasemargin or READincreasemargin commands (they don't have any
- default key assignments though).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- QUOTE REFLOW GoldED Manual, Page 75
-
-
- ──────────────────────────────────────────────────────────────────────
- 27. CARBON COPY AND CROSSPOSTING
- ──────────────────────────────────────────────────────────────────────
-
-
- Carbon Copying
- ──────────────────────────────────────────────────────────────────────
-
- Carbon copy (CC) is a way to send the same message to a number of
- people without the trouble of manually entering and copying a message
- for each of them. The CC works only in netmail or local areas. You can
- send any message, including fileattaches (in netmail) with the CC
- function.
-
- Carbon copies are created by putting the string "CC:" followed by one
- or more names or addresses, separated by commas, on one or more lines
- at the beginning of the message. The names and addresses must follow
- the same rules as when using the lookup function in the netmail
- header. Example:
-
- CC: 16, Joergensen, #230/143
-
- If you put a "#" in front of a name or address, that node will be left
- out of the list, but will still receive a carbon copy.
-
- You can also use address macros (see the NAMESFILE keyword) instead of
- names or addresses.
-
- If you often send carbon copies to the same people, it can get a bit
- tedious to type (and remember) every time. Therefore you can also
- specify a file with the names and addresses:
-
- CC: @TESTERS.LST
-
- Files names and addresses can be mixed on the same line. The lines in
- the file must be the same format as above. No nesting is allowed: You
- can't specify files within files.
-
- When you save the CC message, GoldED will scan the message text to
- find and process the CC: lines. When this is done, a menu will pop up
- and allow you change the format of the CC: lines, the attributes of
- the CC messages or drop the copies.
-
- When processing the CC list, GoldED will check each node in the
- nodelist and pop up the nodelist browser in case of more than one
- match or if the node was not found.
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CARBON COPY AND CROSSPOSTING GoldED Manual, Page 76
-
-
- Crossposting
- ──────────────────────────────────────────────────────────────────────
-
- Crosspost is similar to Carbon Copy, except that instead of sending
- copies to a list of persons, it posts copies of a message in several
- different conferences. Typical usage is announcement of files, vital
- BBS information and other general interest info.
-
- To crosspost a message is simple - just add lines in this format:
-
- XC: <echoid> [echoid] [..]
-
- The "XC:" must be the first three characters on the line. The <echoid>
- must be valid echoid's defined in GoldED. Example:
-
- XC: GOLDED, NEWFILES.R23, ENET.SOFT
-
- This would produce the following output in the message:
-
- * Crossposted in GOLDED
- * Crossposted in NEWFILES.R23
- * Crossposted in ENET.SOFT
-
- And post it in the conferences.
-
- Please moderate your use of this feature - it adds duplicate infor-
- mation to the mail flow, and excessive use may be frowned upon by
- cost-sensitive individuals.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- CARBON COPY AND CROSSPOSTING GoldED Manual, Page 77
-
-
- ──────────────────────────────────────────────────────────────────────
- 28. ENCRYPTING MESSAGES
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED allows you to en/decrypt messages encoded with the ROT13
- encryption method. ROT13 is very simple: It just swaps the letters
- "A-M", "a-m" with "N-Z", "n-z" and vice-versa.
-
- ROT13 is mostly used in UUCP (or whatever they are called :-) net-
- works, where it is used as a "spoiler warning", so that game solu-
- tions, joke punchlines and other stuff is not read by accident. In
- those networks, all message readers have ROT13 de/crypting capabili-
- ties.
-
- In FidoNet, not all message readers have ROT13 capability, and the
- current policy (Policy 4) states:
-
- 2.1.4 Encryption and Review of Mail
-
- FidoNet is an amateur system. Our technology is such that the
- privacy of messages cannot be guaranteed. As a sysop, you have the
- right to review traffic flowing through your system, if for no
- other reason than to ensure that the system is not being used for
- illegal or commercial purposes. Encryption obviously makes this
- review impossible. Therefore, encrypted and/or commercial traffic
- that is routed without the express permission of all the links in
- the delivery system constitutes annoying behavior.
-
- If you have registered GoldED, you will be able to encrypt your
- messages with ROT13, but you should not use the crypting facility of
- GoldED, unless your network allows it, and *never* in international
- echoes.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- ENCRYPTING MESSAGES GoldED Manual, Page 78
-
-
- ──────────────────────────────────────────────────────────────────────
- 29. NODELIST BROWSE AND LOOKUPS
- ──────────────────────────────────────────────────────────────────────
-
-
- When you write a netmail message, you must know the name and net
- address of the recipient. Unless you have a remarkable memory, this
- information can be a bit hard to remember. Therefore GoldED uses a
- special nodelist/userlist index to enable you to quickly lookup any
- node.
-
- The index is created by the GoldNODE nodelist/userlist compiler.
- GoldNODE supports the standard "St.Louis" nodelists, the FrontDoor
- Boss/Point pvt/nodelist extensions (also known as Version7 extensions)
- and the simpler FIDOUSER.LST userlist.
-
- When you enter a name or address in the header (the TO: field) and
- press <Enter>, GoldED looks in the nodelist index to find the missing
- data. You can enter the address in the name field. Names to be
- searched for must be entered last name first (because of the way the
- index is structured). If you enter a partial name or address, GoldED
- will find the closest match. Addresses can be entered in short form,
- based on the current AKA, like .3 for the address of your third Point,
- or 33 for node 33 in your net.
-
- Before the nodelist is searched, the list of address macros are first
- scanned, and if a match is found there, the information there is used
- instead.
-
-
- Nodelist browser
- ──────────────────────────────────────────────────────────────────────
-
- When GoldED has found a match, it looks a bit further to see if there
- are more matches. If not, the matching data is inserted in the header,
- and you can continue editing. If more than one match was found, it
- starts the nodelist browser. Here you can browse around and find the
- correct destination node. When found, you select it with <Enter>. The
- full name and address of the node you selected is then placed in the
- appropriate fields in the header. Pressing <Esc> in the browser quits
- it without inserting any node information.
-
- The list of nodes in the browser is sorted differently, according to
- what you entered. If you entered a name, the list is sorted alpha-
- betically by last name. If you entered an address, the list is sorted
- ascending by address.
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- NODELIST BROWSE AND LOOKUPS GoldED Manual, Page 79
-
-
- Lookups
- ──────────────────────────────────────────────────────────────────────
-
- The nodelist browser can also be accessed in other ways. The keys F10
- and Shift-F10 brings up the browser at the FROM and TO names (nodes)
- respectively, to let you inspect their nodelist data. It's quite
- handy, you will wonder how you could do without it - I did :-)
-
- This nodelist lookup feature can also be used when in the internal
- editor, but an even more useful key is available there. By pressing
- Alt-L, the browser will pop up for the name or address at the editor
- cursor position!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- NODELIST BROWSE AND LOOKUPS GoldED Manual, Page 80
-
-
- ──────────────────────────────────────────────────────────────────────
- 30. USER DATABASE LOOKUP
- ──────────────────────────────────────────────────────────────────────
-
-
- For BBS sysops:
-
- In QBBS and Squish (and *.MSG, if you are using Maximus) type areas,
- GoldED can perform an additional type of name lookup, using wildcards.
-
- This form of lookup is triggered by using DOS/4DOS-style wildcard
- characters in the name you want to lookup. Examples:
-
- To: Joe*
- To: *Blow
- To: Od?n*
-
- The lookup is performed in the QBBS-style USERS.BBS (and variants), or
- the Maximus-style USER.BBS. Depending on the size of your user data-
- base and the speed of your computer, the lookup may take a little
- while.
-
- As currently implemented, this user database lookup is only good for
- simple one-shot lookups - you can't bring up a browser to pick the
- user, or see his/hers other user data.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- USER DATABASE LOOKUP GoldED Manual, Page 81
-
-
- ──────────────────────────────────────────────────────────────────────
- 31. MARKING MESSAGES
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED has a message marking system, which allows flexible mani-
- pulation with selected messages.
-
- You can either mark messages manually one by one using the
- READtogglemark command <Space>, or use the READmarkingoptions menu
- <Alt-S>. With the marking menu, you can for example mark all messages
- in a particular thread (replychain), or all messages that match a
- certain string or a number of other criteria.
-
- When you have marked the messages, you can then Copy, Move, Delete or
- Write them. Or you can switch to reading only the marked messages.
-
- The marks stay in position until removed (unmarked) or you exit
- GoldED. Marks are kept even if you leave the current area and do
- business in another for a while.
-
- Another, more volatile, form of mark is the "bookmark". Bookmarks can
- be used for returning to a certain position after a stroll out a long
- reply chain and stuff like that. There is only one bookmark, and it is
- reset when you leave the area. Using the Find function leaves a
- bookmark at the current message.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- MARKING MESSAGES GoldED Manual, Page 82
-
-
- ──────────────────────────────────────────────────────────────────────
- 32. THE FILE REQUEST FEATURE
- ──────────────────────────────────────────────────────────────────────
-
-
- Often when you see a msg where new files are announced, you wish you
- could simply press a key and select files to request. Well, with
- GoldED you can!
-
- The file request function (default key Ctrl-F) will scan the current
- message and present you with a list of the requestable files it found.
- If the message was generated with one of the "standard" file announ-
- cement programs (like RFD, Ticket etc), GoldED will even show the file
- descriptions.
-
- You select the files by toggling marks with the Space key. A '+' will
- show in front of the selected files. The selections can be discarded
- by pressing Esc. When done with the selections, press Enter to con-
- tinue.
-
- Now the destination area must be selected from the list. You have to
- pick a netmail area of the *.MSG type, since the QBBS and Squish
- netmail areas are currently not supported by most mailers today.
-
- After selecting the area, check that the header data (TO name etc) is
- correct. You can now go on to perhaps write a thank you note in the
- accompanying msg, or you can save (empty) your msg immediately (if you
- have the EDITMENU keyword set to Yes).
-
- At the moment you start editing the header, the filenames and descrip-
- tions are written to a FILES.BBS in the INBOUNDPATH. This can be very
- helpful if you are getting files for your own BBS and are tired of
- inventing or finding descriptions for all those files.. The fact that
- the FILES.BBS is written to disk before you even save you msg, can be
- used to get "free" descriptions later from the response msgs some
- mailers send back when you do a file request.
-
- There are currently a couple of limitations/gotcha's in the file
- request function:
-
- ■ You can only request as many files as can fit in the subject line
- of one msg.
- ■ GoldED recognizes several different types of file announcement
- formats, but some may not be fully supported. This means that
- legitimate descriptions may not be found by GoldED, or that some
- files are not recognized as such.
- ■ If a msg does not conform to a known announcement format, it is
- instead (actually it is _also_) scanned for a number of standard
- archive extensions. These extensions are currently not con-
- figurable. The supported extensions are: .ARC .ARJ .COM .EXE .LHA
- .LZH .PAK .RUN .SDA .SDN .ZIP .ZOO. Only one such file per line
- can be found by GoldED, and only if it is "straight" - no spaces
- between name and extension, and no "funny" characters in the
- filename. The description is simply the rest of the line.
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE FILE REQUEST FEATURE GoldED Manual, Page 83
-
-
- ──────────────────────────────────────────────────────────────────────
- 33. KLUDGE LINES
- ──────────────────────────────────────────────────────────────────────
-
-
- Kludge lines are special control lines, that begin with a ^a (01h) as
- the first character of the line, followed by a unique identifying name
- and the relevant control information.
-
- GoldED is aware of a lot of these kludges, and supports a number of
- them, if you want to have them inserted in your messages.
-
- Some kludges are useless junk and commercials for this and that
- software, but a few are useful for miscellaneous purposes. In the
- following, I will list the known and supported kludges, and a short
- description of what they are used for.
-
- AREA:<echoname>
- ──────────────────────────────────────────────────────────────────────
- This is not really a kludge, and it doesn't begin with a ^a, but I
- included it on the kludge list because it sometimes turned up in
- echomail areas where it should have been stripped off by the mail
- tosser.
-
- CC: <name> <address>
- ──────────────────────────────────────────────────────────────────────
- When GoldED produces carbon copies, it adds to each message a full
- list of the persons who get a copy. One version of this list is
- hidden behind the CC: kludge.
-
- CHARSET:<charset identifier>
- ──────────────────────────────────────────────────────────────────────
- Proposed in FSC-0050 and FSC-0054, this kludge is an attempt to
- find a solution to the problem of the high-bit characters (like
- the IBM PC vs Amiga vs Mac etc. national chars) in messages.
- GoldED can recognize, use and generate this kludge.
-
- CHRC:<font change id>
- ──────────────────────────────────────────────────────────────────────
- Proposed in FSC-0054, this is a kludge for changing fonts, under-
- lining and other stuff.
-
- CHRS:<charset identifier>
- ──────────────────────────────────────────────────────────────────────
- Alternative FSC-0054 version of the CHARSET kludge.
-
- DESTADDR:<destaddress>
- ──────────────────────────────────────────────────────────────────────
- This one is not proposed anywhere, but it looks like it gives the
- address of the intended recipient. GoldED takes the address for
- the dest field.
-
- DOMAIN <destdomain> <destaddress> <origdomain> <origaddress>
- ──────────────────────────────────────────────────────────────────────
- Proposed in FSC-0038, this tries to solve the problem of mail
- crossing domain boundaries. GoldED takes both addresses.
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KLUDGE LINES GoldED Manual, Page 84
-
-
- EID:<crc16> <stamp> [replycrc16] <replystamp>
- ──────────────────────────────────────────────────────────────────────
- Proposed in FSC-0031, this is used for dupe checking and reply
- linking. The EID is today generally considered as garbage, but a
- lot of older mail processors such as QMail still generate it.
-
- FLAGS <special attributes>
- ──────────────────────────────────────────────────────────────────────
- Proposed in FSC-0053, this is a special netmail kludge used by the
- FrontDoor and D'Bridge mailers and the IMail mail processor. It
- provides extra attributes not found among the standard attributes
- in the normal message/packet headers. GoldED uses and generates
- this kludge, if you set the attributes.
-
- FMPT <from point>
- ──────────────────────────────────────────────────────────────────────
- Defined in FTS-0001, this tells the Point number of the
- originator. Netmail only. GoldED can generate this line.
-
- GATECHK:<???>
- ──────────────────────────────────────────────────────────────────────
- Some sort of gating kludge? Don't know what it's for.
-
- GROUP:<echoname>
- ──────────────────────────────────────────────────────────────────────
- I think this one comes from stray Groupmail messages. Similar to
- the AREA: kludge.
-
- I51 (no parameters)
- ──────────────────────────────────────────────────────────────────────
- Proposed in FSC-0051, this indicates that the message text con-
- forms to the ISO 8859-1 (LATIN-1) character set, and may contain
- certain escape codes. The ISO 8859-1 set is used by the Amiga,
- Window 3.0 and several mainframes. GoldED can recognize, use and
- generate this kludge.
-
- INTL <destaddress> <origaddress>
- ──────────────────────────────────────────────────────────────────────
- Defined in FTS-0001, this one solves the problem of crossing Zone
- boundaries. Netmail only. GoldED can generate this line.
-
- MSGID: <origaddress> <serialno>
- ──────────────────────────────────────────────────────────────────────
- Defined in FTS-0009, this is a method for unique identification of
- a message. It can be used for dupe checking and replylinking.
- GoldED can generate this line.
-
- MSGTO: <destaddress>
- ──────────────────────────────────────────────────────────────────────
- This one is not proposed anywhere, but it looks like it gives the
- address of the intended recipient. GoldED takes the address for
- the dest field.
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KLUDGE LINES GoldED Manual, Page 85
-
-
- Original: <Carbon copy, original name>
- ──────────────────────────────────────────────────────────────────────
- Generated by the FrontDoor FM editor when it produces carbon copi-
- es.
-
- PATH: <list of nodes>
- ──────────────────────────────────────────────────────────────────────
- Defined in FTS-0004, this is a valuable tool for finding dupe
- links and other structural faults in the net structures. Unfor-
- tunately the list of nodes is 2D (net/node), and this creates
- problems when exporting echomail across zones.
-
- PTH: <list of nodes>
- ──────────────────────────────────────────────────────────────────────
- Not yet a FSC (or is it?), this is a 5D-version of the PATH
- kludge, which sticks to the top of the msg.
-
- PID: <identifier> <version> [serialno]
- ──────────────────────────────────────────────────────────────────────
- Proposed in FSC-0046, this takes a stab at the tearline abuse, and
- puts "safe" information about the first mail processing software
- in the line. This could be message editors, mail scanners and
- other stuff.
-
- RFD: <id>
- ──────────────────────────────────────────────────────────────────────
- Received For Distribution. A kludge inserted by one of the file
- announcement programs.
-
- REPLY: <replyaddress> <replyserialno>
- ──────────────────────────────────────────────────────────────────────
- Defined in FTS-0009, this is the MSGID: counterpart. When replying
- to a message with a MSGID:, the MSGID: of the original is renamed
- to REPLY:.
-
- RID:<stuff>
- ──────────────────────────────────────────────────────────────────────
- Unknown kludge which looks suspiciously like the EID.
-
- SEEN-BY: <list of nodes>
- ──────────────────────────────────────────────────────────────────────
- Defined in FTS-0004, this is a tool for finding dupe links and
- other structural faults in the net structures. Depending on the
- mail tosser, the seen-by's may or may not have a preceding ^a
- character. Unfortunately the list of nodes is 2D (net/node), and
- this can create problems when exporting echomail across zones.
-
- SN:<serialno>
- ──────────────────────────────────────────────────────────────────────
- Serial number inserted by the Dutchie message editor.
-
- TCL1:, TCL2: <long hex string>
- ──────────────────────────────────────────────────────────────────────
- Old obsolete swedish dupecheck/replylink kludge.
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KLUDGE LINES GoldED Manual, Page 86
-
-
- TOPT <to point>
- ──────────────────────────────────────────────────────────────────────
- Defined in FTS-0001, this tells the Point number of the destina-
- tion. Netmail only. GoldED can generate this line.
-
- TZ <offset from UTC>
- ──────────────────────────────────────────────────────────────────────
- Specifies the time to *add* to the header time to get the UTC
- (Universal Time Coordinated) time. Generated by newer versions of
- the TrackMail netmail processor.
-
- VIA: <netmail tossing info>
- ──────────────────────────────────────────────────────────────────────
- Routed netmail messages usually gets a Via line for each node it
- passes through. This can be used for tracing faults in the netmail
- routing structure.
-
- XID:<stuff>
- ──────────────────────────────────────────────────────────────────────
- Unknown kludge which looks suspiciously like the EID.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KLUDGE LINES GoldED Manual, Page 87
-
-
- ──────────────────────────────────────────────────────────────────────
- 34. KNOWN BUGS
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED contains a number of still unfixed bugs or semi-unsolvable
- problems. The following list is not necessarily complete.
-
-
- Internal editor
- ──────────────────────────────────────────────────────────────────────
-
- The internal editor has many odd bugs, most prominently the line wrap-
- ping when editing at the end of lines and the block (cut/paste)
- functions. As you may know, the internal editor code is ported from
- the source of another editor, Msged 2.00, and the code was buggy from
- the start - my implementation did not make it much better... It is
- almost impossible to removed the bugs (I have tried many times), and I
- have resolved to simply write a completely new internal editor in a
- future version.
-
-
- Swapping
- ──────────────────────────────────────────────────────────────────────
-
- Several users have experienced problems using the swapping facility in
- GoldED to shell to DOS or an external editor. Usually this is a result
- of conflicts between various EMS/XMS/extended memory managers. Try
- using "DOSSWAP DISK", this usually always work (if there is enough
- free disk ;-). You might also try turning off the OVERLAY keyword, if
- you had it on.
-
-
- Overlays
- ──────────────────────────────────────────────────────────────────────
-
- In at least one case, I have heard of conflicts between an overlayed
- version of Binkley, running in a multitasking environment with GoldED.
- Binkley and GoldED both seems to use and grab the same overlay manager
- interrupt...
-
-
- There are other bugs and problems, but I can't remember them right
- now...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- KNOWN BUGS GoldED Manual, Page 88
-
-
- ──────────────────────────────────────────────────────────────────────
- 35. RESTRICTED FEATURES
- ──────────────────────────────────────────────────────────────────────
-
-
- GoldED has a few non-vital features restricted for unregistered users:
-
- ■ Tearline definition.
- ■ The LoadLanguage feature.
- ■ ROT13 message encryption.
- ■ Most of the keywords that can be specified more than once (like
- ORIGIN) are restricted to a max of 10.
-
- In addition, the program will add an extra random pause when
- initializing. You can press a key to bypass the pause, or use the
- keystacking mechanism.
-
- These restrictions and the pause will go away when you register...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- RESTRICTED FEATURES GoldED Manual, Page 89
-
-
- ──────────────────────────────────────────────────────────────────────
- 36. FUTURE PLANS
- ──────────────────────────────────────────────────────────────────────
-
-
- I have a long list of features waiting to be implemented, and it grows
- all the time. Here are a few of the bigger ones:
-
- ■ New internal editor.
- ■ Fully menued setup program (built-in).
- ■ Menu system to supplement direct keyboard operation.
- ■ More flexible random system / area definition.
- ■ Scan for/read your mail in all areas.
- ■ Better marking facilities.
- ■ Highest read.
- ■ Replies reading mode.
- ■ Nodelist browsing in levels a'la FrontDoor.
- ■ Offline reader compatibility (QWK, XRS, XPress etc).
- ■ Other msg formats such as PCBoard, WildCat, XBBS, GSBBS etc.
- ■ Smarter error handling.
- ■ Better mouse support.
- ■ Improved message template format.
- ■ Conditional macros and macro recording.
- ■ Versions for OS/2 and Windows 3.x.
- ■ Simpler "Lite" version.
- ■ Many other things!
- ■ Bugfixes...
-
- Keep the suggestions coming!
-
- -- ++ -- ++ --
-
- At the time of writing, this version (2.40) is planned to be the last
- in 2.xx series. There may be a couple of bugfix/maintenance releases,
- but that's it.
-
- The program has become so large and the sourcecode so complex and
- tangled, that further development would simply be irresponsible.
-
- I am now working on a complete rewrite of GoldED. The first results of
- this pretty massive effort will be most likely be a "lite" version
- with only the most important features. It may be released under a
- different name. See the GOLDED and GOLDED.BETA echoes for further
- information on the development of the new versions, but don't hold
- your breath - it will probably be many months until I have anything
- interesting to show.
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- FUTURE PLANS GoldED Manual, Page 90
-
-
- ──────────────────────────────────────────────────────────────────────
- 37. DISTRIBUTION AND REGISTRATION SITES
- ──────────────────────────────────────────────────────────────────────
-
-
- The major public releases of GoldED are distributed via the SDS (Soft-
- ware Distribution System), and should therefore be available around
- the world at your local SDS node.
-
- In addition to this, public beta versions may be available from the
- registration sites, and many other nodes.
-
- See the REGISTER.DOC for more information about registering and a list
- of the registration sites.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- DISTRIBUTION AND REGISTRATION SITES GoldED Manual, Page 91
-
-
- ──────────────────────────────────────────────────────────────────────
- 38. SUPPORT CONFERENCES
- ──────────────────────────────────────────────────────────────────────
-
-
- Echoid GOLDED, available on all major backbones around the world. The
- author is present, and does his best to answer questions, well
- assisted by many enthusiastic users. Comments and suggestions are
- always welcome.
-
- Local support echoes may be available in some nets/regions. Ask your
- Boss/Hub/NEC/REC/ZEC or the local registration site, if any.
-
- PLEASE NOTE: I receive a lot of netmail, and read a lot of echomail.
- This takes time. Lots of time. Answering my mail usually takes even
- *more* time. All the (net)mail takes time away from development of
- GoldED, so please consider if your questions could be answered by
- other users in your network or region instead.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- SUPPORT CONFERENCES GoldED Manual, Page 92
-
-
- ──────────────────────────────────────────────────────────────────────
- 39. ACKNOWLEDGEMENTS
- ──────────────────────────────────────────────────────────────────────
-
-
- I would like to thank the following persons, who have, in one way or
- another, helped GoldED to become what it is: (alphabetical list)
-
- Adam Hudson QuickBBS.
- Andrew Milner The RemoteAccess BBS.
- Chris Irwin The D'Bridge mailer.
- Fabian Fabris The IMail mail processor.
- Hansen & Wolthers The YAMMED editor.
- Jim Nutt The Msged editor and source.
- Joaquim H. Homrighausen FrontDoor and TosScan.
- Kristian Ottosen The ME2 editor.
- Mike Smedley and IDC The CXL/TCXL library.
- P.J.Muller The Msged/Q editor and source.
- Scott Dudley Maximus and Squish.
- Stig Jacobsen Various source code and testing.
-
- Not least, I thank all the registration sites, betatesters and users
- for all their inspiring suggestions and bug reports. Keep'em coming!
-
- Without the following software, GoldED would have been much harder to
- write:
-
- QEdit (SemWare). My favorite text-editor.
- Borland C++. My favorite C++ compiler (hmm...)
- 4DOS (J.P.Software). My favorite COMMAND.COM replacement.
-
- I thank the authors and companies for producing those fantastic pieces
- of software.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- ACKNOWLEDGEMENTS GoldED Manual, Page 93
-
-
- ──────────────────────────────────────────────────────────────────────
- 40. THE AUTHOR
- ──────────────────────────────────────────────────────────────────────
-
-
- Name:
- Odinn Sorensen (Full name: Odinn Hagleman Sφrensen)
-
- Birthdate:
- 17 February 1969, born in Iceland, now lives in Denmark.
-
- Occupation:
- Self-taught C/C++ programmer. Started his own business (Goldware
- International) after quitting a boring job in november '91. Now
- working full-time on GoldED and a couple of free-lance programming
- jobs.
-
- Personality:
- Quiet, all-round nice guy.
-
- Equipment:
- 486/33, 8MB RAM, SuperVGA/ET4000/HiColor, 2x128MB HD. (Power! :-)
- 386/25, 5MB RAM, VGA/Mono, 128MB HD, USR New HST/DS modem. (BBS).
- Canon BJ-10e BubbleJet printer.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- THE AUTHOR GoldED Manual, Page 94
-
-
- ──────────────────────────────────────────────────────────────────────
- APPENDIX A - Attributes
- ──────────────────────────────────────────────────────────────────────
-
-
- The letters in square brackets [], indicates the compatibility with
- message formats or major software.
-
- F FLAGS kludge. (FrontDoor, D'Bridge).
- M *.MSG format. (Fido, Opus etc).
- Q QuickBBS format. (QuickBBS, RemoteAccess, SuperBBS).
-
- <attributes> =
- A/S [F..] Archive Sent.
- ARQ [.MQ] Audit Request.
- ATT [FMQ] Attached File.
- CFM [F..] Confirmation Request.
- CRA [FMQ] Crash.
- DIR [F..] Direct.
- FRQ [FM.] File Request.
- HLD [FM.] Hold.
- HUB [F..] Hub/Host Route.
- IMM [F..] Immediate.
- K/S [FMQ] Kill Sent.
- KFS [F..] Delete File Sent.
- LOC [.MQ] Local (always on by default).
- LOK [F..] Locked.
- ORP [.M.] Orphan.
- PVT [FMQ] Private.
- RCV [.MQ] Received.
- RRC [.MQ] Return Receipt.
- RRQ [FMQ] Return Receipt Request.
- SNT [.MQ] Sent.
- TFS [F..] Truncate File Sent.
- TRS [.M.] Transit.
- URQ [.M.] Update File Request.
- XMA [F..] XMail.
- ZON [F..] Zonegate Route.
-
-
- NOTE: Not all the FLAGS attributes are supported completely by any one
- program.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- APPENDIX A - Attributes GoldED Manual, Page 95
-
-
- ──────────────────────────────────────────────────────────────────────
- APPENDIX B - Address masks
- ──────────────────────────────────────────────────────────────────────
-
-
- <addressmask> = Normal address specifications + special "macronames":
-
- MYZONE, MYNET, MYNODE, MYPOINT = parts of main address.
-
- ALL, ? Wildcard for one address part.
- NETxxx MYZONE:NETxxx/ALL.0
- NCxxx MYZONE:NCxxx/0.0
- RCxxx MYZONE:RCxxx/0.0
- ZCxxx ZCxxx:ZCxxx/0.0
- ZONExx ZONExx:ALL/ALL.0
- EARTH ALL:ALL/ALL.ALL
- WORLD ALL:ALL/ALL.0
- OURNET MYZONE:MYNET/ALL.0
- MYPOINTS MYZONE:MYNET/MYNODE.ALL
- OURPOINTS MYZONE:MYNET/ALL.ALL
- ZONEGATEx MYZONE:MYZONE/ZONEGATEx.0
-
- Please note that these macronames are not fully implemented, and
- cannot be used in situations like Carbon Copy.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ──────────────────────────────────────────────────────────────────────
- APPENDIX B - Address masks GoldED Manual, Page 96
-