; Sample Configuration file for HeadEdit
;
;   Call HeadEdit as HEADEDIT <configfile> [application]
;        (defaults to HeadEdit.CFG, no application)
;
; Not all keywords are required...there are defaults for most.
; Keywords must begin in first column
; Lines beginning with a semicolon ";" are comments
;
;
; If you're running as a point and want to let HeadEdit import and/or
; export your mail for you, you need the following keywords.  You also
; need UNARC.CMD in the default directory or on your DOS path.  HeadEdit
; will spawn it to unpack archived mail as:
; %COMSPEC% UNARC.CMD <inbound> <archive_name>
; A typical UNARC.CMD might have just the line "POLYXARC.EXE" in it.
; After packeting outgoing mail, HeadEdit attempts to spawn ROUTE.CMD as
; %COMSPEC% ROUTE.CMD <outbound>
; What ROUTE.CMD does is highly dependent on your mailer.  This step
; should archive the packet and do anything to it your mailer requires
; to get it to its destination.

; If you're a mailerless point off of an XBBS system, you need to be sure
; the archive filename is 00000000.MO? (where ? is a number from 0 to 9).
; Remember that, before archiving a packet, it's renamed from .?UT (where
; ? is O, N, D, H, or C) to .PKT.  You'll probably need to rely on
; directories to separate files destined for multiple XBBS Boss nodes,
; since they'll all have the same basic filenames.  You could just write
; a batch file to handle your mailerless point archiving; no real need
; for something like oMMM or MakeArc. Remember that *.?UT files are named
; according to this convention:
; <4-hex-digit-destnet><4-hex-digit-destnode>.?UT.
;
; Binkley will require a .FLO attach from your pointnet address to your
; Boss; FD will require a .MSG attach from your point or pointnet to your
; Boss.  For Bink there are a lot of utilities (AMAX, BONK, BOOM, and
; PLEASE to name a few) to create the attach.  Dunno what you'd use for FD.
;
; Note that HeadEdit's built-in mail tosser/scanner is *only* for point
; systems!  It is also still in beta-testing stages and should be used
; only under supervision (don't just let it run and pollute the net if
; it contains a bug!).
;
;INBOUND  g:\BT\FILES\
;OUTBOUND g:\BT\OUTBOUND\
;
;
;
; SCREENSIZE tells HeadEdit what size screen to use.  It'll set the screen
; to the indicated size.  Won't do what OS/2's VioSetMode() won't do.
;
;SCREENSIZE 80 43
;
;
;
; PRIORITY sets the priority of HeadEdit's main thread.
;
;PRIORITY 2 31
;
;
;
; SEADATES tells HeadEdit to use the SEA format date (leading alphabetic
; abbreviation for day of week) instead of Fido format.  Both are as
; specified in FTS-0001.  Which is more than we can say for QMail 1.00a
;
SEADATES
;
;
;
; If you use the BELL keyword, HeadEdit will beep a little more often than
; it does by default.  Useful for when you're just learning to use it, as
; it helps you know when your input is invalid.
;
;BELL
;
;
;
; MSGAREAS is the name of your MSGAREAS.XBS-style area file.  The default
; is MSGAREAS.XBS in the message base directory.
;
;MSGAREAS g:\XBBS\ALTAREAS.XBS
;
;
; START determines which area you come up in
;
START    5
;
;
; TOTALAREAS determines how many areas you're keeping Last Message Read
; (LMR) pointers for.  If you're running XBBS, this must match the
; number in CONFIG.BBS.  If not, put whatever you like.  This number,
; once set, should be left alone if you've got more than one "account".
;
TOTALAREAS 50
;
;
; USERNUMBER determines your entry position in the LASTREAD.BBS file
; This must be given!  For SysOps running XBBS, this is always 1 (same
; as your user number in the USERS.BBS file).  For other users (say a
; spouse, parent or child in the same household), it should be their
; user number as well.  CAUTION:  Make sure you have users with access
; to HeadEdit in positions 2+ where they won't be moved during packing!
; For Point systems, this will probably be #1, but you can add other
; users from there (multiple users on the same point)...
;
USERNUMBER 1
;
;
; ALIAS designates a name for you...you can use up to 23, and must have
; at least 1.  The first is considered your real name, the second is
; considered your handle unless you turn this "tracking" off with the
; NOTRACK keyword.
;
ALIAS    Mark Kimes
ALIAS    Hector Plasmic
;
;
; ADDRESS is your net address...you can use up to 23.  Domains are
; limited to 36 characters, zone:/node.point to 1-65535 and net to
; 1-65533
;
ADDRESS  69:69/69.69@Dufusnet
;
;
; EDITOR is the string to spawn for entering messages.
; Include the extension of the executable.  If you don't have this,
; HeadEdit will use its built-in mini text editor (barf).
;
EDITOR   Q.EXE
;
;
;
; WRAP is the string to spawn to wrap entered messages...optional, as
; HeadEdit has internal wrapping (but if you don't like the way HeadEdit
; does it, this lets you change it).  Include the extension of the
; executable.
;
;WRAP     WRAPPER.EXE 71
;
;
; WRAPLEN is how wide your text lines are (right margin) less 1 (seems
; to work best...experiment).  Set to 0 and don't use WRAP to disable
; wrapping permanently (it can also be disabled inside HeadEdit
; temporarily).  Set to > 0 && < 30 and for a different sort of wrapping
; (the type 4MIKE.COM used to do, as opposed to the type WRAPPER.EXE
; used to do).  If you have Scroll Lock on when you save a message,
; no internal wrapping will take place.
;
WRAPLEN  71
;
;
; The PATH to your message files...note the trailing backslash!
; You can have up to 23 paths, but probably will never need them
;
PATH     g:\XBBS\MESS\
;
;
; ORIGIN should be followed by your default origin line (up to 60 chars)
; You can have a file called ORIGINS.BBS in the message area path that
; contains special origin lines for given areas.  Format:
; <board #>;<origin text>  (i.e. 22;My Point System) one per line.
; You can also do away with either the origin or tear (---) or both
; (for advanced use only when you *know* it's all right!):
; <board #>;NOORIGIN (no origin, just a tear line)
; <board #>;NOTEAR<origin text> (no tear line, just an origin)
; <board #>;NOORIGIN/NOTEAR (no origin or tear line)
;
ORIGIN   An XBBS
;
;
; ANSIEDITOR is the string to spawn when entering messages in an ANSI
; area...required if you have an ANSI area.  ANSIEd is recommended, since
; ANSI messages should confine themselves to certain areas of the screen
; (ANSIEd takes care of this for you)
; Include the extension of the executable
;
;ANSIEDITOR ANSIEd.EXE 0 0 999 16
;
;
; ATTRIBUTES sets the default attribute bits for netmail messages
; MSGPRIVATE 1
; MSGCRASH   2
; MSGREAD    4
; MSGSENT    8
; MSGFILE    16
; MSGFWD     32
; MSGORPHAN  64
; MSGKILL    128
; MSGLOCAL   256
; MSGXX1     512
; MSGXX2     1024
; MSGFRQ     2048
; MSGRRQ     4096
; MSGCPT     8192
; MSGARQ     16384
; MSGURQ     32768
; Add these together to get the number you need
;
ATTRIBUTES  385
;
;
; LINES determines how many line pointers the system allocates.  Each
; pointer requires two bytes (it's a word).  Pointers are what allow you
; to page backward as well as forward in a message.  10240 is the
; default (48K of pointers), but you can increase this or decrease it to
; as little as 257.  When you overrun your pointers (read more lines
; than you have pointers for), all it means is that you'll be at the
; start of the message if you try to go up.
;
LINES 10240
;
;
; NOCHECK turns off automatic address checking when editting Net Mail
; headers.  You can still check manually with F6 if you have the
; nodelist loaded.  Points running without a nodelist should use this
; keyword.
;
NOCHECK
;
;
; SELECTIVE tells HeadEdit to start up allowing searching during Global
; scan from the Main Menu.
;
;SELECTIVE
;
;
; UNLISTED tells HeadEdit to start up showing unlisted areas
;
;UNLISTED
;
;
; NONODELIST tells HeadEdit not to load the nodelist index.  You won't
; be able to look up net/node numbers if you do this, but you can still
; send net mail and even use a FIDOUSER.LST (even one you type up).
; I'd suggest turning it off only if you don't use HeadEdit for net mail
; or are a point operating without a nodelist.
; It does save some memory to use this keyword.
;
NONODELIST
;
;
; NODELIST tells HeadEdit where to look for your nodelist file(s).
; HeadEdit uses a Version 6 NodeList.
; It will also use a FIDOUSER.LST (in the same path).  The default is
; HeadEdit's default directory if you don't use this keyword.  Note that
; the trailing backslash is REQUIRED.  You don't need this if you're a
; point operating without a nodelist.
;
;NODELIST g:\XBBS\
;
;
; Note that the following color defaults are for monochrome systems...
; TEXTCOLOR tells HeadEdit what color you want text to be while reading
; messages.  It can have one of the following values:
;  BLACK         = 0
;  BLUE          = 1
;  GREEN         = 2
;  CYAN          = 3
;  RED           = 4
;  MAGENTA       = 5
;  BROWN         = 6
;  LIGHTGRAY     = 7
;  DARKGRAY      = 8
;  LIGHTBLUE     = 9
;  LIGHTGREEN    = 10
;  LIGHTCYAN     = 11
;  LIGHTRED      = 12
;  LIGHTMAGENTA  = 13
;  YELLOW        = 14
;  WHITE         = 15
;
TEXTCOLOR  7
;
; TEXTBACK tells HeadEdit what color to use for the background while
; reading messages.  It can have one of the following values:
;  BLACK         = 0
;  BLUE          = 1
;  GREEN         = 2
;  CYAN          = 3
;  RED           = 4
;  MAGENTA       = 5
;  BROWN         = 6
;
TEXTBACK   0
;
; STATCOLOR and STATBACK serve the same purpose and have the same
; potential values as the above, only they apply to the bottom and
; division lines when reading.
;
STATCOLOR  0
STATBACK   7
;
; HEADCOLOR and HEADBACK are for the message header info displayed while
; reading.
;
HEADCOLOR  7
HEADBACK   0
;
; Miscellaneous other special colors.  The names should tell you when
; they're used.  Set the the same as TEXTCOLOR and TEXTBACK to effectively
; disable the hightlighting.  There are defaults if you want to comment
; them out completely.  You can also use NOHILITE to totally disable this
; hilighting (should speed processing fractionally, too).
;
QUOTEFORE   7
QUOTEBACK   0
TEARFORE    7
TEARBACK    0
ORIGFORE    7
ORIGBACK    0
KLUDGEFORE  7
KLUDGEBACK  0
;
; EXPORTNAME is followed by the name of the default export file
;
;EXPORTNAME TEMP.TXT
;
;
; USEROOTNAME is followed by a root name (no extension!) of an export
; file.  HeadEdit appends .### to the file (where ### is a three-digit
; hex number representing the area #).  The file is always appended to
; if it exists.  This makes it easier to keep things organized.
;
USEROOTNAME G:\BT\MYMSGS
;
;
; BEFOREQUOTE is a string that will precede quoted text in a reply if
; you blank the quote string.  It has four arguments that follow it:
; the original msg's date, original poster, original recipient, and
; msg subject.  These can be accessed (in order only, sorry) by putting
; a %s in the BEFOREQUOTE string.  Not all must be used.
;
;BEFOREQUOTE On %s %s wrote to %s:
;
; AFTERBEFORE is a string printed after BEFOREQUOTE.  Has the same
; arguments but you can skip them.
;
;AFTERBEFORE ************************************************************
;
; AFTERQUOTE is a string printed when the quoted text is complete.
; No arguments follow.
;
;AFTERQUOTE ************************ END QUOTE **************************
;
;
; Here's some stuff used when you print messages in HeadEdit.  BTW, you can
; change that PRN that comes up by default to a regular filename.  Don't
; change it to CON unless you want an unpleasant surprise...
;
; BEFOREHEADER is followed by anything you might want sent to the printer
; after a message header is displayed.  The tilde ~ is translated in this
; case to an ESC character, and the reverse apostrophe ` is translated to
; a carriage return/line feed.
;
; AFTERHEADER is the same sort of thing for after the header is printed.
;
;
; AFTERTEXT is, again, the same thing after the message body is printed.
;
AFTERTEXT ``
;
; AFTERPRINTING is, one last time, the same thing when a batch print job
; is completed.
;
; PAGELENGTH tells HeadEdit how long your printed page is.
;
PAGELENGTH 66
;
; TOPMARGIN is how many blank lines you want at the top of a page.
;
TOPMARGIN 6
;
; BOTTOMMARGIN is how many blank lines at the bottom of the page.
;
BOTTOMMARGIN 6
;
; LEFTMARGIN is how many blank spaces at the left of the page.
;
LEFTMARGIN 6
;
; TEXTWIDTH is how wide you want the message text to be.
;
TEXTWIDTH 72
;
;
;
; ALT-Function keys can be used for spawning programs.  This spawn swaps
; if you have swapping enabled.  It does *not* go through COMMAND.COM,
; so if you want to run a batch file you need something like
; CMD.EXE BATCHFIL.CMD
; Format is FKEY #(1-10) Spawn string...
; There are a few metastrings (prefaced by * as in XBBS):
;
; *F   From name of current msg (spaces replaced by _)
; *T   To name of current msg   (spaces replaced by _)
; *A   Name of current msg area (spaces replaced by _)
; *a   # of current msg area
; *#   # of current msg
; *P   Path to msg base files
; *D   Date of current msg      (spaces replaced by _)
; *f   From name of current msg
; *t   To name of current msg
; *N   Name of current msg area
; *d   Date of current msg
;
FKEY 1 XUSERPM.EXE USER *F
FKEY 2 Q.EXE
;
;
;
; NETBOARD tells HeadEdit which board is your netmail board.
;
NETBOARD 5
;
; ALTBOARD tells HeadEdit which board is your alternate address netmail
; board.
;
ALTBOARD 5
;
;
; USEDEFAULT would start HeadEdit up to ignore ORIGINS.BBS and use only
; the default origin line
;
;USEDEFAULT
;
;
; NO*PT tells HeadEdit not to insert ^aFMPT and ^aTOPT kludge lines (which
; are obsolete with ^aMSGID & ^aMSGTO)
;
;NO*PT
;
;
; NOINTL tells HeadEdit not to insert ^aINTL kludge lines (which are
; obsolete with ^aMSGID & ^aMSGTO).  HeadEdit never inserts a ^aDOMAIN.
;
;NOINTL
;
;
; FLSEARCH tells HeadEdit the path to your FLSEARCH.CTL-type file that
; is used when looking up associated files.
;
FLSEARCH g:\XBBS\FLSEARCH.CTL
;
;
; SPAWNVIEW tells HeadEdit what to spawn to view associated files.  I'd
; suggest SHEZ.  HeadEdit will add the filename to the spawn line.
;
SPAWNVIEW SHEZ.EXE
;
;
; TEMPLATE tells HeadEdit that you want to execute a Template program
; to work on MSGTMP before invoking the internal editor.
;
;TEMPLATE Template.EXE
;
;
; MAKEINFO tells HeadEdit to write a MSGTMP.INF file before it spawns
; the editor.  This can be used to wedge in a Template program.  If
; MAKEINFO is commented out, a MSGTMP.INF file will *not* be written.
; As of this writing (04/17/90), only one template program is available
; for HeadEdit, from Renee Teunissen (2:512/34.5).
;
; Format of MSGTMP.INF file:
;
; REPLY    (keyword present if this is a reply)
; NET      (keyword present if this is netmail)
; ECHO     (keyword present if this is echomail)
; ECHO2NET (keyword present if this is a net reply to echo)
; FROM     Name (present only if this is a reply)
; WASTO    Name (present only if this is a reply)
; TO       Name
; DATE     Fido-style datestring of original (present only if this is a reply)
;          Note that this is the datestring *as it was imported* and is not
;          guaranteed to be in accordance with FTS-0001's spec (HeadEdit's
;          dates are, most Opii dates aren't, grumble, grumble).
; ORIG     Net address of originating node (net only)
; DEST     Net address of destination node (net only)
; SUBJ     Subject of message
; WRITER   Name
; AREANAME Area Name
; AREA#    Area #
; AREAATTR Area's attribute word
; MSGATTR  Message's "FidoNet" attribute word
; MSGATTR2 Message's XBBS extended attribute word
; READER   ReaderName Version#
; NODE#    Nodenumber (if software uses it; HeadEdit doesn't, XBBS does)
;
; Template programs should not expect keywords in any particular order.
; They should be tolerant of variable quantities of spaces between
; keyword and arguments (where arguments are required).  They should not
; be case sensitive regarding keywords.  They should be tolerant of
; additional (unlisted) keywords and not freak if one expected isn't
; present, nor if the MSGTMP.INF file itself is not present (as it won't
; be when editting a msg).  They should be installable in such a manner
; that they run, create a "finished" MSGTMP file for the editor to
; manipulate, then call the editor, which will return to HeadEdit on
; completion.  For multinode compatibility, they should tolerate
; filenames such as MSGTMP1.INF, MSGTMP2.INF, etc.  The user should be
; aware that editting the header info after the message has been written
; (from the [S]ave [A]bort [E]dit Header prompt) may cause a mismatch
; between header information and the information that the Template
; program used (if, for instance, you change the To: field).
;
MAKEINFO
;
;
; COMPRESS tells HeadEdit what size message to compress if the current
; area allows compression.  A message will have to be at least this size
; before compression will take place.  Compression/decompression uses a
; lot of memory, so you may not want to enable this if you're operating
; under a RAM-tight situation (like a multitasker).  This extra memory
; usage is minimized but not totally eliminated by HeadEdit's overlays.
;
COMPRESS 2048
;
;
; SKIPDELETED tells HeadEdit to ignore deleted messages.
;
;SKIPDELETED
;
;
; APPLICATION <idstring> is available.  If you call HeadEdit with
; HEADEDIT <configfile> <idstring>, HeadEdit will read until it finds a
; matching APPLICATION statement and use text after that, up to the next
; APPLICATION statement, as its config info.  This can let you have more
; than one HeadEdit config in a single file. Other programs could also use
; this device to let you keep their config info in the same file (the
; above Template program, for example).
;
;
;APPLICATION Template
;
;
; APPLICATION areas are terminated by the ENDAPP statement.  HeadEdit
; immediately stops parsing the config file when it reaches this keyword.
;
;ENDAPP
;
;
; DOMAIL <#> tells HeadEdit to do some mail processing on startup.
; The following values are valid:
;
;  1.  Import mail and continue
;  2.  Import mail and stop HeadEdit
;  3.  Export mail and continue
;  4.  Export mail and stop HeadEdit
;  5.  Import then export and continue
;  6.  Import then export and stop HeadEdit
;
;DOMAIL 2
;
;
; MONOCHROME tells HeadEdit to make all the windows basic black and
; white even if you have a color monitor.  This will not affect the
; colors you see when reading, but you can adjust them separately above.
;
;MONOCHROME
;
;
;    Last line in file should always be a comment or blank line because
; of the way HeadEdit parses the config file.