home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-04-04 | 131.8 KB | 3,732 lines |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ------------
-
- GoldED
-
- ------------
-
-
- A full-feature Sysop/Point message reader/editor
-
-
- Version 2.30
-
- Released april 5, 1991
-
-
- Program and manual written by Odinn Sorensen
-
- Copyright (C) 1990-1991 by Odinn Sorensen. All Rights Reserved
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 1
- ----------------------------------------------------------------------
-
- F E A T U R E S
-
- * Supports the QuickBBS-style (MSG*.BBS) message database.
- * Supports the Fido/Opus-style (*.MSG) message files.
- * Supports most popular mailer/processor area configurations.
- * Many configuration options.
- * Has an internal editor for writing messages.
- * Can call an external shellchecker from the internal editor.
- * Can use external editor or word processor for writing messages.
- * Supports character translation via FSC-0050/51/54 and Composed.
- * Message templates.
- * Carbon Copy and Crossposting feature.
- * Random System for origins and other data.
- * Nodelist/userlist lookup and browsing.
- * Bulk message marking and copy/move/printing.
- * Forwarding and moved replys to other conferences.
- * File selection for file attaching.
- * Full keyboard redefinition.
- * Keyboard macros and keystacking from the commandline.
- * Configurable language.
- * Configurable colors.
- * Context-sensitive help system.
- * Twitting of names and subjects.
-
- ... And many other neat features!
-
-
-
- R E Q U I R E M E N T S
-
- * Any IBM PC compatible computer with at least 512K memory.
- * MS-DOS or PC-DOS 3.00 or above.
- * Diskspace for the GoldED files + msgbase files.
- * Enough free file handles in CONFIG.SYS (I have FILES=30).
- * A QuickBBS or Fido/Opus compatible messagebase.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 2
- ----------------------------------------------------------------------
-
- T H I S M A N U A L
-
- As you will find out, this is essentially a reference manual for
- the configuration of GoldED.
-
- There are currently no contents page or word index, this will be
- added in a future version of this manual. Consider yourselves
- lucky that there are page numbers! :-)
-
- I wish I had time to write a more general introduction to the
- world of echomail communication and the hands-on use of my
- program, but manual writing is not my favorite passtime, fun as it
- might be at times.
-
- GoldED is designed to be very configurable, and unfortunately this
- always 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 confident with the
- operation of GoldED.
-
- I hope you will like and enjoy what you see - many others have.
-
- Have a nice day!
-
- Odinn Sorensen, Author of GoldED.
-
-
-
- L E G A L S T U F F
-
- GoldED is provided as is, with no warranty of any kind, either
- expressed 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 information about the legal
- uses of this program.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 3
- ----------------------------------------------------------------------
-
- Q U I C K I N S T A L L A T I O N
-
- GoldED is a very complex program with many options meant for
- experienced users. If you have been using GoldED before, or
- consider yourself a configuration wizard, go ahead and use the
- advanced configuration provided. It contains just about *all* the
- possible configuration options available, and has been known to be
- hard nut to crack even for experienced users!
-
- For new and/or inexperienced users, a simple standard setup has
- been provided to get you going fairly painlessly.
-
- This is a step-by-step procedure for quick installation:
-
- * Make a new directory. GoldED uses a lot of 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
- directory.
-
- Simple configuration:
- ---------------------
- * Edit GOLDED.CFG to fit your setup.
- * Run GOLDLANG.EXE to compile various configfiles.
- * Run GOLDNODE.EXE to compile your nodelists or userlists.
- * 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 many interesting and useful things there!
-
- Advanced configuration:
- -----------------------
- * Run ADVANCED.EXE to unpack the advanced configuration.
- * Edit GOLDED.CFG and GOLDED.ARE to fit your setup.
- * Run GOLDLANG.EXE to compile various configfiles.
- * Run GOLDNODE.EXE to compile your nodelists/userlists.
- * Run GOLDED.EXE.
-
- Good luck!
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 4
- ----------------------------------------------------------------------
-
- C O M M A N D L I N E A R G U M E N T S
-
- Syntax: GOLDED [keystacking] [options]
-
- Options:
- -C<configname>
- Specifies another configuration file than GOLDED.CFG.
-
- -E<echoid>
- If specified, GoldED starts directly in that echo,
- bypassing the area selection screen. See the STARTECHO
- configuration keyword for more info.
-
- -O<ovlsize>
- Specifies the overlay size for GoldED (the default is
- approximately 64K). Higher values (up to 200K) causes
- GoldED to run faster, and use more memory. Lower values
- (down to about 30K) makes it run slower, in less memory.
-
- -S<sortspec>
- Sort all areas according to <sortspec>. (see AREASORT
- config keyword).
-
- -T<seconds>
- Set the timeout value. A value of zero (0) means never
- timeout. (TIMEOUT config keyword).
-
-
- Keystacking:
-
- Any non-option characters on the commandline are stuffed into
- the keyboard buffer. See the chapter on keyboard definition
- and the STACKKEYS keyword for more info.
-
- Example: GOLDED @S A
- Makes GoldED go to the area scanning menu <Alt-S>, and
- select scanning of <A>ll areas.
-
- >>> See the Macros and Keystacking section for more info.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 5
- ----------------------------------------------------------------------
-
- E N V I R O N M E N T V A R I A B L E S
-
- GoldED recognizes and uses several environment variables.
-
- These are specific to GoldED:
- -----------------------------
-
- SET GOLDED=<Path>
- Path to the GOLDED.CFG file. It is recommended to set this
- variable.
-
- SET GEDCMD=<Commandline Arguments>
- Specifies additional commandline arguments. Use this if you
- want to specify arguments, but need to run GoldED without them
- (for example when renaming GOLDED.EXE to DBEDIT.EXE). You can
- override the environment arguments with "real" commandline
- arguments.
-
- These are used by the area config reader in GoldED:
- ---------------------------------------------------
-
- SET FD=<Path>
- Path to the FrontDoor/TosScan system files.
-
- SET RA=<Path>
- Path to the RemoteAccess system files.
-
- SET QBBS=<Path>
- Path to the QuickBBS system files.
-
- SET DB=<Path>
- Path to the D'Bridge system files.
-
- SET OPUS=<Path>
- Path to the Opus system files.
-
- SET IMAIL=<Path>
- Path to the IMail system files.
-
- SET DUTCHIE=<Path>
- Path to the Dutchie system files.
-
- SET MAXIMUS=<Path>
- Path to the Maximus system files.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 6
- ----------------------------------------------------------------------
-
- E R R O R L E V E L S
-
- To ease operation in batchfiles, GoldED exits with a set of
- errorlevels:
-
- 100 = QBBS Index errors. (See REBUILD keyword).
- 004 = Echomail entered.
- 002 = Netmail entered.
- 001 = Local mail entered.
- 000 = Exit okay. No mail entered.
-
- Other values: Some sort of error.
-
- Add values together to find the combined errorlevels. For example,
- errorlevel 6 is returned if netmail (2) and echomail (4) was
- entered.
-
- See the RUNGOLD.BAT file for a useful skeleton for automated
- operation using the errorlevels.
-
-
-
- L O G F I L E
-
- 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 FrontDoor format, and the filename is defined
- with the GOLDEDLOG keyword.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 7
- ----------------------------------------------------------------------
-
- G O L D E D U T I L I T I E S
-
- The distribution archive comes with a few utility programs,
- described here.
-
- GOLDLANG.EXE
- ------------
- GoldLANG has no commandline parameters.
-
- This utility "compiles" severeal configuration files to binary
- versions for easy digestion by GoldED:
-
- GOLDED.HLP (Help system).
- GOLDED.KEY (Keyboard definitions).
- GOLDED.LNG (Language definitions).
- GOLDED.RAN (Random system).
- *.CHS (Charset translation tables).
- *.ESC (Escape sequence translation tables).
-
- You must run GoldLANG each time you change any one of these files.
-
-
- GOLDNODE.EXE
- ------------
- Command line syntax: GOLDNODE [-options] [configfile]
-
- [-options] = -C Conditional compile.
- -F Forced compile.
- -D Remove duplicate nodes from index.
- -M<n> Compile max <n> nodes (default is 16000).
- -U<file> Create sorted FIDOUSER.LST userlist file.
-
- [configfile] = The path AND filename of the GOLDED.CFG
- configuration file to read.
-
- In order to enable nodelist/userlist lookup and browsing, GoldED
- needs to use a set of special nodelist index files. GoldNODE takes
- care of this by compiling your nodeslists and userlists to the
- index files GOLDNODE.ADX and GOLDNODE.NDX.
-
- None of the existing types of nodelist indexes were sufficiently
- useful or documented, so I had to create my own format, sorry.
-
- 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. 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.
-
-
- GOLDRAND.EXE
- ------------
- Commandline syntax: GOLDRAND [randomtext] [randomindex] [-?]
-
- [randomtext] Defaults to RANDOM.TXT.
- [randomindex] Defaults to RANDOM.IDX.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 8
- ----------------------------------------------------------------------
-
- [-?] Shows a short help screen.
-
- This is an optional utility, which can even be used without
- GoldED. By default it uses a file called RANDOM.TXT - see an
- example in the ADVANCED archive. When run, GoldRAND creates an
- index file for the RANDOM.TXT file and displays one random text.
- On subsequent runs, it just displays new random texts.
-
- The most obvious use for GoldRAND is to maintain and display
- random "Cookies" (wisdom, jokes etc). GoldED can read the random
- file and insert these random texts or cookies into the template
- when you write messages. Another, less obvious use is to make
- random varieties of the headers ("In a message of...") and footers
- ("Greetings from...") in your messages. See the RANDOM.TXT for an
- example of this.
-
- The format of the RANDOM.TXT is simple: It's a normal textfile,
- and each random text is separated by one blank line. When used in
- the GoldED template, most of the template tokens are recognized.
-
- Remember to run GoldRAND each time you change the RANDOM.TXT file.
-
- WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
- Be aware that cookies are often considered "Annoying Behavior",
- since they are usually not "on-topic" in most conferences, and
- just add more bytes to the mailflow, resulting in increased phone
- bills... However, in local BBS conferences or where the moderator
- allows it, they can be nice and refreshing. SO DO NOT ABUSE IT!!!
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 9
- ----------------------------------------------------------------------
-
- K E Y W O R D R E F E R E N C E
-
- This is an alphabetical list of all the configuration keywords
- used in GoldED. For simplicity, the following symbols are used:
-
- [] = Optional.
- <> = Required/Non-Optional.
- () = Default value.
- , = Separates the possible values.
- path = DOS path, optionally ending in a backslash (\).
- file = DOS filename.
- string = String of characters, optionally enclosed in quotes.
- nodespec = FidoNet-style address [zone:][net/][node][.point].
-
- You can have comments in the configuration file by adding a
- semicolon (;) in front of them.
-
-
- ADDRESS <nodespec>
-
- Your network address. Several addresses can be specified if
- you are member of more than one network.
-
-
- AKA <nodespec>
-
- See ADDRESS. AKA is simply an alias for ADDRESS.
-
-
- AREA <areaspec>
-
- With this keyword you define the message areas GoldED knows
- about.
-
- >>> See the Area Configuration section for details.
-
-
- AREAPATH <path>
-
- When you read areas from the various AREA -FILE options,
- GoldED needs to know where the area specific files are placed.
- This keyword specifies where they are found, if not current
- directory.
-
-
- AREASORT <sortspec>
- <sortspec> =
- A(ka) : Sort by area aka.
- D(escription) : Sort by area description.
- E(choid) : Sort by area echoid.
- G(roup) : Sort by area group (if any).
- T(ype) : Sort by area type (net/echo/local).
- U(nread) : Sort by unread messages (try it!).
-
- This keyword defines how the area list is sorted upon
- initialization and when you change areas. If U(nread) is
- defined, the list will be sorted ascending by the number of
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 10
- ----------------------------------------------------------------------
-
- messages left in the list. You can override the default
- setting from the command line with the -S<sortspec> option.
-
- Example: AREASORT TUE
-
- This sorts by Type, Unread and Echoid.
-
-
- AUTOATTACH <yes,no> (no)
-
- If enabled, drivespec (C: etc) in the subject in netmail will
- automatically turn on the file attach attribute. The
- autoattach only works if the subject has been edited - i.e. it
- will not automatically re-attach the subject files in replies.
-
- NOTE: This feature is only available to REGISTERED USERS!
-
-
- BEEPYOURMAIL <yes,no> (yes)
-
- If enabled, GoldED will make a noise if it finds a
- non-received message to one of your SYSOP names.
-
-
- BLANKTIME <seconds> (180)
-
- If non-zero, GoldED will blank the screen after the defined
- number of seconds, and put a small moving window up instead.
- Pressing any key (including shiftkeys) will return the screen
- to normal. If zero, no blanking is done.
-
-
- BOARDNOS <yes,no> (no)
-
- If enabled, GoldED will display the QBBS board numbers in the
- area menu instead of sequential numbers.
-
-
- CCATTRIB <attributes>
- <attributes> = See appendix A for definitions.
-
- Defines the default attributes of Carbon Copy messages. CC
- attributes are always *added* to the existing attributes of
- the original message. Usually used to add the Kill/Sent
- attribute...
-
- >>> See the Carbon Copy and Crosspost section for more info.
-
-
- CFMATTRIB
- <attributes> = See appendix A for definitions.
-
- Defines the default attributes of the Confirmation Receipt
- message.
-
- >>> See the GOLDEDCFM keyword for more info.
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 11
- ----------------------------------------------------------------------
-
-
- CCLIST <listspec> (Names)
- <listspec> =
- 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.
-
- This specifies the format of the Carbon Copy list, as it will
- look after processing. You can change the format in the CC
- menu before processing.
-
- >>> See the Carbon Copy and Crosspost section for more info.
-
-
- CHARSET <importid> <exportid> <file>
- <importid> = Charset import identifier.
- <exportid> = Charset export identifier.
- <file> = Charset translation table file.
-
- This keyword defines characterset translation table files.
-
- >>> See the Character Translation section for details.
-
-
- CLEARKEYS <yes,no> (no)
-
- Tells GoldED whether or not to clear the keyboard buffer on
- startup. This also clears STACKKEYS or commandline key
- stuffing. In previous versions of GoldED, it was nescessary to
- enable this keyword if you had renamed GOLDED.EXE to
- DBEDIT.EXE. This version detects the .EXE renaming and
- automatically enables CLEARKEYS, regardless of the
- configuration setting.
-
-
- COLOR <colorspec>
-
- With this keyword, you define the colors used in GoldED.
-
- >>> See the Color Configuration section for details.
-
-
- COLOUR <colourspec>
-
- See COLOR. COLOUR is simply an alias for COLOR.
-
-
- CRLFTERM <yes,no> (yes)
-
- If enabled, all text paragraphs in your messages will be
- terminated with a CR/LF combination. If not, only a CR is
- used. This option was created to fix a problem with a Dutchie
- packer that appearantly needs CR/LF termination of kludge
- lines.
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 12
- ----------------------------------------------------------------------
-
-
- DELORIG <yes,no> (yes)
-
- If enabled, you will be asked if the message you just replied
- to should be deleted. Otherwise it is left untouched.
-
-
- ECHOATTRIB <attributes>
- <attributes> = See appendix A for definitions.
-
- Defines the default attributes of echomail messages.
-
-
- ECHOINFO <yes,no> (yes)
-
- Specifies if you want tearline and origin in your echomail
- messages. They will be added by your echomail processor, if
- you disable them here.
-
-
- EDITOR <commandline> [@file] [@line]
- <commandline> = Program commandline.
- @file : Token which is replaced by the editor message
- filename.
- @line : Token which is replaced by the @Position template
- line number.
-
- In 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 SWAPALL
- keyword, if the EDITOR requires a lot of free memory.
-
-
- ELIMSNOW <yes,no> (no)
-
- By default GoldED writes directly to the screen, but
- unfortunately 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.
-
-
- 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 the FidoNet document
- FSC-0046.
-
-
- ESCSET <import> <export> <escfile>
- <importid> = Charset import identifier.
- <exportid> = Charset export identifier.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 13
- ----------------------------------------------------------------------
-
- <file> = Escape sequence translation table file.
-
- This keyword defines escape sequence translation table files.
-
- >>> See the Character Translation section for details.
-
-
- EXCLAREA <echoid>
-
- With this keyword, you can define areas which will be ignored
- by GoldED. This simply means that they will be left out of the
- area pick list. It is possible to use the DOS-style wildcards
- (*,?) in the echoid. The '*' works like in the 4DOS
- COMMAND.COM replacement. Examples: "EXCLAREA *" - excludes all
- areas, "EXCLAREA *SYSOP*" - excludes all areas containing
- "SYSOP" anywhere in the echoid, "EXCLAREA S*.*" - excludes all
- areas beginning with 'S' and containing a '.' anywhere in the
- echoid.
-
-
- EXCLUDENODES <nodemask>
- <nodemask> = See Appendix B for valid nodemasks.
-
- You can define up to 50 different nodemasks to be excluded
- from the compiled nodelists. Use this if you are short of
- space. This keyword is used by GoldNODE, and must be present
- in the main .CFG file (not in INCLUDE'ed .CFG's).
-
- >>> See also the INCLUDENODES keyword.
-
-
- EXPORTCHARSET <charsetid>
-
- Defines the export charset for your messages.
-
- >>> See the Character Translation section for details.
-
-
- EXTKEYS <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 tricks,
- I have made it possible to use the extended keys even with a
- non-extended keyboard.
-
-
- FIELDCLEAR <yes,no> (yes)
-
- If enabled, the edit-field (in Write file, import etc.) will
- be automatically cleared for new entry, if a non-edit key is
- the first key pressed.
-
-
- GOLDEDCFM [path]<file> ([GOLDPATH\]GOLDED.CFM)
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 14
- ----------------------------------------------------------------------
-
- GoldED supports the Confirmation Receipt attribute, as
- introduced in FrontDoor 2.00 with the FLAGS CFM kludge. If
- GoldED finds an unreceived message to one of your SYSOP names
- with the CFM (or the RRQ Return Receipt Request) attribute
- set, it generates an automatic response message from the
- content of the GOLDEDCFM file. In the GOLDEDCFM 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 CFMATTRIB keyword.
-
- >>> See the Message Template section for details of tokens.
-
-
- GOLDEDHLP [path]<file> ([GOLDPATH\]GOLDED.HLP)
-
- Defines the name of the GoldED raw ASCII help textfile. The
- file extension must be .HLP, otherwise GoldLANG will not
- compile it to the binary .HLX version.
-
-
- GOLDEDLOG [path]<file> ([GOLDPATH\]GOLDED.LOG)
-
- Defines the name of the GoldED logfile. The logfile is in
- FrontDoor format, and only generated if GoldED exits with an
- error.
-
-
- GOLDEDLST [path]<file> ([NODEPATH\]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 userlist outputfile generated with the READmakeuserlist
- command.
-
- NOTE: This feature is only available to REGISTERED USERS!
-
-
- GOLDEDMSG [path]<file> ([GOLDPATH\]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.
-
-
- GOLDEDNAM [path]<file> ([AREAPATH\]NAMES.FD)
-
- GoldED supports the "address macro" file used in FrontDoor
- 1.99c and above. If no path is specified, the path is first
- searched in the "FD" environment variable and then the
- GOLDPATH, if the FD variable failed.
-
- >>> See the Address Macros section for details.
-
-
- GOLDEDRAN [path]<file> ([GOLDPATH\]GOLDED.RAN)
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 15
- ----------------------------------------------------------------------
-
- Defines the name of the Random System configuration file. The
- file extension must be .RAN, otherwise GoldLANG will not
- compile it to the binary .RLX and .RLN versions.
-
- >>> See the Random System section for details.
-
-
- GOLDPATH <path>
-
- This is the path where GoldED finds all it's control files. It
- is not nescessary to define this, unless you have special
- needs. The GOLDPATH defaults to directory where the GOLDED.CFG
- file was found.
-
-
- HARDLINE <string> ("<<")
-
- The HARDLINE string is needed if you use an external editor
- that terminates all lines with a CR. The hardline string acts
- as a paragraph terminator, and the normal CR's are ignored.
-
-
- HARDLINES <yes,no> (yes)
-
- This keyword enables the HARDLINE feature. If disabled, the
- HARDLINE 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.
-
-
- IGNORE
-
- This tells the configuration reader to ignore all subsequent
- lines until another IGNORE keyword is encountered. Useful for
- testing and quickly switching portions of configuration.
-
-
- INCLUDE [path]<file> ([GOLDPATH\]<file>)
-
- This tells the configuration reader to stop reading the
- current .CFG file, and start reading the <file> as an extra
- configuration file until EOF, then resume reading the previous
- .CFG The INCLUDE filenames are stored and their timestamps
- checked when GoldED is started. INCLUDE's can be nested ten
- deep, but don't push it ;-)
-
-
- INCLUDENODES <nodemask>
- <nodemask> = See Appendix B for valid nodemasks.
-
- You can define up to 50 different nodemasks to be included
- from the compiled nodelists. This is only used in conjuction
- with the EXCLUDENODES keyword to include excluded nodes. This
- keyword is used by GoldNODE, and must be present in the main
- .CFG file (not in INCLUDE'ed .CFG's).
-
- >>> See also the EXCLUDENODES keyword.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 16
- ----------------------------------------------------------------------
-
-
-
- INTERNALEDITOR <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 before you start writing your
- message.
-
-
- INVALIDATE <invalidate> <findstring> <replacestring>
- <invalidate> =
- Tearline : Invalidate tearline ("---").
- Origin : Invalidate origin (" * Origin: ").
- Seenby : Invalidate SEEN-BY.
-
- 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 nul string, they will not be quoted at all.
-
- By default, the following invalidations are used:
-
- "---" -> "-!-"
- " * Origin: " -> " ! Origin: "
- "SEEN-BY" -> "SEEN!BY"
-
-
- LOCALATTRIB <attributes>
- <attributes> = See appendix A for definitions.
-
- Defines the default attributes of local messages.
-
-
- LASTREAD <file> (LASTREAD.)
-
- This is the name (WITHOUT PATH!) of the lastread files in
- *.MSG message bases. Not used in a clean QBBS-style system.
-
-
- LASTREADUSER <userno> (0)
-
- This is the index into the LASTREAD file, if you share the
- *.MSG message base with other users. Not used in a clean
- QBBS-style system.
-
-
- LOCALCHARSET <charsetid> (IBMPC)
-
- Defines the local charset for your machine.
-
- >>> See the Character Translation section for details.
-
-
- LOCALINFO <yes,no> (yes)
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 17
- ----------------------------------------------------------------------
-
- Specifies if you want tearline and origin in your local
- messages. Tearline/origin is not required in local areas, so
- you only need to enable them if you absolutely want to.
-
-
- 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 in running locally on another machine in
- 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, the drives would
- be all wrong. This problem is solved by using MAPDRIVE to
- remap drive specs.
-
-
- MATCHAKA <yes,no> (yes)
-
- If enabled, GoldED will try to find an AKA that matches the
- destination address of the original message when replying in
- netmail.
-
-
- MAXCOLS <columns> (0)
- MAXROWS <rows> (0)
-
- On some systems it is not possible to detect the correct
- display size. With these keywords you can force a specific
- size. If zero, autodetect is used.
-
-
- MIXCASE <yes,no> (yes)
-
- When entering names in the header, GoldED can automatically
- format the name with uppercase the first letter in words and
- lowercase the rest. This is called mixcasing.
-
-
- MOUSE <yes,no> (no)
-
- GoldED has very limited mouse support. It is not worth trying,
- believe me :-)
-
-
- NETATTRIB <attributes>
- <attributes> = See appendix A for definitions.
-
- Defines the default attributes of local messages.
-
-
- NETINFO <yes,no> (no)
-
- Specifies if you want tearline and origin in your netmail
- messages. Tearline/origin is not required in netmail, so you
- only need to enable them if you absolutely want to.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 18
- ----------------------------------------------------------------------
-
-
-
- NETNAME <string>
-
- This is the netname that is placed in the originline,
- preceding the address:
-
- " * Origin: <origin> ([netname]<addresse>)".
-
-
- NETTEAR <yes,no> (yes)
-
- Specifies if you want a tearline in your netmail messages.
- Tearline is not required in netmail, so you only need to
- enable it if you absolutely want to.
-
-
- NEXTAREA <yes,no> (yes)
-
- If enabled, GoldED will automatically jump to the next area
- with unread mail.
-
-
- NEXTMSGS <yes,no> (yes)
-
- If enabled, GoldED will automatically jump to the next
- message, when entering an area.
-
-
- NODELIST [path]<file> [zone]
- [path] = Path to the file. Default is NODEPATH.
- <file> = Nodelist file. If extension is numeric, the newest
- file with with numeric extension is used.
- [zone] = Default zone for the nodelist (if no zone info is
- present).
-
- Here you define the nodelists that are used by GoldED. The
- nodelists must be in the standard nodelist format, but they
- can also contain FrontDoor style Boss/Point extensions. The
- default zone is defined by the first ADDRESS or AKA, but can
- be overridden by adding the zone number after the filename.
- GoldED needs special index files to use the nodelists. These
- index files are created by the GoldNODE nodelist compiler.
-
- >>> See also the USERLIST keyword.
- >>> See the Nodelist Browsing section for details.
-
-
- NODEPATH <path>
-
- This is where GoldED and GoldNODE finds the nodelist files.
-
-
- ORIGIN <string>
-
- You can define any number of different default origins.
- Leading and/or trailing spaces can be added by enclosing the
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 19
- ----------------------------------------------------------------------
-
- origin in quotes. You can change the current origin for an
- area, using the popup selection menu (READchangeorigin) or
- from the editor menu or even in the save menu after editing.
- Origins defined in the Random System overrides the default
- origins defined with this keyword, except when selected from
- the editor/save menu.
-
-
- OUTPUTFILE [path]<file> ([GOLDPATH\]GOLDED.OUT)
-
- This is the default name of the file written using the
- READwritemsg command.
-
-
- OVERLAYEMS <yes,no> (no)
- OVERLAYEXT <yes,no> (no)
-
- These two keywords control where GoldED places the overlay
- swap blocks. GoldED uses the Borland VROOMM dynamic overlays
- to decrease the resident executable code. If not enabled, disk
- is used.
-
- >>> See the SWAPALL keyword for a warning note.
-
-
- PAGEBAR <yes,no> (yes)
-
- If enabled, a "PageBar" will appear on the right margin, to
- tell you about the relative size and position in the message
- you are reading. The PageBar decreases the RIGHTMARGIN by one
- char.
-
-
- POINTNET <pointnet>
-
- If you are using low-tech software that does not recognize the
- FMPT and TOPT kludges, you may want to enable the POINTNET. If
- set, GoldED will convert your (4D) address in netmail messages
- to the so-called "3D Fakenet" (Zone:PointNet/Point.0) format,
- but only in message addressed to your Boss or another point
- off your Boss. In messages to any other node, the 4D address
- is used, with the FMPT kludge.
-
-
- PRINTFORMFEED <yes,no> (yes)
-
- Used when printing messages. If enabled, adds a Form Feed
- (12d) character after each message.
-
-
- PRINTINIT <printstring>
- <printstring> =
- #Decimal : A decimal (integer) number.
- $Hex : Hexadecimal string.
- #Decimal : A decimal (integer) number.
- "String" : Text string, enclosed in double quotes.
- 'String' : Text string, enclosed in single quotes.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 20
- ----------------------------------------------------------------------
-
- All other characters are ignored.
-
- This keyword defines the command string sent to your printer
- to initialize it before the actual printing.
-
-
- PRINTLENGTH <lines> (66)
-
- 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>
- <printstring> = See the PRINTINIT keyword.
-
- This keyword defines the command string sent to your printer
- to reset it after printing.
-
-
- QMSGPATH <path>
-
- Specifies the directory where GoldED can find the QBBS-style
- message base files (MSG*.BBS, USERS.BBS, LASTREAD.BBS etc.).
- Not used in a clean *.MSG style system.
-
-
- QSYSPATH <path>
-
- Specifies the directory where GoldED can find the QuickBBS
- CONFIG.BBS or the RemoteAccess MESSAGES.RA area definition
- files, if these are being read with "AREA -FILE QuickBBS" or
- "AREA -FILE RemoteAccess". Not used in a clean *.MSG style
- system.
-
-
- QUOTEBLANK <yes,no> (no)
-
- If enabled, GoldED will put the QUOTESTRING on blank lines in
- the quote.
-
-
- QUOTEMARGIN <characters> (70)
-
- The margin to which quotes are wrapped.
-
-
- QUOTESTRING <quotespec> (" > ")
- <quotespec> =
- 'F' : Replaced with the first letter of the first name.
- 'M' : Replaced with the letters of all the middle names.
- 'L' : Replaced with the first letter of the last name.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 21
- ----------------------------------------------------------------------
-
- '>' : Required quote-char.
- ' ' : Spaces.
- Other chars are allowed but *not* recommended.
-
- With this keyword you define how you want the quotestring to
- look in your quoted replies.
-
-
- REALMSGNO <yes,no> (no)
-
- GoldED can either display the message numbers as they appear
- in the messages, or as "relative" numbers.
-
-
- REBUILD <yes,no> (yes)
-
- If enabled, GoldED will rebuild the QBBS msgbase index files,
- if fatal errors were detected. If disabled, GoldED will exit
- with an errorlevel and log the cause. Fatal errors are
- mismatched sizes of the MSGHDR/IDX/TOIDX files.
-
-
- REGISTERKEY <keycode>
- REGISTERNAME <keyname>
-
- These keywords are only used in registered setups.
-
-
- RENAREA <fromechoid> <toechoid>
-
- Renames one echoid to another just before the test for
- EXCLAREA's. The feature is meant to be used like this:
- "RENAREA NETMAIL001 NETMAIL" or "RENAREA ECHOMAIL001
- BAD_MSGS", but you can use it any way you wish.
-
- NOTE: This feature is only available to REGISTERED USERS!
-
-
- REPLYRE <yes,no> (no)
-
- If enabled, GoldED inserts the "RE:" string in front of the
- subject when you reply to a message.
-
- NOTE: This feature is only available to REGISTERED USERS!
-
-
- RIGHTMARGIN <characters>
-
- This is the right margin you want messages displayed with.
- When the PAGEBAR is enabled, the right margin is decreased by
- one char.
-
-
- SAVETIME <seconds> (30)
-
- If defined, the internal editor will automatically execute the
- EDITsavefile function with intervals of <seconds>. Good for
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 22
- ----------------------------------------------------------------------
-
- 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 GOLDEDMSG keyword.
-
-
- SAYBIBI <yes,no> (yes)
-
- If enabled, GoldED makes appropriate noises (beeps, gwynks,
- melodies) when it wants attention.
-
-
- SCANAREA <echoid,wildcards>
-
- This keyword defines areas, which will be automatically
- scanned when starting GoldED. Works only for *.MSG style
- areas. It is possible to use the DOS-style wildcards (*,?) in
- the echoid. The '*' works like in the 4DOS COMMAND.COM
- replacement. Examples: "SCANAREA *" - scan all areas,
- "SCANAREA *SYSOP*" - scan all areas containing "SYSOP"
- anywhere in the echoid, "SCANAREA S*.*" - scan all areas
- beginning with 'S' and containing a '.' anywhere in the
- echoid.
-
-
- SCREENSIZE <sizespec> (Auto)
- <sizespec> =
- Auto : Use detected lines.
- 25 : Switch to 25 lines.
- 4350 : Switch to 43/50 lines.
-
- Use this to force GoldED to use either 25 or 43/50 lines by
- switching the screen mode.
-
-
- SHADOWS <yes,no> (yes)
-
- If enabled, all relevant windows and menus in GoldED will have
- shadows.
-
-
- SHARE <yes,no> (no)
-
- If enabled, GoldED opens all files in "Share, Deny None" mode.
- NOTE: This *DOES NOT* nescessarily mean that it is safe to run
- GoldED on a multitasking system with other programs accessing
- the same files!!! There have been reports of problems when
- enabling this, but I don't know for sure what or how, since I
- cannot test it myself :-(
-
-
- SHOWTWITS <twitspec> (Show)
- <twitspec> =
- Show : Show twit messages.
- Blank : Blank twit messages.
- Skip : Skip twit messages, unless to your SYSOP name.
- Ignore : Skip twit messages, always.
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 23
- ----------------------------------------------------------------------
-
- 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.
-
- >>> See the TWITNAME and TWITSUBJ keywords for more info.
-
-
- SIGNALFILE <type> [path]<file>
- <type> =
- QNETSCAN : QBBS-style netmail scanning index file.
- QECHOSCAN : QBBS-style echomail scanning index file.
- NETSCAN : Empty netmail scan file (for D'Bridge or FD).
- ECHOSCAN : Empty echomail scan file (for D'Bridge).
- EXPORTLIST : Echoid-list of your new messages.
- IMPORTLIST : Echoid-list of new imported messages.
-
- This keyword defines some "semaphore" (signal) files, for use
- with some mailer/mail processing programs.
-
-
- SPACEQUOTES <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 readability of certain messages.
-
-
- SPELLCHECKER <commandline> [@file] [@line]
- <commandline> = Program commandline.
- @file : Token which is replaced by the message filename.
-
- 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 uses the EDITsavefile and
- EDITloadfile commands.
-
-
- STACKKEYS <keystring>
- <keystring> =
- ^Char : Ctrl-key (^Letter).
- @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.
-
- With this, you can "stack" keys in the keyboard buffer. The
- STACKKEYS can be overridden by commandline keystacking, which
- uses the same syntax.
-
- >>> See the Macros and Keystacking section for more info.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 24
- ----------------------------------------------------------------------
-
- STARTECHO <echoid>
-
- With this keyword, you can define what area GoldED should
- start in (bypassing the area selection menu). If not defined,
- GoldED starts in the area selection menu instead. You can
- override the setting with the -E<echoid> commandline option.
-
-
- SWAPALL <yes,no,xms,ems,disk> (no)
-
- With this keyword, you can specify what storage locations the
- swapper should try or use, and what order to try them in. It
- accepts the following parameters: YES, NO, XMS, EMS and DISK.
- YES automatically tells the swapper to try XMS, EMS, DISK in
- that order and NO tells it not to swap at all. You can specify
- you own order: "SWAPALL EMS, XMS, DISK" makes it try it in
- that order, or "SWAPALL EMS, DISK" makes it ignore XMS.
- Delimiters are space, tab and comma (,). IMPORTANT NOTE: Some
- programs which uses extended memory, may conflict with the XMS
- extended memory driver, causing crashes. If you have problems,
- you should first try turning OVERLAYEXT off, and if it still
- fails, turn off SWAPALL (or stop using the other programs :-)
-
-
- SYSOP <name>
-
- You can define any number of different names (aliases). When
- GoldED finds an un-received message to one of your SYSOP
- names, 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, you MUST have the *first* SYSOP name
- defined in the USERS.BBS file.
-
-
- TABSIZE <characters>
-
- The display tabsize. If you use an external editor, you should
- switch it to create spaces instead of TAB characters.
-
-
- TEARLINE <string> (GoldED @Version)
-
- Here you can define your default tearline. Tearlines defined
- in the Random System always overrides the default tearline
- defined with this keyword. A tearline can be maximum 35 chars
- long, including the "---".
-
- NOTE: This feature is only available to REGISTERED USERS!
-
-
- TEMPLATE [path]<file> ([GOLDPATH\]<file>)
-
- You can define any number of different default template files.
- The templates can be switched using the READchangetemplate
- popup menu or the editor menu. The Random System overrides the
- default templates, except when selected from the editor menu.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 25
- ----------------------------------------------------------------------
-
- NOTE: If no template is defined, or one is missing, the
- template (MS_TemplateMsg) from the .LNG language definition
- file is used instead.
-
-
- TEMPPATH <path>
-
- This is the directory where temporary files and swapfiles are
- placed. Be sure it has at least 4-500K free space, when
- SWAPALL is enabled and disk swapping is used.
-
-
- TIMEOUT <seconds> (360)
-
- Similar to the screen blanking (BLANKTIME) feature, GoldED can
- auto-exit after a specified period of time. Useful if you are
- in a hurry, and run GoldED from your mailer shell. The timeout
- value can be overridden by the -T<seconds> commandline option.
-
-
- TIMESLICEDV <yes,no> (yes)
-
- If enabled, GoldED will call the DesqView<tm> time-slice
- interrupt, when the keyboard is idle, and DesqView is
- detected.
-
-
- TWITNAME <name,nodemask>
- <nodemask> = See Appendix B for valid nodemasks.
-
- With this keyword, you can specify any number of "Twit" names
- and/or nodemasks. When a Twit name is detected, the SHOWTWITS
- setting will determine the action taken.
-
-
- TWITSUBJ <string>
-
- With this keyword, you can specify any number of "Twit"
- subjects. When a Twit subject is detected, the SHOWTWITS
- 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 35 characters.
-
-
- USEBIOS <yes,no> (no)
-
- If enabled, GoldED will use BIOS calls for screen updates.
- This is VERY slow, and should only be used if really needed.
- Normally GoldED uses direct screen writes.
-
-
- 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
- more and more newer software. GoldED uses FLAGS to emulate the
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 26
- ----------------------------------------------------------------------
-
- Hold and Freq attributes which are not defined in the QBBS
- message format.
-
-
- USEINTL <intlspec> (Auto)
- <intlspec> =
- Auto : Only insert in inter-zone netmail.
- Yes : Always insert.
- No : Never insert.
-
- The INTL kludge is normally only inserted in netmail, if the
- origination zone is different from the destination zone
- (Auto), but on systems with many AKA's in the mailer, it might
- be useful/nescessary to add it ALWAYS (Yes). The (No) option
- should never be used. NOTE: Some 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.
-
-
- USEREPLY <yes,no> (yes)
-
- If enabled, the REPLY kludge is inserted in netmail and
- echomail, when replying to a message with a MSGID.
-
-
- USERLIST [path]<file> [zone]
- [path] = Path to the file. Default is NODEPATH.
- <file> = Userlist file in FIDOUSER.LST format.
- [zone] = Default zone for the nodelist (if no zone info is
- present).
-
- 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 after the filename.
-
- >>> See the NODELIST keyword for more info.
-
-
- VIEWHIDDEN <yes,no> (yes)
- VIEWKLUDGE <yes,no> (no)
-
- Hidden lines are "unknown" kludge lines. If enabled,
- hidden/kludge lines will be displayed.
-
-
- WHOTO <name>
-
- This name is inserted in the destination name field, when
- entering a new echomail/local message.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 27
- ----------------------------------------------------------------------
-
-
-
- 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).
-
- >>> See also the USEINTL keyword.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 28
- ----------------------------------------------------------------------
-
- A R E A C O N F I G U R A T I O N
-
- GoldED has a wide variety of methods for defining message areas.
- You can define each area manually in the .CFG file (or an
- INCLUDE'ed .ARE file), or you can tell GoldED to read the external
- area configuration files of many different mailer/mail processing
- software packages. All area configuration in GoldED is done by
- using the AREA keyword.
-
-
- Syntax for manually defined areas:
- ----------------------------------
-
- AREA <echoid> <"desc"> <msgbase>[type] <location> [attrs,aka]
- <echoid> = Echomail area identifier.
- <"desc"> = Area description in "" or '' quotes.
- <msgbase> = O(pus), F(ido), S(td_FTS), Q(uickBBS), R(A).
- [type] = N(etmail), E(echomail), L(ocal).
- <location> = Directory Path or QBBS/RA Board Number.
- [attrs,aka] = R/O(readonly), AKAnumber and/or Attributes.
-
- "O(pus)" and "F(ido)" are synonyms (*.MSG files).
- "S(td_FTS)" is also *.MSG files, but with special header fields.
- "Q(BBS)" and "R(A)" are also synonyms (MSG*.BBS files).
-
- See the included GOLDED.ARE file for examples.
-
-
- Syntax for external area configuration:
- ---------------------------------------
-
- AREA -FILE DBridge [-S<sortspec>]
- Reads the DBRIDGE.AA1/.AA2 or DBRIDGE.ADF files.
-
- AREA -FILE FrontDoor [-S<sortspec>] [AREAS.BBS file(s)]
- Reads the FD.SYS and FOLDER.SYS files.
-
- AREA -FILE Opus [-S<sortspec>] [path]
- Reads the Opus 1.1x SYSTEM??.DAT files.
-
- AREA -FILE QuickBBS [-S<sortspec>] [AREAS.BBS file(s)]
- Reads the CONFIG.BBS file.
-
- AREA -FILE RemoteAccess [-S<sortspec>] [AREAS.BBS file(s)]
- Reads the MESSAGES.RA file.
-
- AREA -FILE AreasBBS [-S<sortspec>] [AREAS.BBS file(s)]
- Reads CONFMAIL/QBBS style AREAS.BBS files.
-
- AREA -FILE ME2 [-S<sortspec>] <AREADESC.ME2> [AREAS.BBS file(s)]
- Reads the ME2 editor AREADESC.ME2 file and AREAS.BBS files.
-
- AREA -FILE IMail [-S<sortspec>] [path]
- Reads the IMAIL.CF and IMAIL.AR files.
- NOTE: The IMail support covers version 1.00 - 1.10. Newer
- versions will be supported in the future.
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 29
- ----------------------------------------------------------------------
-
- AREA -FILE TosScan [-S<sortspec>]
- Reads the FD.SYS and AREAFILE.FD files.
-
- AREA -FILE Dutchie [-S<sortspec>] [path]
- Reads the DUTCHIE.ARE file.
-
- AREA -FILE Maximus [-S<sortspec>] [path\filename]
- Reads the AREA.DAT file.
-
- See the AREASORT keyword for definition of <sortspec>. Sorting
- here is only useful you *don't* use the AREASORT keyword, because
- if you use AREASORT, *all* areas will be sorted.
-
- If no path is specified, the AREAPATH is used to find the files.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 30
- ----------------------------------------------------------------------
-
- C O L O R C O N F I G U R A T I O N
-
- 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 some example color
- setups, provided by my many good users. I suggest you try them all
- and use the one that suits you best, and perhaps tune it a bit.
-
-
- The COLOR keyword uses the following syntax:
-
- COLOR <colorspec>
- COLOUR <colorspec>
- <colorspec> = <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.
- <colors> : [blinking] <ink> [on <paper>].
- <ink> : Black, Blue, Green, Cyan, Red, Magenta,
- Brown, LGrey, DGrey, LBlue, LGreen, LCyan,
- LRed, LMagenta, Yellow, White.
- (Monocrome:) Normal, Highlight, Reverse,
- Underline.
- <paper> : Black, Blue, Green, Cyan, Red, Magenta,
- Brown, LGrey.
-
- The SHADOW color does not need a <part>.
-
- The paper color defaults to the last paper color, starting Black.
-
- 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 is always BTYPE 0.
-
-
- The following is a description of the different window parts:
-
- Various general items.
- ----------------------
- SHADOW = Shadow below windows and menus.
- STATUS WINDOW = Statusline at the bottom.
- BACKGROUND WINDOW = Background for the startup window.
-
- Startup screen / logo window.
- -----------------------------
- BRAG WINDOW = The Copyright window.
- BRAG BORDER = Lines around the Copyright window.
- BRAG TITLE = The logo text.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 31
- ----------------------------------------------------------------------
-
- 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 the 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.
-
- 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.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 32
- ----------------------------------------------------------------------
-
- HELP SELECTOR = Current keyword.
- HELP HIGHLIGHT = Other keywords.
- HELP BTYPE = Window border type.
-
- PopUp Information Windows.
- ------------------------------
- INFO WINDOW = Window text.
- INFO BORDER = Lines.
- INFO TITLE = Info title.
- INFO BTYPE = Window border type.
-
- See the included COLOR*.COL and MONO*.COL files for examples.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 33
- ----------------------------------------------------------------------
-
- R A N D O M S Y S T E M
-
- With the GoldED Random System, you can define a number of Origins,
- netnames, tearlines (if you are registered), templates and
- usernames for each conference.
-
- As in the configuration file, semicolons begins comments and blank
- lines can be used for better readability.
-
- The GoldED Random System is built on the idea of "groups". A group
- is a collection of "items", relevant for the group.
-
- You can assign one or more echomail areas, designated by their
- echotags (as seen in AREAS.BBS etc) to a group. In this way, you
- could for example use one group for all national echos, another
- for special local echos, and a third for international echos etc.
-
- In the random file, a semicolon in the first column makes the line
- a comment, which is ignored. Blank lines are also ignored.
-
-
- Defining Groups
- ---------------
-
- Group definitions start with a group "label" ending in a colon.
- The group label can be placed on any position of the line, but for
- readability, it is recommended to put it at the first column. On
- the lines following the label, you list all the items that belong
- in the group. The item list ends, when a new group label is
- encountered, or the end of the file is reached. Group labels are
- not case-sensitive.
-
- Items start with a special character, followed by the item
- definition. Items can be indented freely for better readbility.
- Currently supported items are:
-
- - Tearline (Editor/mail software identifier)
- * Origin (The "system name")
- # Netname (Should be short)
- $ Template (Filename of editor message template)
- = Username[, Address] (Name/address to use in the group)
- + <Special> (Area specific configuration)
-
- <Special> =
- A<attribs>, F<findstring>, O<outputfile>, T<showtwits>,
- V<hidd/klud=yes/no>, W<whoto>, X<exportcharset>.
-
- If more than one item of the same type is defined within the same
- group, items will be picked randomly from the possible choices.
-
- By enclosing the item definition in quotes "" or '', you can force
- leading or trailing spaces in the item.
-
- The items may be listed in any order.
-
- NOTE: Tearline definition is only available to REGISTERED USERS!
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 34
- ----------------------------------------------------------------------
-
-
- Assigning echos to groups
- -------------------------
-
- Echos need to be assigned to the appropriate group before they can
- be used. That is done with statements of this syntax:
-
- Label = [{]echoname[<sep>echoname][<sep>echoname][}]
-
- The "{}" are only needed if the assignments need to be split over
- a number of lines. Note! Echonames on lines with '{' or '}' are
- ignored! Each echoname must be separated by at least one
- separation/whitespace character. Separation characters are: Space,
- Tab, Comma and Semicolon.
-
- DO NOT assign the same echo to more than one group.
-
- It is also possible to assign items directly to echos. In that
- case, you just replace the Group label with the actual echoname
- (with no trailing colon).
-
- There is a special group, which all echos with no group will be
- automatically assigned to: "Default:".
-
- See the included GOLDED.RAN for examples.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 35
- ----------------------------------------------------------------------
-
- M E S S A G E T E M P L A T E
-
- The message template gives you a ready-made skeleton for writing
- your messages in the editor. The template is one of GoldED's
- 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: (replaced by 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.
- @Message Inserts the original message (in Forward and Change).
- @Quote Inserts a quote of the original message.
- @Random [random.txt [random.idx]] - Inserts random text.
- @SetSubj <"subject"> - Sets the message subject, if empty.
-
- Replacement tokens:
- -------------------
- @CAddr Current user address.
- @CDate Current date (fixed width: 9 chars).
- @CDesc Current area description.
- @CEcho Current echoid.
- @CFName Current user first name.
- @CLName Current user last name.
- @CName Current user name.
- @CTime Current time (fixed width: 5 chars).
- @DAddr Destination address.
- @DFName Destination first name.
- @DLName Destination last name.
- @DName Destination name.
- @OAddr Original address.
- @ODate Original date (fixed width: 9 chars).
- @ODesc Original area description if moved, otherwise current.
- @OEcho Original echoid if moved, otherwise current.
- @OFName Original first name.
- @OLName Original last name.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 36
- ----------------------------------------------------------------------
-
- @OName Original name.
- @OTime Original time (fixed width: 5 chars).
- @Subject The message subject line.
- @TAddr Destination to address.
- @TFName Destination to first name.
- @TLName Destination to last name.
- @TName Destination to name.
- @Version The version number of GoldED (ie. 2.30).
- @_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 examples.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 37
- ----------------------------------------------------------------------
-
- A D D R E S S M A C R O S
-
- GoldED supports the FrontDoor-style NAMES.FD address macro file.
- This file will be found in the directory pointed to by the FD
- environment variable, or otherwise in the GoldPath. The format of
- the lines in the file is:
-
- <macro>,<name>,<address>[,subject]
-
- Examples:
-
- AM16,AreaMgr,2:231/16,Password
- FF16,FileFix,2:231/16,Password
- LJ,Lars Joergensen,2:231/16.32
-
- The macros are not case-sensitive. The optional subject field is
- not supported by FD v1.99c, but is supported in FD v2.00 and
- newer. The address macro list is always the first to be searched,
- when you use the lookup feature. As in FrontDoor, you can prefix
- macros with a "*", but in GoldED this is not nescessary. The
- macros can also be used in the Carbon Copy feature.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 38
- ----------------------------------------------------------------------
-
- H E L P S Y S T E M
-
- GoldED has a built-in context sensitive help system, tied to the
- <F1> key. It contains 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 will be improved in future versions.
-
- You can completely redefine the help screens if you wish - the
- GOLDED.HLP file is a text file which contains all help definition.
- es. 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
- Also see: ^Help Category 1^
- *E
-
- The "*B" indicator specifies the beginning of a help category. The
- format is "*B helpcatnumber[,helpcatname]". In GoldED the help
- categories 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-references to that help category, then you can leave the
- helpcatname parameter 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 embedding the cross- reference category name (not number)
- inside carats (^). If you need to display a carat inside the help
- file, use a double carat (^^).
-
- 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
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 39
- ----------------------------------------------------------------------
-
- treated as an "*E".
-
- The help file is compiled to an indexed version by GoldLANG.
-
- 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.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 40
- ----------------------------------------------------------------------
-
- C H A R A C T E R T R A N S L A T I O N
-
- GoldED implements several different proposals for character
- translation 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 implemented in the OPMED 3.00 message
- editor, and will be implemented in Opus 1.20. It uses the same
- identifier as FSC-0054 (a ^aCHARSET kludge), but is a lot simpler
- (but not nescessarily better).
-
- The "I51" and "CHARSET" proposals are in the process of being
- merged to one proposal, which will 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 escape sequences for
- characters not found in the LATIN-1 set.
-
- Composed Characters has become quite popular in Holland, but the
- author has decided to drop his proposal because it relies on
- escape sequences using the so called "soft-cr" (141d, 8Dh)
- character. GoldED will continue to support Composed as long as it
- seems nescessary.
-
- If you want to know more about the details, I suggest you read the
- proposals or contact the authors.
-
- GoldED currently(*) uses two types of translation tables:
-
- (*) = NOTHING IS FINAL YET. The implementation is still on the
- testing stage, and later versions of GoldED will PROBABLY use
- different formats for these tables. So don't spend a lot of
- time reworking the tables - leave them as they are.
-
- 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. <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
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 41
- ----------------------------------------------------------------------
-
- character. The map chars can be either the characters themselves,
- or decimal or hexadecimal numbers of the form "\d<dec>" or
- "\x<hex>" (like in the C programming language).
-
- *** The format of this file is probably stable.
-
-
- The *.CHS files
- ---------------
- These files are used for import and export translation of the
- CHARSET 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 format of this file is probably *NOT* stable! (at least in
- my implementation...)
-
-
- The two keywords ESCSET and CHARSET 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 LOCALCHARSET defines which charset you have on your
- own machine - this would normally be "IBMPC", and should not be
- changed.
-
- The keyword EXPORTCHARSET and Random System item X<charset>
- defines the charset your messages should be exported to, if any.
-
-
- Confused? Yeah, I know - this is a confusing subject, and my
- implementation and documentation is not perfect. Normally you will
- not have to worry about it.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 42
- ----------------------------------------------------------------------
-
- C O M M A N D R E F E R E N C E
-
- Most of the GoldED keyboard commands can be reached with just one
- keystroke. To ease operation for experienced users of other
- message editors, GoldED has several sets of keys for each of the
- keyboard commands - direct non-shifted keys, Alt/Ctrl-keys and
- function 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> <default key assignment(s)>
- <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 GOLDED.KEY file (compiled to .KBD by GoldLANG),
- which also handles macro definition (see later).
-
-
- AREA SELECTION COMMANDS
- -----------------------
-
- AREAabort <Alt-A>
- Abort the area selection.
-
- AREAaskexit <Alt-X>, <Esc>
- Exit GoldED, prompt for final decision.
-
- AREAboardnos <Alt-B>
- Toggle between sequential areas or QBBS board numbers.
-
- AREAdosshell <Alt-O>
- Shell to DOS.
-
- AREAgotofirst <Home>
- Move selection bar to first area.
-
- AREAgotolast <End>
- Move selection bar to last area.
-
- AREAgotonext <Right>
- Move selection bar to next area.
-
- AREAgotoprev <Left>
- Move selection bar to previous area.
-
- AREAjump <Alt-J>, <Ctrl-Left>, <Ctrl-Right>
- Move selection bar to next marked area.
-
- AREAquitnow <Ctrl-Q>
- Exit immediately, no questions asked.
-
- AREAscan <Alt-S>
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 43
- ----------------------------------------------------------------------
-
- Scan areas - all or marked.
-
- AREAselect <Enter>
- Enter the reader for the selected area.
-
- AREAtoggle <Alt-T>, <Ins>
- Toggle mark on the selected area.
-
-
- INTERNAL EDITOR COMMANDS
- ------------------------
-
- EDITabort <Esc>
- Abort editing this message - ask first.
-
- EDITanchor <Alt-A>
- Set a block "anchor" on the current line.
-
- EDITaskexit <Alt-X>
- Exit from GoldED - ask first.
-
- EDITcut <Alt-C>
- "Cut" the current block to the Cut'n'Paste buffer.
-
- EDITdelchar <Del>
- Delete the character at the cursor position.
-
- EDITdeleteeol <Alt-K>, <Alt-Y>
- Delete from cursor position to end of line.
-
- EDITdelleft <BackSpace>
- Delete the character to the left of the cursor position.
-
- EDITdelline <Alt-D>, <Ctrl-Y>
- Delete the current line. (Copied to the Killbuffer).
-
- EDITdelltword <Ctrl-BackSpace>, <Ctrl-F5>
- Delete the word to the left of the cursor.
-
- EDITdelrtword <Ctrl-T>, <Ctrl-F6>
- Delete the word to the right of the cursor.
-
- EDITdosshell <Alt-O>
- Shell to DOS.
-
- EDITdupline <F4>
- Duplicates the current line.
-
- EDITexitmsg (no default)
- Drop this message - NO ASKING! DANGEROUS!
-
- EDITexporttext <Alt-W>
- Export block to a file.
-
- EDITgobegline <Home>
- Move cursor to beginning of line.
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 44
- ----------------------------------------------------------------------
-
- EDITgobotline <Ctrl-End>
- Move cursor to the bottom line in the display.
-
- EDITgobotmsg <Ctrl-PgDn>
- Move cursor to the last line in the message.
-
- EDITgodown <Down>
- Move cursor down to next line.
-
- EDITgoeol <End>
- Move cursor to the end of the line.
-
- EDITgoleft <Left>
- Move cursor one position left.
-
- EDITgopgdn <PgDn>
- Move cursor one page of lines down.
-
- EDITgopgup <PgUp>
- Move cursor one page of lines up.
-
- EDITgoright <Right>
- Move cursor one position right.
-
- EDITgotopline <Ctrl-Home>
- Move cursor to the top line in the display.
-
- EDITgotopmsg <Ctrl-PgUp>
- Move cursor to the first line in the message.
-
- EDITgoup <Up>
- Move cursor up to the previous line.
-
- EDITgowordleft <Ctrl-Left>, <Alt-Left>
- Move cursor to the previous word.
-
- EDITgowordright <Ctrl-Right>, <Alt-Right>
- Move cursor to the next word.
-
- EDITheader <Alt-H>
- Change attributes.
-
- EDITimporttext <Alt-I>, <Alt-R>, <F3>
- Import text file into this message.
-
- EDITloadfile <F8>
- Loads the message file saved with EDITsavefile.
-
- EDITnewline <Enter>
- Terminate paragraph and/or add a new line.
-
- EDITpaste <Alt-P>
- "Paste" a previously "Cut" block at the cursor position.
-
- EDITquitnow <Ctrl-Q>
- Quit GoldED immediately - no asking.
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 45
- ----------------------------------------------------------------------
-
- EDITsavefile <F7>
- Saves the current message as a file.
-
- EDITsavemsg <Alt-S>, <F2>
- Save this message.
-
- EDITspellcheck <F9>
- Calls an external spell checker for the current message.
-
- EDITtab <Tab>
- Add spaces to the next tab-stop.
-
- EDITtogglecase <Alt-3>
- Toggle the case of the cursor character.
-
- EDITtoggleinsert <Ins>
- Toggle insert mode.
-
- EDITtolower <Alt-2>
- Change the cursor character to lowercase.
-
- EDITtoupper <Alt-1>
- Change the cursor character to uppercase.
-
- EDITundelete <Ctrl-U>
- Undelete previously deleted lines.
-
-
- FILE SELECTION COMMANDS
- -----------------------
-
- FILEabort <Esc>
- Abort file selection.
-
- FILEaskexit <Alt-X>
- Exit GoldED - ask first.
-
- FILEdosshell <Alt-O>
- Shell to DOS.
-
- FILEgotofirst <Home>
- Go to first file.
-
- FILEgotolast <End>
- Go to last file.
-
- FILEgotonext <Right>
- Go to next file.
-
- FILEgotoprev <Left>
- Go to previous file.
-
- FILEmark <Ins>
- Mark file.
-
- FILEmarkall <Ctrl-Home>
- Mark all files.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 46
- ----------------------------------------------------------------------
-
-
- FILEquitnow <Ctrl-Q>
- Quit GoldED immediately.
-
- FILEselect <Enter>
- Select the marked file(s).
-
- FILEtogglemark <Space>
- Toggle file mark.
-
- FILEunmark <Del>
- Unmark file.
-
- FILEunmarkall <Ctrl-End>
- Unmark all files.
-
-
- MESSAGE LISTER COMMANDS
- -----------------------
-
- LISTabort <Esc>
- Abort message lister.
-
- LISTaskexit <Alt-X>
- Exit GoldED - ask first.
-
- LISTdosshell <Alt-O>
- Shell to DOS.
-
- LISTgotobookmark <Shift-Tab>, <BackSpace>
- Go to BookMark message.
-
- LISTgotofirst <Home>
- Go to first message.
-
- LISTgotolast <End>
- Go to last message.
-
- LISTgotonext <Right>
- Go to next message.
-
- LISTgotoprev <Left>
- Go to previous message.
-
- LISTmarkingoptions <Alt-S>
- Marking menu.
-
- LISTquitnow <Ctrl-Q>
- Quit GoldED immediately.
-
- LISTselect <Enter>
- Go to reader at the selected message.
-
- LISTtogglebookmark <Tab>
- Toggle BookMark on the selected message.
-
- LISTtogglemark <Space>
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 47
- ----------------------------------------------------------------------
-
- Toggle Mark on the selected message.
-
-
- NODELIST BROWSER COMMANDS
- -------------------------
-
- NODEabort <Esc>
- Abort nodelist browsing.
-
- NODEaskexit <Alt-X>
- Exit GoldED - ask first.
-
- NODEdosshell <Alt-O>
- Shell to DOS.
-
- NODEgotofirst <Home>
- Go to first node.
-
- NODEgotolast <End>
- Go to last node.
-
- NODEgotonext <Right>
- Go to next node.
-
- NODEgotoprev <Left>
- Go to previous node.
-
- NODEquitnow <Ctrl-Q>
- Quit GoldED immediately.
-
- NODEselect <Enter>
- Select node.
-
-
- MESSAGE READER COMMANDS
- -----------------------
-
- READaskexit <X>, <Alt-X>
- Exit GoldED, prompt for final decision.
-
- READchangeaka <Ctrl-A>
- Change default AKA address for the current area.
-
- READchangeattrs <Ctrl-S>
- Change the attributes of the current message.
-
- READchangemsg <C>, <Alt-C>, <Shift-F2>
- Change current message.
-
- READchangeorigin <Ctrl-O>
- Change default origin for the current area.
-
- READchangetemplate <Ctrl-T>
- Change default template.
-
- READchangeusername <Ctrl-U>
- Change default username.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 48
- ----------------------------------------------------------------------
-
-
- READcopymoveforward <M>, <Alt-M>, <Shift-F8>
- Enter the Copy/Move/Forward function menu.
-
- READdecreasemargin <Shift-F9>
- Decrease right message margin. For test purposes.
-
- READdeletemsg <D>, <Alt-D>, <Del>
- Delete current/marked message(s). Ask first.
-
- READdosshell <O>, <Alt-O>, <Ctrl-F10>
- Shell to DOS.
-
- READfidorenumber <Ctrl-R>, <Shift-F4>
- Renumber Fido/Opus *.MSG files.
-
- READfindall <F>, <Alt-F>, <Shift-F6>
- Find string(s) in message header and text.
-
- READfindheader <Z>, <Alt-Z>, <F6>
- Find string(s) in message header.
-
- READgotobookmark <Shift-Tab>, <BackSpace>
- Go to the "BookMark" message.
-
- READgotodownlink <Ctrl-Left>, <Alt-Left>, <->
- Go to the previous message in the replylink.
-
- READgotofirstmsg <Ctrl-Home>, <<>
- Go to the first message in the area.
-
- READgotolastmsg <Ctrl-End>, <>>
- Go to the last message in the area.
-
- READgotomsgno <Ctrl-G>, <any numeric key>
- Go to a specific message number.
-
- READgotonextarea <Ctrl-N>
- Go directly to the next area.
-
- READgotonextmsg <Right>
- Go to the next message.
-
- READgotoprevarea <Ctrl-P>
- Go directly to the previous area.
-
- READgotoprevmsg <Left>
- Go to the previous message.
-
- READgotouplink <Ctrl-Right>, <Alt-Right>, <+>
- Go to the next message in the replylink.
-
- READincreasemargin <Shift-F10>
- Increase right message margin. For test purposes.
-
- READmakeuserlist <Ctrl-L>
- Generate FIDOUSER.LST userlist of all users in the area.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 49
- ----------------------------------------------------------------------
-
-
- READmarkingoptions <S>, <Alt-S>, <Alt-F9>
- Enter the marking menu.
-
- READmessagelist <L>, <Alt-L>, <F9>
- Enter the message lister.
-
- READmovequotemsg <N>, <Alt-N>, <F5>
- Quote-Reply in another area.
-
- READmsgcontinue <Enter>
- Page down or go to next message.
-
- READmsgend <End>
- Display last part of current message.
-
- READmsghome <Home>
- Display first part of current message.
-
- READmsglinedown <Down>
- Scroll message display.
-
- READmsglineup <Up>
- Scroll message display.
-
- READmsgpgdn <PgDn>
- Page message display.
-
- READmsgpgup <PgUp>
- Page message display.
-
- READnewarea <A>, <Alt-A>, <Ctrl-F1>, <Esc>
- Enter the area selection screen.
-
- READnewmsg <E>, <Alt-E>, <Ins>
- Start a new message.
-
- READquitnow <Ctrl-Q>
- Exit GoldED immediately, no questions asked.
-
- READquotemsg <Q>, <Alt-Q>, <F4>
- Quote-Reply to the current message. (Reply to FROM name).
-
- READcommentmsg <G>, <Alt-G>
- Comment-Reply to the current message. (Reply to TO name).
-
- READreplymsg <R>, <Alt-R>, <F3>
- Reply to the current message, without quoting.
-
- READtogglebookmark <Tab>
- Toggle a "BookMark" on the current message.
-
- READtogglehexdump <I>, <Alt-I>, <Ctrl-F9>
- Toggle hexdump mode. For test/debugging purposes.
-
- READtogglehiddklud <V>, <Alt-V>, <Ctrl-F5>
- Toggle display of Hidden and Kludge lines.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 50
- ----------------------------------------------------------------------
-
-
- READtogglehidden <H>, <Alt-H>, <Ctrl-F7>
- Toggle display of Hidden lines.
-
- READtogglekludge <K>, <Alt-K>, <Ctrl-F6>
- Toggle display of Kludge lines.
-
- READtogglemark <Space>
- Toggle a message mark on the current message.
-
- READtogglemarkread <J>, <Alt-J>, <Alt-F10>
- Toggle "Read Marked" mode.
-
- READtogglepagebar <P>, <Alt-P>, <Ctrl-F8>
- Toggle the "PageBar" feature.
-
- READtogglerot13 <U>, <Alt-U>, <Ctrl-F3>
- Toggle ROT13 crypting for the current message.
-
- READtogglerealmsgno <Y>, <Alt-Y>, <Ctrl-F4>
- Toggle between sequential or real message numbers.
-
- READtoggletwits <T>, <Alt-T>
- Toggle Twit display - Show/Blank/Skip/Ignore.
-
- READwritemsg <W>, <Alt-W>, <F7>
- Write current/marked message(s) to file or printer.
-
-
- See the Key Reference below for a list of the key symbols you can
- use in keyboard redefintion.
-
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 51
- ----------------------------------------------------------------------
-
- M A C R O S A N D K E Y S T A C K I N G
-
- GoldED has a fairly simple keyboard macro facility, which you can
- use to automate certain common operations. A keystacking facility
- allows 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 GOLDED.KEY file, where you can also find
- several examples.
-
- 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
- environment variable.
-
- See the Key Reference below for a list of the key symbols you can
- use in macros and keystacking.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 52
- ----------------------------------------------------------------------
-
- K E Y R E F E R E N C E
-
- Below is the list of key symbols recognized by GoldLANG for
- keyboard/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
-
- 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:
- ---------------
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 53
- ----------------------------------------------------------------------
-
- Up ^Up @Up
- Down ^Down @Down
-
- Misc keys:
- ----------
- Esc ^Grey* Key5 Space
- Tab #Tab @Tab
- BackSpace ^BackSpace @BackSpace
- Enter ^Enter @Enter
-
- Note that some of the Alt-keys, especially the cursor-releated
- 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.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 54
- ----------------------------------------------------------------------
-
- L A N G U A G E D E F I N I T I O N
-
- GoldED is one of the very few programs that allows the user to
- almost completely redefine the language dependent text.
-
- The language dependent text in GoldED is defined in the GOLDED.LNG
- file, which in turn is compiled to a binary version by the
- GoldLANG program.
-
- See the example language file for the actual method and format of
- language 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 distribution of your files with future versions and/or
- with disk registrations.
-
-
- NOTES:
- ------
-
- In the continuing development of GoldED, it is impossible to
- completely maintain backward compatibility if the language format
- or the text defined there. New features may add and/or obsolete
- some definitions, or may change the format of others.
-
- The existing langauge file contains several definitions which are
- already obsolete, but which I haven't had time to search for and
- remove, as well as there are some texts in GoldED which are not
- yet definable. All this will of course be corrected in future
- versions.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 55
- ----------------------------------------------------------------------
-
- E N T E R I N G M E S S A G E S
-
- 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 (the FROM person).
- READcommentmsg - Quote-reply the current msg (the 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.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 56
- ----------------------------------------------------------------------
-
- T H E H A R D L I N E F E A T U R E
-
- 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 editor
- 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 ====
- ---------- Thu 28 Mar 91
- + 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 nescessary, because a
- blank line always ends the preceeding line or paragraph with a
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 57
- ----------------------------------------------------------------------
-
- hard-cr. In 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 preceeding paragraph.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 58
- ----------------------------------------------------------------------
-
- Q U O T E R E F L O W
-
- 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 <Shift-F9> or READincreasemargin <Shift-F10>
- commands.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 59
- ----------------------------------------------------------------------
-
- C A R B O N C O P Y A N D C R O S S P O S T
-
- 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/13
-
- 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 GOLDEDNAM 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
- popup 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 popup the nodelist browser in case of more than one
- match or if the node was not found.
-
-
- 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:
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 60
- ----------------------------------------------------------------------
-
- 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, Z27.SOFT
-
- This would produce the following output in the message:
-
- * Crossposted in GOLDED
- * Crossposted in NEWFILES.R23
- * Crossposted in ENET.SOFT
- * Crossposted in Z27.SOFT
-
- And post it in the conferences.
-
- Please moderate your use of this feature - it adds duplicate
- information to the mail flow, and excessive use may be frowned
- upon by cost-sensitive individuals.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 61
- ----------------------------------------------------------------------
-
- E N C R Y P T I N G M E S S A G E S
-
- GoldED allows you to en/decrypt messages encoded with the ROT13
- crypting 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 networks, where it is used as a
- "spoiler warning", so that game solutions, jokes and other stuff
- is not read by accident. In those networks, all message readers
- have ROT13 de/crypting capabilites.
-
- In FidoNet, not many message readers have ROT13 capabiblity, 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 echos.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 62
- ----------------------------------------------------------------------
-
- N O D E L I S T B R O W S I N G
-
- 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 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.
-
- 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
- alphabetically by last name. If you entered an address, the list
- is sorted ascending by address.
-
- Before the userlist is searched, the list of address macros are
- first scanned, and if a match is found there, the information
- there is used instead.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 63
- ----------------------------------------------------------------------
-
- M A R K I N G M E S S A G E S
-
- GoldED has a sophisticated message marking system, which allows
- flexible manipulation 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 replychain 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.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 64
- ----------------------------------------------------------------------
-
- K L U D G E L I N E S
-
- 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,
- underlining 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.
-
- 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
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 65
- ----------------------------------------------------------------------
-
- 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
- conforms 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>
- Proposed in FSC-0041, 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.
-
- Original: <Carbon copy, original name>
- Generated by the FrontDoor FM editor when it produces carbon
- copies.
-
- 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.
- Unfortunately 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, this is a 4D-version of the PATH kludge.
-
- 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. GoldED inserts this line, if the
- tearline is not "GoldED @Version".
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 66
- ----------------------------------------------------------------------
-
- RFD: <id>
- Received For Distribution. A kludge inserted by one of the file
- announcement programs.
-
- REPLY: <replyaddress> <replyserialno>
- Proposed in FSC-0041, 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 creates problems when exporting echomail
- across zones.
-
- SN:<serialno>
- Serial number inserted by the Dutchie message editor.
-
- TCL1:, TCL2: <long hex string>
- Obsolete swedish dupecheck/replylink kludge.
-
- TOPT <to point>
- Defined in FTS-0001, this tells the Point number of the
- destination. 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.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 67
- ----------------------------------------------------------------------
-
- K N O W N B U G S
-
- GoldEd contains a number of still unfixed bugs or semi-unsolvable
- problems. The following list is *not* complete.
-
- Internal editor
- ---------------
- The internal editor has many odd bugs, most prominently the line
- wrapping 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 for a future version.
-
- Multitasking environment
- ------------------------
- It *is* possible to run GoldED and read/write mail, while a user
- is online on your networked or multitasking RA/Super/QuickBBS, but
- it is *NOT* safe! This is something I will surely be taking care
- of in a near 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 SWAPALL DISK, this usually always work
- (if there is enough free disk ;-). You might also try turning off
- the OVERLAYEXT/EMS keywords, if you had them 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.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 68
- ----------------------------------------------------------------------
-
- R E S T R I C T E D F E A T U R E S
-
- GoldED has a few non-vital features restricted for unregistered
- users:
-
- * AUTOATTACH keyword.
- * GOLDEDLST keyword.
- * RENAREA keyword.
- * REPLYRE keyword.
- * Tearline definition.
- * ROT13 message encryption.
-
- In addition, the program will add an extra random pause when
- initializing. You can press a key to bypass the pause.
-
- These restrictions and the pause will go away when you register...
-
-
-
- F U T U R E P L A N S
-
- 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.
- * Menu system to supplement direct keyboard operation.
- * More flexible random system / area definition.
- * Scan for/read your mail in all areas.
- * Smart file request function.
- * Better marking facilities.
- * Highest read.
- * Replies reading mode.
- * Nodelist browsing in levels a'la FrontDoor.
- * Xpress and XRS compatibility.
- * Other msg formats such as XBBS.
- * Smarter error handling.
- * Better mouse support.
- * Different message template format.
- * Conditional macros and macro recording.
- * Windows 3 version: GoldED 3.xx.
- * Many other things!
-
- Keep the suggestions coming!
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 69
- ----------------------------------------------------------------------
-
- D I S T R I B U T I O N S I T E S
-
- The major public releases of GoldED are distributed via the SDS
- (Software Distribution System), and should therefore be available
- around the world at your local SDS node.
-
- In addition to this, public beta versions will be available from
- the systems in the list below.
-
- Primary distribution and registration sites:
- --------------------------------------------
- South o'the Border! 1:106/215 HST/V32/V42 U.S.A.
- The Golden Wizard 2:231/77 2400 Denmark
- Beta-System 2:246/10 HST/V42 Germany
- * Delmare * 2:500/133 2400 Holland
-
- See the REGISTER.DOC for more information about registering.
-
- Secondary distribution sites:
- -----------------------------
- Group Medical BBS 1:138/116 HST U.S.A.
- Mirage BBS 1:160/202 HST U.S.A.
- Falcon BBS 2:231/19 2400 Denmark
- The Thunderbolt CBCS 2:231/60 HST/V32/V42 Denmark
- Soft-Sector BBS 2:231/79 HST/V32/V42 Denmark
- The Bag of Tricks 2:231/82 HST/V32/V42 Denmark
- THE 208 MONSTER 2:231/91 2400 Denmark
- ADLATUS BBS 2:243/44 HST/V32/V42 Germany
- The Pig Pen 2:250/124 HST/V32 U.K.
- TMS-INW 2:321/7 V32 France
- DMRT Board Two [SDN] 2:512/101 V32/V32B Holland
- The Owl's Nest Node 2:512/39 HST/V32/V42 Holland
-
- ... And many many others eventually ...
-
-
-
- S U P P O R T C O N F E R E N C E
-
- 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 echos 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.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 70
- ----------------------------------------------------------------------
-
- A C K N O W L E D G E M E N T S
-
- I would like to thank the following persons, who have, in one way
- or another, helped GoldED to become what it is:
-
- (alphabetical)
- Adam Hudson QuickBBS.
- 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 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.
- Stig Jacobsen Various source code and testing.
- The RemoteAccess Team The RemoteAccess BBS.
-
- Not least, I thank all the testers and users for all their
- inspiring suggestions and bugreports. Keep'em coming!
-
- Without the following software, GoldED would have been much harder
- to write:
-
- QEdit (SemWare). My favorite text-editor.
- Turbo/Borland C++. My favorite C compiler.
- 4DOS (J.P.Software). My favorite COMMAND.COM replacement.
-
- I thank the authors and companies for producing those fantastic
- pieces of software.
-
-
-
- T H E A U T H O R
-
- Name:
- Odinn Sorensen
-
- Birthday:
- 17 Feb 1969, born in Iceland, now lives in Denmark.
-
- Occupation:
- Self-taught C programmer, currently unemployed. Will be
- studying for engineer after summer'91.
-
- Personality:
- Quiet, all-round nice guy.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 71
- ----------------------------------------------------------------------
-
- A P P E N D I X 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: Currently not all the FLAGS attributes are supported
- completely by FrontDoor or D'Bridge.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 72
- ----------------------------------------------------------------------
-
- A P P E N D I X B - Node masks
-
- <nodemask> = normal address specifications + special "macronames":
-
- MYZONE, MYNET, MYNODE, MYPOINT = parts of main address.
- ALL, ? = Wildcard for one part.
- NETxxx = MYZONE:NETxxx/ALL.0
- NCxxx = MYZONE:NCxxx/0.0
- RCxxx = MYZONE:RCxxx/0.0
- ZCxxx = ZCxxx:ZCxxx/0.0
- NECxxx = MYZONE:NECxxx/2.0 (Common usage, not official)
- ZECxxx = ZECxxx:ZECxxx/200.0 (Common usage, not official)
- 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
- ZONEGATExx = MYZONE:MYZONE/ZONEGATExx.0
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 73
- ----------------------------------------------------------------------
-
- A P P E N D I X C - Files
-
- GoldED uses a lot of different files for different purposes. Here
- is a fairly complete list.
-
- These are files from the distribution archive:
- ----------------------------------------------
- ADVANCED EXE Self-extracting archive (advanced configuration).
- COLORS COL Example color configuration.
- GOLDED CFG Main configuration file (simple version).
- GOLDED CFM Example confirmation receipt template.
- GOLDED DOC GoldED manual.
- GOLDED EXE Main executable.
- GOLDED HLP Help definition file.
- GOLDED KEY Keyboard definition file.
- GOLDED LNG Language definition file.
- GOLDED TPL Message template.
- GOLDLANG EXE Configuration files compiler.
- GOLDNODE EXE GoldED nodelist/userlist index compiler.
- MONOS COL Example monocrome color configuration.
- README DOC News since previous versions.
- REGISTER * Docs and forms for registration.
-
-
- The ADVANCED.EXE archive contains:
- ----------------------------------
- AREAS BBS Example AREAS.BBS file.
- COLOR* COL Example color configurations.
- GOLDED ARE Example area configuration.
- GOLDED CFG Example advanced configuration file.
- GOLDED RAN Example Random System definition file.
- GOLDRAND EXE Random (Cookie) text compiler/display util.
- MONO* COL Example monocrome color configurations.
- RANDOM TXT Example random file. (For GOLDRAND.EXE).
- * CHS Example charset translation tables.
- * ESC Example escape sequence translation tables.
-
-
- Files generated by GoldED, GoldLANG, GoldNODE or GoldRAND:
- ----------------------------------------------------------
- GOLDED DAT Binary configuration data.
- GOLDED HLX Binary help file.
- GOLDED KBD Binary keyboard definition.
- GOLDED LNX Binary language definition.
- GOLDED LOG Logfile, generated at error exits.
- GOLDED LST Output FIDOUSER.LST compatible userlist.
- GOLDED MSG Temporary external editor message file.
- GOLDED OUT Default write output file.
- GOLDED RDX Random System index file.
- GOLDED RLN Random System index file.
- GOLDNODE ADX Nodelist index file.
- GOLDNODE NDX Nodelist index file.
- RANDOM IDX Index file for RANDOM.TXT.
- * CHX Binary charset translation tables.
- * ESX Binary escape sequence translation tables.
-
-
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 74
- ----------------------------------------------------------------------
-
- External files used/accessed by GoldED:
- ---------------------------------------
- QuickBBS:
- CONFIG.BBS Areas.
- AREAS.BBS Area echoids.
-
- RemoteAccess:
- MESSAGES.RA Areas.
- AREAS.BBS Area echoids.
-
- FrontDoor:
- FD.SYS Netmail area, origins.
- FOLDER.SYS Areas.
- AREAS.BBS Area echoids.
- NAMES.FD Address macros.
- FDRESCAN.NOW Netmail rescan semaphore file.
-
- TosScan:
- FD.SYS Netmail area, origins.
- AREAFILE.FD Areas.
- NAMES.FD Address macros.
-
- D'Bridge:
- DBRIDGE.PRM Netmail, badecho areas.
- DBRIDGE.AA1/AA2 Areas (DB 1.30).
- DBRIDGE.ADF Areas (DB 1.31 and newer betas).
- DBRIDGE.LRQ Lastread pointers.
- DBRIDGE.RSN/RSE Rescan semaphore files.
- DBRIDGE.NMW/EMW Mail waiting semaphore files.
- ECHOMAIL.CTL Echomail scanning file.
-
- Opus:
- SYSTEM??.DAT Areas.
-
- IMail:
- IMAIL.CF Netmail, badecho and dup areas.
- IMAIL.AR Areas.
-
- Maximus:
- AREA.DAT Areas.
-
- ME2:
- AREADESC.ME2 Area descriptions.
- AREAS.BBS Areas.
-
- Dutchie:
- DUTCHIE.ARE Areas.
-
-
- QuickBBS-style messagebase files:
- ---------------------------------
- MSGHDR.BBS Message headers.
- MSGIDX.BBS Message header index.
- MSGINFO.BBS Messagebase info.
- MSGTOIDX.BBS Name index.
- MSGTXT.BBS Message text.
- LASTREAD.BBS Lastread pointers.
-
- GoldED - A full-feature Sysop/Point message reader/editor. Page 75
- ----------------------------------------------------------------------
-
- USERS.BBS User database.
- NETMAIL.BBS Header index for unscanned netmail.
- ECHOMAIL.BBS Header index for unscanned echomail.
-
-
-
- ----------------------------------------------------------------------
-