16916 lines
504 KiB
Plaintext
16916 lines
504 KiB
Plaintext
<!doctype tei.2 public '-//TEI//DTD TEI Tools 0.1//EN'>
|
|
<!-- $Id$ -->
|
|
<TEI.2 lang='en'>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<teiHeader>
|
|
<fileDesc>
|
|
<titleStmt>
|
|
<title>
|
|
GoldED+ Reference Manual
|
|
</title>
|
|
</titleStmt>
|
|
<sourceDesc>
|
|
<p>
|
|
Created in electronic form.
|
|
</p>
|
|
</sourceDesc>
|
|
</fileDesc>
|
|
<profileDesc>
|
|
<langUsage>
|
|
<language id="en">
|
|
English
|
|
</language>
|
|
</langUsage>
|
|
</profileDesc>
|
|
</teiHeader>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<text>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<front>
|
|
<titlePage>
|
|
<docTitle>
|
|
<titlePart type=main>
|
|
GoldED+
|
|
</titlePart>
|
|
<titlePart type=desc>
|
|
Reference Manual
|
|
</titlePart>
|
|
</docTitle>
|
|
<docAuthor>
|
|
Odinn Sorensen, Dirk A. Mueller, Alexander S. Aganichev and others
|
|
</docAuthor>
|
|
<docDate>
|
|
1990-2003
|
|
</docDate>
|
|
</titlePage>
|
|
<divGen type=toc>
|
|
</front>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<body>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<div1>
|
|
<head>
|
|
Introduction
|
|
</head>
|
|
<p>
|
|
<name/GoldED+/ is a successor of the wellknown <name/GoldED/ mail editor
|
|
originally written by <name/Odinn Sorensen/.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ is run under <name/DOS/ with 32-bit <abbr/DPMI/ driver,
|
|
<name/Microsoft Windows/, <name>IBM OS/2</name>, <name/Linux/,
|
|
<name/FreeBSD/, <name/QNX/, and <name/BeOS/. There should be no serious
|
|
problem to compile it on other <name/UNIX/-like systems running on
|
|
<name/Intel/ <name/80x86/ architecture. Unlike the original version of
|
|
<name/GoldED/, <name/GoldED+/ is not supported on CPUs lower than
|
|
<name/80386/.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ takes his history from the patch collection made by
|
|
<name/Alexander Aganichev/. A lot of code was contributed to
|
|
<name/GoldED+/ by different people around the world. At least,
|
|
<name/GoldED+/ contains portions of code written by the core team of
|
|
<name/GoldED/ (<name/Odinn Sorensen/, <name>Dirk A. Mueller</name>, and
|
|
<name/Leonid Lisovsky/), <name/Mike Smedley/, <name/Pavel Gulchouck/,
|
|
<name/Denis Zavorotny/, <name/Alexander Batalov/, <name/Eugene Roshal/,
|
|
<name/Igor Vanin/, <name/Alexey Froloff/, <name/Andrew Shakhmatov/,
|
|
<name/Roman Trunov/, <name/Alex Druinsky/, <name>Alexander
|
|
Tsvyashchenko</name>, <name/Pavel Tsekov/, <name/Alexander Reznikov/,
|
|
<name/Siarzhuk Zharski/ and
|
|
(of course) by the maintainers of <name/GoldED+/ (<name>Alexander
|
|
Aganichev</name> and <name/Jacobo Tarrio/). Some portions of code was
|
|
taken from C/C++ snippets collected by <name/Bob Stouts/ (personal thanks
|
|
goes to <name/Thad Smith/, <name/Raymond Gardner/, <name/Jeff Dunlop/,
|
|
<name/Mark G. Mendel/, <name/Gary S. Brown/, <name/John Rex/, and
|
|
<name/Walter Bright/) and some other from <name/GNU/ libraries
|
|
(thanks goes to <name/GNU/ C library maintainers, <name/Rob Swindell/,
|
|
<name/Frank Pilhofer/, <name/Haruhiko Okumura/, <name>Haruyasu
|
|
Yoshizaki</name>, <name/SLang/ maintainers, <name/TIN/ maintainers, and
|
|
<name/Eric Newton/). Also, there are portions of code which are courtesy
|
|
of various FTN software authors: <name/Scott J. Dudley/ and <name>Lanius
|
|
Corporation</name>, <name/Bit Bucket Software/, <name/Husky Team/,
|
|
<name/Thomas Waldmann/, <name/Peter Davies/, <name/Ron Clark/,
|
|
<name/Tobias Burchhardt/, <name/Andreas Klein/, <name>Folkert J.
|
|
Wijnstra</name>, <name/Gerard J. van der Land/, <name/Peter Stewart/ and
|
|
<name/InterZone Software, Inc./, <name/Marco Maccaferri/,
|
|
<name/Wynn Wagner III/, <name/Andrew Milner/ and <name>Continental
|
|
Software</name>, <name/Bjarne Maschoreck/, <name/Roger Kirchhoff/,
|
|
<name/Stefan Graf/, <name/Nicolai Dufva/, and <name/Morten Baun/. If you
|
|
feel that your name is missed here please drop an e-mail to the
|
|
<name/GoldED+/ maintainers.
|
|
</p>
|
|
<p>
|
|
We also need to thanks all that people who have contributed configuration
|
|
files: <name/Richard Menedetter/, <name/Peter Karlsson/,
|
|
<name/Daniel Hahler/, <name/Marco Van den Bovenkamp/, <name>Steve
|
|
Shapiro</name>, <name/Teddy Winstead/, <name/Richard Merit/,
|
|
<name/Thomas Kraft/, <name/Magnus Jacobsen/, <name/Lars Pehrsson/,
|
|
<name/Tony Van den Bogaert/, <name/Karsten Palmvig/, <name>Michael
|
|
Hembo</name>, <name/Thomas Endres/, <name/Nathan Moschkin/,
|
|
<name/Micheal Dunnagan/, <name/Joseph Carnage/, <name/Thomas Endres/,
|
|
<name/Niels Axelsson/, <name/Gustav Brock/, <name/Stig Jacobsen/,
|
|
<name/Erik Wachtmeester/, <name/Dirk Frieborg/, <name/Gd'A/,
|
|
<name/Cees Schouten/, <name/Andrew Voronin/, <name/Arkady Grikurov/,
|
|
<name/Mik Karlsson/, <name/K. Simonsen/, <name/Thomas Gradin/,
|
|
<name/Andre van de Wijdeven/, <name/Robert Bashe/, <name>Kees
|
|
Bergwerf</name>, <name/Ferdinand Grassmann/, <name/Laurent Jumet/,
|
|
<name/Andrew Porokhnyak/, and <name/Oleksandr Liutyi/.
|
|
</p>
|
|
<p>
|
|
Special thanks goes to <name/Fra`2k/ for helping in testing :-)
|
|
</p>
|
|
</div1>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<div1>
|
|
<head>
|
|
License Agreement and Copyright Notices
|
|
</head>
|
|
<p>
|
|
<name/GoldED+/ - Copyright © 1990-1999 by <name/Odinn Sorensen/,
|
|
copyright © 1999-2002 by <name/Alexander S. Aganichev/,
|
|
<name/Jacobo Tarrio/ and others.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ and the <name/Goldware Utilities/ are covered by the
|
|
<name/GNU General Public License</name> (<name/GPL/), version 2.
|
|
For details see the file <code/COPYING/.
|
|
</p>
|
|
<p>
|
|
The <name/Goldware Library/ is licensed under the <name>GNU Library
|
|
General Public License</name> (<name/LGPL/), version 2. For the full
|
|
text of the license, see the file <code/COPYING.LIB/. If necessary to
|
|
comply with <name/GPL/, <name/the Goldware Library/ is also licensed
|
|
under <name/GPL/, version 2.
|
|
</p>
|
|
<p>
|
|
Additionally, permission is hereby specifically given to link
|
|
<name/GoldED+/, the <name/Goldware Utilities/ and the <name>Goldware
|
|
Library</name> with any software or software library that meets the
|
|
<name/Open Source Definition/, as given on
|
|
<xref type='URL'>http://www.opensource.org</xref>. This includes
|
|
<name/GPL/, <name/LGPL/, <name/BSD/, <name/X Consortium/,
|
|
<name/Artistic/, <name/MozPL/, <name/QPL/ and most derivatives of
|
|
<name/MozPL/.
|
|
</p>
|
|
<p>
|
|
The additional permission to link with <name>non-GPL/LGPL</name> software
|
|
may be slightly controversial. The intent is to allow developers a
|
|
greater freedom to create specialized versions of GoldED. Examples could
|
|
be a <abbr/GUI/ <name/KGoldED/ linked with <name/QT/, a <name/MozGoldED/
|
|
mail/news component for <name/Mozilla/ using <name/NGLayout/ for
|
|
displaying <abbr/HTML/, a <name/GoldED+/ with an embedded <name/Perl/
|
|
scripting engine or whatever. However, we cannot allow the core
|
|
<name/GoldED+/ or <name/Goldware Library/ to be dependent on these
|
|
specialized versions, so developers should take care to make their
|
|
specialized modifications modular and <q/stubifiable/ if necessary.
|
|
</p>
|
|
<p>
|
|
Parts of the <name/Goldware Library/ is derived from the source of the
|
|
old shareware <name/CXL/ 5.2 library by <name/Mike Smedley/, from which
|
|
<name/Odinn Sorensen/ bought a source license many years ago.
|
|
<name/Odinn/ has made very extensive modifications (for example, the
|
|
original was <name/DOS/ only), but much code is essentially unchanged
|
|
(<code/gwin*.cpp/). <name/CXL/ was taken over from <name/Mike Smedley/
|
|
by <name/Innovative Data Concepts/ (<name/IDC/), which renamed it
|
|
<name/TCXL/ and continued development along somewhat different lines,
|
|
which <name/Odinn/ did not agree with (or at least not easily port
|
|
<name/GoldED/ to). However, it seems that <name/TCXL/ never really became
|
|
successful. At least <name/Odinn/ could not find anything new about
|
|
<name/TCXL/ and <name/Innovative Data Concepts/ on the <name/Internet/
|
|
(as of november 15, 1998). <name/Odinn/ could not even find
|
|
<name/IDC/'s website, so in this day and age where any succesful business
|
|
has a website, <name/Odinn/ suspects that they no longer exist.
|
|
<name/Odinn/ even tried to find <name/Mike Smedley/, but apparently he
|
|
has vanished off the face of the earth, or has lost interest in
|
|
programming entirely. <name/Odinn/ found some postings (on
|
|
<name/DejaNews/) on a sports newsgroup by a <name/Mike Smedley/, but
|
|
he doubts that it's the same guy.
|
|
</p>
|
|
<p>
|
|
So, even though parts of the <name/Goldware Library/ technically are
|
|
still copyrighted by <name/Mike Smedley/, <name/Odinn/ see so serious
|
|
problems in using them. If anyone should happen to know <name>Mike
|
|
Smedley</name> and how to contact him, <name/Odinn Sorensen/ would very
|
|
much appreciate to get the information, so we can clear up this issue.
|
|
</p>
|
|
<p>
|
|
<name/Squish/ and <name/Maximus/ are trademarks of <name>Lanius
|
|
Corporation</name>.
|
|
</p>
|
|
<p>
|
|
<name/JAM(mbp)/ - Copyright © 1993 <name/Joaquim Homrighausen/,
|
|
<name/Andrew Milner/, <name/Mats Birch/, <name/Mats Wallin/.
|
|
</p>
|
|
<p>
|
|
Products and company names listed are trademarks or trade names of their
|
|
respective companies.
|
|
</p>
|
|
</div1>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<div1>
|
|
<head>
|
|
The Message Database Formats
|
|
</head>
|
|
<div2>
|
|
<head>
|
|
Opus, FTS-0001
|
|
</head>
|
|
<p>
|
|
These are two variants of the same type of msgbase. It works by using
|
|
one physical file per message (<code/1.msg/, <code/2.msg/ etc.),
|
|
collecting them in a directory for each area. Depending on the
|
|
clustersize on the harddisk, this can be a very wasteful and slow
|
|
way to store messages. With a clustersize of about 512 bytes, the
|
|
waste may be acceptable, but the access speed can be dramatically
|
|
slow if there are many <code/*.msg/ files, due to the file system.
|
|
Cache adjustments can improve it, but there are limits.
|
|
</p>
|
|
<p>
|
|
In echomail areas, this format has a special quirk: The first message
|
|
(<code/1.msg/) is normally used to store the so-called
|
|
<q/highwatermark/. The highwatermark tells the echomail processor
|
|
where it should start scanning for new messages entered by users.
|
|
By deleting (zapping) the highwatermark, you can make the echomail
|
|
processor re-scan the whole area again. This may cause messages to
|
|
be sent out as <q/dupes/, so this should be used sparingly and
|
|
carefully, if at all! The highwatermark can also be <q/heated/ -
|
|
which means that it is set to the last msg in the area. This
|
|
prevents the echomail processor from finding newly entered
|
|
unscanned msgs. Use with care.
|
|
</p>
|
|
<p>
|
|
The variants: The <name/Opus/ format originated in the <name/Opus/
|
|
<abbr/BBS/ system. It put some <name/Fido/ undocumented (?) fields to
|
|
use as date/time stamps. The <name/FTS-0001/ (defined in FTS-0001,
|
|
revision 12 and later) format uses the undocumented fields to set the
|
|
zone/point information for the message. To the authors knowledge, the
|
|
<name/Opus/ variant is the dominant, and the <name/FTS-0001/ variant
|
|
is doomed to oblivion. If in doubt, use the <name/Opus/ format.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QuickBBS, RemoteAccess, and Hudson
|
|
</head>
|
|
<p>
|
|
This msgbase format was invented by <name/Adam Hudson/, and was first
|
|
used in his <name/QuickBBS/ package. Later several other
|
|
<abbr/BBS/'es were cloned from <name/QuickBBS/ (like
|
|
<name/RemoteAccess/ and <name/SuperBBS/).
|
|
</p>
|
|
<p>
|
|
The format limits the total size of <code/msgtxt.bbs/ to a maximum of
|
|
16MB, which translates to about 16000 msgs of <q/average/ length.
|
|
<name/GoldED+/ automatically warns you if the limit is close to being
|
|
reached, and advises you to pack the messagebase.
|
|
</p>
|
|
<p>
|
|
The first incarnations of <name/QuickBBS/ did not support <q/sharing/
|
|
of the msgbase. This became more and more important in later years as
|
|
multitaskers and networks got cheaper. <name/RemoteAccess/ <abbr/BBS/
|
|
was the first to implement a useful method, and later a better method
|
|
was evolved (known as <name/RA/ 1.01 or <name/RA/ 1.1x), which is now
|
|
the standard for all modern software that supports msgbase sharing.
|
|
<name/GoldED+/ fully supports the new standard of course.
|
|
</p>
|
|
<p>
|
|
The main virtue of this format is that it is very fast to access the
|
|
msgbase.
|
|
</p>
|
|
<p>
|
|
The main disadvantage is that it can be very sensitive to disk
|
|
problems, and it is a common horror story that people loose their
|
|
entire msgbase because the disk developed bad clusters or some
|
|
program went berserk and messed up the msgbase files.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Goldbase
|
|
</head>
|
|
<p>
|
|
This is an enhanced version of the <name/Hudson/ format, introduced
|
|
in <name/QuickBBS/ 2.80 by the <name/QuickBBS/ group.
|
|
</p>
|
|
<p>
|
|
The <name/Goldbase/ format removes the 16MB size limit and allows up
|
|
to 500 message areas instead of the 200 in <name/Hudson/.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Squish
|
|
</head>
|
|
<p>
|
|
The <name/Squish/ format was invented by <name/Maximus/ <abbr/BBS/
|
|
author <name/Scott Dudley/ in 1991, and was first used in
|
|
<name/Maximus CBCS/ v2.00.
|
|
</p>
|
|
<p>
|
|
The use of a database for each area - instead of one file per msg,
|
|
or all msgs in one big database - makes this format fast, very
|
|
safe and resistant to disk problems. Even if something messed up a
|
|
<name/Squish/ area, it can almost always be fixed and recovered,
|
|
using the <name/SQFIX/ or <name/SQREIDX/ utilities that come with the
|
|
<name/Squish/ echomail processor.
|
|
</p>
|
|
<p>
|
|
A special feature of <name/Squish/ areas is that they can be
|
|
self-maintaining. You can setup a <name/Squish/ area so that it may
|
|
only contain a maximum of so-and-so many msgs, and then it will
|
|
automatically re-use the space used by old msgs when the limit is
|
|
reached, and so it will practically stop growing. It will still need
|
|
packing, but not nearly as often as a <name/Hudson/ msgbase has to.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Ezycom
|
|
</head>
|
|
<p>
|
|
<name/Ezycom/ format is supported by <name/GoldED+/. Status is not
|
|
known.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
JAM
|
|
</head>
|
|
<p>
|
|
<name/JAM/ format as defined in the <name/JAM(mbp)/ revision 001.
|
|
Also <name/CrashMail/, <name/CrashEcho/, and <name/SMAPI/ (<name/HPT/)
|
|
highwater marks are supported.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ currently ignores revision number of header structure
|
|
and assumes that future revisions will remain backward compatible.
|
|
When creating new msgs, <name/GoldED+/ uses the revision 1 header
|
|
structure.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ currently doesn't support passwords to access the
|
|
message base and/or indiviual messages. When creating a new
|
|
<name/JAM/ msgbase and/or new <name/JAM/ msgs, <name/GoldED+/ sets
|
|
the password to FFFFFFFFh. If you change an existing message which
|
|
has a password, the password is <hi/NOT/ preserved, but reset to
|
|
FFFFFFFFh.
|
|
</p>
|
|
<p>
|
|
The <name/JAM/ lastread file is designed such that is has to be
|
|
searched for a user ID/CRC, because one cannot assume that the
|
|
records are in a specific order. The <name/JAM/ <abbr/API/ searches
|
|
the userid field. However <name/GoldED+/ searches for the user CRC,
|
|
not the user ID. In any case, it seems that <name/RemoteAccess/ 2.x
|
|
sets both the user ID and CRC to the same value.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ currently doesn't support the escaping described in
|
|
the <name/JAM/ specs. The specs state that the current revision of
|
|
<name/JAM/ does not support it either, so it seems to be not great
|
|
loss.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ does not supports the following <name/JAM/ subfields:
|
|
<q/Force pickup/, and <q>Msg may not be displayed to user</q> (always
|
|
displayed).
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ optionally may use tricky method invented by
|
|
<name/Odinn/ and aprooved by the <name/JAM/ developers when deleting
|
|
messages. The configuration keyword
|
|
<ref target=JAMHARDDELETE><kw/JAMHARDDELETE/</ref> specifies which
|
|
method to use.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PCBoard
|
|
</head>
|
|
<p>
|
|
The supported <name/PCBoard/ messagebase corresponds to the v15.x of
|
|
<name/PCBoard/ <abbr/BBS/.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ is aware of <name/PCBoard/ v15.x extended headers in
|
|
the message text. The <gi/TO/, <gi/TO2/, <gi/FROM/, <gi/FROM2/ and
|
|
<gi/SUBJECT/ extended headers are directly supported and
|
|
<q/swallowed/ when reading a message. Other extended headers are
|
|
currently treated like normal message text and is therefore not
|
|
hidden to the reader.
|
|
</p>
|
|
<p>
|
|
Passwords are not supported.
|
|
</p>
|
|
<p>
|
|
The <gi/Private/, <gi/Received/, <gi/Crash/, and <gi/Direct/ attributes
|
|
are supported.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ reads the <code/pcboard.dat/ file to determine whether
|
|
to use E3h or 0Dh (<gi/CR/) as the line/paragraph termination
|
|
character when reading and writing message text.
|
|
</p>
|
|
<p>
|
|
The mail waiting flags are updated when you write to people that are
|
|
named in the userbase.
|
|
</p>
|
|
<p>
|
|
When changing a message, the new edition is saved as if it were a new
|
|
message, with a new message number, and then the old edition is
|
|
deleted. This behaviour is consistent with the way <name/PCBoard/
|
|
itself works when changing a message. The old edition will still
|
|
exist with the <gi/DEL/ attribute.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
AdeptXBBS
|
|
</head>
|
|
<p>
|
|
The implementation is based on the documentation in version 1.05,
|
|
experimentation and questions to the authors. Thanks go to
|
|
<name/Frank Jacobberger/ for the initial testing and prodding of the
|
|
authors to answer <name/Odinns/ questions.
|
|
</p>
|
|
<p>
|
|
The <name/AdeptXBBS/ format does not have a quick method of finding
|
|
deleted messages via the index file. This means that deleted messages
|
|
left in the messagebase marked with the <gi/DEL/ attribute.
|
|
</p>
|
|
<p>
|
|
Mixing of netmail and echomail or other types of mail in the same
|
|
area is not directly supported. If an area is setup as both netmail
|
|
and echomail, <name/GoldED+/ will treat it as netmail. If an area is
|
|
neither netmail nor echomail, <name/GoldED+/ wil treat it as a local
|
|
area.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ detects <name/Usenet/ (newsgroup) and <name/Internet/
|
|
e-mail areas in the <name/AdeptXBBS/ setup and uses them as such, but
|
|
it has not yet been tested if <name/GoldED+/ and <name/AdeptXBBS/ are
|
|
compatible in the way they store and process <name/Internet/ header
|
|
information.
|
|
</p>
|
|
<p>
|
|
The <name/AdeptXBBS/ personal mail feature (the index in the
|
|
<code/Personal_Mail/ directory) is supported for mails you write to
|
|
other users on the <abbr/BBS/. However, personal mail for you via
|
|
this feature or by other means is not yet supported.
|
|
</p>
|
|
<p>
|
|
The replylinking method used by <name/AdeptXBBS/ (whatever the method
|
|
is??!) is not yet supported. This means that links to other messages
|
|
are missing.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
WildCat!
|
|
</head>
|
|
<p>
|
|
The <name/WildCat!/ 4.x format does not have a quick method of
|
|
finding deleted messages via the index file. This means that deleted
|
|
messages left in the messagebase marked with the <gi/DEL/
|
|
attribute.
|
|
</p>
|
|
<p>
|
|
WildCat features which are not supported yet:
|
|
<list type=simple>
|
|
<item/The userbase./
|
|
<item/The message unread chain./
|
|
<item>The message from/to title.</item>
|
|
<item/The message network name./
|
|
<item/The message internal and external attach./
|
|
</list>
|
|
</p>
|
|
<p>
|
|
There is a keyword
|
|
<ref target=WILDCATUSERNO><kw/WILDCATUSERNO/</ref>, which works just
|
|
like the other <kw><msgbase>USERNO</kw> keywords. By default
|
|
<name/GoldED+/ will use the first record in the lastread file
|
|
(<code/*.lrd/), so if you are not the first person in the userbase,
|
|
or you are sharing the messagebase with others, you may have to
|
|
change this user number. The userbase is currently not supported
|
|
(i.e.: you can't set the number to -1 to let <name/GoldED+/ find the
|
|
correct user and lastread automatically).
|
|
</p>
|
|
<p>
|
|
<hi/Note/: The <name/WildCat!/ support is currently not very
|
|
well-tested, so use it with caution. Limited testing shown that
|
|
<name/GoldED+/ not damages the messagebases, but you should probably
|
|
test it on less important areas and/or make backups until it is
|
|
determined that it is safe.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Synchronet
|
|
</head>
|
|
<p>
|
|
<name/Synchronet/ message base as described in <name>Synchronet
|
|
Message Base Specification</name> version 1.21. <name/GoldED+/
|
|
currently linked with <name/SMBLib/ taken from the <name/Synchronet/
|
|
<abbr/BBS/ sources slightly adopted to the <name/GoldED+/ internal
|
|
definitions.
|
|
</p>
|
|
<p>
|
|
Just like <name/WildCat!/ format, <name/Synchronet/ format does not
|
|
have a quick method of finding deleted messages via the index file.
|
|
This means that deleted messages left in the messagebase marked with
|
|
the <gi/DEL/ attribute.
|
|
</p>
|
|
<p>
|
|
<hi/Note/: The <name/Synchronet/ support is currently not tested at
|
|
all.
|
|
</p>
|
|
</div2>
|
|
</div1>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<div1>
|
|
<head>
|
|
Nodelist and Userlist Support
|
|
</head>
|
|
<p>
|
|
<name/GoldED+/ supports the <name/FrontDoor/, <name/Version 7(+)/
|
|
nodelist indexes as well as a plain <code/fidouser.lst/. However, if you
|
|
run software that doesn't use any of these formats, you may want to use
|
|
<name/GoldED+/'s own nodelist index.
|
|
</p>
|
|
<p>
|
|
In order to enable nodelist/userlist lookup and browsing, <name/GoldED+/
|
|
needs to use a set of special nodelist index files, created by the
|
|
<name/GoldNODE/ nodelist compiler.
|
|
</p>
|
|
<p>
|
|
<name/GoldED+/ normally uses and displays information from the nodelist
|
|
when browsing, but it doesn't really need the nodelist for anything. The
|
|
index files contains sufficient information for lookup and browsing of
|
|
names or addresses. This means that you can delete or pack away the
|
|
nodelists and/or userlists after compiling with <name/GoldNODE/, if you
|
|
want to save space and you don't need them for anything else.
|
|
</p>
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Routing Diagram Drawing Tool
|
|
</head>
|
|
<p>
|
|
Routing diagram drawing tool intended to analyse files created by
|
|
pressing key defined for <!-- FIX ME!!! --> <kw>READmakepathreport</kw>
|
|
action. <name/RDDT/ builds routing tree and display it on the screen if
|
|
requested.
|
|
</p>
|
|
</div1>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<div1 id=COMMANDLINE>
|
|
<head>
|
|
Commandline Reference
|
|
</head>
|
|
<div2>
|
|
<head>
|
|
Mail Reader Commandline Syntax
|
|
</head>
|
|
<p>
|
|
Invocation:<eg>
|
|
golded [options] [keystacking]</eg>
|
|
</p>
|
|
<p>
|
|
Depending on used platform <name>GoldED+</name> could be called
|
|
<code>geddjg</code>, <code>gedcyg</code>, <code>gedemx</code>, or
|
|
<code>gedlnx</code>. Available options are (all options are case
|
|
insensitive):
|
|
<list type=gloss>
|
|
<label>
|
|
<code>-?</code>
|
|
</label>
|
|
<item>
|
|
Displays a help screen with all available commandline options.
|
|
</item>
|
|
<label>
|
|
<code>-c<configname></code>
|
|
</label>
|
|
<item>
|
|
Specifies another configuration file than the default. See also
|
|
<ref target=GOLDED><kw/GOLDED/</ref> environment variable.
|
|
</item>
|
|
<label>
|
|
<code>-d</code>
|
|
</label>
|
|
<item>
|
|
Disable old configuration keywords. For backward compatibility,
|
|
<name>GoldED+</name> still supports a number of old names for
|
|
some configuration keywords. It is recommended that you use
|
|
<code>-d</code> sometimes and rename the keywords that are
|
|
reported as unknown.
|
|
</item>
|
|
<label>
|
|
<code>-e<echoid></code>
|
|
</label>
|
|
<item>
|
|
If specified, <name>GoldED+</name> starts directly in the
|
|
specified echo, bypassing the arealist screen. See the
|
|
<ref target=AREASTART><kw>AREASTART</kw></ref> configuration
|
|
keyword for more info.
|
|
</item>
|
|
<label>
|
|
<code>-exportsoup</code>
|
|
</label>
|
|
<item>
|
|
Calls the <name>SOUP</name> packet export feature during the
|
|
startup phase. This is the same as starting it from the
|
|
areascan <code>SOUP Packet->Export</code> menu
|
|
item. The <name>SOUP</name> export happens immediately after the
|
|
regular startup area scanning (if that is enabled) and after
|
|
<name>SOUP</name> import.
|
|
</item>
|
|
<label>
|
|
<code>-f</code>
|
|
</label>
|
|
<item>
|
|
Force recompile of most configuration files, but not all. Does not
|
|
recompile the <code>*.chs</code> files.
|
|
</item>
|
|
<label>
|
|
<code>-ff</code>
|
|
</label>
|
|
<item>
|
|
Force complete recompile of all configuration files, regardless of
|
|
whether they are up-to-date or not. This is equivalent to deleting
|
|
all the <code>*.ge?</code> files.
|
|
</item>
|
|
<label>
|
|
<code>-h</code>
|
|
</label>
|
|
<item>
|
|
Same as option <code>-?</code>.
|
|
</item>
|
|
<label>
|
|
<code>-install[=path]</code>
|
|
</label>
|
|
<item>
|
|
Start the quick install procedure. You should give a path to your
|
|
other mail software if it cannot be found using environment
|
|
variables or in current directory.
|
|
</item>
|
|
<label>
|
|
<code>-importsoup</code>
|
|
</label>
|
|
<item>
|
|
Calls the <name>SOUP</name> packet import feature during the
|
|
startup phase. This is the same as starting it from the areascan
|
|
<code>SOUP Packet->Import</code> menu item. The
|
|
<name>SOUP</name> import happens immediately after the regular
|
|
startup area scanning (if that is enabled).
|
|
</item>
|
|
<label>
|
|
<code/-m/
|
|
</label>
|
|
<item>
|
|
Mute. Disables all sounds in <name/GoldED+/. The same functionality
|
|
provided by the <ref target=BEEPNOISES><kw/BEEPNOISES/</ref>
|
|
keyword in the configuration file.
|
|
</item>
|
|
<label>
|
|
<code>-n</code>
|
|
</label>
|
|
<item>
|
|
No share. If used, this prevents <name>GoldED+</name> from using
|
|
<code>SHARE</code> compatible file-open calls, which are used by
|
|
default. Works only until the
|
|
<ref target=SHAREMODE><kw>SHAREMODE</kw></ref> keyword is used in
|
|
the configuration file. This keyword is normally not useful, but
|
|
may be used to debug your setup or something.
|
|
</item>
|
|
<label>
|
|
<code>-noscan</code>
|
|
</label>
|
|
<item>
|
|
Disable the automatic startup area scanning (if that is enabled).
|
|
This is useful for automated <abbr>SOUP</abbr> import/export in a
|
|
batch file. For example,<eg>
|
|
golded -noscan -importsoup @x y</eg>
|
|
imports <name>SOUP</name> then exits.
|
|
</item>
|
|
<label>
|
|
<code>-p</code>
|
|
</label>
|
|
<item>
|
|
Since it seems that increasing the thread priority for the
|
|
<name/Win32/ version is a mixed blessing, the default is to
|
|
<hi/not/ increase the priority. From other side <name>OS/2</name>
|
|
version runned with reduced priority by default. This option
|
|
increases the priority (<name/Win32/ and <name>OS/2</name> only).
|
|
</item>
|
|
<label>
|
|
<code>-q</code>
|
|
</label>
|
|
<item>
|
|
Quiet. Turns off verbose config compile. On by default. This could
|
|
be used on the commandline to disable a <code>-v</code> option in
|
|
the <ref target=GEDCMD><kw/GEDCMD/</ref> environment variable.
|
|
</item>
|
|
<label>
|
|
<code>-s<sortspec></code>
|
|
</label>
|
|
<item>
|
|
Sort all areas according to <ident>sortspec</ident>. See
|
|
the <ref target=AREALISTSORT><kw/AREALISTSORT/</ref> config
|
|
keyword for details.
|
|
</item>
|
|
<label>
|
|
<code>-t<seconds></code>
|
|
</label>
|
|
<item>
|
|
Set the timeout value. A value of zero (0) means never timeout.
|
|
See the <ref target=TIMEOUT><kw/TIMEOUT/</ref> config keyword
|
|
for details.
|
|
</item>
|
|
<label>
|
|
<code>-v</code>
|
|
</label>
|
|
<item>
|
|
Turns on verbose config compile. When used, <name>GoldED+</name>
|
|
will display the full filename of each main config file it
|
|
compiles. It also displays the name of the detected multitasker, if
|
|
any. This can be useful for debugging your setup, and see if
|
|
<name>GoldED+</name> accesses the files (especially the
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>'s) it is supposed to.
|
|
</item>
|
|
<label>
|
|
<code>-vv</code>
|
|
</label>
|
|
<item>
|
|
Same as <code>-v</code>, but also displays all the active lines
|
|
while compiling. This could be used to find the exact spot if it
|
|
crashes or stops while compiling.
|
|
</item>
|
|
<label>
|
|
<code>-w</code>
|
|
</label>
|
|
<item>
|
|
If used, <name/GoldED+/ will create (and overwrite if existing) the
|
|
file <code/goldarea.inc/, which will then contain all areas in the
|
|
<ref target=AREADEF><kw/AREADEF/</ref> form, sorted by your
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref> specification.
|
|
This is very useful for converting your
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>'s to a form you can edit
|
|
with your favorite text editor and use in <name/GoldED+/. It is
|
|
also useful if you have used the new
|
|
<ref target=AREADESC><kw/AREADESC/</ref> keyword or the
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>
|
|
<ref target=ECHOLIST><gi/EchoList/</ref> reader. The
|
|
<code>goldarea.inc</code> file (created in the
|
|
<ref target=GOLDPATH><kw/GOLDPATH/</ref>) can be used by adding<eg>
|
|
INCLUDE goldarea.inc</eg>
|
|
to your configuration files. When creating the file, <name/GoldED+/
|
|
will use <q/./ if an aka is the same as the main aka, and leave out
|
|
the optional origin if it's the same as the first
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref> in your configuration files.
|
|
This makes it easier to share the same <code/goldarea.inc/ between
|
|
different setups.
|
|
</item>
|
|
<label>
|
|
<code>-x</code>
|
|
</label>
|
|
<item>
|
|
Reserved for debugging purposes.
|
|
</item>
|
|
<label>
|
|
<code>-y</code>
|
|
</label>
|
|
<item>
|
|
Reserved for debugging purposes.
|
|
</item>
|
|
<label>
|
|
<code>-z</code>
|
|
</label>
|
|
<item>
|
|
Reserved for debugging purposes.
|
|
</item>
|
|
</list>
|
|
</p>
|
|
<p>
|
|
Any non-option characters on the commandline are stuffed into the
|
|
keyboard buffer. See the chapter on keyboard definition and the
|
|
<ref target=KEYBSTACK><kw>KEYBSTACK</kw></ref> keyword for more info.
|
|
</p>
|
|
<p>
|
|
For example,<eg>
|
|
golded @S A</eg>
|
|
makes <name>GoldED+</name> go to the area scanning menu <Alt-S>,
|
|
and select scanning of <A> all areas.
|
|
</p>
|
|
<p>
|
|
See the <ptr target=MACROSANDKEYSTACKING> chapter for more info. Note,
|
|
that only those combinations described in the
|
|
<ref target=KEYBSTACK><kw>KEYBSTACK</kw></ref> chapter are allowed
|
|
here.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
<name/GoldED+/ Batchfile Errorlevels
|
|
</head>
|
|
<p>
|
|
For operation in batch files, <name>GoldED+</name> has a set of
|
|
errorlevel values:
|
|
<table rows=5 cols=2>
|
|
<row>
|
|
<cell>
|
|
032 or higher
|
|
</cell>
|
|
<cell>
|
|
Error exit (check the logfile for details).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
004
|
|
</cell>
|
|
<cell>
|
|
Echomail entered.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
002
|
|
</cell>
|
|
<cell>
|
|
Netmail entered.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
001
|
|
</cell>
|
|
<cell>
|
|
Local mail entered.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
000
|
|
</cell>
|
|
<cell>
|
|
No errors. No mail entered.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</p>
|
|
<p>
|
|
Add values together to find the combined error levels. For example, error
|
|
level 6 is returned if netmail and echomail (2+4) was entered.
|
|
</p>
|
|
<p>
|
|
Example of <code>rungold.bat</code> file:<eg>
|
|
golded.exe
|
|
if errorlevel 007 goto e_n_l
|
|
if errorlevel 006 goto e_n__
|
|
if errorlevel 005 goto e___l
|
|
if errorlevel 004 goto e____
|
|
if errorlevel 003 goto __n_l
|
|
if errorlevel 002 goto __n__
|
|
if errorlevel 001 goto ____l
|
|
if errorlevel 000 goto nomail
|
|
:error
|
|
echo GoldED+ error exit!
|
|
goto end
|
|
:e_n_l
|
|
echo **** New echo, net and local mail entered.
|
|
goto end
|
|
:e_n__
|
|
echo **** New echo and netmail entered.
|
|
goto end
|
|
:e___l
|
|
echo **** New echo and local mail entered.
|
|
goto end
|
|
:e____
|
|
echo **** New echomail entered.
|
|
goto end
|
|
:__n_l
|
|
echo **** New net and local mail entered.
|
|
goto end
|
|
:__n__
|
|
echo **** New netmail entered.
|
|
goto end
|
|
:____l
|
|
echo **** New local mail entered.
|
|
goto end
|
|
:nomail
|
|
echo **** No new mail entered.
|
|
:end
|
|
echo.
|
|
echo Thank you for using GoldED+! :-)</eg>
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Nodelist Compiler Commandline Syntax
|
|
</head>
|
|
<p>
|
|
Invocation:<eg>
|
|
goldnode [options] [configfile]</eg>
|
|
</p>
|
|
<p>
|
|
Depending on used platform <name>GoldNODE</name> could be called
|
|
<code>gndjg</code>, <code>gncyg</code>, <code>gnemx</code>, or
|
|
<code>gnlnx</code>. Available options:
|
|
<list type=gloss>
|
|
<label>
|
|
<code>-c</code>
|
|
</label>
|
|
<item>
|
|
Conditional compile.
|
|
</item>
|
|
<label>
|
|
<code>-d</code>
|
|
</label>
|
|
<item>
|
|
Remove duplicate nodes from index.
|
|
</item>
|
|
<label>
|
|
<code>-f</code>
|
|
</label>
|
|
<item>
|
|
Forced compile.
|
|
</item>
|
|
<label>
|
|
<code>-q</code>
|
|
</label>
|
|
<item>
|
|
Quite compiled. No screen output improves speed.
|
|
</item>
|
|
<label>
|
|
<code>-s<size></code>
|
|
</label>
|
|
<item>
|
|
Set the max size of names. Normally not used.
|
|
</item>
|
|
<label>
|
|
<code>-u<file></code>
|
|
</label>
|
|
<item>
|
|
Create sorted <code/fidouser.lst/ userlist file.
|
|
</item>
|
|
</list>
|
|
</p>
|
|
<p>
|
|
The <ident/configfile/ is the path and filename of the configuration
|
|
file to read. If no filename is given and it could not be found by
|
|
using environment variables then current path is used.
|
|
See also <ref target=GOLDNODE><kw/GOLDNODE/</ref> and
|
|
<ref target=GOLDED><kw/GOLDED/</ref> environment variables.
|
|
</p>
|
|
<p>
|
|
The nodelist index files are named <code/goldnode.gx?/ are are
|
|
placed in the path pointed to by the
|
|
<ref target=NODEPATH><kw/NODEPATH/</ref> keyword.
|
|
</p>
|
|
<p>
|
|
The <name>V7+</name> index is automatically used if your
|
|
<ref target=NODEPATHV7><kw/NODEPATHV7/</ref> is set correctly. If
|
|
<name/GoldED+/ shows<eg>
|
|
xxxx / nodex.dtp</eg>
|
|
at the bottom of the browser window, the displayed information is taken
|
|
from the raw nodelist entry, taken from the <name>V7+</name> index.
|
|
</p>
|
|
<p>
|
|
<name>GoldNODE</name> can read the german <name>POINTS24</name>-format
|
|
directly!
|
|
</p>
|
|
<p>
|
|
<hi/NOTE/: If you use the
|
|
<ref target=EXCLUDENODES><kw/EXCLUDENODES/</ref> and
|
|
<ref target=INCLUDENODES><kw/INCLUDENODES/</ref> keywords, please note
|
|
that the <ident>addressmask<ident> does <hi>not</hi> accept <q/ALL/
|
|
or <q/WORLD/, etc. You must use wildcard <q/*/ instead.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Routing Diagram Drawing Tool Commandline Syntax
|
|
</head>
|
|
<p>
|
|
Invocation:<eg>
|
|
rddt <routefile> [options] [address or name]</eg>
|
|
</p>
|
|
<p>
|
|
Depending on used platform <name>RDDT</name> could be called
|
|
<code>rddtdjg</code>, <code>rddtcyg</code>, <code>rddtemx</code>, or
|
|
<code>rddtlnx</code>. Available options:
|
|
<list type=gloss>
|
|
<label>
|
|
<code>-d</code>
|
|
</label>
|
|
<item>
|
|
Reserved for debugging purposes.
|
|
</item>
|
|
<label>
|
|
<code>-i<n></code>
|
|
</label>
|
|
<item>
|
|
Sets indent to <ident>n</ident>.
|
|
</item>
|
|
<label>
|
|
<code>-l<link address></code>
|
|
</label>
|
|
<item>
|
|
This option used to specify yours link address. Requires option
|
|
<code>-n</code>.
|
|
</item>
|
|
<label>
|
|
<code>-n<address></code>
|
|
</label>
|
|
<item>
|
|
Use this option to specify your address.
|
|
</item>
|
|
<label>
|
|
<code>-p</code>
|
|
</label>
|
|
<item>
|
|
Decode path.
|
|
</item>
|
|
</list>
|
|
</p>
|
|
<p>
|
|
Example:<eg>
|
|
RDDT path.rpt -n2:5020/604.19 -l2:5020/604 2:5020/604.19 -p</eg>
|
|
</p>
|
|
</div2>
|
|
</div1>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<div1>
|
|
<head>
|
|
Environment Variables
|
|
</head>
|
|
<p>
|
|
These are the <name>GoldED+</name> specific environment variables:
|
|
<list type=gloss>
|
|
<label id=GOLDED>
|
|
<kw/GOLDED/, <kw/GED/
|
|
</label>
|
|
<item>
|
|
Path to the <code/golded.cfg/ configuration file. Note, that
|
|
<name/Win32/ version tries to open <code/gedw32.cfg/ first, and
|
|
<name>OS/2</name> version tries to open <code/ged2.cfg/ first.
|
|
You may specify path <hi/and/ filename of configuration file here.
|
|
It is recommended to set this variable, but don't forget to change it
|
|
if you move your <name>GoldED+</name> setup to a different directory!
|
|
</item>
|
|
<label>
|
|
<kw/GED2/
|
|
</label>
|
|
<item>
|
|
Same as above, but for <name>OS/2</name> version only.
|
|
</item>
|
|
<label>
|
|
<kw/GEDW32/
|
|
</label>
|
|
<item>
|
|
Same as above, but for <name/Win32/ version only.
|
|
</item>
|
|
<label id=GEDCMD>
|
|
<kw/GEDCMD/
|
|
</label>
|
|
<item>
|
|
Specifies additional commandline options. Use this if you want to
|
|
specify options, but need to run <name>GoldED</name> without them
|
|
(for example when renaming <code>GOLDED.EXE</code> to
|
|
<code>DBEDIT.EXE</code> in older versions of <name>D'Bridge</name>).
|
|
You can override the environment options with commandline options.
|
|
</item>
|
|
<label id=GOLDNODE>
|
|
<kw/GOLDNODE/
|
|
</label>
|
|
<item>
|
|
The path where <name/GoldNODE/ can find a configuration file to use.
|
|
See also <ref target=GOLDED><kw/GOLDED/</ref> environment variable.
|
|
</item>
|
|
<label>
|
|
<kw/MAXIMUS/, <kw/SQUISH/
|
|
</label>
|
|
<item>
|
|
If <ref target=SQUISHUSERPATH><kw/SQUISHUSERPATH/</ref> is not
|
|
defined in the configuration file then value of these variables are
|
|
used.
|
|
</item>
|
|
<label>
|
|
<kw/FD/
|
|
</label>
|
|
<item>
|
|
Path where <code/names.fd/ could be found if not explicitly defined
|
|
by the <ref target=NAMESFILE><kw/NAMESFILE/</ref> keyword.
|
|
</item>
|
|
<label>
|
|
<kw/ESCDELAY/
|
|
</label>
|
|
<item>
|
|
This variable is only used by <name/Linux/ and <name/FreeBSD/
|
|
versions compiled with <name/ncurses/ support. See <name/ncurses/
|
|
reference for details. If not devined then default value <q/50/ is
|
|
used.
|
|
</item>
|
|
</list>
|
|
</p>
|
|
<p>
|
|
When using the <ref target=AREAFILE><kw/AREAFILE/</ref> feature to read
|
|
external area configuration from the other programs, the individual
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>'s may use specific environment
|
|
variables to find the files. Please read the
|
|
<ptr target=AREACONFIGURATION> chapter for specific details of each
|
|
supported <ref target=AREAFILE><kw/AREAFILE/</ref>.
|
|
</p>
|
|
</div1>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
<div1>
|
|
<head>
|
|
Configuration Keyword Reference
|
|
</head>
|
|
<p>
|
|
The following special symbols are used in the keyword parameter lists:
|
|
<table rows=6 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident>[]</ident>
|
|
</cell>
|
|
<cell>
|
|
Optional parameter.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident><></ident>
|
|
</cell>
|
|
<cell>
|
|
Required parameter, not optional.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<q></q>
|
|
</cell>
|
|
<cell>
|
|
Parameter must be inclosed in quotes.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>/</ident>
|
|
</cell>
|
|
<cell>
|
|
Separates mutually exclusive values.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>,</ident>
|
|
</cell>
|
|
<cell>
|
|
Separates possible values for the keyword.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</p>
|
|
<p>
|
|
There's no mandatory keywords but the mail reader should have defined at
|
|
least name, address and area; nodelist compiler should have address and
|
|
either nodelist or userlist defined.
|
|
</p>
|
|
<p>
|
|
Whenever path is expected you may use environment variables enclosed in
|
|
percent signs, f.e. <code>%FIDO%/myfile.txt</code>. This also valid for
|
|
input prompts where path is expected :-)
|
|
</p>
|
|
<div2 id=REM>
|
|
<head>
|
|
Remarks
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/REM/ <ident/[text]/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Signifies a remark (comment) line.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/text/ contains remark line. The line is ignored.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Any non-alphabetic non-whitespace character at the beginning of a
|
|
line makes the line a comment. By tradition, the semicolon is the
|
|
standard comment character. The semicolon (and only that) can also
|
|
be used to add a comment at the end of a configuration line.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader and nodelist compiler.
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
REM This is a comment
|
|
; This is a comment
|
|
% This is a comment
|
|
* This is a comment
|
|
// This is a comment
|
|
/* This is a comment */
|
|
ADDRESS 2:236/77 ; Main address.
|
|
AKA 2:236/77.1 ; SysOp point.</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CONDITIONALS>
|
|
<head>
|
|
Conditionals
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/IF/ <ident/<condition>/<lb>
|
|
<kw/ELIF/ <ident/<condition>/<lb>
|
|
<kw/ELSEIF/ <ident/<condition>/<lb>
|
|
<kw/ELSE/<lb>
|
|
<kw/ENDIF/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
These control keywords can be used to setup sections of configuration
|
|
which enable different sets of keywords depending on which version
|
|
that is used.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The following conditions can be used:
|
|
<table rows=8 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/DOS/, <ident/386/, <ident/DPMI32/
|
|
</cell>
|
|
<cell>
|
|
true, if <name>DPMI32</name> version is used
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>OS/2</ident>, <ident/OS2/
|
|
</cell>
|
|
<cell>
|
|
true, if <name>OS/2</name> version is used
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/WIN32/, <ident/W32/, <ident/NT/
|
|
</cell>
|
|
<cell>
|
|
true, if <name>Win32</name> version is used
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>Linux, UNIX</ident>
|
|
</cell>
|
|
<cell>
|
|
true, if <name/Linux/ or <name/FreeBSD/ version is used
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>Firebird</ident>
|
|
</cell>
|
|
<cell>
|
|
true, if <name/GoldED/ 3.xx or <name/GoldED+/ is used
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>ASA</ident>
|
|
</cell>
|
|
<cell>
|
|
true, if <name/GoldED-asa/ or <name/GoldED+/ is used
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>Yes</ident>, <ident>True</ident>, <ident>On</ident>
|
|
</cell>
|
|
<cell>
|
|
always true
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader and nodelist compiler.
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
IF OS2
|
|
EDITOR c:\qedit\os2\q.exe @file -n@line
|
|
EDITSPELLCHECK c:\os2\cmd.exe /c c:\ss\ss.exe @file
|
|
ELIF DOS
|
|
EDITOR c:\qedit\dos\q.exe @file -n@line
|
|
EDITSPELLCHECK c:\ss\ss.exe @file
|
|
ELIF WIN32
|
|
EDITOR c:\progra~1\far\far.exe -i -e@line @file
|
|
EDITSPELLCHECK c:\fido\goldkorr\goldkorr.exe @file /A /Q
|
|
ENDIF</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=IGNORE>
|
|
<head>
|
|
IGNORE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/IGNORE/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This tells the configuration file reader to ignore all subsequent
|
|
lines until another <kw/IGNORE/ or <kw/IF/ keyword is encountered.
|
|
Useful for testing and quickly switching portions of configuration.
|
|
However it is probably more useful to use the
|
|
<ref target=CONDITIONALS/conditionals/ control keywords.
|
|
</item>
|
|
<label>
|
|
Bugs:
|
|
</label>
|
|
<item>
|
|
This keyword may cause unpredicable results if used within
|
|
<ref target=CONDITIONALS/conditionals/ control keywords.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=CONDITIONALS/Conditionals/
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ADDRESS>
|
|
<head>
|
|
ADDRESS
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ADDRESS/
|
|
<ident><zone:net/node[.point][@domain]
|
|
[,pointnet]></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Your network address, <name/FidoNet/-style. More than one address can
|
|
be specified if you are member of more than one network. The keywords
|
|
<kw/ADDRESS/ and <ref target=AKA><kw/AKA/</ref> can be used
|
|
interchangeably.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If a <ident/pointnet/ is specified with a point address,
|
|
<name/GoldED+/ will use the so-called <term/3D/ addressing method in
|
|
netmail msgs, otherwise the <term/4D/ method is used. The <term/3D/
|
|
method works by putting the address
|
|
<ident>zone:pointnet/point.0</ident> in the msg header, instead of
|
|
the <term/4D/ format <ident>zone:net/node.point</ident>. Most modern
|
|
mailers and mail processors now supports the <term/4D/ format,
|
|
but if you are a point, you should always consult your boss about
|
|
which format to use.<lb>
|
|
The optional <ident/@domain/ part can be used to specify a
|
|
<term/fifth/ dimension to the <term/4D/ address. It is normally not
|
|
necessary to specify a domain. Domains are never shown in the header.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader and nodelist compiler.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AKA><kw/AKA/</ref>,
|
|
<ref target=NETNAME><kw/NETNAME/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
ADDRESS 2:236/77 ; Node address
|
|
ADDRESS 2:236/77.1 ; Point address (4D)
|
|
ADDRESS 2:236/77.1, 16077 ; Point address (3D)
|
|
ADDRESS 2:236/77@fidonet ; Node address with domain</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ADDRESSBOOKADD
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ADDRESSBOOKADD/ <ident><YES/NO/ALWAYS></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ will add unknown
|
|
addressees into the addressbook when writing new or quoted mails.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Setting this keyword to <ident/ALWAYS/ means that <name/GoldED+/ will
|
|
always add unknown addressees to the addressbook when writing new or
|
|
quoted mails automatically. If you set the value to <ident/YES/,
|
|
<name/GoldED+/ will add them only if it's a netmail/email. Setting to
|
|
<ident/NO/ disables this feature entirely.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
<name/GoldED+/ won't add unknown users if their name match one of the
|
|
following criterias:
|
|
<list type=simple>
|
|
<item>
|
|
It's a <ref target=ROBOTNAME><kw/ROBOTNAME/</ref>
|
|
</item>
|
|
<item>
|
|
It's a <ref target=USERNAME><kw/USERNAME/</ref>
|
|
</item>
|
|
<item>
|
|
It's the <ref target=WHOTO><kw/WHOTO/</ref>
|
|
</item>
|
|
<item>
|
|
It's the mailinglist's sender address
|
|
</item>
|
|
<item>
|
|
It's an UUCP
|
|
</item>
|
|
<item>
|
|
It's already an email address
|
|
</item>
|
|
<item>
|
|
Address/aka is unknown
|
|
</item>
|
|
<item>
|
|
It's an <ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>
|
|
</item>
|
|
</list>
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=INTERNETGATE><kw/INTERNETGATE/</ref>,
|
|
<ref target=MAILINGLIST><kw/MAILINGLIST/</ref>,
|
|
<ref target=ROBOTNAME><kw/ROBOTNAME/</ref>,
|
|
<ref target=USERNAME><kw/USERNAME/</ref>,
|
|
<ref target=WHOTO><kw/WHOTO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ADDRESSLOOKUPFIRST
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ADDRESSLOOKUPFIRST/ <ident><MSGID/ORIGIN></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines the first source to lookup address. If valid
|
|
address could not be found in the specifyed location then second
|
|
source is used.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If defined to <ident/ORIGIN/ then address of sender taken from
|
|
<gi/Origin/ line. If this keyword set to <ident/MSGID/ then
|
|
<name/GoldED+/ looks for correct <abbr/FTN/ address in <gi/MSGID/
|
|
kludge first.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/ORIGIN/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ADDRESSMACRO>
|
|
<head>
|
|
ADDRESSMACRO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ADDRESSMACRO/ <ident/<macro>, <name>, <address>
|
|
[,<q>subject</q>] [,attribs]/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines a short name for often used addresses. Typical uses are for
|
|
<name/AreaFix//<name/AreaMgr/, your uplink, boss, points or others
|
|
you write to often. To use a defined address macro, you just type it
|
|
in the <gi/To:/ name field.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If (and <hi>only</hi> if) the subject is enclosed in quotes (<q//
|
|
or ''), <name/GoldED+/ will look for message attributes after the
|
|
<ident/subject/ field. See the <ptr target=MESSAGEATTRS> for the
|
|
valid attributes. You cannot have quotes within quotes (not the same
|
|
type anyway). The attribues are <hi/added/ to the ones already there,
|
|
they do <hi/not/ replace them.<lb>
|
|
A special format is supported for <abbr/UUCP/ or <name/Internet/
|
|
gateways. The special format is indicated with a <q/@/ as the first
|
|
character in the <ident/name/ field. You may specify <name/Internet/
|
|
gate name here if it other then default specifyed with
|
|
<ref target=INTERNETGATE><kw/INTERNETGATE/</ref> keyword, just put
|
|
gate name right after the <q/@/ and terminate it with the slash
|
|
(<q>/</q>).
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
The address macros can also be specified in an external file, like
|
|
the <code/names.fd/ file supported by the <name/FrontDoor/
|
|
mailer/editor and <name/Maximus/ <abbr/BBS/. See the keyword
|
|
<ref target=NAMESFILE><kw/NAMESFILE/</ref> for details. However, you
|
|
should not use the syntax with the attributes in the <code/names.fd/
|
|
file, because <name/FrontDoor/ and <name/Maximus/ do not know this
|
|
syntax.<lb>
|
|
When used in the <name/Internet/ area, <q/@/ as the first character
|
|
in the <ident/name/ field may be omitted.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=INTERNETGATE><kw/INTERNETGATE/</ref>,
|
|
<ref target=NAMESFILE><kw/NAMESFILE/</ref>
|
|
</item>
|
|
<label>
|
|
Examples:
|
|
</label>
|
|
<item><eg><![ CDATA [
|
|
ADDRESSMACRO afup,AreaFix,2:236/512,"password -q -l",K/S
|
|
ADDRESSMACRO ffup,FileFix,2:236/512,password
|
|
ADDRESSMACRO odin,Odinn Sorensen,2:236/77,GoldED - What else? :-)
|
|
ADDRESSMACRO jfu,@fallesen@diku.dk,2:310/33
|
|
ADDRESSMACRO vp,@vasya@pupkin.ru (Vasya Pupkin),2:5020/128
|
|
ADDRESSMACRO dn,@INTERNET/david@csource.oz.au,2:241/999]]></eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ADEPTXBBSPATH>
|
|
<head>
|
|
ADEPTXBBSPATH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ADEPTXBBSPATH/ <ident/<path>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifyes the path where you keep your <name/AdeptXBBS/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/path/ where you keep your <name/AdeptXBBS/.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=AREACONFIGURATION> chapter,
|
|
<ref target=ADEPTXBBSUSERNO><kw/ADEPTXBBSUSERNO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ADEPTXBBSUSERNO>
|
|
<head>
|
|
ADEPTXBBSUSERNO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ADEPTXBBSUSERNO/ <ident/<userno>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifyes the record number in the userfile and lastreads.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If you are not the first user in the userfile, or are sharing the
|
|
messagebase with other <name/GoldED+/ users, you must either set this
|
|
keyword to -1, or use a different number for each user. Each user
|
|
must be defined in the userbase.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
By default <name/GoldED+/ will use the first record in the userfile
|
|
and lastreads.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=AREACONFIGURATION> chapter,
|
|
<ref target=ADEPTXBBSPATH><kw/ADEPTXBBSPATH/</ref>,
|
|
<ref target=EZYCOMUSERNO><kw/EZYCOMUSERNO/</ref>,
|
|
<ref target=FIDOUSERNO><kw/FIDOUSERNO/</ref>,
|
|
<ref target=GOLDBASEUSERNO><kw/GOLDBASEUSERNO/</ref>,
|
|
<ref target=HUDSONUSERNO><kw/HUDSONUSERNO/</ref>,
|
|
<ref target=PCBOARDUSERNO><kw/PCBOARDUSERNO/</ref>,
|
|
<ref target=SQUISHUSERNO><kw/SQUISHUSERNO/</ref>,
|
|
<ref target=WILDCATUSERNO><kw/WILDCATUSERNO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AKA>
|
|
<head>
|
|
AKA
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AKA/
|
|
<ident><zone:net/node[.point][@domain]
|
|
[,pointnet]></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Your network address, <name/FidoNet/-style. More than one address can
|
|
be specified if you are member of more than one network. The keywords
|
|
<ref target=ADDRESS><kw/ADDRESS/</ref> and <kw/AKA/ can be used
|
|
interchangeably.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If a <ident/pointnet/ is specified with a point address,
|
|
<name/GoldED+/ will use the so-called <term/3D/ addressing method in
|
|
netmail msgs, otherwise the <term/4D/ method is used. The <term/3D/
|
|
method works by putting the address
|
|
<ident>zone:pointnet/point.0</ident> in the msg header, instead of
|
|
the <term/4D/ format <ident>zone:net/node.point</ident>. Most modern
|
|
mailers and mail processors now supports the <term/4D/ format,
|
|
but if you are a point, you should always consult your boss about
|
|
which format to use.<lb>
|
|
The optional <ident/@domain/ part can be used to specify a
|
|
<term/fifth/ dimension to the <term/4D/ address. It is normally not
|
|
necessary to specify a domain. Domains are never shown in the header.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader and nodelist compiler.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ADDRESS><kw/ADDRESS/</ref>,
|
|
<ref target=NETNAME><kw/NETNAME/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AKAMATCH>
|
|
<head>
|
|
AKAMATCH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AKAMATCH/ <ident/<pattern> <aka>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This is an enhancement of the existing aka matching logic, which in
|
|
some circumstances fails to find the correct aka.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If the destination address matches <ident/pattern/ then
|
|
<name/GoldED+/ will use <ident/aka/ specifyed instead of default
|
|
best-match rule. All patterns are checked in the order they follow
|
|
in the configuration files.<lb>
|
|
Wildcards are not strictly necessary in the match <ident/pattern/,
|
|
you could write f.e. <q>zone:*/*.*</q> or <q>zone:</q>, etc.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
When an address does not match any <kw>AKAMATCH</kw> definition, the
|
|
normal aka matching logic takes over.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>,
|
|
<ref target=AKAMATCHING><kw/AKAMATCHING/</ref>,
|
|
<ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>,
|
|
<ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
ADDRESS 2:236/77 ; this is primary address
|
|
AKA 22:33/44 ; this address valid for zones 21:, 22:, and 23
|
|
AKAMATCH 21:*/*.* 22:33/44
|
|
AKAMATCH 23: 22:33/44</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AKAMATCHECHO>
|
|
<head>
|
|
AKAMATCHECHO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AKAMATCHECHO/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ should do akamatching
|
|
in echomail areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, <name/GoldED+/ will attempt to match one of
|
|
your akas to the address of the person you are replying to in
|
|
echomail areas.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Normally it is not desirable to enable aka matching in echomail,
|
|
because some echoes may be restricted to members of one particular
|
|
network, and an accidental wrong aka matching may attract unwanted
|
|
attention from the moderator or the compulsive flamers :-)
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AKAMATCH><kw/AKAMATCH/</ref>,
|
|
<ref target=AKAMATCHING><kw/AKAMATCHING/</ref>,
|
|
<ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>,
|
|
<ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AKAMATCHING>
|
|
<head>
|
|
AKAMATCHING
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AKAMATCHING/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ should do akamatching
|
|
in areas within <ref target=RANDOMSYSTEM>Random System</ref> group it
|
|
is defined. When used, it overrides any global
|
|
<ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>,
|
|
<ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>, or
|
|
<ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref> you may have.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, <name/GoldED+/ will attempt to match one of
|
|
your akas to the address of the person you are replying to.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword is valid <hi/ONLY/ in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AKAMATCH><kw/AKAMATCH/</ref>,
|
|
<ref target=AKAMATCHING><kw/AKAMATCHING/</ref>,
|
|
<ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>,
|
|
<ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AKAMATCHLOCAL>
|
|
<head>
|
|
AKAMATCHLOCAL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AKAMATCHLOCAL/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ should do akamatching
|
|
in local areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, <name/GoldED+/ will attempt to match one of
|
|
your akas to the address of the person you are replying to in local
|
|
areas.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
It doesn't really make sense to do aka matching in local areas. The
|
|
keyword is just there for completeness.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AKAMATCH><kw/AKAMATCH/</ref>,
|
|
<ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>,
|
|
<ref target=AKAMATCHING><kw/AKAMATCHING/</ref>,
|
|
<ref target=AKAMATCHNET><kw/AKAMATCHNET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AKAMATCHNET>
|
|
<head>
|
|
AKAMATCHNET
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AKAMATCHNET/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ should do akamatching
|
|
in netmail areas. This is especially useful if you are a member in
|
|
more than one network, and therefore have more than one address.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, <name/GoldED+/ will attempt to match one of
|
|
your akas to the address of the person you are replying to in
|
|
netmail areas.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Normally it is not desirable to enable aka matching in echomail,
|
|
because some echoes may be restricted to members of one particular
|
|
network, and an accidental wrong aka matching may attract unwanted
|
|
attention from the moderator or the compulsive flamers :-)
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AKAMATCH><kw/AKAMATCH/</ref>,
|
|
<ref target=AKAMATCHECHO><kw/AKAMATCHECHO/</ref>,
|
|
<ref target=AKAMATCHING><kw/AKAMATCHING/</ref>,
|
|
<ref target=AKAMATCHLOCAL><kw/AKAMATCHLOCAL/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
APP
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/APP/ <ident><programname> [text]</ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword provides a way for other programs to place configuration
|
|
data in <name/GoldED+/'s configuration file.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/programname/ parameter defines name of the software which
|
|
wants to read its configuration from <name/GoldED+/ configuration
|
|
file. <name/GoldED+/ itself will ignore <kw/APP/ lines just like
|
|
<ref target=REM/remark/ lines.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=REM/Remarks/
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
APP OtherProg REGKEY xyaxajlsaduoiweqeq
|
|
APP OtherProg IRQ 5</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREA>
|
|
<head>
|
|
AREA
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREA/ <ident><echoid> <<![ CDATA ["desc"]]>>
|
|
<msgbase>[type] <location> [akano]
|
|
[attrs]</ident><lb>
|
|
<kw/AREA/ <ident><-FILE> <type> [path/file]
|
|
[switches]</ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This <strong/obsolete/ keyword defines a mail area or external
|
|
area setup.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=7 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/echoid/
|
|
</cell>
|
|
<cell>
|
|
Mail area identifier.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/desc/
|
|
</cell>
|
|
<cell>
|
|
Area description in (<q></q>) quotes.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/msgbase/
|
|
</cell>
|
|
<cell>
|
|
F, O (<name/Opus/ <code/*.msg/);
|
|
S (<name/FTS-0001/ <code/*.msg/);
|
|
H, R, Q (<name/Hudson/, <name/QuickBBS/, <name/RemoteAccess/);
|
|
M (<name/Squish/); J (<name/JAM/); E (<name/Ezycom/);
|
|
G (<name/Goldbase/); P (<name/PCBoard/); X (<name/AdeptXBBS/);
|
|
W (<name/WildCat!/); Y (<name/Synchronet/)
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/type/
|
|
</cell>
|
|
<cell>
|
|
N (Netmail), E (Echomail), L (Local).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/location/
|
|
</cell>
|
|
<cell>
|
|
Directory path/file or board number.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/akano/
|
|
</cell>
|
|
<cell>
|
|
AKA number (starting from 0)
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/attrs/
|
|
</cell>
|
|
<cell>
|
|
<gi>R/O</gi> (Read-Only), and/or other attributes.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
It is recommended to use the newer
|
|
<ref target=AREADEF><kw/AREADEF/</ref> keyword, which allows more
|
|
detailed mail area setup.<lb>
|
|
If more than one area defined to the same path or areatag then last
|
|
definition overrides previous ones.<lb>
|
|
For the <ident/-FILE/ parameters see
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref> keyword.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAEXCL><kw/AREAEXCL/</ref>,
|
|
<ref target=AREAINCL><kw/AREAINCL/</ref>,
|
|
<ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>,
|
|
<ref target=AREAISNEWS><kw/AREAISNEWS/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>,
|
|
<ref target=AREASEP><kw/AREASEP/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=GOLDBASEPATH><kw/GOLDBASEPATH/</ref>,
|
|
<ref target=GOLDBASESYSPATH><kw/GOLDBASESYSPATH/</ref>,
|
|
<ref target=HUDSONPATH><kw/HUDSONPATH/</ref>,
|
|
<ref target=HUDSONSYSPATH><kw/HUDSONSYSPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAAUTOID>
|
|
<head>
|
|
AREAAUTOID
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAAUTOID/ <ident><SHORT/VERBOSE/LONG></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines how an automatically created echoid should look, when
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref> finds an area without an
|
|
echoid.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=3 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident>VERBOSE</ident>
|
|
</cell>
|
|
<cell>
|
|
The echoids are given a name similar to the function of the
|
|
area, such as <gi/NETMAIL/, <gi/NET_SENT/, <gi/ECHO_BAD/,
|
|
<gi/ECHO_DUPES/ and so on.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>LONG</ident>
|
|
</cell>
|
|
<cell>
|
|
The echoids are numbered sequentially like this:
|
|
<gi/NETMAILxxx/, <gi/ECHOMAILxxx/ and <gi/LOCALxxx/.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>SHORT</ident>
|
|
</cell>
|
|
<cell>
|
|
The echoids are numbered sequentially like this: <gi/NETxxx/,
|
|
<gi/ECHOxxx/ and <gi/LOCALxxx/.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/LONG/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
AREAAUTONEXT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAAUTONEXT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls where to put cursor in arealist on startup
|
|
and after exiting from an area you have been reading.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will automatically jump to the first
|
|
marked area in the arealist on startup, and the next marked area
|
|
after exiting from an area you have been reading.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
AREACATCHUPREAD
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREACATCHUPREAD/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <!-- FIX ME!!! --><kw/AREAcatchup/
|
|
will set all skipped messages to read or not.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will set all skipped messages to read when
|
|
using <!-- FIX ME!!! --><kw/AREAcatchup/ in the arealist-screen.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This implies that
|
|
<ref target=HIGHLIGHTUNREAD><kw/HIGHLIGHTUNREAD/</ref> feature is
|
|
used, otherwise it has no function.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/AREAcatchup/,
|
|
<ref target=HIGHLIGHTUNREAD><kw/HIGHLIGHTUNREAD/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREACFMREPLYTO>
|
|
<head>
|
|
AREACFMREPLYTO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREACFMREPLYTO/ <ident/<echoid>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Sets the area where <name/GoldED+/ will create confirmation messages.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The destination area for the confirmation messages.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref>
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref>,
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>,
|
|
<ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>,
|
|
<ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>,
|
|
<ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREACOPYADDID>
|
|
<head>
|
|
AREACOPYADDID
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREACOPYADDID/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
It is useful if you copy echomails to some local archive areas. In
|
|
this case <name/GoldED+/ can add the<eg>
|
|
AREA:<OriginalEchoID></eg>
|
|
kludge line to inform you from where you copied the mail to. This
|
|
keyword should be enabled in the destination area parameters when
|
|
used in the <ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name>GoldED+</name> will insert the <gi/AREA/ kludge
|
|
at the top of each message that is copied or moved.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.<lb>
|
|
Do not enable this unless you know what you doing!
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READcopymoveforward/,
|
|
<ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>,
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREACOPYDIRECT>
|
|
<head>
|
|
AREACOPYDIRECT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREACOPYDIRECT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether copy/move functions should bypass area
|
|
selection screen. The destination area should be set with
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref> keyword.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, the destination area selection list is bypassed, thereby
|
|
making possible a <q/seamless/ copy/move to the default destination
|
|
area.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READcopymoveforward/,
|
|
<ref target=AREACOPYADDID><kw/AREACOPYADDID/</ref>,
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref>,
|
|
<ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>,
|
|
<ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>,
|
|
<ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREACOPYTO>
|
|
<head>
|
|
AREACOPYTO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREACOPYTO/ <ident/<echoid>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Sets the default area for the copy/move functions. Typically you
|
|
could set it to a safe/permanent storage type of area.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The default destination area for the copy/move functions.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.<lb>
|
|
The forward function uses the
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> area instead.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READcopymoveforward/,
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=AREACOPYADDID><kw/AREACOPYADDID/</ref>,
|
|
<ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>,
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref>,
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>,
|
|
<ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREADEF>
|
|
<head>
|
|
AREADEF
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREADEF/ <ident><echoid> <<![ CDATA ["desc"]]>>
|
|
<group> <type> <msgbase> <path/board>
|
|
<aka> <(attrs)>
|
|
[<![ CDATA ["origin"]]>]</ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines a mail area in <name>GoldED+</name>. It looks a
|
|
lot like the <ref target=AREA><kw/AREA/</ref> keyword. Additional
|
|
parameters are the <ident/group/, the verbose <ident/type/ and
|
|
<ident/msgbase/, the fully specified <ident/aka/ address, the
|
|
brackets for the attributes and the optional <ident/origin/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=9 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident>echoid</ident>
|
|
</cell>
|
|
<cell>
|
|
Mail area identifier.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident><![ CDATA ["desc"]]></ident>
|
|
</cell>
|
|
<cell>
|
|
Area description in quotes.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>group</ident>
|
|
</cell>
|
|
<cell>
|
|
Group ID uppercase letter (A-Z) or 0 if not in a group. Use
|
|
#groupnumber to specify group numbers in the 1-999 range.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>type</ident>
|
|
</cell>
|
|
<cell>
|
|
<ident/Net/, <ident/Echo/, <ident/Local/, <ident/EMail/ or
|
|
<ident/News/.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>msgbase</ident>
|
|
</cell>
|
|
<cell>
|
|
<ident/Opus/, <ident/FTS1/, <ident/Hudson/, <ident/Squish/,
|
|
<ident/Ezycom/, <ident/JAM/, <ident/Goldbase/, <ident/PCBoard/,
|
|
or <ident/SMB/.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>path/board</ident>
|
|
</cell>
|
|
<cell>
|
|
Area path, board number or base filename.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>aka</ident>
|
|
</cell>
|
|
<cell>
|
|
Address for the area, or <q>.</q> for the main address.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>(attrs)</ident>
|
|
</cell>
|
|
<cell>
|
|
Default attributes in brackets.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident><![ CDATA ["origin"]]></ident>
|
|
</cell>
|
|
<cell>
|
|
Optional default origin in quotes.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
If more than one area defined to the same path or areatag then last
|
|
definition overrides previous ones.<lb>
|
|
The possibility of using <q/./ to specify the main <abbr/AKA/ and
|
|
the optional default origin makes it simpler to create a common
|
|
<ref target=INCLUDE><kw/INCLUDE/</ref>'able area configuration
|
|
for several setups with different addresses, for example two people
|
|
sharing the same msgbase.<lb>
|
|
If you wish to read packed area (f.e. from CD archive) <name/GoldED+/
|
|
allows you that. You need to specify pathname <hi/with/ extension
|
|
in the <ident>path/board</ident> field, set <gi/PKD/ attribute and
|
|
define packer with <ref target=UNPACKER><kw/UNPACKER/</ref> keyword.
|
|
This feature is not supported for <name/Hudson/ and <name/GoldBase/
|
|
messagebases.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=AREAEXCL><kw/AREAEXCL/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAINCL><kw/AREAINCL/</ref>,
|
|
<ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>,
|
|
<ref target=AREAISNEWS><kw/AREAISNEWS/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>,
|
|
<ref target=AREASEP><kw/AREASEP/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=GOLDBASEPATH><kw/GOLDBASEPATH/</ref>,
|
|
<ref target=GOLDBASESYSPATH><kw/GOLDBASESYSPATH/</ref>,
|
|
<ref target=HUDSONPATH><kw/HUDSONPATH/</ref>,
|
|
<ref target=HUDSONSYSPATH><kw/HUDSONSYSPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREADESC>
|
|
<head>
|
|
AREADESC
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREADESC/ <ident><echoid> <<![ CDATA ["desc"]]>>
|
|
[group] [aka] [(attrs)]
|
|
[<![ CDATA ["origin"]]>]</ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Adds a description and optionally a group letter, <abbr>AKA</abbr>,
|
|
attributes and origin to an <hi>existing</hi> (previously defined)
|
|
area. This is useful if you use an areafile that does not contain
|
|
descriptions, groups, akas, attributes or origins.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=6 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident>echoid</ident>
|
|
</cell>
|
|
<cell>
|
|
Mail area identifier.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident><![ CDATA ["desc"]]></ident>
|
|
</cell>
|
|
<cell>
|
|
Area description in quotes.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>group</ident>
|
|
</cell>
|
|
<cell>
|
|
Optional groupid uppercase letter (A-Z) or 0 if not in a group.
|
|
Use #groupnumber to specify group numbers in the 1-999
|
|
range or <q>-</q> to keep the existing groupid.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>aka</ident>
|
|
</cell>
|
|
<cell>
|
|
Optional <abbr>AKA</abbr> address for the area, or <q>.</q> for
|
|
main <abbr>AKA</abbr>, or <q>-</q> to keep the existing
|
|
<abbr>AKA</abbr>.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>(attrs)</ident>
|
|
</cell>
|
|
<cell>
|
|
Optional default attributes in brackets, <q>-</q> to keep the
|
|
existing attributes. Note that if they are specified, they are
|
|
<hi>added</hi> to the default net/echo/local attributes.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident><![ CDATA ["origin"]]></ident>
|
|
</cell>
|
|
<cell>
|
|
Optional default origin in quotes.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
You cannot skip any of the optional parts in the middle, even if you
|
|
only want to set, say, an origin. Use <q>-</q> to keep the existing
|
|
value for the parts you skip.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>,
|
|
<ref target=AREAISNEWS><kw/AREAISNEWS/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>,
|
|
<ref target=AREASEP><kw/AREASEP/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAEXCL>
|
|
<head>
|
|
AREAEXCL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAEXCL/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
With this keyword, you can define the echoids of areas which should
|
|
be ignored by <name/GoldED+/ (thereby leaving them out of the
|
|
arealist). This is normally used in connection with
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>, to exclude areas you are
|
|
not interested in reading.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
You can use the <ref target=AREAINCL><kw/AREAINCL/</ref> keyword to
|
|
reinclude areas which have been excluded with <kw/AREAEXCL/.<lb>
|
|
This keyword must be placed before any of
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAINCL><kw/AREAINCL/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREAEXCL * ; Excludes all areas.
|
|
AREAEXCL *INTER* ; Excludes all areas containing INTER anywhere in the
|
|
; echoid.
|
|
AREAEXCL INT*.* ; Excludes all areas beginning with INT and
|
|
; containing a dot anywhere in the echoid.</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAFILE>
|
|
<head>
|
|
AREAFILE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAFILE/ <ident><type> [path/file]
|
|
[switches]</ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
<name/GoldED+/ can read the area setup of many popular mailers,
|
|
mail processors and <abbr/BBS/'es, thereby making it much easier
|
|
and simpler to configure <name/GoldED+/ for the mail areas you
|
|
receive, by eliminating the need to write area definition lines for
|
|
all or most of your areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=3 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/type/
|
|
</cell>
|
|
<cell>
|
|
Name of the program.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>path/file</ident>
|
|
</cell>
|
|
<cell>
|
|
Filename or path to the area setup files.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/switches/
|
|
</cell>
|
|
<cell>
|
|
Areafile specific switches.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
For most programs, <name>GoldED+</name> can automatically find the
|
|
path or filename using environment variables. By default,
|
|
<name/GoldED+/ will look for the area setup files in the
|
|
<ref target=AREAPATH><kw/AREAPATH/</ref>.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=AREACONFIGURATION> chapter,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAEXCL><kw/AREAEXCL/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>,
|
|
<ref target=AREAINCL><kw/AREAINCL/</ref>,
|
|
<ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>,
|
|
<ref target=AREAISNEWS><kw/AREAISNEWS/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>,
|
|
<ref target=AREAPATH><kw/AREAPATH/</ref>,
|
|
<ref target=AREASEP><kw/AREASEP/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAFILEGROUPS>
|
|
<head>
|
|
AREAFILEGROUPS
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAFILEGROUPS/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
In some <ref target=AREAFILE><kw/AREAFILE/</ref> setups, you can
|
|
groups the areas using single letters (A-Z) or numbers (#1-999).
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If this keyword is enabled, <name>GoldED+</name> will use the area
|
|
groupid instead of the area echoid when gathering area specific
|
|
information from the <ref target=RANDOMSYSTEM>Random System</ref>
|
|
group.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This have only sence if you using <ref target=RANDOMSYSTEM>Random
|
|
System</ref> groups.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=RANDOMSYSTEM> chapter
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAFORWARDDIRECT>
|
|
<head>
|
|
AREAFORWARDDIRECT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAFORWARDDIRECT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether forward functions should bypass area
|
|
selection screen. The destination area should be set with
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref> keyword.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, the destination area selection list is bypassed, thereby
|
|
making possible a <q/seamless/ forward to the default destination
|
|
area.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READcopymoveforward/,
|
|
<ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>,
|
|
<ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>,
|
|
<ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>,
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAFREQDIRECT>
|
|
<head>
|
|
AREAFREQDIRECT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAFREQDIRECT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether filerequest functions should bypass
|
|
area selection screen. The destination area should be set with
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref> keyword.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, the destination area selection list is bypassed, thereby
|
|
making possible a <q/seamless/ filerequest in the default
|
|
destination area.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.<lb>
|
|
If you (like most) only have one mailer netmail area, you can enable
|
|
this feature globally for simpler file requests.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READfilerequest/,
|
|
<ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>,
|
|
<ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>,
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref>,
|
|
<ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=FRQEXT><kw/FRQEXT/</ref>,
|
|
<ref target=FRQNODEMAP><kw/FRQNODEMAP/</ref>,
|
|
<ref target=FRQOPTIONS><kw/FRQOPTIONS/</ref>,
|
|
<ref target=FRQWAZOO><kw/FRQWAZOO/</ref>,
|
|
<ref target=OUTBOUNDPATH><kw/OUTBOUNDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAFREQTO>
|
|
<head>
|
|
AREAFREQTO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAFREQTO/ <ident/<echoid>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Sets the default area for the filerequest functions.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The default destination area for the filerequest functions.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
First netmail area.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READfilerequest/,
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref>,
|
|
<ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>,
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>,
|
|
<ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=FRQEXT><kw/FRQEXT/</ref>,
|
|
<ref target=FRQNODEMAP><kw/FRQNODEMAP/</ref>,
|
|
<ref target=FRQOPTIONS><kw/FRQOPTIONS/</ref>,
|
|
<ref target=FRQWAZOO><kw/FRQWAZOO/</ref>,
|
|
<ref target=OUTBOUNDPATH><kw/OUTBOUNDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAINCL>
|
|
<head>
|
|
AREAINCL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAINCL/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
With this keyword, you can define the echoids of areas which should
|
|
be reincluded by <name/GoldED+/, if they have been excluded with the
|
|
<ref target=AREAEXCL><kw/AREAEXCL/</ref> keyword.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword must be placed before any of
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAEXCL><kw/AREAEXCL/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREAINCL * ; Includes all areas.
|
|
AREAINCL *INTER* ; Includes all areas containing INTER anywhere in the
|
|
; echoid.
|
|
AREAINCL INT*.* ; Includes all areas beginning with INT and
|
|
; containing a dot anywhere in the echoid.</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAISEMAIL>
|
|
<head>
|
|
AREAISEMAIL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAISEMAIL/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
These keyword is designed to mark areas which are read from an
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref> as <name/Internet/ e-mail.
|
|
This may be necessary in some cases to enable the <name/Internet/
|
|
specific features without having to manually define all
|
|
<name/Internet/ areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword must be placed before any of
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAISNEWS><kw/AREAISNEWS/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREAISEMAIL djgpp*, golded-plus*</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAISNEWS>
|
|
<head>
|
|
AREAISNEWS
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAISNEWS/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
These keyword is designed to mark areas which are read from an
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref> as <name/Internet/
|
|
newsgroup. This may be necessary in some cases to enable the
|
|
<name/Internet/ specific features without having to manually define
|
|
all <name/Internet/ areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword must be placed before any of
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
or <ref target=AREAFILE><kw/AREAFILE/</ref> keywords.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>,
|
|
<ref target=AREARENAME><kw/AREARENAME/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREAISNEWS alt.*, rec.*, sci.*</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAKEEPLAST>
|
|
<head>
|
|
AREAKEEPLAST
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAKEEPLAST/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ should write the file
|
|
<code/goldlast.lst/ in the <ref target=GOLDPATH><kw/GOLDPATH/</ref>
|
|
at exit and read it back when run next time. The contents of the file
|
|
is a list of lastread information for each area as it was at last
|
|
scan.<lb>
|
|
This feature is helpful when you know that there have not been tossed
|
|
new mail and don't want to wait for a full msgbase scan. Now you can
|
|
just hit <ESC> at the startup screen to abort the area scan and
|
|
<name/GoldED+/ will put up the lastread info from the previous
|
|
session.<lb>
|
|
It also makes the <q/new mail since last scan/ feature even better,
|
|
because the new mail marker now shows which areas that have new mail
|
|
since last session even when scanning areas at startup.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Setting this keyword to <ident/YES/ enables <code/goldlast.lst/
|
|
usage, setting to <ident/NO/ disables writes to this file.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
<name/GoldED+/ only writes the <code/goldlast.lst/ file at exit if it
|
|
survived the initial startup scan.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/AREAscan/,
|
|
<!-- FIX ME!!! --><kw/AREAscanpm/,
|
|
<!-- FIX ME!!! --><kw/AREAwritegoldlast/,
|
|
<ref target=AREALISTSCAN><kw/AREALISTSCAN/</ref>,
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>,
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTECHOMAX>
|
|
<head>
|
|
AREALISTECHOMAX
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTECHOMAX/ <ident/<size>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Allows you to specify a fixed or dynamically sized width of the
|
|
<gi/EchoID/ column in the arealist.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If a negative value is specified, the width will be the that of the
|
|
widest echoid in the arealist plus the negative value. This might be
|
|
useful if some long-name echoes have uninteresting ends, such as
|
|
<gi/VERYLONGECHOID_R23.PUB/ (could benefit from a <ident/size/ of
|
|
-7). There is currently no provision for long echoids with common
|
|
beginning.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/0/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
The arealist can dynamically resize the <gi/EchoID/ and
|
|
<gi/Description/ columns, so that long echoids are not cut off. The
|
|
sizing of the <q>EchoID</q> column is done against the
|
|
<gi/Description/ column, which thereby looses or gains width.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>,
|
|
<ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>,
|
|
<ref target=AREALISTNOS><kw/AREALISTNOS/</ref>,
|
|
<ref target=AREALISTPAGEBAR><kw/AREALISTPAGEBAR/</ref>,
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>,
|
|
<ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref>,
|
|
<ref target=AREASEP><kw/AREASEP/</ref>,
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTFORMAT>
|
|
<head>
|
|
AREALISTFORMAT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTFORMAT/ <ident/<string>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
The arealist column layout is configurable. This keyword allows you
|
|
to change the layout to whatever you like.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The string should be composed from the following letters:
|
|
<table rows=10 cols=3>
|
|
<row>
|
|
<cell>
|
|
Letter
|
|
</cell>
|
|
<cell>
|
|
Meaning
|
|
</cell>
|
|
<cell>
|
|
Default width
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/A/
|
|
</cell>
|
|
<cell>
|
|
Area number
|
|
</cell>
|
|
<cell>
|
|
4
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/M/
|
|
</cell>
|
|
<cell>
|
|
Marked
|
|
</cell>
|
|
<cell>
|
|
1
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/D/
|
|
</cell>
|
|
<cell>
|
|
Description
|
|
</cell>
|
|
<cell>
|
|
Dynamic
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/C/
|
|
</cell>
|
|
<cell>
|
|
Number of messages
|
|
</cell>
|
|
<cell>
|
|
6
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/P/
|
|
</cell>
|
|
<cell>
|
|
Personal mail mark (<q/+/)
|
|
</cell>
|
|
<cell>
|
|
1
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/U/
|
|
</cell>
|
|
<cell>
|
|
Number of unread/new messages
|
|
</cell>
|
|
<cell>
|
|
6
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/N/
|
|
</cell>
|
|
<cell>
|
|
Changed since last scan mark (<q/*/)
|
|
</cell>
|
|
<cell>
|
|
1
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/E/
|
|
</cell>
|
|
<cell>
|
|
Echoid
|
|
</cell>
|
|
<cell>
|
|
<ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref>
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/G/
|
|
</cell>
|
|
<cell>
|
|
Groupid
|
|
</cell>
|
|
<cell>
|
|
Dynamic: 0, 1 or 3
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
You can also specify widths for each or particular fields if you
|
|
don't like the defaults by putting number right after the letter.<lb>
|
|
If you leave out a letter, that column will not be shown.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident><![ CDATA ["AM D CPUN E G "]]></ident>
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Use only the defined letters. Use spaces to specify required space
|
|
between columns. Use only positive numbers for widths. Failure to
|
|
obey these rules may cause undocumented behaviour.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref>,
|
|
<ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>,
|
|
<ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>,
|
|
<ref target=AREALISTNOS><kw/AREALISTNOS/</ref>,
|
|
<ref target=AREALISTPAGEBAR><kw/AREALISTPAGEBAR/</ref>,
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>,
|
|
<ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref>,
|
|
<ref target=AREASEP><kw/AREASEP/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg><![ CDATA [
|
|
AREALISTFORMAT "AM D C4PU4N E G "]]></eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTGROUPID>
|
|
<head>
|
|
AREALISTGROUPID
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTGROUPID/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This feature provides a way to hide group ID on the arealist screen,
|
|
in a column to the right of the <gi/EchoID/ column. If a group ID is
|
|
not a letter in the range A-Z (a value in the range #65-#90),
|
|
the groupid is not shown anyway.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, the arealist screen will display the groupid letters, if
|
|
any.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
The same effect is achieved by skipping <ident/G/ letter in the
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref> definition.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>,
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTGROUPORDER>
|
|
<head>
|
|
AREALISTGROUPORDER
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTGROUPORDER/ <ident/<string>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows to change the order in which areas will be sorted
|
|
when sorting by group ID is used. If some groups are not found in the
|
|
<ident/string/ they will be placed below specifyed ones in
|
|
alphabetical order.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The only parameter is string which specifies groups order. You may
|
|
use #groupnumber to specify group numbers in the 1-999 range.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
Empty string.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>,
|
|
<ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>,
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTNOS>
|
|
<head>
|
|
AREALISTNOS
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTNOS/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows to specify whether board number or sequential
|
|
area number will be displayed in the arealist.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will display the board numbers of
|
|
<name/Hudson/ or <name/GoldBase/ areas in the arealist instead of
|
|
the default sequential numbers.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/AREAboardnos/,
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref>,
|
|
<ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref>,
|
|
<ref target=DISPAREANO><kw/DISPAREANO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTPAGEBAR>
|
|
<head>
|
|
AREALISTPAGEBAR
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTPAGEBAR/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Enables or disables a pagebar (scrollbar) in the arealist.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will display pagebar in the arealist, if
|
|
disabled - will not.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=DISPPAGEBAR><kw/DISPPAGEBAR/</ref>,
|
|
<ref target=FILELISTPAGEBAR><kw/FILELISTPAGEBAR/</ref>,
|
|
<ref target=MSGLISTPAGEBAR><kw/MSGLISTPAGEBAR/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTSCAN>
|
|
<head>
|
|
AREALISTSCAN
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTSCAN/ <ident><<![ CDATA ["L menu text"]]>>
|
|
[path]<filename> [-delete]</ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows you to define additional menu items for the
|
|
arealist scanning menus (<!-- FIX ME!!! --><kw/AREAscan/ or
|
|
<!-- FIX ME!!! --><kw/AREAscanpm/).
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The first two characters of the menu text are the <q/hotkey/ letter
|
|
that will be highlighted in the menu text, plus a space.<lb>
|
|
The filename specifies a plain text file, with the echoids (wildcards
|
|
allowed) of the areas you want to scan when the menu item is
|
|
selected. There can be several echoids on each line in the file. If
|
|
no path is given, the file is loaded from the
|
|
<ref target=GOLDPATH><kw/GOLDPATH/</ref>.<lb>
|
|
The <ident/-delete/ option will cause <name/GoldED+/ to delete the
|
|
list file after scanning the areas in it. For example, if your mail
|
|
processor generates a list of the areas that it tossed new mail to,
|
|
you could add the list as a menu item on the scanning menu and use it
|
|
to scan only those areas with new mail.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Some mail processors automatically delete their list after using it
|
|
for replylinking. You may want to do some creative stuff with
|
|
batchfiles to grab a copy.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/AREAscan/,
|
|
<!-- FIX ME!!! --><kw/AREAscanpm/
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg><![ CDATA [
|
|
AREALISTSCAN "g Scan Newsgroups" NEWSGRPS.LST
|
|
AREALISTSCAN "L Scan Latest" R:\GECHO\IMPORT.ALL -delete]]></eg>
|
|
<eg>
|
|
=== Cut, NEWSGRPS.LST ===
|
|
ALT.*, COMP.*, MISC.*, NEWS.*
|
|
REC.*, SOC.*, SCI.*, TALK.*
|
|
=== Cut ===</eg>
|
|
<eg>
|
|
=== Cut from an import batchfile ===
|
|
gecho mgr toss pack -tossbad
|
|
if exist import.jam type import.jam >>import.all
|
|
if exist import.hmb type import.hmb >>import.all
|
|
if exist import.sdm type import.sdm >>import.all
|
|
mbutil link -clean
|
|
=== Cut ===</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTSORT>
|
|
<head>
|
|
AREALISTSORT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTSORT/ <ident/<sortspec>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines how the area list should be sorted. You can
|
|
override the default setting from the commandline with the
|
|
<code>-s</code> switch.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <sortspec> can be composed of the following types:
|
|
<table rows=16 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/A/
|
|
</cell>
|
|
<cell>
|
|
Sort by aka.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/B/
|
|
</cell>
|
|
<cell>
|
|
Sort by board number.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/D/
|
|
</cell>
|
|
<cell>
|
|
Sort by description.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/E/
|
|
</cell>
|
|
<cell>
|
|
Sort by echoid.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/F/
|
|
</cell>
|
|
<cell>
|
|
Sorts all <q/fuzzy search/ matches first.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/G/
|
|
</cell>
|
|
<cell>
|
|
Sort by group (if any).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/M/
|
|
</cell>
|
|
<cell>
|
|
Sorts all marked areas first.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/O/
|
|
</cell>
|
|
<cell>
|
|
Sort by original order.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/P/
|
|
</cell>
|
|
<cell>
|
|
Sort by personal mail count.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/p/
|
|
</cell>
|
|
<cell>
|
|
Sort by personal mail presence.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/S/
|
|
</cell>
|
|
<cell>
|
|
Sort area separators first.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/T/
|
|
</cell>
|
|
<cell>
|
|
Sort by type (according to
|
|
<ref target=AREATYPEORDER><kw/AREATYPEORDER/</ref>).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/U/
|
|
</cell>
|
|
<cell>
|
|
Sort by unread messages count (try it!).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/u/
|
|
</cell>
|
|
<cell>
|
|
Sort by unread messages presence (try it!).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/X/
|
|
</cell>
|
|
<cell>
|
|
Sort by msgbase type.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/Y/
|
|
</cell>
|
|
<cell>
|
|
Sorts all areas with <q/new/ mail first.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/Z/
|
|
</cell>
|
|
<cell>
|
|
Sort by msgbase path.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/-/
|
|
</cell>
|
|
<cell>
|
|
Descending sort (largest first).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/+/
|
|
</cell>
|
|
<cell>
|
|
Ascending sort (smallest first) (default).
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/FYTUE/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
In practice <ident/M/ and <ident/Y/ will usually give the same
|
|
result, because <name/GoldED+/ automatically marks scanned areas if
|
|
they contain new mail.<lb>
|
|
The <ident/F/ enables fuzzy match sorting, which is very handy when
|
|
looking for an echoid containing a particular word. Let's say you
|
|
want a list of all <name/GoldED/ echoes. You can simply type
|
|
<q/GOLDED/ and then the arealist automatically sorts itself so that
|
|
all echoes with an echoid containing <q/GOLDED/ comes first.<lb>
|
|
The <ident/X/ sort type sorts areas according to msgbase type, in the
|
|
following order: <name/Hudson/, <name/Goldbase/, <name/JAM/,
|
|
<name/Squish/, <name/Opus/ <code/*.msg/, <name/FTS-0001/
|
|
<code/*.msg/, <name/Ezycom/, <name/PCBoard/.<lb>
|
|
The <ident/X/ and <ident/Z/ sort types were implemented for internal
|
|
use, to optimize area scanning speed. When scanning areas,
|
|
<name/GoldED+/ starts by sorting the arealist using the sortspec
|
|
defined with the <ref target=AREASCANSORT><kw/AREASCANSORT/</ref>
|
|
keyword.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=AREACONFIGURATION> chapter,
|
|
<ptr target=COMMANDLINE> chapter,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAEXCL><kw/AREAEXCL/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>,
|
|
<ref target=AREAINCL><kw/AREAINCL/</ref>,
|
|
<ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>,
|
|
<ref target=AREAISNEWS><kw/AREAISNEWS/</ref>,
|
|
<ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>,
|
|
<ref target=AREASCANSORT><kw/AREASCANSORT/</ref>,
|
|
<ref target=AREASEP><kw/AREASEP/</ref>,
|
|
<ref target=AREATYPEORDER><kw/AREATYPEORDER/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREALISTSORT -U+TE</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREALISTTYPE>
|
|
<head>
|
|
AREALISTTYPE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREALISTTYPE/ <ident><NEW/LAST></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the contents of the 4th column (the one after the <gi/Total/
|
|
column).
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=2 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/NEW/
|
|
</cell>
|
|
<cell>
|
|
Displays the amount of new (unread) msgs (Actually number of
|
|
messages after lastread mark).
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/LAST/
|
|
</cell>
|
|
<cell>
|
|
Displays the number of the last msg read.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NEW/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=AREALISTGROUPID><kw/AREALISTGROUPID/</ref>,
|
|
<ref target=AREALISTNOS><kw/AREALISTNOS/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAPATH>
|
|
<head>
|
|
AREAPATH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAPATH/ <ident/<path>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines where the area setup files are located when
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref> keyword is used. It is
|
|
also defines default path for the semaphores.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/path/ defines the path to the area setup files.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Most <ref target=AREAFILE><kw/AREAFILE/</ref> types can find the path
|
|
using the environment variable(s) specific for the program(s). Such
|
|
environment variables (or a path specified with the
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref> definition) always overrides
|
|
the <ref target=AREAFILE><kw/AREAFILE/</ref>.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=AREACONFIGURATION> chapter,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=SEMAPHORE><kw/SEMAPHORE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAPMSCAN>
|
|
<head>
|
|
AREAPMSCAN
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAPMSCAN/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines areas which will be automatically scanned for
|
|
personal mail when starting <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas. If mask started with the > (greater) character, then
|
|
it represent group ID.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
It is recommended to have to scan all areas at startup. If you don't
|
|
want to wait for the scan to complete, you can abort the scan by
|
|
pressing <ESC> during startup.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>,
|
|
<ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>,
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref>,
|
|
<ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>,
|
|
<ref target=AREASCANINCL><kw/AREASCANINCL/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREAPMSCAN * ; Scan all areas.
|
|
AREAPMSCAN *INTER* ; Scan all areas containing INTER anywhere in the
|
|
; echoid
|
|
AREAPMSCAN INT*.* ; Scan all areas beginning with INT and
|
|
; containing a dot anywhere in the echoid</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAPMSCANEXCL>
|
|
<head>
|
|
AREAPMSCANEXCL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAPMSCANEXCL/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
With this keyword you can prevent areas from being scanned with
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref> on startup.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas. If mask started with the > (greater) character, then
|
|
it represent group ID.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This is good if you use <ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>
|
|
to scan all areas, but have some big areas which slows it down.<lb>
|
|
You can use the <ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>
|
|
keyword to reinclude areas which have been excluded with
|
|
<kw/AREAPMSCANEXCL/.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>,
|
|
<ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>,
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref>,
|
|
<ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>,
|
|
<ref target=AREASCANINCL><kw/AREASCANINCL/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAPMSCANINCL>
|
|
<head>
|
|
AREAPMSCANINCL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAPMSCANINCL/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows to specify areas which are to be scanned with
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref> even if they were
|
|
excluded with <ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>.
|
|
Useful for partial reversal of wildcard specs in the excludes.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas. If mask started with the > (greater) character, then
|
|
it represent group ID.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>,
|
|
<ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>,
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref>,
|
|
<ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>,
|
|
<ref target=AREASCANINCL><kw/AREASCANINCL/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAREADONLY>
|
|
<head>
|
|
AREAREADONLY
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAREADONLY/ <ident><SOFT/HARD></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This option is designed for those who setup a system for new computer
|
|
users who might be confused enough to enter a message in a read-only
|
|
area despite the warning menu.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If this keyword is set to <ident/HARD/, it is no longer possible to
|
|
enter/reply/change messages in areas marked read-only with the
|
|
<gi>R/O</gi> area attribute. The <ident/SOFT/ setting uses a menu to
|
|
ask permission as in the previous versions.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/SOFT/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREARENAME>
|
|
<head>
|
|
AREARENAME
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREARENAME/ <ident/<from echoid> <to echoid>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Renames one echoid to another. The feature is meant to be used in
|
|
connection with <kw>AREAFILE</kw>, where some types do not store
|
|
echoids with the areas (and <name>GoldED+</name> then automatically
|
|
gives them unique echoids). Also you may rename areas with long
|
|
echoid to the shorter one.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<ident/<From echoid>/ defines the original name for the area
|
|
(given by the <name/GoldED+/ automatically) and
|
|
<ident/<to echoid>/ defines echoid in the form it will be
|
|
listed in the arealist.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAAUTOID><kw/AREAAUTOID/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREARENAME NET001 NETMAIL
|
|
AREARENAME ECHO001 BAD_MSGS
|
|
AREARENAME LOCAL001 BBS.USERS</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAREPLYDIRECT>
|
|
<head>
|
|
AREAREPLYDIRECT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAREPLYDIRECT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <!-- FIX ME!!! --><kw/READcommentmsg/,
|
|
<!-- FIX ME!!! --><kw/READquotemsg/, and
|
|
<!-- FIX ME!!! --><kw/READreplymsg/ functions should reply
|
|
to the different area bypassing area selection screen. The
|
|
destination area is choosen as follows:
|
|
<list type=simple>
|
|
<item>
|
|
Contents of the <gi/AREA/ kludge if enabled with
|
|
<ref target=USEAREA><kw/USEAREA/</ref>.
|
|
</item>
|
|
<item>
|
|
Area set with <ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>
|
|
keyword.
|
|
</item>
|
|
<item>
|
|
Current area.
|
|
</item>
|
|
</list>
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will bypass area selection screen, if
|
|
disabled - will not.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.<lb>
|
|
It is probably not a good idea to enable this keyword globally.<lb>
|
|
If you run a utility or have a mail processor which copies personal
|
|
mail to a separate area and puts an <gi/AREA/ kludge at the top of
|
|
the messages, you should create a random system group for the area
|
|
and enable <kw>AREAREPLYDIRECT</kw> in it.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READcommentmsg/,
|
|
<!-- FIX ME!!! --><kw/READquotemsg/,
|
|
<!-- FIX ME!!! --><kw/READreplymsg/,
|
|
<ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>,
|
|
<ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>,
|
|
<ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>,
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
GROUP ECHO_PERSONAL
|
|
AREAREPLYDIRECT YES
|
|
ENDGROUP</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAREPLYTO>
|
|
<head>
|
|
AREAREPLYTO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAREPLYTO/ <ident/<echoid>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Sets the default area for the reply and forward functions. Typically
|
|
you could set it to a safe/permanent storage type of area.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The default destination area for the reply and forward functions.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
First netmail area.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READcopymoveforward/,
|
|
<!-- FIX ME!!! --><kw/READmovecommentmsg/,
|
|
<!-- FIX ME!!! --><kw/READmovequotemsg/,
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref>,
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref>,
|
|
<ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>,
|
|
<ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREASCAN>
|
|
<head>
|
|
AREASCAN
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREASCAN/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines areas which will be automatically scanned for
|
|
new mail when starting <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas. If mask started with the > (greater) character, then
|
|
it represent group ID.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
It is recommended to have to scan all areas at startup. If you don't
|
|
want to wait for the scan to complete, you can abort the scan by
|
|
pressing <ESC> during startup.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>,
|
|
<ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>,
|
|
<ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>,
|
|
<ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>,
|
|
<ref target=AREASCANINCL><kw/AREASCANINCL/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
AREASCAN * ; Scan all areas.
|
|
AREASCAN *INTER* ; Scan all areas containing INTER anywhere in the
|
|
; echoid
|
|
AREASCAN INT*.* ; Scan all areas beginning with INT and
|
|
; containing a dot anywhere in the echoid</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREASCANEXCL>
|
|
<head>
|
|
AREASCANEXCL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREASCANEXCL/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
With this keyword you can prevent areas from being scanned with
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref> on startup.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas. If mask started with the > (greater) character, then
|
|
it represent group ID.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This is good if you use <ref target=AREASCAN><kw/AREASCAN/</ref>
|
|
to scan all areas, but have some big areas which slows it down.<lb>
|
|
You can use the <ref target=AREASCANINCL><kw/AREASCANINCL/</ref>
|
|
keyword to reinclude areas which have been excluded with
|
|
<kw/AREASCANEXCL/.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>,
|
|
<ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>,
|
|
<ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>,
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref>,
|
|
<ref target=AREASCANINCL><kw/AREASCANINCL/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREASCANINCL>
|
|
<head>
|
|
AREASCANINCL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREASCANINCL/ <ident/<echoid mask>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows to specify areas which are to be scanned with
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref> even if they were
|
|
excluded with <ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>.
|
|
Useful for partial reversal of wildcard specs in the excludes.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid mask>/ may contain <name/4DOS/-style
|
|
wildcards (<q/*/ and <q/?/). You may specify multiple masks separated
|
|
with commas. If mask started with the > (greater) character, then
|
|
it represent group ID.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREAPMSCAN><kw/AREAPMSCAN/</ref>,
|
|
<ref target=AREAPMSCANEXCL><kw/AREAPMSCANEXCL/</ref>,
|
|
<ref target=AREAPMSCANINCL><kw/AREAPMSCANINCL/</ref>
|
|
<ref target=AREASCAN><kw/AREASCAN/</ref>,
|
|
<ref target=AREASCANEXCL><kw/AREASCANEXCL/</ref>,
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREASCANSORT>
|
|
<head>
|
|
AREASCANSORT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREASCANSORT/ <ident/<sortspec>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
When scanning areas, <name/GoldED+/ can optimize area scanning
|
|
speed if it first sorts the arealist in an order so that each msgbase
|
|
format is scanned in sequence rather than on semi-random order.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <sortspec> described in details in the
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/XZBE/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREASEP>
|
|
<head>
|
|
AREASEP
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREASEP/ <ident><echoid> <<![ CDATA ["desc"]]>>
|
|
<group> <type> <aka></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
You can define area separation lines between groups or areatypes.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=9 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/echoid/
|
|
</cell>
|
|
<cell>
|
|
Mail area identifier.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident><![ CDATA ["desc"]]></ident>
|
|
</cell>
|
|
<cell>
|
|
Area description in quotes.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/group/
|
|
</cell>
|
|
<cell>
|
|
Group ID uppercase letter (A-Z) or 0 if not in a group. Use
|
|
#groupnumber to specify group numbers in the 1-999 range.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/type/
|
|
</cell>
|
|
<cell>
|
|
<ident/Net/, <ident/Echo/, <ident/Local/, <ident/EMail/ or
|
|
<ident/News/.
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident>aka</ident>
|
|
</cell>
|
|
<cell>
|
|
Address for the area, or <q>.</q> for the main address.
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
The area separation lines are implemented like a special kind of
|
|
area, and are therefore sorted in the arealist just as if they were
|
|
actual areas. This is also the reason why you can place the cursor
|
|
bar on the separation lines. The fuzzy feature may be used to quickly
|
|
go to an area group, that's why cursor can be placed on separation
|
|
lines.<lb>
|
|
When configuring area separation lines, be careful to consider the
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>, so that the lines
|
|
are sorted into the positions you want. If you don't sort areas, you
|
|
must make sure that the <kw/AREASEP/ definitions are placed correctly
|
|
in your configuration file, that is, between/before
|
|
<ref target=AREA><kw/AREA/</ref> and
|
|
<ref target=AREADEF><kw/AREADEF/</ref> lines.<lb>
|
|
You will note that the separation lines are not fully connected into
|
|
the left and right edges. This is both by design and for practical
|
|
reasons (easier to implement), not a bug.<lb>
|
|
Currently the descriptions are hardcoded to the natural location in
|
|
the description column.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREAFILE><kw/AREAFILE/</ref>,
|
|
<ref target=AREAFILEGROUPS><kw/AREAFILEGROUPS/</ref>,
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=AREALISTGROUPORDER><kw/AREALISTGROUPORDER/</ref>,
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>,
|
|
<ref target=AREATYPEORDER><kw/AREATYPEORDER/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg><![ CDATA [
|
|
; In this example areas will be separated by types
|
|
AREALISTSORT TYUE
|
|
AREASEP !NET "Netmail areas" 0 Net
|
|
AREASEP !EMAIL "E-mail areas" 0 EMail
|
|
AREASEP !ECHO "Echomail areas" 0 Echo
|
|
AREASEP !NEWS "Newsgroup areas" 0 News
|
|
AREASEP !LOCAL "Local areas" 0 Local]]></eg>
|
|
<eg><![ CDATA [
|
|
; And in this one areas will be separated by groups
|
|
AREALISTSORT GYUE
|
|
AREASEP !A "Group A" A Local
|
|
AREASEP !B "Group B" B Local
|
|
AREASEP !C "Group C" C Local]]></eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREASTART>
|
|
<head>
|
|
AREASTART
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREASTART/ <ident/<echoid>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Normally <name>GoldED+</name> starts by displaying the arealist, to
|
|
let you select which area you want to read. If this keyword is
|
|
defined, the arealist is bypassed and <name/GoldED+/ starts directly
|
|
in the configured area. You can override <kw>AREASTART</kw> with the
|
|
<code>-e</code> commandline switch.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/<echoid>/ parameter specifies the echo
|
|
<name/GoldED+/ should start directly in.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=COMMANDLINE> chapter
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREATYPEORDER>
|
|
<head>
|
|
AREATYPEORDER
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREATYPEORDER/ <ident><type1> <type2> <type3>
|
|
<type4> <type5></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows you to change the ordering of the different
|
|
area types when sorted by
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The following types are allowed: <ident/NET/, <ident/ECHO/,
|
|
<ident/LOCAL/, <ident/EMAIL/ and <ident/NEWS/.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NET/ <ident/EMAIL/ <ident/ECHO/ <ident/NEWS/ <ident/LOCAL/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=AREALISTSORT><kw/AREALISTSORT/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=AREAYOUWROTETO>
|
|
<head>
|
|
AREAYOUWROTETO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/AREAYOUWROTETO/ <ident/<echoid>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
<name/GoldED+/ automatically copies mails written by yourself to the
|
|
given area when saving a new mail. <name/GoldED+/ will also add an
|
|
<gi/AREA/ kludge so you can see from which area the mail originally
|
|
is copied from.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The default destination area for the mails written by you.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword can be used globally and in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.<lb>
|
|
The mail will not be copied if you use
|
|
<!-- FIX ME!!! -->READchangemsg function.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref>,
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref>,
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ASKDELORIG
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ASKDELORIG/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows to automatically delete mail in netmail and local
|
|
area after replying on it.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, you will be asked if the message you just replied to
|
|
should be deleted. Otherwise it is left untouched.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword is only functional in netmail and local areas.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/READcommentmsg/,
|
|
<!-- FIX ME!!! --><kw/READmovecommentmsg/,
|
|
<!-- FIX ME!!! --><kw/READmovequotemsg/,
|
|
<!-- FIX ME!!! --><kw/READquotemsg/,
|
|
<!-- FIX ME!!! --><kw/READreplymsg/,
|
|
<ref target=AREALISTFORMAT><kw/AREALISTFORMAT/</ref>,
|
|
<ref target=AREALISTECHOMAX><kw/AREALISTECHOMAX/</ref>,
|
|
<ref target=AREALISTTYPE><kw/AREALISTTYPE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTACHPATH>
|
|
<head>
|
|
ATTACHPATH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTACHPATH/ <ident/<path>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default path when selecting files for attachement.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The default <ident/path/ for the fileattach feature.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ptr target=FILESELECTION> chapter,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=EDITAUTOATTACH><kw/EDITAUTOATTACH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSATTACH>
|
|
<head>
|
|
ATTRIBSATTACH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSATTACH/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the attributes that are <hi>added</hi> to the existing
|
|
attributes of a message when the file attach attribute is toggled on.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ATTACHPATH><kw/ATTACHPATH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=DISPATTACHSIZE><kw/DISPATTACHSIZE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSCC>
|
|
<head>
|
|
ATTRIBSCC
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSCC/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes of carbon copy messages. <abbr/CC/
|
|
attributes are <hi/added/ to the existing attributes of the
|
|
original message. Usually used to add the <gi>K/S</gi> attribute.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<!-- FIX ME!!! -->Carbon Copy and Crossposting chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CARBONCOPYLIST><kw/CARBONCOPYLIST/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSCFM>
|
|
<head>
|
|
ATTRIBSCFM
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSCFM/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes of the confirmation receipt message.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Suggested attribute is: <gi/RRC/.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>,
|
|
<ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>,
|
|
<ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSECHO>
|
|
<head>
|
|
ATTRIBSECHO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSECHO/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes of messages entered in echomail areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSEMAIL>
|
|
<head>
|
|
ATTRIBSEMAIL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSEMAIL/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes of messages entered in e-mail areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=AREAISEMAIL><kw/AREAISEMAIL/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSFRQ>
|
|
<head>
|
|
ATTRIBSFRQ
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSFRQ/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the attributes to use for messages generated with the file
|
|
request function.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/FRQ/ <gi/LOC/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Suggested attributes are: <gi/PVT/ <gi>K/S</gi> <gi/CRA/.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>,
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=FRQEXT><kw/FRQEXT/</ref>,
|
|
<ref target=FRQNODEMAP><kw/FRQNODEMAP/</ref>,
|
|
<ref target=FRQOPTIONS><kw/FRQOPTIONS/</ref>,
|
|
<ref target=FRQWAZOO><kw/FRQWAZOO/</ref>,
|
|
<ref target=OUTBOUNDPATH><kw/OUTBOUNDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSLOCAL>
|
|
<head>
|
|
ATTRIBSLOCAL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSLOCAL/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes of messages entered in local areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSNET>
|
|
<head>
|
|
ATTRIBSNET
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSNET/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes of messages entered in netmail areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CTRLINFONET><kw/CTRLINFONET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBSNEWS>
|
|
<head>
|
|
ATTRIBSNEWS
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBSNEWS/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes of messages entered in news groups.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<gi/LOC/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=ATTRIBUTES>
|
|
<head>
|
|
ATTRIBUTES
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/ATTRIBUTES/ <ident/<attributes>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default attributes for area members of the current
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Available <ident/attributes/ are described in the
|
|
<ptr target=MESSAGEATTRS> chapter.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword is valid <hi/ONLY/ in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=ADDRESSMACRO><kw/ADDRESSMACRO/</ref>,
|
|
<ref target=AREA><kw/AREA/</ref>,
|
|
<ref target=AREADEF><kw/AREADEF/</ref>,
|
|
<ref target=AREADESC><kw/AREADESC/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=ATTRIBSCC><kw/ATTRIBSCC/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=ATTRIBSFRQ><kw/ATTRIBSFRQ/</ref>,
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=ATTRIBSNET><kw/ATTRIBSNET/</ref>,
|
|
<ref target=ATTRIBSNEWS><kw/ATTRIBSNEWS/</ref>,
|
|
<ref target=CTRLINFO><kw/CTRLINFO/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=BEEPCOMMENT>
|
|
<head>
|
|
BEEPCOMMENT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/BEEPCOMMENT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword enables or disables noise when the cursor in the
|
|
internal editor is moved across a word defined with the
|
|
<ref target=EDITCOMMENT><kw/EDITCOMMENT/</ref> keyword.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will make a noise, otherwise will not.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>,
|
|
<ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>,
|
|
<ref target=BEEPNOISES><kw/BEEPNOISES/</ref>,
|
|
<ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>,
|
|
<ref target=EDITCOMMENT><kw/EDITCOMMENT/</ref>,
|
|
<ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>,
|
|
<ref target=SOUNDPATH><kw/SOUNDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=BEEPFACTOR>
|
|
<head>
|
|
BEEPFACTOR
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/BEEPFACTOR/ <ident/<value>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows to change the noise speed made by the
|
|
<ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>,
|
|
<ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>,
|
|
<ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>,
|
|
<ref target=EVENT><kw/EVENT/</ref>, and
|
|
<ref target=PLAY><kw/PLAY/</ref> keywords.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/value/ specifies the constant to be used in noise speed
|
|
calculation.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/1000/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword is valid <hi/ONLY/ in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>,
|
|
<ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>,
|
|
<ref target=BEEPNOISES><kw/BEEPNOISES/</ref>,
|
|
<ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>,
|
|
<ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=BEEPLOCALMSG>
|
|
<head>
|
|
BEEPLOCALMSG
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/BEEPLOCALMSG/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword enables or disables noise when <name/GoldED+/ finds a
|
|
message with the <gi/LOC/ attribute set. This can be useful for the
|
|
sysop who wants to monitor the messages entered by users on his/her
|
|
<abbr/BBS/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will make a noise, otherwise will not.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>,
|
|
<ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>,
|
|
<ref target=BEEPNOISES><kw/BEEPNOISES/</ref>,
|
|
<ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>,
|
|
<ref target=DISPLOCALHIGH><kw/DISPLOCALHIGH/</ref>,
|
|
<ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>,
|
|
<ref target=SOUNDPATH><kw/SOUNDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=BEEPNOISES>
|
|
<head>
|
|
BEEPNOISES
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/BEEPNOISES/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This is the <hi/master switch/ for all noises in <name/GoldED+/. The
|
|
<code/-m/ commandline switch overrides this option.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will make a noises, otherwise will keep
|
|
silence.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=COMMANDLINE> chapter,
|
|
<ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>,
|
|
<ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>,
|
|
<ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>,
|
|
<ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>,
|
|
<ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>,
|
|
<ref target=SOUNDPATH><kw/SOUNDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=BEEPYOURMAIL>
|
|
<head>
|
|
BEEPYOURMAIL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/BEEPYOURMAIL/ <ident><YES/NO/ALWAYS></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword enables or disables noise when <name/GoldED+/ finds a
|
|
message to one of your <ref target=USERNAME><kw/USERNAME/</ref>'s.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, <name/GoldED+/ will make a noise if it finds
|
|
a non-received message. If set to <ident/ALWAYS/, <name/GoldED+/ will
|
|
make the noise even if it has already been marked as received.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=BEEPCOMMENT><kw/BEEPCOMMENT/</ref>,
|
|
<ref target=BEEPFACTOR><kw/BEEPFACTOR/</ref>,
|
|
<ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>,
|
|
<ref target=BEEPNOISES><kw/BEEPNOISES/</ref>,
|
|
<ref target=EVENT><kw/EVENT/</ref>, <ref target=PLAY><kw/PLAY/</ref>,
|
|
<ref target=SOUNDPATH><kw/SOUNDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CARBONCOPYLIST>
|
|
<head>
|
|
CARBONCOPYLIST
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CARBONCOPYLIST/
|
|
<ident><KEEP/NAMES/VISIBLE/HIDDEN/REMOVE></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword specifies the format of the carbon copy list, as it will
|
|
look after processing. You can also change the format in the
|
|
<abbr/CC/ menu before processing.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The list specification items have the following meaning:
|
|
<table rows=5 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/KEEP/
|
|
</cell>
|
|
<cell>
|
|
Keep the list as entered
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NAMES/
|
|
</cell>
|
|
<cell>
|
|
Convert list to <q/CC: Name, Name, Name../ format
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/VISIBLE/
|
|
</cell>
|
|
<cell>
|
|
Convert list to <q/CC: Name Address/ format
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/HIDDEN/
|
|
</cell>
|
|
<cell>
|
|
Convert list to <q/^ACC: Name Address/ format
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/REMOVE/
|
|
</cell>
|
|
<cell>
|
|
Remove the list completely
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NAMES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! -->Carbon Copy and Crossposting chapter,
|
|
<ref target=CROSSPOSTLIST><kw/CROSSPOSTLIST/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=COLOR>
|
|
<head>
|
|
COLOR
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/COLOR/ <ident/<colorspec>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Using this keyword you can define or redefine all the colors used
|
|
in <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The detailed description for <kw/COLOR/ parameters provided in
|
|
<ptr target=COLORCONFIG> chapter.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=COLORCONFIG> chapter,
|
|
<ref target=COLORSET><kw/COLORSET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=COLORSET>
|
|
<head>
|
|
COLORSET
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/COLORSET/ <ident><NORMAL/INTENSE/MONO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Three color setups are built-in, and can be selected with this
|
|
keyword.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/NORMAL/ scheme has all black background, with bright
|
|
neon-like colors for the window frames. The <ident/INTENSE/ scheme
|
|
has all bright white background (this achieved by switching off the
|
|
<q/blink/ attribute, thereby enabling the use of intense (bright)
|
|
colors for the background (<ident/paper/) colors as well as the
|
|
foreground (<ident/ink/) colors). The <ident/MONO/ scheme is
|
|
optimized for the monochrome adapters.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
If color video adapter is detected then <ident/NORMAL/ color scheme
|
|
used, otherwise <ident/MONO/ scheme.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=COLORCONFIG> chapter,
|
|
<ref target=COLOR><kw/COLOR/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CONFIRMFILE>
|
|
<head>
|
|
CONFIRMFILE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CONFIRMFILE/ <ident/<filename>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
<name/GoldED+/ supports the Confirmation Receipt attribute, as used
|
|
in FrontDoor 2.xx with the <gi/FLAGS CFM/ kludge. If <name/GoldED+/
|
|
finds an unreceived message to one of your
|
|
<ref target=USERNAME><kw/USERNAME/</ref>'s with the <gi/CFM/ (or
|
|
<gi/RRQ/) attribute set, it generates an automatic response message
|
|
from the content of the <kw/CONFIRMFILE/. In the file you can use
|
|
many of the template tokens to personalize the automatic message.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/filename/ specifies the name of the template file used
|
|
for the response message generation.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<code/golded.cfm/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ptr target=MESSAGETEMPLATE> chapter,
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>,
|
|
<ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CONFIRMRESPONSE>
|
|
<head>
|
|
CONFIRMRESPONSE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CONFIRMRESPONSE/ <ident><YES/NO/ASK></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
An unreceived message to you with the CFM attribute set tells
|
|
<name/GoldED+/ that the sender has requested a receipt that you have
|
|
read the message. With this keyword you tell <name/GoldED+/ what to
|
|
do when such a message is found.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<ident/YES/ tells <name/GoldED+/ to always automatically generate the
|
|
receipt, <ident/NO/ cause to always ignore the requests, and if set
|
|
to <ident/ASK/ you will be prompted in each case.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/ASK/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>,
|
|
<ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>,
|
|
<ref target=RCVDISABLESCFM><kw/RCVDISABLESCFM/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
COOKIEPATH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/COOKIEPATH/ <ident/<path>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Defines the default path for the <!-- FIX ME!!! --><kw/@random/
|
|
template token.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The default <ident/path/ for the <!-- FIX ME!!! --><kw/@random/
|
|
template token.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ref target=GOLDPATH><kw/GOLDPATH/</ref>
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGETEMPLATE> chapter,
|
|
<ref target=GOLDPATH><kw/GOLDPATH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CROSSPOST>
|
|
<head>
|
|
CROSSPOST
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CROSSPOST/ <ident><YES/NO/ASK></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword configure prompt appearance when saving message which
|
|
contains crosspost tokens in the body.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<ident/YES/ tells <name/GoldED+/ to always automatically process
|
|
crosspost tokens, <ident/NO/ cause to always ignore them, and if set
|
|
to <ident/ASK/ you will be prompted in each case.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/ASK/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=CROSSPOSTLIST><kw/CROSSPOSTLIST/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CROSSPOSTLIST>
|
|
<head>
|
|
CROSSPOSTLIST
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CROSSPOSTLIST/
|
|
<ident><RAW/VERBOSE/YES/NONE></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword specifies the format of the crosspost list, as it will
|
|
look after processing. You can also change the format in the
|
|
<ref target=CROSSPOST><kw/CROSSPOST/</ref> menu before processing
|
|
(if menu enabled).
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The list specification items have the following meaning:
|
|
<table rows=4 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/RAW/
|
|
</cell>
|
|
<cell>
|
|
Keep the list as entered
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/VERBOSE/
|
|
</cell>
|
|
<cell>
|
|
Change the list to lines of "* Crossposted in ..."
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/YES/
|
|
</cell>
|
|
<cell>
|
|
Same as above, but expand echolist in line rather than in
|
|
column
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NONE/
|
|
</cell>
|
|
<cell>
|
|
Crosspost without a list in the msgs
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/VERBOSE/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! -->Carbon Copy and Crossposting chapter,
|
|
<ref target=CARBONCOPYLIST><kw/CARBONCOPYLIST/</ref>,
|
|
<ref target=CROSSPOST><kw/CROSSPOST/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CTRLINFO>
|
|
<head>
|
|
CTRLINFO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CTRLINFO/ <ident><YES/NO/TEARLINE,ORIGIN></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies if you want a tearline and/or origin in your messages.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The tokens have the following meaning:
|
|
<table rows=4 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/YES/
|
|
</cell>
|
|
<cell>
|
|
Enable both tearline and origin
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NO/
|
|
</cell>
|
|
<cell>
|
|
Disable all control info
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/TEARLINE/
|
|
</cell>
|
|
<cell>
|
|
Enable tearline, can be used with <ident/ORIGIN/
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/ORIGIN/
|
|
</cell>
|
|
<cell>
|
|
Enable origin, can be used with <ident/TEARLINE/
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword is valid <hi/ONLY/ in a
|
|
<ref target=RANDOMSYSTEM>Random System</ref> group.<lb>
|
|
This may be helpful for <abbr/QWK/ users, who can create a group for
|
|
the <abbr/QWK/ areas and disable <kw/CTRLINFO/ there.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>,
|
|
<ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>,
|
|
<ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>,
|
|
<ref target=CTRLINFONET><kw/CTRLINFONET/</ref>,
|
|
<ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>,
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref>,
|
|
<ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>,
|
|
<ref target=TEARLINE><kw/TEARLINE/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg>
|
|
CTRLINFO YES ; Add both tearline and origin
|
|
CTRLINFO TEARLINE ORIGIN ; Same as above in other words
|
|
CTRLINFO TEARLINE ; Add only a tearline
|
|
CTRLINFO ORIGIN ; Add only an origin</eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CTRLINFOECHO>
|
|
<head>
|
|
CTRLINFOECHO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CTRLINFOECHO/ <ident><YES/NO/TEARLINE,ORIGIN></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies if you want a tearline and/or origin in your echomail
|
|
messages.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The tokens have the following meaning:
|
|
<table rows=4 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/YES/
|
|
</cell>
|
|
<cell>
|
|
Enable both tearline and origin
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NO/
|
|
</cell>
|
|
<cell>
|
|
Disable all control info
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/TEARLINE/
|
|
</cell>
|
|
<cell>
|
|
Enable tearline, can be used with <ident/ORIGIN/
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/ORIGIN/
|
|
</cell>
|
|
<cell>
|
|
Enable origin, can be used with <ident/TEARLINE/
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Changing the default may cause unpredictable behaviour with some
|
|
echomail processors so it is not recommended to change it.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>,
|
|
<ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>,
|
|
<ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>,
|
|
<ref target=CTRLINFONET><kw/CTRLINFONET/</ref>,
|
|
<ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>,
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref>,
|
|
<ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>,
|
|
<ref target=TEARLINE><kw/TEARLINE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CTRLINFOEMAIL>
|
|
<head>
|
|
CTRLINFOEMAIL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CTRLINFOEMAIL/ <ident><YES/NO/TEARLINE,ORIGIN></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies if you want a tearline and/or origin in your
|
|
<name/Internet/ e-mail messages. This is not recommended.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The tokens have the following meaning:
|
|
<table rows=4 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/YES/
|
|
</cell>
|
|
<cell>
|
|
Enable both tearline and origin
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NO/
|
|
</cell>
|
|
<cell>
|
|
Disable all control info
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/TEARLINE/
|
|
</cell>
|
|
<cell>
|
|
Enable tearline, can be used with <ident/ORIGIN/
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/ORIGIN/
|
|
</cell>
|
|
<cell>
|
|
Enable origin, can be used with <ident/TEARLINE/
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Changing the default is not recommended.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTRIBSEMAIL><kw/ATTRIBSEMAIL/</ref>,
|
|
<ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>,
|
|
<ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>,
|
|
<ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>,
|
|
<ref target=CTRLINFONET><kw/CTRLINFONET/</ref>,
|
|
<ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>,
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref>,
|
|
<ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>,
|
|
<ref target=TEARLINE><kw/TEARLINE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CTRLINFOLOCAL>
|
|
<head>
|
|
CTRLINFOLOCAL
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CTRLINFOLOCAL/ <ident><YES/NO/TEARLINE,ORIGIN></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies if you want tearline and origin in your messages in
|
|
local areas.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The tokens have the following meaning:
|
|
<table rows=4 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/YES/
|
|
</cell>
|
|
<cell>
|
|
Enable both tearline and origin
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NO/
|
|
</cell>
|
|
<cell>
|
|
Disable all control info
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/TEARLINE/
|
|
</cell>
|
|
<cell>
|
|
Enable tearline, can be used with <ident/ORIGIN/
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/ORIGIN/
|
|
</cell>
|
|
<cell>
|
|
Enable origin, can be used with <ident/TEARLINE/
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
In local areas, the tearline and origin is normally never required
|
|
but can be used for cosmetic purposes.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTRIBSLOCAL><kw/ATTRIBSLOCAL/</ref>,
|
|
<ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>,
|
|
<ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>,
|
|
<ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>,
|
|
<ref target=CTRLINFONET><kw/CTRLINFONET/</ref>,
|
|
<ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>,
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref>,
|
|
<ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>,
|
|
<ref target=TEARLINE><kw/TEARLINE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CTRLINFONET>
|
|
<head>
|
|
CTRLINFONET
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CTRLINFONET/ <ident><YES/NO/TEARLINE,ORIGIN></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies if you want tearline and origin in your netmail messages.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The tokens have the following meaning:
|
|
<table rows=4 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/YES/
|
|
</cell>
|
|
<cell>
|
|
Enable both tearline and origin
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NO/
|
|
</cell>
|
|
<cell>
|
|
Disable all control info
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/TEARLINE/
|
|
</cell>
|
|
<cell>
|
|
Enable tearline, can be used with <ident/ORIGIN/
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/ORIGIN/
|
|
</cell>
|
|
<cell>
|
|
Enable origin, can be used with <ident/TEARLINE/
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/TEARLINE/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
In netmail areas, the tearline and origin is normally never required
|
|
but can be used for cosmetic purposes. Some robots reqire tearline
|
|
in the message.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>,
|
|
<ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>,
|
|
<ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>,
|
|
<ref target=CTRLINFONET><kw/CTRLINFONET/</ref>,
|
|
<ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>,
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref>,
|
|
<ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>,
|
|
<ref target=TEARLINE><kw/TEARLINE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=CTRLINFONEWS>
|
|
<head>
|
|
CTRLINFONEWS
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/CTRLINFONEWS/ <ident><YES/NO/TEARLINE,ORIGIN></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies if you want a tearline and/or origin in your
|
|
<name/Internet/ news articles.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The tokens have the following meaning:
|
|
<table rows=4 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/YES/
|
|
</cell>
|
|
<cell>
|
|
Enable both tearline and origin
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NO/
|
|
</cell>
|
|
<cell>
|
|
Disable all control info
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/TEARLINE/
|
|
</cell>
|
|
<cell>
|
|
Enable tearline, can be used with <ident/ORIGIN/
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/ORIGIN/
|
|
</cell>
|
|
<cell>
|
|
Enable origin, can be used with <ident/TEARLINE/
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Changing the default is not recommended.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTRIBSECHO><kw/ATTRIBSECHO/</ref>,
|
|
<ref target=CTRLINFOECHO><kw/CTRLINFOECHO/</ref>,
|
|
<ref target=CTRLINFOEMAIL><kw/CTRLINFOEMAIL/</ref>,
|
|
<ref target=CTRLINFOLOCAL><kw/CTRLINFOLOCAL/</ref>,
|
|
<ref target=CTRLINFONET><kw/CTRLINFONET/</ref>,
|
|
<ref target=CTRLINFONEWS><kw/CTRLINFONEWS/</ref>,
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref>,
|
|
<ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>,
|
|
<ref target=TEARLINE><kw/TEARLINE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPAREANO>
|
|
<head>
|
|
DISPAREANO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPAREANO/ <ident><YES/NO/ALWAYS></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword specifies if <name/GoldED+/ should display the area
|
|
number on the top line in the reader. The area number is the same as
|
|
that displayed in the leftmost column in the arealist. This also
|
|
means that the number displayed can be either the board number
|
|
(Hudson/Goldbase/Ezycom board) or the standard sequential number.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
When set to <ident/YES/ <name/GoldED+/ displays area number only if
|
|
non-zero, setting to <ident/NO/ disables display at all, and
|
|
<ident/ALWAYS/ forces to display the area number in any case.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTNOS><kw/AREALISTNOS/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPATTACHSIZE>
|
|
<head>
|
|
DISPATTACHSIZE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPATTACHSIZE/ <ident><BYTES/KBYTES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Controls how the size of attached files is displayed in the header.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The following options are provided: the exact size in <ident/BYTES/,
|
|
the rounded size in <ident/KBYTES/, or <ident/NO/ display at all.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/KBYTES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
If the <ident/KBYTES/ setting is chosen, the value is rounded
|
|
according to the following formula: kbytes = (bytes + 512) / 1024.
|
|
So a 600 bytes file is rounded up to <q/1k/, but a 500 bytes
|
|
file is rounded down to <q/0k/.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>,
|
|
<ref target=DISPMSGSIZE><kw/DISPMSGSIZE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPAUTONEXT>
|
|
<head>
|
|
DISPAUTONEXT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPAUTONEXT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Controls which message will be displayed when entering an area.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will automatically jump to the next
|
|
message when entering an area. Otherwise message under the lastread
|
|
pointer will be displayed.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=MSGLISTFIRST><kw/MSGLISTFIRST/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPHDRDATESET>
|
|
<head>
|
|
DISPHDRDATESET
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPHDRDATESET/ <ident/<position> <length>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies the position and length of the date field in the header
|
|
display.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Specifies the <ident/position/ and <ident/length/ of the date field
|
|
in the header display. If a negative value is specified, that value
|
|
is added to the current display width.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
-20 20
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=DISPHDRNAMESET><kw/DISPHDRNAMESET/</ref>,
|
|
<ref target=DISPHDRNODESET><kw/DISPHDRNODESET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPHDRNAMESET>
|
|
<head>
|
|
DISPHDRNAMESET
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPHDRNAMESET/ <ident/<position> <length>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specifies the position and length of the from/to name field in the
|
|
header display.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Specifies the <ident/position/ and <ident/length/ of the from/to name
|
|
field in the header display. If a negative value is specified, that
|
|
value is added to the current display width.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
8 36
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=DISPHDRDATESET><kw/DISPHDRDATESET/</ref>,
|
|
<ref target=DISPHDRNODESET><kw/DISPHDRNODESET/</ref>,
|
|
<ref target=EDITHDRNAMESET><kw/EDITHDRNAMESET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPHDRNODESET>
|
|
<head>
|
|
DISPHDRNODESET
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPHDRNODESET/ <ident/<position> <length>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Specfies the position and length of the from/to node address field in
|
|
the header display.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
Specfies the <ident/position/ and <ident/length/ of the from/to node
|
|
address field in the header display. If a negative value is
|
|
specified, that value is added to the current display width.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
44 16
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
The attributes display moves along with the <kw>DISPHDRNODESET</kw>
|
|
values.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=DISPHDRDATESET><kw/DISPHDRDATESET/</ref>,
|
|
<ref target=DISPHDRNAMESET><kw/DISPHDRNAMESET/</ref>,
|
|
<ref target=EDITHDRNODESET><kw/EDITHDRNODESET/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPLISTCURSOR>
|
|
<head>
|
|
DISPLISTCURSOR
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPLISTCURSOR/
|
|
<ident><TOP/NEARTOP/MIDDLE/NEARBOTTOM/BOTTOM></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Selects the starting position of selection bar in the message list
|
|
and nodelist browsers.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
<table rows=5 cols=2>
|
|
<row>
|
|
<cell>
|
|
<ident/TOP/
|
|
</cell>
|
|
<cell>
|
|
At the top if possible
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NEARTOP/
|
|
</cell>
|
|
<cell>
|
|
At top + 1/3 if possible
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/MIDDLE/
|
|
</cell>
|
|
<cell>
|
|
At middle of possible
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/NEARBOTTOM/
|
|
</cell>
|
|
<cell>
|
|
At bottom - 1/3
|
|
</cell>
|
|
</row>
|
|
<row>
|
|
<cell>
|
|
<ident/BOTTOM/
|
|
</cell>
|
|
<cell>
|
|
At bottom
|
|
</cell>
|
|
</row>
|
|
</table>
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/MIDDLE/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPLISTWRAP>
|
|
<head>
|
|
DISPLISTWRAP
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPLISTWRAP/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Enables or disables wrap-around when the selection bar in the main
|
|
list/browser windows reaches the top or bottom.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, <name/GoldED+/ will wrap-around when the
|
|
selection bar in the main list/browser windows reaches the top or
|
|
bottom. If set to <ident/NO/, the selection bar will stop at the
|
|
top or bottom when reaches them.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPLOCALHIGH>
|
|
<head>
|
|
DISPLOCALHIGH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPLOCALHIGH/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ will display the
|
|
<gi/FROM/ name with the highlight color if a message has the
|
|
<gi/LOC/ attribute set.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will display the <gi/FROM/ name with the
|
|
highlight color if a message has the <gi/LOC/ attribute set,
|
|
otherwise will not.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=BEEPLOCALMSG><kw/BEEPLOCALMSG/</ref>,
|
|
<ref target=BEEPYOURMAIL><kw/BEEPYOURMAIL/</ref>,
|
|
<ref target=COLOR><kw/COLOR/</ref>,
|
|
<ref target=HIGHLIGHTUNREAD><kw/HIGHLIGHTUNREAD/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPMARGIN>
|
|
<head>
|
|
DISPMARGIN
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPMARGIN/ <ident/<width>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines the right margin (display width) used for
|
|
message display.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If the <ident/width/ is 0 (zero), <name/GoldED+/ will default to the
|
|
current screen width. If a negative value is specified, that value
|
|
will be added to the current screen width (thereby decreasing the
|
|
display width relative to the screen width).
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
0
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
If the <ref target=DISPPAGEBAR><kw/DISPPAGEBAR/</ref> keyword is
|
|
enabled, the right margin is automatically decreased by one char.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! -->READdecreasemargin,
|
|
<!-- FIX ME!!! -->READincreasemargin,
|
|
<ref target=DISPPAGEBAR><kw/DISPPAGEBAR/</ref>,
|
|
<ref target=EDITQUOTEMARGIN><kw/EDITQUOTEMARGIN/</ref>,
|
|
<ref target=PRINTMARGIN><kw/PRINTMARGIN/</ref>,
|
|
<ref target=QUOTEMARGIN><kw/QUOTEMARGIN/</ref>,
|
|
<ref target=SOUPEXPORTMARGIN><kw/SOUPEXPORTMARGIN/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPMSGSIZE>
|
|
<head>
|
|
DISPMSGSIZE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPMSGSIZE/ <ident><BYTES/KBYTES/LINES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
When enabled, this keyword displays the msgbody size in the lower
|
|
left side of the header. The size displayed is for the message body
|
|
text only, the header and NUL-terminator (and anything that may lurk
|
|
beyond it) is excluded from the calculation.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The following options are provided: the exact size in <ident/BYTES/,
|
|
the rounded size in <ident/KBYTES/, the number of <ident/LINES/, or
|
|
<ident/NO/ display at all.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/BYTES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This feature only works when <hi/reading/ messages. While editing a
|
|
message in the internal editor, this feature is disabled - however,
|
|
the size will be displayed when you are in the save message menu
|
|
(if <ref target=EDITSAVEMENU><kw/EDITSAVEMENU/</ref> is enabled).<lb>
|
|
If the <ident/KBYTES/ setting is chosen, the value is rounded
|
|
according to the following formula: kbytes = (bytes + 512) / 1024.
|
|
So a 600 bytes file is rounded up to <q/1k/, but a 500 bytes
|
|
file is rounded down to <q/0k/.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=DISPATTACHSIZE><kw/DISPATTACHSIZE/</ref>,
|
|
<ref target=EDITSAVEMENU><kw/EDITSAVEMENU/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPPAGEBAR>
|
|
<head>
|
|
DISPPAGEBAR
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPPAGEBAR/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
If enabled, a <q/pagebar/ (similar to the scrollbar in GUI's) will
|
|
appear on the right margin, telling you about the relative size
|
|
and position in the message you are reading.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will display the pagebar, otherwise will
|
|
not.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Pagebar is only displayed if a message is longer than a
|
|
screenful.<lb>
|
|
The pagebar automatically decreases the
|
|
<ref target=DISPMARGIN><kw/DISPMARGIN/</ref> by one char.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=AREALISTPAGEBAR><kw/AREALISTPAGEBAR/</ref>,
|
|
<ref target=DISPMARGIN><kw/DISPMARGIN/</ref>,
|
|
<ref target=FILELISTPAGEBAR><kw/FILELISTPAGEBAR/</ref>,
|
|
<ref target=MSGLISTPAGEBAR><kw/MSGLISTPAGEBAR/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPREALMSGNO>
|
|
<head>
|
|
DISPREALMSGNO
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPREALMSGNO/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls how the <name/GoldED+/ displays message number
|
|
in the message reader.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/ the actual (real) message numbers will be
|
|
displayed. When set to <ident/NO/, <name/GoldED+/ will display
|
|
<q/relative/ numbers, which are always sequential from msg number 1.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Normally the relative numbers are best, because they reflect the
|
|
actual number of messages in the system.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! -->READtogglerealmsgno
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPSOFTCR>
|
|
<head>
|
|
DISPSOFTCR
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSOFTCR/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This option controls how <name/GoldED+/ will process the so-called
|
|
<gi/Soft-CR/ character (<name/ASCII/ 141, hexadecimal 8Dh) when
|
|
display message containing this character.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If enabled, <name/GoldED+/ will treat the <gi/Soft-CR/ character just
|
|
like any other displayable character, instead of ignoring it like
|
|
linefeed chars.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
Enabling this feature is <hi/mandatory/ to make
|
|
<ref target=EDITSOFTCRXLAT><kw/EDITSOFTCRXLAT/</ref> feature
|
|
working.<lb>
|
|
The <name/Ezycom/ message base format requires the <gi/Soft-CR/ to
|
|
terminate each line. Therefore this feature is unlikely to be useful
|
|
to <name/Ezycom/ sysops.<lb>
|
|
The similar functionality may be obtained by defining translation
|
|
table with <gi/Soft-CR/ translated to the space character. This may
|
|
be useful if you need different settings for the different areas.<lb>
|
|
Note that by enabling this feature, you <hi/disable/ the character
|
|
translation feature that uses the <gi/Soft-CR/ as an escape character
|
|
(this applies only to so-called <q/COMPOSED/ charset).
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=EDITSOFTCRXLAT><kw/EDITSOFTCRXLAT/</ref>,
|
|
<ref target=XLATIMPORT><kw/XLATIMPORT/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPSTATUSLINE>
|
|
<head>
|
|
DISPSTATUSLINE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DISPTABSIZE>
|
|
<head>
|
|
DISPTABSIZE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPTABSIZE/ <ident/<size>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines the tab size (number of spaces) used when
|
|
displaying the tab (<name/ASCII/ 9) character, when pressing
|
|
keys assigned to <!-- FIX ME!!! -->EDITtab and
|
|
<!-- FIX ME!!! -->EDITtabreverse, and when importing external data
|
|
in the internal editor.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/size/ specifies tab width in the characters.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
8
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
If you use an external editor, you should switch it to create spaces
|
|
instead of tabs, because tabs are technically not allowed in
|
|
<name/FidoNet/ technology messages.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! -->EDITimportquotebuf,
|
|
<!-- FIX ME!!! -->EDITimporttext,
|
|
<!-- FIX ME!!! -->EDITpaste,
|
|
<!-- FIX ME!!! -->EDITtab,
|
|
<!-- FIX ME!!! -->EDITtabreverse
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=DOSPROMPT>
|
|
<head>
|
|
DOSPROMPT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DOSPROMPT/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
Controls whether <name/GoldED+/ should add a message about itself to
|
|
the operating system shell prompt when shelling out.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, the <name/GoldED+/ will add the message
|
|
defined with <ref target=LOADLANGUAGE><kw/MS_PROMPT/</ref> keyword in
|
|
the language configuration file to the system shell.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Bugs:
|
|
</label>
|
|
<item>
|
|
This feature is known to be broken on some platforms.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! -->AREAdosshell,
|
|
<!-- FIX ME!!! -->EDITdosshell,
|
|
<!-- FIX ME!!! -->FILEdosshell,
|
|
<!-- FIX ME!!! -->LISTdosshell,
|
|
<!-- FIX ME!!! -->NODEdosshell,
|
|
<!-- FIX ME!!! -->READdosshell,
|
|
<ref target=EVENT><kw/EVENT/</ref>,
|
|
<ref target=LOADLANGUAGE><kw/LOADLANGUAGE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITAUTOATTACH>
|
|
<head>
|
|
EDITAUTOATTACH
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITAUTOATTACH/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
If you use drivespec (<code/C:/, <code/D:/, etc.) in the subject in
|
|
a netmail message, <name/GoldED+/ can automatically turn on the file
|
|
attach attribute. Autoattaching only works if the subject has been
|
|
edited, so that subject files will not automatically be re-attached
|
|
in replies.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/ this feature is enabled, otherwise disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=ATTACHPATH><kw/ATTACHPATH/</ref>,
|
|
<ref target=ATTRIBSATTACH><kw/ATTRIBSATTACH/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITAUTOSAVE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITAUTOSAVE/ <ident/<seconds>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword provides the way for keeping automatic backup of the
|
|
message you are writing. The saved file can be restored with the
|
|
<!-- FIX ME --><kw/EDITloadfile/ command. The name of the saved file
|
|
is defined with the <ref target=EDITORFILE><kw/EDITORFILE/</ref>
|
|
keyword.<lb>
|
|
If disaster strikes (crash, lockup, power blackout, etc.) while
|
|
you are writing a message in the internal editor, this feature
|
|
lets you continue from the last autosaved message, which will
|
|
popup automatically when you enter the internal editor again.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If a non-zero value is given, the internal editor will automatically
|
|
execute the <!-- FIX ME!!! --><kw/EDITsavefile/ function with
|
|
intervals of <ident/seconds/.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
30
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This feature only works 100% if
|
|
<ref target=KEYBMODE><kw/KEYBMODE/</ref> is set to <ident/POLL/.
|
|
If <ref target=KEYBMODE><kw/KEYBMODE/</ref> is set to <ident/BLOCK/,
|
|
autosave won't happen until you press a key after the interval has
|
|
passed.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/EDITloadfile/,
|
|
<!-- FIX ME!!! --><kw/EDITsavefile/,
|
|
<ref target=EDITORFILE><kw/EDITORFILE/</ref>,
|
|
<ref target=KEYBMODE><kw/KEYBMODE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITCHANGEDATE>
|
|
<head>
|
|
EDITCHANGEDATE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITCHANGEDATE/ <ident><ALWAYS/YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls whether <name/GoldED+/ should change the date
|
|
timestamp of the changed message.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/ALWAYS/, <name/GoldED+/ will always <q/touch/ the
|
|
message date in the header after saving it. If set to <ident/YES/,
|
|
<name/GoldED+/ will only <q/touch/ the message date in the header,
|
|
if you change a message written by yourself. This is useful in cases
|
|
such as when you need to edit messages written by other people
|
|
which may be mis-addressed or something without messing up the date.
|
|
If set to <ident/NO/, the message date is not changed when changing a
|
|
message.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! -->READchangemsg
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITCHARPARA>
|
|
<head>
|
|
EDITCHARPARA
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITCHARPARA/ <ident/[']<char>[']/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines the character <name/GoldED+/ will display at the
|
|
end of paragraphs in the internal editor. This is where the <gi/CR/
|
|
character will be placed once the msg is saved.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/char/ defines the character <name/GoldED+/ will display at
|
|
the end of paragraphs in the internal editor. The space character
|
|
should be enclosed in quotes.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/' '/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword is primarily for debugging, the suggested replacement
|
|
is a paragraph sign (<name/ASCII/ 20).
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=EDITCHARSPACE><kw/EDITCHARSPACE/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITCHARSPACE>
|
|
<head>
|
|
EDITCHARSPACE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITCHARSPACE/ <ident/[']<char>[']/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword defines the character <name/GoldED+/ will display
|
|
instead of a space character in the internal editor.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/char/ defines the character <name/GoldED+/ will display
|
|
instead of a space character in the internal editor. The space
|
|
character should be enclosed in quotes.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/' '/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This keyword is primarily for debugging, the suggested replacement
|
|
is a small dot (CP437 250).
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=EDITCHARPARA><kw/EDITCHARPARA/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITCOMMENT>
|
|
<head>
|
|
EDITCOMMENT
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITCOMMENT/ <ident><<![ CDATA ["word"]]>>
|
|
<<![ CDATA ["comment"]]>></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This feature allows you to define words which causes <name/GoldED+/
|
|
to display a comment in the statusline, when you place the cursor on
|
|
the word in the internal editor.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/word/ defines the substring which should cause displaying
|
|
of the <ident/comment/ in the statusline.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=DISPSTATUSLINE><kw/DISPSTATUSLINE/</ref>,
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg><![ CDATA [
|
|
EDITCOMMENT ":-(" "Don't worry, be happy!"
|
|
EDITCOMMENT ":-)" "Are we having fun yet?"
|
|
EDITCOMMENT ";-)" "Wink wink, nudge nugde..."
|
|
EDITCOMMENT "!!!" "Flame Warning!"
|
|
EDITCOMMENT "GoldED" "Great program, isn't it?"
|
|
EDITCOMMENT "Odin" "One more 'n' please."
|
|
EDITCOMMENT "Odinn" "That's right :-)"]]></eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITCOMPLETION
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITCOMPLETION/ <ident><<![ CDATA ["abbreviation"]]>>
|
|
<<![ CDATA ["completion"]]>></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword allows you to define abbreviations which will be
|
|
automatically expanded to full words or sentences when typed in
|
|
the internal editor.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/abbreviation/ defines the substring which should will be
|
|
automatically expanded to <ident/completion/.
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
The abbreviation is case-sensitive. If <![ CDATA ["XX"]]> is defined
|
|
as an abbreviation, completion will <b/not/ be triggered if
|
|
<![ CDATA ["xx"]]> is typed.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<!-- FIX ME!!! --><kw/Macro/,
|
|
<!-- FIX ME!!! --><kw/EDITmacro/,
|
|
<ref target=DISPSTATUSLINE><kw/DISPSTATUSLINE/</ref>,
|
|
<ref target=EDITCOMMENT><kw/EDITCOMMENT/</ref>
|
|
</item>
|
|
<label>
|
|
Example:
|
|
</label>
|
|
<item><eg><![ CDATA [
|
|
EDITCOMPLETION "/Odin" "Odinn"
|
|
EDITCOMPLETION "/GED" "GoldED"
|
|
EDITCOMPLETION "/V7" "Version 7"
|
|
EDITCOMPLETION "/FD" "FrontDoor"
|
|
EDITCOMPLETION "/WfW" "Windows for Workgroups"]]></eg>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITCRLFTERM
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITCRLFTERM/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls the format to be used for the paragraph line
|
|
termination.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, all text paragraphs in your messages will be
|
|
terminated with a <gi>CR/LF</gi> combination. If set to <ident/NO/,
|
|
only a single <gi/CR/ is used.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/NO/
|
|
</item>
|
|
<label>
|
|
Notes:
|
|
</label>
|
|
<item>
|
|
This option was created to fix a problem with an older version of the
|
|
<name/Dutchie/ mail processor, that apparently needed the
|
|
<gi>CR/LF</gi> termination of kludge lines.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITFIELDCLEAR
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/EDITFIELDCLEAR/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls the behaviour of the input-fields, if a
|
|
non-edit key is the first key pressed.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/YES/, the input-fields will be automatically cleared
|
|
for new entry, if a non-edit key is the first key pressed.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
|
|
|
|
<!-- finished here -->
|
|
|
|
|
|
<div2>
|
|
<head>
|
|
EDITHARDLINE <string>
|
|
</head>
|
|
<p>
|
|
("<<")
|
|
</p>
|
|
<p>
|
|
The string is needed if you use an external editor that terminates
|
|
all lines with a CR or CR/LF. The hardline string acts as a text
|
|
paragraph terminator, and the normal CR's are ignored.
|
|
</p>
|
|
<p>
|
|
The concept of "hardlines" is explained in the Hardline Feature
|
|
chapter.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITHARDLINES <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
This keyword enables the "hardline" feature. If disabled, the
|
|
<kw>EDITHARDLINE</kw> 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.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITHARDTERM>
|
|
<head>
|
|
EDITHARDTERM <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will hard-terminate all lines in your messages
|
|
at the editor margin. It is recommended to enable this keyword for
|
|
Internet e-mail and newsgroups, because some user-unfriendly
|
|
Internet software does not wrap long lines properly. But DON'T
|
|
enable it in normal FidoNet echomail.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
<ref target=DISPMARGIN><kw/DISPMARGIN/</ref>,
|
|
<ref target=SOUPEXPORTMARGIN><kw/SOUPEXPORTMARGIN/</ref>
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITHDRNAMESET>
|
|
<head>
|
|
EDITHDRNAMESET <pos> <len>
|
|
</head>
|
|
<p>
|
|
(8 36)
|
|
</p>
|
|
<p>
|
|
Specfies the position and length of the from/to name field in the
|
|
header edit display. If a negative value is specified, that value
|
|
is added to the current display width.
|
|
</p>
|
|
</div2>
|
|
<div2 id=EDITHDRNODESET>
|
|
<head>
|
|
EDITHDRNODESET <pos> <len>
|
|
</head>
|
|
<p>
|
|
(44 36)
|
|
</p>
|
|
<p>
|
|
Specfies the position and length of the from/to node address field
|
|
in the header edit display. If a negative value is specified, that
|
|
value is added to the current display width.
|
|
</p>
|
|
</div2>
|
|
<div2 id=EDITHEADERATTRS>
|
|
<head>
|
|
EDITHEADERATTRS <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
This keyword allows you to turn off the large attributes window
|
|
that is shown during header edit. Even if the window is turned
|
|
off, the Alt-keys are still active for toggling attributes.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITHEADERFIRST <new,changes,replies,forwards,yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
This keyword controls the circumstances that will present you with
|
|
the header editor first of all.
|
|
</p>
|
|
<p>
|
|
New When entering a new message.
|
|
Changes When changing a message
|
|
Replies When making a reply.
|
|
Forwards When forwarding a message.
|
|
Yes Always (all of the above).
|
|
No Never.
|
|
</p>
|
|
<p>
|
|
The New, Changes, Replies and Forwards values can be combined. YES
|
|
is equivalent to enabling all four of these.
|
|
</p>
|
|
<p>
|
|
For example, we want to edit the header only when entering a new
|
|
message or when changing a message:
|
|
</p>
|
|
<p>
|
|
EDITHEADERFIRST New, Changes
|
|
</p>
|
|
<p>
|
|
If the circumstances match the setup of this keyword, the header
|
|
edit will be bypassed and you will start directly in the <kw>EDITMENU</kw>
|
|
(if enabled) or in the internal or external editor. A new menu
|
|
item has been added in the <kw>EDITSAVEMENU</kw>, "Edit Header", which
|
|
allows you to edit the header after you have written your message,
|
|
but before it is finally saved.
|
|
</p>
|
|
<p>
|
|
If you set <kw>EDITHEADERFIRST</kw> to NO, you must either have the
|
|
<kw>EDITSAVEMENU</kw> enabled, or use the internal editor, because
|
|
otherwise it is not possible to edit the header at all.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITINTERNAL <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
Specifies if the internal editor should be the default, even if an
|
|
external editor is defined. You can always change the setting in
|
|
the editor menu (if <kw>EDITMENU</kw> is enabled) before you start writing
|
|
your message.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITMENU <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
This keyword enables or disables the "Edit menu" that pops up
|
|
right after you have edited the message header. If you disable the
|
|
menu, you will go to the internal or external editor immediately
|
|
and save a keystroke, but you will of course lose the features
|
|
available from the menu, such as selection of template etc.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITMIXCASE>
|
|
<head>
|
|
EDITMIXCASE <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If this keyword is enabled, <name>GoldED+</name> will automatically format the
|
|
name with uppercase the first letter in words and lowercase the
|
|
rest, when entering names in the header.
|
|
</p>
|
|
<p>
|
|
Examples:
|
|
</p>
|
|
<p>
|
|
"odinn sorensen" or "ODINN SORENSEN"
|
|
</p>
|
|
<p>
|
|
These would be re-cased to "Odinn Sorensen".
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITOR <commandline> [@file] [@line]
|
|
</head>
|
|
<p>
|
|
With <name>GoldED+</name> 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.
|
|
</p>
|
|
<p>
|
|
If you use a word processor, be sure to make it export clean ASCII
|
|
text files without control codes.
|
|
</p>
|
|
<p>
|
|
<commandline> Program commandline.
|
|
@file Token which is replaced by the editor message
|
|
filename.
|
|
@line Token which is replaced by the @Position
|
|
template line number.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITORFILE>
|
|
<head>
|
|
EDITORFILE <file>
|
|
</head>
|
|
<p>
|
|
(GOLDED.MSG)
|
|
</p>
|
|
<p>
|
|
Defines the name of the temporary editor message file. This file
|
|
is written by <name>GoldED+</name> when swapping to the external editor, or when
|
|
using the <kw>EDITsavefile</kw> command in the internal editor.
|
|
</p>
|
|
<p>
|
|
The file is written in the GOLDPATH if there is no explicit path.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITQUOTEMARGIN>
|
|
<head>
|
|
EDITQUOTEMARGIN <margin>
|
|
</head>
|
|
<p>
|
|
(75)
|
|
</p>
|
|
<p>
|
|
Sets the right margin for editing quoted lines in the internal
|
|
editor. This should be set to the same or wider than the
|
|
<kw>QUOTEMARGIN</kw>.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITREPLYRE>
|
|
<head>
|
|
EDITREPLYRE <yes/no/numeric>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> inserts the "Re:" string in front of the
|
|
subject when you reply to a message. If not enabled, <name>GoldED+</name> will
|
|
strip any leading "Re:" when you reply to a msg.
|
|
</p>
|
|
<p>
|
|
The "Re:" string in subjects is an obsolete practice, and today it
|
|
only slows down modern replylinking software. Do yourself and
|
|
others a favor and let <name>GoldED+</name> strip the Re: in your replies.
|
|
</p>
|
|
<p>
|
|
The "numeric" option makes <name>GoldED+</name> use numeric Re:'s, of the form
|
|
"Re^n:".
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITSAVEMENU>
|
|
<head>
|
|
EDITSAVEMENU <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
This keyword enables or disables the "Save menu" that pops up
|
|
after you have edited your message in the internal or external
|
|
editor. If you disable the menu, your message will be saved (or
|
|
discarded if not edited) immediately and save you a keystroke, but
|
|
you will also lose the features available from the menu.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITSAVEUTIL <utilno> <"L menu text">
|
|
</head>
|
|
<p>
|
|
Defines the external utilities that will be added to the
|
|
<kw>EDITSAVEMENU</kw> (if enabled). The menu text is inserted in the menu.
|
|
The first two characters of the menu text are the "hotkey" letter
|
|
that will be highlighted in the menu text, plus a space. Example:
|
|
</p>
|
|
<p>
|
|
EDITSAVEUTIL 1 "S PGP Sign the msg"
|
|
EDITSAVEUTIL 2 "l PGP Clear-Sign the msg"
|
|
EDITSAVEUTIL 3 "E PGP Encrypt the msg"
|
|
EDITSAVEUTIL 4 "p PGP Encrypt & Sign the msg"
|
|
</p>
|
|
<p>
|
|
If you have changed the default language in this menu (in
|
|
GOLDLANG.CFG), then make sure the highlight letters don't clash.
|
|
</p>
|
|
<p>
|
|
With <kw>EDITSAVEUTIL</kw> definitions and <kw>EDITSAVEMENU</kw> enabled, you can
|
|
directly call an external utility to do things like encoding or
|
|
encrypting msgs before saving them.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EDITSOFTCRXLAT>
|
|
<head>
|
|
EDITSOFTCRXLAT <char>
|
|
</head>
|
|
<p>
|
|
If a translation char is defined, <name>GoldED+</name> will translate the
|
|
soft-cr character (ASCII 141, HEX 8D) while saving message to base.
|
|
The following example translates the soft-cr to an 'H' (for use in Russia):
|
|
</p>
|
|
<p>
|
|
EDITSOFTCRXLAT H
|
|
</p>
|
|
<p>
|
|
You also have to enable the <kw>DISPSOFTCR</kw> keyword.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITSPELLCHECK <commandline> [@file]
|
|
</head>
|
|
<p>
|
|
While in the internal editor, you can use the <kw>EDITspellcheck</kw>
|
|
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
|
|
<kw>EDITspellcheck</kw> command internally uses the <kw>EDITsavefile</kw> and
|
|
<kw>EDITloadfile</kw> commands.
|
|
</p>
|
|
<p>
|
|
<commandline> Spellchecker program commandline.
|
|
[@file] Token which is replaced by the message filename
|
|
(defined by the <kw>EDITORFILE</kw> keyword).
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EDITUNDELETE <lines>
|
|
</head>
|
|
<p>
|
|
(50)
|
|
</p>
|
|
<p>
|
|
This keyword defines the number of lines to keep in the undelete
|
|
buffer between messages.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EMPTYTEARLINE <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
With this keyword enabled, <name>GoldED+</name> will always strip the tearline
|
|
down to just the three dashes, "---", and instead inserts the PID
|
|
(Product IDentification) kludge line, which contains the same
|
|
information, but in a safer form in a safer place. The PID kludge
|
|
is proposed in FidoNet document FSC-0046.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ENCODEEMAILHEADERS <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
By default headers in e-mails MIME-encoded according to RFC. In
|
|
Russia it is general practice not to encode headers, so you
|
|
probably want to say No here if you're in Russia ;-) This keyword
|
|
supported only in -asa versions.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ENDGROUP
|
|
</head>
|
|
<p>
|
|
Ends a Random System <kw>GROUP</kw> definition.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EVENT>
|
|
<head>
|
|
EVENT <eventtype> <eventcommand [parameters]>
|
|
</head>
|
|
<p>
|
|
This keyword allows you to specify which soundfile to play when a
|
|
specfic event occurs. The following <eventtype>'s are defined:
|
|
</p>
|
|
<p>
|
|
EVENTTYPE TRIGGER:
|
|
</p>
|
|
<p>
|
|
Arealist When the arealist shows.
|
|
AskYesNo Any Yes/No type prompt.
|
|
Attention Warnings or information popup messages.
|
|
DosShell When entering a DOS or OS/2 shell.
|
|
EditComment When an editcomment is found.
|
|
EndOfMsgs When there are no more msgs in the area.
|
|
ErrorFatal Fatal error exit.
|
|
Exit Exit from <name>GoldED+</name>.
|
|
JobDone Successful completion of a job.
|
|
JobFailed Unsuccessful completion of a job.
|
|
MsgDeleting When deleting a msg.
|
|
MsgFromYou When a msg from you is found.
|
|
MsgIsLocal When a msg marked Local is found.
|
|
MsgIsTwit When a msg from a Twit is found.
|
|
MsgToYou When a msg to you is found.
|
|
SearchFailed Search operation failed.
|
|
SearchSuccess Search operation was successful.
|
|
Startup When the <name>GoldED+</name> startup screen shows.
|
|
</p>
|
|
<p>
|
|
There is currently only one <eventcommand> defined:
|
|
</p>
|
|
<p>
|
|
PLAY <filename.ext/beepnoise>.
|
|
</p>
|
|
<p>
|
|
The parameter to PLAY can be either a sound file or one of the
|
|
following standard beepnoises:
|
|
</p>
|
|
<p>
|
|
TheEnd A high and a low note.
|
|
GotIt Two sets of low-high notes.
|
|
TooBad A falling note.
|
|
ToYou A rising and falling note.
|
|
SayBiBi A single beep.
|
|
SOS Morse S O S (...---...).
|
|
</p>
|
|
<p>
|
|
If a sound file is specified, the sound driver must support the
|
|
format.
|
|
</p>
|
|
<p>
|
|
The DOS and 386 versions need a Goldware Sound API compatible TSR
|
|
or program loader which installs an interrupt service function on
|
|
the multiplex interrupt 2Dh. See the chapter about the Goldware
|
|
Sound API for more details. The GCTVSAPI program loader (released
|
|
separately) currently only supports the CT-VOICE.DRV driver for
|
|
.VOC files.
|
|
</p>
|
|
<p>
|
|
The OS/2 version relies on MMPM/2 (using the mciSendString API
|
|
call) to play the sound files. On my system with a Sound Blaster
|
|
Pro, MMPM/2 plays both .WAV and (to my surprise) .VOC files. It
|
|
even plays .MID files :-)
|
|
</p>
|
|
<p>
|
|
The Win32 version uses the Win32 API to play the sound files. It
|
|
should be able to play any multimedia file that Windows knows how
|
|
to handle.
|
|
</p>
|
|
<p>
|
|
Example usages:
|
|
</p>
|
|
<p>
|
|
EVENT MsgToYou PLAY HIMAN.VOC
|
|
EVENT MsgIsTwit PLAY SHOTGUN.VOC
|
|
</p>
|
|
<p>
|
|
You have to select the sounds carefully and probably with a lot of
|
|
experimentation, unless you want to turn your mailreader into a
|
|
honking, wailing and farting monster and drive your poor family or
|
|
yourself nuts with a cacophony of noises...
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EXCLUDENODES>
|
|
<head>
|
|
EXCLUDENODES <addressmask>
|
|
</head>
|
|
<p>
|
|
You can define up to 50 different addressmasks to be excluded from
|
|
the compiled nodelists. Use this if you are short of space, or the
|
|
nodelist compile takes very long on your system. This keyword is
|
|
used by GoldNODE.
|
|
</p>
|
|
<p>
|
|
Excluded nodes can be re-included with the <kw>INCLUDENODES</kw> keyword.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EXTERNOPTIONS <-options>
|
|
</head>
|
|
<p>
|
|
Defines the default options for the <kw>EXTERNUTIL</kw>'s. Valid options:
|
|
</p>
|
|
<p>
|
|
-Cls * Clear screen.
|
|
-Cursor * Cursor in shell.
|
|
-KeepCtrl * Keep control lines in the message.
|
|
-Pause Pause for keypress before returning to <name>GoldED+</name>.
|
|
-PauseOnError * Pause only if utility errorlevel is nonzero.
|
|
-Reload * Reload the message file (@file).
|
|
-Wipe Wipe editorfile and temporary file after use.
|
|
</p>
|
|
<p>
|
|
Plus the reverse options with a "No" prefix, for example -NoCls.
|
|
The default options are marked with an asterisk (*).
|
|
</p>
|
|
<p>
|
|
Use -NoKeepCtrl when you want to clearsign a message. This will
|
|
strip the control lines (kludges, tearline and origin) from the
|
|
message before passing it to the external utility. The tearline
|
|
and origin is appended to the message when reloading it. The
|
|
default is to keep control lines in the message.
|
|
</p>
|
|
<p>
|
|
Use -Wipe when you want the temporary unencrypted message files to
|
|
be wiped and removed from the disk after they have been read into
|
|
memory. <name>GoldED+</name> wipes a file by writing a block of 512 random bytes
|
|
over the entire length of the file, then truncating it to zero
|
|
bytes and finally deleting it. The default is not to wipe files.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EXTERNUTIL <utilno> [-options] <commandline>
|
|
</head>
|
|
<p>
|
|
This new feature can be used to "filter" msgs, for example calling
|
|
PGP or other encryption utilities.
|
|
</p>
|
|
<p>
|
|
The <utilno> must be in the range 1 to 24 for utilities that will
|
|
be called with key definitions (see below). Higher numbers can be
|
|
used for utilities that are called from the <kw>EDITSAVEMENU</kw> (if
|
|
enabled). See the <kw>EDITSAVEUTIL</kw> keyword for details.
|
|
</p>
|
|
<p>
|
|
The default options are those specified with the <kw>EXTERNOPTIONS</kw>
|
|
keyword. With [-options], you can change the those options locally
|
|
for specific utils. See the <kw>EXTERNOPTIONS</kw> keyword for a list of
|
|
valid options.
|
|
</p>
|
|
<p>
|
|
The <commandline> specfies the DOS or OS/2 commandline you want to
|
|
execute. This works in the same way as for the external editor and
|
|
spellchecker. See the manual for details about this, especially if
|
|
you want to execute batchfiles. In the <commandline> you can use
|
|
@tokens to transfer information from the msg to the commandline.
|
|
The @tokens are the same as for templates, and in addition you can
|
|
use two other @tokens:
|
|
</p>
|
|
<p>
|
|
@path The GOLDPATH, including a trailing backslash.
|
|
@file The full filename of the message file (GOLDED.MSG)
|
|
that will be written to disk before the utility is
|
|
called.
|
|
@tmpfile The full filename of a temporary message file
|
|
(GEDTMPxx.xxx) that will be written to disk before the
|
|
utility is called.
|
|
</p>
|
|
<p>
|
|
Examples:
|
|
</p>
|
|
<p>
|
|
EXTERNUTIL 1 c:\4dos\4dos.com /c c:\crypt\encrypt.bat @file
|
|
EXTERNUTIL 2 c:\4dos\4dos.com /c c:\crypt\decrypt.bat @file
|
|
</p>
|
|
<p>
|
|
To call a defined external utility, you must assign a key to it.
|
|
There are 24 new keyboard commands you can use in GOLDKEYS.CFG for
|
|
this purpose:
|
|
</p>
|
|
<p>
|
|
ExternUtilNN
|
|
</p>
|
|
<p>
|
|
Where NN is in the range 01 to 24 _with_ leading zero. Examples:
|
|
</p>
|
|
<p>
|
|
F11 ExternUtil01
|
|
F12 ExternUtil02
|
|
</p>
|
|
<p>
|
|
Then if you press F11, you would call external utility number 1
|
|
and so on. The <kw>ExternUtilNN</kw> keywords ONLY work in reader mode, not
|
|
in the internal editor or any other place.
|
|
</p>
|
|
<p>
|
|
HOW IT WORKS:
|
|
</p>
|
|
<p>
|
|
1. Just before the external utility is called, <name>GoldED+</name> writes the
|
|
current message text to the GOLDED.MSG file in the GOLDPATH.
|
|
The file is written as a textfile with each line CR-LF
|
|
terminated. The content is exactly as you see it on the
|
|
screen, which means that kludges are only included if you have
|
|
enabled kludge viewing. If the -NoKeepCtrl option is used,
|
|
kludges, tearline and origin are stripped before the file is
|
|
written. If the token @tmpfile is used, a temporary file named
|
|
GEDTMPxx.xxx (where xx.xxx is something unique) is created
|
|
with exactly the same content as @file.
|
|
</p>
|
|
<p>
|
|
2. <name>GoldED+</name> clears the screen and then calls the utility.
|
|
</p>
|
|
<p>
|
|
3. The utility can now load and process the @file and/or
|
|
@tmpfile, or do anything else you want. It doesn't have to
|
|
have anything to do with the current msg. You could call a
|
|
spreadsheet, a game, whatever. But I think this feature will
|
|
mainly be used for utilities that process the @file. If the
|
|
utility processes the @file, it could write the changes back
|
|
to the @file.
|
|
</p>
|
|
<p>
|
|
4. After returning from the utility, <name>GoldED+</name> reloads the @file and
|
|
displays it just as if it was the current message. For
|
|
example, if your utility was a decrypter and the msg was
|
|
encrypted, you would now see the decrypted msg. Neat eh? :-)
|
|
</p>
|
|
<p>
|
|
5. If you want to make the reloaded text permanent (save it in
|
|
the msg), you can use the Change Msg function and immediately
|
|
choose "Save Message" from the Editing menu (if enabled with
|
|
EDITMENU Yes). This is in fact the method you could use if you
|
|
wanted to EN-crypt a msg (however, it is easier to use the
|
|
method which involves the EDITSAVEUTIL keyword).
|
|
</p>
|
|
<p>
|
|
The QUOTESPACING feature can interfere with encoded msgs that
|
|
include the '>' character at the beginning of lines (often seen in
|
|
uuencoded msgs), by automatically inserting blank lines before and
|
|
after the lines with '>'. I have therefore changed the
|
|
quotespacing default from YES to NO. Be sure to check if you have
|
|
a different setting if you are using an older edition of the
|
|
advanced configuration files.
|
|
</p>
|
|
<p>
|
|
If the string "-----BEGIN PGP MESSAGE-----" is found as the first
|
|
27 characters in a reloaded message, <name>GoldED+</name> will automatically add
|
|
the FSC-0073 kludge "^aENC: PGP" to indicate that the message is
|
|
encrypted. This kludge may be used by some software to set up
|
|
alternative routing for encrypted mail which would otherwise be
|
|
bounced if sent through normal channels.
|
|
</p>
|
|
<p>
|
|
See the "Using PGP as an External Utility" chapter for batchfile
|
|
examples and instructions on how to use this new feature with PGP.
|
|
</p>
|
|
<p>
|
|
!!! IMPORTANT !!! From FidoNet Policy 4.07 (chapter 2.1.4):
|
|
</p>
|
|
<p>
|
|
"[..] Therefore, encrypted and/or commercial traffic that is
|
|
routed without the express permission of all the links in the
|
|
delivery system constitutes annoying behavior."
|
|
</p>
|
|
<p>
|
|
So be careful with this feature!
|
|
</p>
|
|
<p>
|
|
TIP: You can use the EXTERNUTIL feature to setup keys to view or
|
|
print an attached fax. Use something like this in GOLDED.CFG:
|
|
</p>
|
|
<p>
|
|
EXTERNUTIL 11 c:\zfax\zfax.com pf @subject ; print fax
|
|
EXTERNUTIL 12 c:\zfax\zfax.com vf @subject ; view fax
|
|
</p>
|
|
<p>
|
|
And this in GOLDKEYS.CFG:
|
|
</p>
|
|
<p>
|
|
@F11 ExternUtil11 ; Press Alt-F11 to print the fax
|
|
@F12 ExternUtil12 ; Press Alt-F12 to view the fax
|
|
</p>
|
|
<p>
|
|
Or choose your own key assignments and fax view/print utils.
|
|
</p>
|
|
<p>
|
|
Note that this assumes that the fax file is listed in the subject
|
|
line like an attached file.
|
|
</p>
|
|
<p>
|
|
NOTE: If you're running <name>GoldED+</name>/386 and try to use a Win32 program
|
|
as an EXTERNUTIL, you might get the error "This program cannot be
|
|
run in DOS mode". You can work around this by calling the Win32
|
|
program via the shell. For example if this call fails:
|
|
</p>
|
|
<p>
|
|
EXTERNUTIL 1 c:\utl\mywin32.exe @file
|
|
</p>
|
|
<p>
|
|
Replace it with:
|
|
</p>
|
|
<p>
|
|
EXTERNUTIL 1 command.com /c c:\utl\mywin32.exe @file
|
|
</p>
|
|
<p>
|
|
Then it should work. If not, try using full path to command.com.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EZYCOMMSGBASE <path>
|
|
</head>
|
|
<p>
|
|
Defines the base path for the Ezycom msgbase. If not set, AREAFILE
|
|
Ezycom will set it.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EZYCOMUSERBASE <path>
|
|
</head>
|
|
<p>
|
|
Defines the base path for the Ezycom userbase. If not set,
|
|
AREAFILE Ezycom will set it.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=EZYCOMUSERNO>
|
|
<head>
|
|
EZYCOMUSERNO <userno>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
Defines the lastread set used in the Ezycom message base.
|
|
</p>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/DISPSTATUSLINE/ <ident><YES/NO></ident>
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This keyword controls statusline appearance in the <name/GoldED+/.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
If set to <ident/NO/, the statusline at the bottom will be disabled.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<ident/YES/
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader.
|
|
</item>
|
|
<label>
|
|
See also:
|
|
</label>
|
|
<item>
|
|
<ref target=STATUSLINECLOCK><kw/STATUSLINECLOCK/</ref>,
|
|
<ref target=STATUSLINEHELP><kw/STATUSLINEHELP/</ref>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<div2>
|
|
<head>
|
|
FIDOHWMARKS <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will use the echomail "highwater mark" (1.MSG)
|
|
to determine if a message is "sent" or "unsent" in *.MSG areas.
|
|
</p>
|
|
<p>
|
|
NOTE: Some older echomail processors do not update the highwater
|
|
mark in a way that <name>GoldED+</name> can recognize. If all messages appear to
|
|
marked "Uns", even after the mail has been scanned out, try
|
|
turning off this keyword.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FIDOLASTREAD <file>
|
|
</head>
|
|
<p>
|
|
(LASTREAD)
|
|
</p>
|
|
<p>
|
|
Defines the filename of the *.MSG lastread files. DO NOT specify a
|
|
path.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FIDOMSGTYPE <Opus/FTS1>
|
|
</head>
|
|
<p>
|
|
(Opus)
|
|
</p>
|
|
<p>
|
|
This keyword defines the default format of Fido *.MSG files. It is
|
|
only used by some AREAFILE's when reading external area
|
|
configuration files, where the preferred format is unknown.
|
|
</p>
|
|
<p>
|
|
The FTS1 (FTS-0001.012 and later) format uses zone/point fields,
|
|
where the Opus format uses date/time stamps. When set to Opus
|
|
format, <name>GoldED+</name> interprets the date/time stamps as DOS-style
|
|
bitmapped date/time.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FIDONULLFIX <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If set to YES, <name>GoldED+</name> will replace NUL chars with LF chars in the
|
|
msg body when reading a Fido *.MSG file. This is slower of course,
|
|
but not noticably on fast machines.
|
|
</p>
|
|
<p>
|
|
This option was created to enable <name>GoldED+</name> users to read msgs that
|
|
were created/handled by brain-dead programs (I don't have names,
|
|
sorry) which are not obeying our primary technical standard:
|
|
FTS-0001. FTS-1 states that a NUL terminates the msg body. But
|
|
sometimes msgs are encountered which have a NUL as the first char
|
|
in the msg body or perhaps in other places, thereby causing <name>GoldED+</name>
|
|
to show a blank or cut-off msg. In some Pascal-based readers, such
|
|
as FM, these msgs can be read anyway, because in Pascal a NUL does
|
|
not terminate a string like in C/C++.
|
|
</p>
|
|
<p>
|
|
NOTE: Even if the new FIDONULLFIX keyword is disabled, <name>GoldED+</name> will
|
|
still fix a NUL if it is the _first_ character in the msg body.
|
|
This probably fixes most of these buggy msgs without the overhead
|
|
of checking the entire msg.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FIDOUSERLIST <file>
|
|
</head>
|
|
<p>
|
|
Path and filename of a FIDOUSER.LST file.
|
|
</p>
|
|
<p>
|
|
This file is expected to be sorted in ascending alphabetical order
|
|
using plain ASCII case-insensitive sort. Each line in the list is
|
|
expected to be 60 characters plus a CR and a LF, or in other words
|
|
records of 62 bytes each. If the list is produced by a nodelist
|
|
compiler, everything should be okay, but be careful if you have
|
|
edited the file manually. Note that a FIDOUSER.LST file only
|
|
supports a name lookup (to get the address).
|
|
</p>
|
|
</div2>
|
|
<div2 id=FIDOUSERNO>
|
|
<head>
|
|
FIDOUSERNO <userno>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
This is an index into the FIDOLASTREAD file. Each user occupies 2
|
|
bytes in the lastread file.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FILEALIAS <alias> <filename>
|
|
</head>
|
|
<p>
|
|
Used to define short alias names for filenames. If you regularly
|
|
write msgs to different files in different paths, this feature is
|
|
very useful, and reduces the risk of typing wrong.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
FILEALIAS DKB R:\DKBBS\DKBBS
|
|
</p>
|
|
<p>
|
|
With this file alias, you can simply write "DKB" at the filename
|
|
prompt, and the long filename will be used.
|
|
</p>
|
|
</div2>
|
|
<div2 id=FILELISTPAGEBAR>
|
|
<head>
|
|
FILELISTPAGEBAR <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
Enables or disables a pagebar (scrollbar) in the file attach list
|
|
function.
|
|
</p>
|
|
</div2>
|
|
<div2 id=FORCETEMPLATE>
|
|
<head>
|
|
FORCETEMPLATE <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will popup a template selection menu when you
|
|
start writing a new msg or reply. If you have both TEMPLATE(s) and
|
|
FORCETEMPLATE in a Random System group, you can tell <name>GoldED+</name> to use
|
|
the random template(s) by hitting ESC instead of selecting from
|
|
the menu.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FORMFEEDSEPARATOR <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
Used when saving messages to file. If enabled, it inserts a Form
|
|
Feed (12d) character after each message.
|
|
</p>
|
|
</div2>
|
|
<div2 id=FRQEXT>
|
|
<head>
|
|
FRQEXT <.ext>
|
|
</head>
|
|
<p>
|
|
With this keyword you can add extra known filename extensions for
|
|
the filerequest function. The following extensions are already
|
|
known by default, and need not be defined (duplicate definitions
|
|
are ignored):
|
|
</p>
|
|
<p>
|
|
.ARC .ARJ .DOC .EXE .GIF .LHA .LZH .JPG .PAK .PNG .RAR .RUN .SDA
|
|
.SDN .TXT .ZIP .ZOO
|
|
</p>
|
|
<p>
|
|
Each extension _must_ have the leading dot.
|
|
</p>
|
|
<p>
|
|
Example: FRQEXT .XYZ
|
|
</p>
|
|
</div2>
|
|
<div2 id=FRQNODEMAP>
|
|
<head>
|
|
FRQNODEMAP <to-node> <from-node>
|
|
</head>
|
|
<p>
|
|
This keyword is used for the file request feature (Ctrl-F). It
|
|
allows you to define mappings from a nodenumber used in a file
|
|
announcement to another nodenumber. This is useful in the cases
|
|
where a multi-line system announces files using their primary
|
|
nodenumber, which may be a regular V34 modem number, but they also
|
|
have an ISDN number, which you would prefer to use instead.
|
|
Examples:
|
|
</p>
|
|
<p>
|
|
// change-to: from:
|
|
FRQNODEMAP 2:236/99 2:236/100
|
|
FRQNODEMAP 2:236/1043 2:236/43
|
|
</p>
|
|
<p>
|
|
So, if I saw a file announcement from 2:236/100, and requested
|
|
some files, the request would automatically be addressed to
|
|
2:236/99.
|
|
</p>
|
|
</div2>
|
|
<div2 id=FRQOPTIONS>
|
|
<head>
|
|
FRQOPTIONS <options>
|
|
</head>
|
|
<p>
|
|
(FromTop)
|
|
</p>
|
|
<p>
|
|
Defines options for the file request function:
|
|
</p>
|
|
<p>
|
|
Sort Sort the list of files alphabetically.
|
|
FromTop Scan the message from the top of the message.
|
|
NotFromTop Scan the message from the top of the screen.
|
|
NoFiles Don't list the file FILES if no files were found.
|
|
NoWazooMsg Don't save the request message.
|
|
Fast Bypass the header edit and save the msg immediately.
|
|
</p>
|
|
<p>
|
|
By default, the "FromTop" option is enabled. If you often request
|
|
files from very long announcement messages, you might find it very
|
|
useful to set the "NotFromTop" option.
|
|
</p>
|
|
<p>
|
|
The "NoFiles" option was added because if no filenames are found
|
|
in a message, the file request function defaults to listing the
|
|
magic name FILES instead of complaining that no files were found.
|
|
</p>
|
|
<p>
|
|
If the FRQWAZOO keyword is enabled, the default behaviour is to
|
|
save the request message with the FRQ attribute stripped. Use the
|
|
"NoWazooMsg" option if you don't want the request message.
|
|
</p>
|
|
<p>
|
|
Use the "Fast" option if you find that you almost never change the
|
|
destination of the file request message anyway. If you enable this
|
|
option, remember that you can always go over to the netmail area
|
|
and change the file request message before it is sent.
|
|
</p>
|
|
<p>
|
|
The UseFlowFile option enables a feature which was default in
|
|
2.50, but which I have been informed is problematic for modern
|
|
mailers in some setups. The default is now to ONLY create/update
|
|
the .REQ file and NOT also touch/create a .?LO flowfile.
|
|
</p>
|
|
</div2>
|
|
<div2 id=FRQWAZOO>
|
|
<head>
|
|
FRQWAZOO <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will create WaZOO .REQ files instead of file
|
|
request messages. You must define an OUTBOUNDPATH if you enable
|
|
this feature.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
GEDHANDSHAKE <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If this switch set to yes GoldEd displays handshake char in
|
|
statusline. If you annoyed with this feature you could hide this
|
|
character by setting this option to no.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
GERMANKEYBOARD <yes/no>
|
|
</head>
|
|
<p>
|
|
(autodetect)
|
|
</p>
|
|
<p>
|
|
This option is meanful for w32 version only. Due to right Alt key
|
|
required to enter some native characters in german version of
|
|
Windows it could be defined to yes for this.
|
|
</p>
|
|
</div2>
|
|
<div2 id=GOLDBASEPATH>
|
|
<head>
|
|
GOLDBASEPATH <path>
|
|
</head>
|
|
<p>
|
|
Specifies the directory where <name>GoldED+</name> can find the Goldbase msgbase
|
|
files.
|
|
</p>
|
|
</div2>
|
|
<div2 id=GOLDBASESYSPATH>
|
|
<head>
|
|
GOLDBASESYSPATH <path>
|
|
</head>
|
|
<p>
|
|
Specifies the directory where <name>GoldED+</name> can find the NETMAIL.DAT and
|
|
ECHOMAIL.DAT files of the Goldbase msgbase. If not specified, the
|
|
GOLDBASEPATH is used.
|
|
</p>
|
|
</div2>
|
|
<div2 id=GOLDBASEUSERNO>
|
|
<head>
|
|
GOLDBASEUSERNO <userno>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
Specifies the lastread set used in the Goldbase message base.
|
|
</p>
|
|
</div2>
|
|
<div2 id=GOLDPATH>
|
|
<head>
|
|
GOLDPATH <path>
|
|
</head>
|
|
<p>
|
|
This is the path where <name>GoldED+</name> finds all it's control files. It is
|
|
not necessary to define this, unless you have special needs. The
|
|
GOLDPATH defaults to directory where the GOLDED.CFG file was
|
|
found.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
GROUP <groupname>
|
|
</head>
|
|
<p>
|
|
Starts a Random System group. See the Random System chapter for
|
|
details.
|
|
</p>
|
|
</div2>
|
|
<div2 id=HIGHLIGHTUNREAD>
|
|
<head>
|
|
HIGHLIGHTUNREAD <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> updates (increases) the "timesread" field in
|
|
each message that you read. If set to NO, it doesn't touch the
|
|
message. The YES setting causes a slight performance decrease,
|
|
because the header of each message has to be read, the timesread
|
|
field updated and the header written back to disk. The update
|
|
happens immediately after the message is displayed, so you may not
|
|
notice it at all. A message is only updated if the timesread field
|
|
contains the value 0 (zero).
|
|
</p>
|
|
<p>
|
|
This keyword only works in the following msgbase formats: Fido
|
|
(*.MSG), Hudson, Goldbase, JAM, Squish, Ezycom and AdeptXBBS. In
|
|
Squish and Ezycom, there is no timesread field, but I have annexed
|
|
a reserved message attribute (in Squish, 0x00080000, now called
|
|
MSGSEEN; in Ezycom, extattr 0x80) for the purpose of marking a
|
|
message as read at least once. The other formats (PCBoard,
|
|
WildCat) have no timesread field, but they have reserved fields or
|
|
attributes which *could* be used.
|
|
</p>
|
|
</div2>
|
|
<div2 id=HUDSONPATH>
|
|
<head>
|
|
HUDSONPATH <path>
|
|
</head>
|
|
<p>
|
|
Specifies the directory where <name>GoldED+</name> can find the Hudson msgbase
|
|
files.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
HUDSONSIZEWARN <size in bytes>
|
|
</head>
|
|
<p>
|
|
(16000000)
|
|
</p>
|
|
<p>
|
|
When the Hudson MSGTXT.BBS file exceeds this size, <name>GoldED+</name> starts
|
|
to warn that the msgbase is getting dangerously close to the
|
|
structural limit (which is 16MB for the MSGTXT.BBS file). With
|
|
this keyword you can raise or lower the warning size in case you
|
|
think the default is too low or too high.
|
|
</p>
|
|
</div2>
|
|
<div2 id=HUDSONSYSPATH>
|
|
<head>
|
|
HUDSONSYSPATH <path>
|
|
</head>
|
|
<p>
|
|
Specifies the directory where <name>GoldED+</name> can find the NETMAIL.BBS and
|
|
ECHOMAIL.BBS files of the Hudson msgbase. If not specified, the
|
|
HUDSONPATH is used.
|
|
</p>
|
|
</div2>
|
|
<div2 id=HUDSONUSERNO>
|
|
<head>
|
|
HUDSONUSERNO <userno>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
Specifies the lastread set used in the Hudson message base.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
IGNORECHARSET <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If set to yes then GoldEd ignores CHRS kludges in messages thus
|
|
you will be able to switch codepage in messages with inappropriate
|
|
charset.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
IMPORTBEGIN <text>
|
|
</head>
|
|
<p>
|
|
("=== Cut ===")
|
|
</p>
|
|
<p>
|
|
This keyword, together with IMPORTEND, defines some text to add in
|
|
the beginning and end of an imported text file in the internal
|
|
editor. If only IMPORTBEGIN is defined, the text is also used for
|
|
the IMPORTEND. The <text> may be enclosed in quotes ("") if
|
|
leading or trailing spaces are needed. The quotes are stripped.
|
|
</p>
|
|
<p>
|
|
The replacement token "@file" can be used in the <text>. It will
|
|
be replaced with the import filename as entered.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
IMPORTBEGIN === Cut Begin: @file ===
|
|
IMPORTEND === Cut End ===
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
IMPORTEND <text>
|
|
</head>
|
|
<p>
|
|
(same as IMPORTBEGIN)
|
|
</p>
|
|
<p>
|
|
See IMPORTBEGIN.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
INBOUNDPATH <path>
|
|
</head>
|
|
<p>
|
|
(defaults to GOLDPATH)
|
|
</p>
|
|
<p>
|
|
The inbound path is currently only used with the file request
|
|
feature (the READfilerequest command, <Ctrl-F>). If you use this
|
|
feature, <name>GoldED+</name> will put the file descriptions into a FILES.BBS in
|
|
the inbound path, ready for when the requested files are moved to
|
|
the correct file areas.
|
|
</p>
|
|
</div2>
|
|
<div2 id=INCLUDE>
|
|
<head>
|
|
INCLUDE
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/INCLUDE/ <ident/<filename>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
This tells the configuration file reader to stop reading the current
|
|
configuration file, and start reading the file specifyed as an
|
|
extra configuration source, then resume reading the previous
|
|
configuration file. <kw/INCLUDE/ files can be nested without limit.
|
|
</item>
|
|
<label>
|
|
Parameters:
|
|
</label>
|
|
<item>
|
|
The <ident/filename/ parameter should contain absolute path
|
|
and name to the configuration file.
|
|
</item>
|
|
<label>
|
|
Processed by:
|
|
</label>
|
|
<item>
|
|
Mail reader and nodelist compiler.
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=INCLUDENODES>
|
|
<head>
|
|
INCLUDENODES <addressmask>
|
|
</head>
|
|
<p>
|
|
You can define up to 50 different addressmasks to be included from
|
|
the compiled nodelists. This is only used in conjunction with the
|
|
EXCLUDENODES keyword to include otherwise EXcluded nodes. This
|
|
keyword is only used by GoldNODE.
|
|
</p>
|
|
</div2>
|
|
<div2 id=INPUTFILE>
|
|
<head>
|
|
INPUTFILE <filename>
|
|
</head>
|
|
<p>
|
|
(*)
|
|
</p>
|
|
<p>
|
|
Defines the default name in the internal editor file import
|
|
function.
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> can automatically uuencode and apply a base64 encoding to
|
|
the files during importing them into the internal editor.
|
|
</p>
|
|
<p>
|
|
NOTE: This is a very simple implementation of encoders. It cannot
|
|
split large files over several messages. The file mode number 644
|
|
is hard-coded and has nothing to do with the actual file mode.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
INTENSECOLORS <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> is capable of switching off the "blink" color, and thereby
|
|
enabling the use of bright background (paper) colors. Enable this
|
|
keyword, and try out one of the intense color setup examples.
|
|
</p>
|
|
</div2>
|
|
<div2 id=INTERNETADDRESS>
|
|
<head>
|
|
INTERNETADDRESS <internet-address>
|
|
</head>
|
|
<p>
|
|
Specifies your Internet address. This must be the address only, no
|
|
name. The INTERNETADDRESS and USERNAME will be combined to a
|
|
standard "From: internetaddresss (username)" headerline when you
|
|
write e-mail or articles.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
USERNAME Odinn Sorensen
|
|
INTERNETADDRESS odinn@ibm.net
|
|
</p>
|
|
<p>
|
|
Produces the RFC line:
|
|
</p>
|
|
<p>
|
|
From: odinn@ibm.net (Odinn Sorensen)
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
INTERNETDOMAIN <domainname>
|
|
</head>
|
|
<p>
|
|
(username%domain.net)
|
|
</p>
|
|
<p>
|
|
Defines the domain-part of outgouing Message-ID's. If you don't
|
|
know your full domain, leave it as default, which should work just
|
|
fine.
|
|
</p>
|
|
</div2>
|
|
<div2 id=INTERNETGATE>
|
|
<head>
|
|
INTERNETGATE [gatename<,>]<address>
|
|
</head>
|
|
<p>
|
|
Defines the local Internet gate you use when sending netmail to
|
|
Internet users. This option is activated when you write an
|
|
Internet address in the TO: field in the header display. <name>GoldED+</name>
|
|
detects the Internet address by looking for the '@' character. If
|
|
detected, <name>GoldED+</name> puts the gate address from INTERNETGATE in the
|
|
TO: address field. If you have defined the optional gate name
|
|
(typically UUCP), <name>GoldED+</name> also replaces the typed Internet address
|
|
with the gate name and puts the Internet address in a TO: line in
|
|
the message body. Some gate software accepts the Internet address
|
|
directly in the header, while other software may need the special
|
|
(UUCP) name and a separate TO: line. Examples:
|
|
</p>
|
|
<p>
|
|
INTERNETGATE UUCP, 1:105/42 ; Standard, with gate name
|
|
INTERNETGATE 2:230/9316 ; My uplink runs GIGO software
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally in GOLDED.CFG, if you only ever
|
|
use one gate, or in GROUP's for specific areas in GOLDRAND.CFG if
|
|
you have multiple netmail areas and regularly use more than one
|
|
gate.
|
|
</p>
|
|
<p>
|
|
NOTE: If you enable the INTERNETRFCBODY keyword, you should always
|
|
use the gatename UUCP, because otherwise the gateway software may
|
|
send duplicate copies (carbon copies) of your e-mails.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
INTERNETLOOKUP <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If set to Yes, <name>GoldED+</name> will check the systemname in the nodelist
|
|
when doing a lookup and if the systemname looks like an Internet
|
|
address (contains an '@' char), the msg will be addressed to that
|
|
Internet address using the INTERNETGATE name/address if defined.
|
|
</p>
|
|
<p>
|
|
For example, let's say there was something like this in the
|
|
nodelist:
|
|
</p>
|
|
<p>
|
|
,999,somebody@somewhere,Whereever,Some_Body,...
|
|
</p>
|
|
<p>
|
|
And this in my GOLDED.CFG:
|
|
</p>
|
|
<p>
|
|
INTERNETLOOKUP Yes
|
|
INTERNETGATE 2:230/9316
|
|
</p>
|
|
<p>
|
|
Then if I did a lookup of "Some Body" and selected the entry with
|
|
the Internet address, <name>GoldED+</name> would make a msg looking like this:
|
|
</p>
|
|
<p>
|
|
--------------------------------------
|
|
From : odinn@winboss.dk 2:236/77
|
|
To : somebody@somewhere 2:230/9316
|
|
Subj : whatever
|
|
--------------------------------------
|
|
</p>
|
|
<p>
|
|
Or if my gate was defined as "INTERNETGATE UUCP 2:230/9316":
|
|
</p>
|
|
<p>
|
|
--------------------------------------
|
|
From : odinn@winboss.dk 2:236/77
|
|
To : UUCP 2:230/9316
|
|
Subj : whatever
|
|
--------------------------------------
|
|
To: somebody@somewhere
|
|
</p>
|
|
<p>
|
|
So what's the use of all this? It allows you to make a
|
|
nodelist-style list of users with Internet addresses and use it
|
|
with <name>GoldED+</name> so that you can do a lookup of normal names instead of
|
|
trying to remember strange Internet addresses. Of course something
|
|
similar could be done using the ADDRESSMACRO's, but with the
|
|
nodelist approach, you could build a "network" of users which have
|
|
offline Internet access via FTN-gate software and distribute the
|
|
nodelist for automatic processing.
|
|
</p>
|
|
</div2>
|
|
<div2 id=INTERNETMSGID>
|
|
<head>
|
|
INTERNETMSGID <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
Specifies whether the FTN MSGID kludge should contain an RFC1036
|
|
compatible Message-ID or the normal FTS-9 format. Note that using
|
|
the RFC1036 format in MSGID breaks the FTS-9 (version 001)
|
|
specification, so please don't use this feature in FidoNet netmail
|
|
or echomail. As a safeguard, <name>GoldED+</name> will only use the RFC1036
|
|
format in areas specifically marked as e-mail or newsgroups, using
|
|
the SOUPEMAIL and SOUPNEWSRCFILE keywords or using the Email and
|
|
News area types with the AREADEF keyword, even when INTERNETMSGID
|
|
is set to YES globally.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
INTERNETREPLY <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
When INTERNETREPLY is enabled, <name>GoldED+</name> always uses the FSC-35
|
|
REPLYADDR/REPLYTO kludges to gate replies to msgs from Internet
|
|
correctly. If disabled, <name>GoldED+</name> only uses the FSC-35 method if the
|
|
Internet address is too large to fit in the max-35-character TO:
|
|
header field. Some gate software requires that the FSC-35 method
|
|
is used, while other software accepts Internet addresses directly
|
|
in the header.
|
|
</p>
|
|
</div2>
|
|
<div2 id=INTERNETRFCBODY>
|
|
<head>
|
|
INTERNETRFCBODY <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
Tells <name>GoldED+</name> whether to look for and process RFC headerlines at
|
|
the top of the message body, before the first empty line. Also
|
|
tells <name>GoldED+</name> to insert its own RFC headerlines at the top of the
|
|
message body instead of as kludge lines. This option should only
|
|
be used when receiving Internet mail as QWK packets where the RFC
|
|
headerlines are usually found at the top of the messages, or when
|
|
sending Internet mail via FTN packet to a gateway running GIGO.
|
|
GIGO does not recognize RFC header in kludges, but it does
|
|
recognize them at the top of the messages, if it is properly
|
|
configured (with lines of "Allow_Xxx:" in GIGO's HEADERS.CFG,
|
|
where Xxx are the RFC headerlines the gate administrator wants to
|
|
allow).
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
INVALIDATE <type> <"findstring"> <"replacestring">
|
|
</head>
|
|
<p>
|
|
This is used to invalidate (change) certain control strings in
|
|
quoted text. Use this in conjunction with old versions of D'Bridge
|
|
or other software that chokes on control strings in quoted text.
|
|
As an added bonus feature, if the tearline or origin is
|
|
invalidated to a null string (""), they will not be quoted at all.
|
|
</p>
|
|
<p>
|
|
The <type> can be one of the following:
|
|
</p>
|
|
<p>
|
|
Tearline Invalidate tearline ("---").
|
|
Origin Invalidate origin (" * Origin: ").
|
|
Seenby Invalidate SEEN-BY's.
|
|
</p>
|
|
<p>
|
|
By default, the following invalidations are used:
|
|
</p>
|
|
<p>
|
|
INVALIDATE Tearline "---" "-+-"
|
|
INVALIDATE Origin " * Origin: " " + Origin: "
|
|
INVALIDATE Seenby "SEEN-BY" "SEEN+BY"
|
|
</p>
|
|
<p>
|
|
If you want to disable invalidation entirely, use this:
|
|
</p>
|
|
<p>
|
|
INVALIDATE Tearline "---" "---"
|
|
INVALIDATE Origin " * Origin: " " * Origin: "
|
|
INVALIDATE Seenby "SEEN-BY" "SEEN-BY"
|
|
</p>
|
|
<p>
|
|
The defined INVALIDATEs are also used during importing a file when
|
|
editing a mail in the internal message editor.
|
|
</p>
|
|
</div2>
|
|
<div2 id=JAMHARDDELETE>
|
|
<head>
|
|
JAMHARDDELETE <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
The default setting makes <name>GoldED+</name> conform to the JAMAPI specs when
|
|
deleting msgs in JAM msgbases. This means that deleted msgs are
|
|
only marked as such in the message header, not in the index. As a
|
|
result, <name>GoldED+</name> will find and display the deleted msgs until you
|
|
run a message pack utility to physically remove the deleted msgs.
|
|
</p>
|
|
<p>
|
|
If JAMHARDDELETE is set to Yes, <name>GoldED+</name> will zap the reference to
|
|
the message in the index when deleting msgs. This way the deleted
|
|
msgs will not show up again later. The drawback of this approach
|
|
is that it is hard to undelete msgs, and may break other software
|
|
which assume 100% to-the-letter conformance to the specs. Note
|
|
however, that the hard-delete method is transparent to normal use
|
|
of JAM msgbases. Probably the only software that might break are
|
|
undelete utilities.
|
|
</p>
|
|
<p>
|
|
For the techies and programmers, the hard-delete method is simply
|
|
setting both UserCRC and HdrOffset in the index to 0xFFFFFFFF
|
|
instead of only the UserCRC. According to the JAMAPI specs, a
|
|
value of 0xFFFFFFFF in HdrOffset means that "there is no
|
|
corresponding message header". Sounds remarkably like a deleted
|
|
msg, right? :-)
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
JAMPATH <path>
|
|
</head>
|
|
<p>
|
|
(defaults to the HUDSONPATH)
|
|
</p>
|
|
<p>
|
|
Defines the path where <name>GoldED+</name> can access the NETMAIL/ECHOMAIL.JAM
|
|
files, which are used by mail processors to find and scan out mail
|
|
written by users.
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> can handle enviroment variables correctly in paths
|
|
specified in connection with this keyword. For example, if a path
|
|
is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in
|
|
AUTOEXEC.BAT (or whatever), then <name>GoldED+</name> translates the path to
|
|
C:\POINT\path\name.
|
|
NOTE: The translation is done at config compile time, so if you
|
|
change the environment variable and haven't changed anything else
|
|
that would cause <name>GoldED+</name> to recompile it's config, you must force
|
|
it with the -F or -FF command parameter.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
KEYBCLEAR <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
Tells <name>GoldED+</name> whether or not to clear the keyboard buffer on
|
|
startup. This also clears KEYBSTACK or commandline key stuffing.
|
|
In older versions of <name>GoldED+</name>, it was necessary to enable this
|
|
keyword if you had renamed GOLDED.EXE to DBEDIT.EXE. This version
|
|
detects the .EXE renaming and automatically enables KEYBCLEAR,
|
|
regardless of the configuration setting.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
KEYBDEFAULTS <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> defines a default keyboard configuration setup internally.
|
|
The keys can be reconfigured in the GOLDKEYS.CFG file. By default,
|
|
the internal keyboard setup is active always, redefinable with the
|
|
definitions in GOLDKEYS.CFG. But in some cases it can be
|
|
preferrable that the internal keyboard setup is turned off, so
|
|
that only the keys in GOLDKEYS.CFG are active. If you want this,
|
|
set KEYBDEFAULTS to NO.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
KEYBEXT <yes/no>
|
|
</head>
|
|
<p>
|
|
(detect)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will use extended bios calls to read the
|
|
keyboard. With the extended keyboard, you can use keys like
|
|
<Alt-Left>, <Alt-Home> and other extended keys. If you don't have
|
|
an extended keyboard, don't despair - using a few neat tricks, I
|
|
have made it possible to use some of the extended keys even with a
|
|
non-extended keyboard.
|
|
</p>
|
|
</div2>
|
|
<div2 id=KEYBMODE>
|
|
<head>
|
|
KEYBMODE <poll/block>
|
|
</head>
|
|
<p>
|
|
(poll)
|
|
</p>
|
|
<p>
|
|
If this option is set to Poll, <name>GoldED+</name> switches its keyboard
|
|
handling code from "blocking" to "polling" mode. This enables
|
|
<name>GoldED+</name> to provide a continuously running statusline clock,
|
|
automatic internal editor autosave, timeout exit and screensaver.
|
|
If set to Block, the timeout exit and screensaver are disabled,
|
|
and the clock and autosave are dependent on key presses.
|
|
</p>
|
|
<p>
|
|
In order to minimize waste of CPU resources in keyboard polling
|
|
mode, <name>GoldED+</name> automatically detects DESQview, Windows and OS/2 and
|
|
releases timeslices during the keyboard poll.
|
|
</p>
|
|
</div2>
|
|
<div2 id=KEYBSTACK><head>KEYBSTACK <keystring></head>
|
|
<p>
|
|
With this keyword, you can "stack" keys in the keyboard buffer.
|
|
The KEYBSTACK can be overridden by commandline keystacking, which
|
|
uses the same syntax.
|
|
</p>
|
|
<p>
|
|
The <keystring> can be a mixture of the following:
|
|
</p>
|
|
<p>
|
|
^Char Ctrl-key (^Letter).
|
|
~Char Ctrl-key (~Letter). (Use this with 4DOS!).
|
|
@Key Alt-key (@Number or @Letter).
|
|
Char Literal character.
|
|
"String" String, enclosed in double quotes.
|
|
'String' String, enclosed in single quotes.
|
|
Number Keyboard scan code (decimal).
|
|
! Clear keyboard buffer.
|
|
</p>
|
|
<p>
|
|
Whitespace (space and tab) is ignored, except in quoted strings.
|
|
</p>
|
|
<p>
|
|
See the <ptr target=MACROSANDKEYSTACKING> chapter for more info.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
KLUDGE <kludge-definition>
|
|
</head>
|
|
<p>
|
|
The definition may optionally be enclosed in quotes. A definition
|
|
must be enclosed in quotes if it contains leading or trailing
|
|
spaces. The KLUDGE tells <name>GoldED+</name> which kludges it should consider
|
|
as "known" in addition to the built-in known kludges.
|
|
</p>
|
|
<p>
|
|
Here are a bunch of examples, most of which are kludges generated
|
|
by the GIGO Internet gateway software:
|
|
</p>
|
|
<p>
|
|
KLUDGE " " ; For wrapped kludges
|
|
KLUDGE "Content-Type:"
|
|
KLUDGE "Date:"
|
|
KLUDGE "From:"
|
|
KLUDGE "In-Reply-To:"
|
|
KLUDGE "Message-Id:"
|
|
KLUDGE "Mime-Version:"
|
|
KLUDGE "Organization:"
|
|
KLUDGE "Newsgroups:"
|
|
KLUDGE "Received:"
|
|
KLUDGE "Reply-To:"
|
|
KLUDGE "Sender:"
|
|
KLUDGE "Subject:"
|
|
KLUDGE "To:"
|
|
KLUDGE "Errors-To:"
|
|
KLUDGE "FTN-From:" ; X-FTN-From:
|
|
KLUDGE "ORIGREF:" ; Gated?
|
|
KLUDGE "ORIGID:" ; Gated?
|
|
KLUDGE "RFC-" ; Seen in NET_DEV
|
|
</p>
|
|
<p>
|
|
The kludges defined with KLUDGE are not case-sensitive, but when
|
|
<name>GoldED+</name> looks for the kludges, it matches to the exact length. This
|
|
means that for example "RFC-" will match all kludges beginning
|
|
with that string.
|
|
</p>
|
|
<p>
|
|
The ASCII 1 kludge char should not be included in the definition
|
|
string, but <name>GoldED+</name> can handle it if you do.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
KLUDGECHRS <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If set to YES, <name>GoldED+</name> uses the "^aCHRS" kludge instead of the
|
|
"^aCHARSET" kludge when appropriate.
|
|
</p>
|
|
</div2>
|
|
<div2 id=LOADLANGUAGE>
|
|
<head>
|
|
LOADLANGUAGE <file>
|
|
</head>
|
|
<p>
|
|
If defined, this keyword will load a language definition file.
|
|
</p>
|
|
<p>
|
|
This feature can be used to load a small set of national language
|
|
definitions in national areas, an english set in international
|
|
areas, etc. Typically this would be used to load the definitions
|
|
of the date/time strings for use in the template and the
|
|
Msg/From/To/Subj strings in the header display.
|
|
</p>
|
|
<p>
|
|
In the ADVANCED archive, a set of GEDLNG*.CFG files are provided,
|
|
which are designed for use with LOADLANGUAGE. Please note that
|
|
there is also a @loadlanguage template token. This way you can
|
|
choose to load a language file from the template, or by using the
|
|
Random System. The template token takes precedence over the
|
|
LOADLANGUAGE in the Random System, but if both are defined, both
|
|
will be loaded.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups, but
|
|
it is probably not very useful when used globally.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
LOGFILE <file>
|
|
</head>
|
|
<p>
|
|
(GOLDED.LOG)
|
|
</p>
|
|
<p>
|
|
Defines the name of the <name>GoldED+</name> logfile. You should not change the
|
|
default.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
LOGFORMAT <fd,max,bink,qbbs,db>
|
|
</head>
|
|
<p>
|
|
(fd)
|
|
</p>
|
|
<p>
|
|
Defines the log format <name>GoldED+</name> should use when writing to the
|
|
logfile.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
LOOKUPECHO <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will use nodelist lookup when entering the TO:
|
|
name in msgs in echomail areas.
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> *won't* lookup the name if it exactly matches the current
|
|
WHOTO - text. This is a feature, because a lookup of "All" is not
|
|
very useful. :-)
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
LOOKUPLOCAL <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will use nodelist lookup when entering the TO:
|
|
name in msgs in local areas.
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> *won't* lookup the name if it exactly matches the current
|
|
WHOTO - text. This is a feature, because a lookup of "All" is not
|
|
very useful. :-)
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
LOOKUPNET <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will use nodelist lookup when entering the TO:
|
|
name in msgs in netmail areas.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
LOOKUPUSERBASE <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will attempt to find a matching username in the
|
|
user database if a to-name with wildcards is entered in echo or
|
|
local areas.
|
|
</p>
|
|
<p>
|
|
The userbase lookup feature is not new, but a need arose for an
|
|
option to turn off the lookup. I decided to let the default be to
|
|
disable the lookup. Previously the lookup was always enabled.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MAILINGLIST>
|
|
<head>
|
|
MAILINGLIST <echoid> <senderaddress> [contribution address]
|
|
</head>
|
|
<p>
|
|
Defines one or more mailing lists. When importing e-mail from a
|
|
SOUP packet, <name>GoldED+</name> will look at the Internet address in the
|
|
"Sender" header and if it matches one of the MAILINGLIST's, the
|
|
e-mail will be tossed to the defined area. Note that <name>GoldED+</name>
|
|
supports only participation in, not hosting of mailing lists. The
|
|
contribution address is the destination Internet address for mail
|
|
you write to the mailing list - the address is typically given to
|
|
you when you subscribe to a list. If the contribution address is
|
|
not specified, the senderaddress is assumed.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MAILTOSS <echoid> <contribution-address> <pattern>
|
|
</head>
|
|
<p>
|
|
This is acutally the same as MAILINGLIST in disguise with the
|
|
parameters recorded and it also enables the full set of pattern
|
|
matching. The <pattern> can be written exactly as if in the prompt
|
|
for the advanced search feature.
|
|
</p>
|
|
<p>
|
|
Any number of MAILTOSS lines can be given for a particular list,
|
|
if there is for some reason no single way to identify the list.
|
|
</p>
|
|
<p>
|
|
When determining the contribution address, the first MAILTOSS
|
|
(or MAILINGLIST) that matches the echoid is chosen.
|
|
</p>
|
|
<p>
|
|
MAILTOSS and MAILINGLIST can both be used at the same time and for
|
|
the same lists. MAILINGLIST is always the faster, because it looks
|
|
only at specific headerlines. MAILTOSS uses much more complex
|
|
pattern matching and can even match based on message body content.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MAPPATH <server filespec> <local filespec>
|
|
</head>
|
|
<p>
|
|
This keyword is used to map paths, for example if you have
|
|
different drive letters on a server machine and a workstation. You
|
|
might have your FidoNet mailer and mail processor setup to run
|
|
with the server drive letter (C:), but run <name>GoldED+</name> from a
|
|
workstation where that drive is mapped to a different letter (J:).
|
|
If you use AREAFILE's to get the area configuration for <name>GoldED+</name>,
|
|
you need to use MAPPATH to map the server drive letter to the
|
|
workstation equivalent.
|
|
</p>
|
|
<p>
|
|
Another case might be that you have a setup with DOS-style paths
|
|
and want to run the Linux version with the same <name>GoldED+</name> setup. You
|
|
can then use MAPPATH to map the DOS drive-based paths to Unix
|
|
style paths.
|
|
</p>
|
|
<p>
|
|
Examples:
|
|
</p>
|
|
<p>
|
|
MAPPATH C: J:
|
|
MAPPATH C:\ /mnt/dos/c/
|
|
</p>
|
|
<p>
|
|
NOTE: You don't have to worry about backslash/forwardslash in this
|
|
case - they are always mapped automatically to the correct type
|
|
for the operating system.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MEMBER>
|
|
<head>
|
|
MEMBER <echoid>
|
|
</head>
|
|
<p>
|
|
Defines Random System group members. See the Random System chapter
|
|
for details.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MENUDROPMSG <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
Defines the default selection in the "Drop This Msg?" menu.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MENUMARKED <marked/current/previous/default>
|
|
</head>
|
|
<p>
|
|
(default)
|
|
</p>
|
|
<p>
|
|
Specifies the position of the selection bar in the Marked/Current
|
|
menu.
|
|
</p>
|
|
<p>
|
|
Marked Set selector to Marked.
|
|
Current Set selector to Current.
|
|
Previous Set selector to previously selection.
|
|
Default Set selector to Marked if there are marked msgs.
|
|
</p>
|
|
<p>
|
|
Note that older versions (before 2.50) used the equivalent of the
|
|
"previous" setting.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MOUSE <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
The mouse support in <name>GoldED+</name> is currently not functional, so this
|
|
keyword is ignored.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MSGLISTDATE>
|
|
<head>
|
|
MSGLISTDATE <written/arrived/received/no>
|
|
</head>
|
|
<p>
|
|
(written)
|
|
</p>
|
|
<p>
|
|
Can be used globally and in groups. This keyword specifies the
|
|
default date shown in the right column in the message list. If
|
|
"no" is specified, the date column is removed and the space used
|
|
to widen the other columns. Personally I prefer to see the
|
|
"arrived" date, which is why I implemented this feature.
|
|
</p>
|
|
<p>
|
|
The key command LISTtoggledate (Ctrl-D) toggles between them.
|
|
</p>
|
|
<p>
|
|
Note that the "arrived" date doubles as the "processed" date for
|
|
messages that are written locally and scanned out from your
|
|
messagebase.
|
|
</p>
|
|
<p>
|
|
Not all messagebase formats supports all three dates. The table
|
|
below shows which messagebase supports which dates:
|
|
</p>
|
|
<p>
|
|
Written Arrived Received
|
|
JAM X X X
|
|
*.MSG X X
|
|
Squish X X
|
|
Ezycom X X
|
|
Hudson X
|
|
Goldbase X
|
|
PCBoard X
|
|
</p>
|
|
<p>
|
|
If a date is not supported, "n/a" (for "not available") is shown
|
|
instead.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MSGLISTFAST>
|
|
<head>
|
|
MSGLISTFAST <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
The message lister can operate in two ways, fast or slow. In the
|
|
fast mode, only the message headers are loaded for the list
|
|
information. Depending on the msgbase format and message type,
|
|
some information may not be quite the same when presented in the
|
|
lister because information which is gathered from kludges or other
|
|
control information in the message text will be missing. Most of
|
|
the time this may not be a problem, so if you want speed, chose
|
|
the fast mode (default).
|
|
</p>
|
|
<p>
|
|
The slow mode loads and fully interprets the content of each
|
|
message before the message list is presented. The slowness is most
|
|
noticable when entering the lister and when paging up and down.
|
|
You may want to use the slow mode for areas with Internet
|
|
newsgroups and e-mail, where <name>GoldED+</name> uses the "From" kludge to get
|
|
the real name of the message writer.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MSGLISTFIRST>
|
|
<head>
|
|
MSGLISTFIRST <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> automatically starts the message lister when
|
|
entering an area.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MSGLISTHEADER>
|
|
<head>
|
|
MSGLISTHEADER <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> shows the header of the current message when
|
|
you scroll the bar up and down. This is how it worked in previous
|
|
versions. If disabled, <name>GoldED+</name> does not show the header and instead
|
|
uses the screen space to show more messages. By eliminating the
|
|
header display, it is also much faster at scrolling the list.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MSGLISTPAGEBAR>
|
|
<head>
|
|
MSGLISTPAGEBAR <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
Enables or disables a pagebar (scrollbar) in the message list.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MSGLISTVIEWSUBJ <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will display the full subject in the bottom
|
|
border of the list window. Note that this feature slows down
|
|
scrolling a bit.
|
|
</p>
|
|
</div2>
|
|
<div2 id=MSGLISTWIDESUBJ>
|
|
<head>
|
|
MSGLISTWIDESUBJ <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, the Subject column is made wider by removing the To
|
|
column. This is especially useful in gated Internet newsgroups,
|
|
where the To name is always "All".
|
|
</p>
|
|
<p>
|
|
You can toggle between wide and short subject with Ctrl-B
|
|
(keycommand LISTtogglewidesubj).
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
</div2>
|
|
<div2 id=NAMESFILE>
|
|
<head>
|
|
NAMESFILE <file>
|
|
</head>
|
|
<p>
|
|
(NAMES.FD)
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> supports the "address macro" file supported by FrontDoor
|
|
and Maximus. If no path is specified, the file is first searched
|
|
for in the path from the "FD" environment variable and then the
|
|
GOLDPATH, if the FD variable failed.
|
|
</p>
|
|
<p>
|
|
The address macros are added *after* those defined with the
|
|
ADDRESSMACRO keyword (if any) (see this for details on the
|
|
format).
|
|
</p>
|
|
</div2>
|
|
<div2 id=NETNAME>
|
|
<head>
|
|
NETNAME <q/string/
|
|
</head>
|
|
<!--
|
|
This is the "netname" that is placed in the originline, after
|
|
the address.
|
|
|
|
Example:
|
|
|
|
NETNAME fidonet
|
|
|
|
Produces:
|
|
|
|
* Origin: Whatever (2:236/77@fidonet)
|
|
|
|
This keyword can be used globally and in a Random System group.
|
|
|
|
NOTE: The netname is a non-standard practice with no technical
|
|
merit and should not be used. It is provided for cosmetical
|
|
purposes and backward compatibility only.
|
|
-->
|
|
<p>dummy text</p>
|
|
</div2>
|
|
<div2 id=NICKNAME>
|
|
<head>
|
|
NICKNAME <your pseudo>
|
|
</head>
|
|
<p>
|
|
Defines the nick name (pseudo) for the current USERNAME. Can be
|
|
used globally and in random system groups.
|
|
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
NODELIST <file> [zone/addr]
|
|
</head>
|
|
<p>
|
|
Here you define up to 255 nodelists that are used by <name>GoldED+</name> and the
|
|
companion nodelist compiler GoldNODE. The nodelists must generally
|
|
be in the standard "St.Louis" nodelist format, but they can also
|
|
contain FrontDoor/Version7 style Boss/Point extensions. The
|
|
default zone is defined by the first ADDRESS or AKA, but can be
|
|
overridden by adding the zone number or a full address after the
|
|
filename. <name>GoldED+</name> currently needs it's own special index files to
|
|
use the nodelists. These index files are created by GoldNODE.
|
|
</p>
|
|
<p>
|
|
<file> Nodelist file. If the extension is .999 or a
|
|
wildcard (".*"), the newest file with a numeric
|
|
extension is used.
|
|
[zone/addr] Default zone or address for the nodelist (if no
|
|
zone info is present in the list itself).
|
|
</p>
|
|
<p>
|
|
See also the USERLIST keyword, and the Nodelist Browsing chapter.
|
|
</p>
|
|
<p>
|
|
NOTE: If you have nodelists with duplicate some of each others
|
|
nodes, the nodelist with the newest or most correct entries should
|
|
be placed LAST, and you should use the -D (remove duplicates)
|
|
option with GoldNODE.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
NODELISTWARN <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If set to YES, <name>GoldED+</name> will warn you during startup if one or more
|
|
nodelists are missing. Use NO to disable the warning if it bothers
|
|
you or you delete/pack your nodelists when the nodelists are
|
|
compiled.
|
|
</p>
|
|
<p>
|
|
NOTE: <name>GoldED+</name> can work fine with lookups etc. without nodelists as
|
|
long as it can access its own indexes (GOLDNODE.GX?). Only the
|
|
extra details will be missing.
|
|
</p>
|
|
</div2>
|
|
<div2 id=NODEPATH>
|
|
<head>
|
|
NODEPATH <path>
|
|
</head>
|
|
<p>
|
|
This is where <name>GoldED+</name> and GoldNODE finds the nodelist files and
|
|
indexes.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
NODEPATHFD <path>
|
|
</head>
|
|
<p>
|
|
Path where <name>GoldED+</name> can find the FrontDoor nodelist index files.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
NODEPATHIM <path>
|
|
</head>
|
|
<p>
|
|
Path to the InterMail nodelist index files. This is actually just
|
|
an alias name of the NODEPATHFD keyword, since InterMail and
|
|
FrontDoor uses the same nodelist index files.
|
|
</p>
|
|
</div2>
|
|
<div2 id=NODEPATHV7>
|
|
<head>
|
|
NODEPATHV7 <path>
|
|
</head>
|
|
<p>
|
|
Path where <name>GoldED+</name> can find the Version 7 nodelist index files.
|
|
</p>
|
|
<p>
|
|
NOTE: For the Version 7 nodelist index support, <name>GoldED+</name> *requires*
|
|
that the files SYSOP.NDX, NODEX.NDX and NODEX.DAT are present.
|
|
None of these files may be missing and no other filenames are
|
|
supported. Multiple sets of index files are not supported.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
NODEV7FLAGS <flag> <value>
|
|
</head>
|
|
<p>
|
|
The Version 7 nodelist index does not by default define any
|
|
nodelist flags except the CM flag. Unfortunately the V7 index does
|
|
not point to the actual nodelist, it only has some bits which are
|
|
marked "reserved" in the specifications. The NODEV7FLAGS keyword
|
|
allows you to define the meaning of each of these bits.
|
|
</p>
|
|
<p>
|
|
The <value> field can be a number or a bit number. Allowed numbers
|
|
are: 32, 64, 128, 256, 512, 1024, 2048, 8192 and 16384. Allowed
|
|
bit numbers are: b5, b6, b7, b8, b9, b10, b11, b13 and b14.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
NODEV7FLAGS MO b5
|
|
NODEV7FLAGS LO b6
|
|
NODEV7FLAGS MN b7
|
|
NODEV7FLAGS NC b8
|
|
NODEV7FLAGS ZEC b9
|
|
NODEV7FLAGS REC b10
|
|
NODEV7FLAGS NEC b11
|
|
NODEV7FLAGS XA b13
|
|
NODEV7FLAGS XX b14
|
|
</p>
|
|
<p>
|
|
See also the NODEV7MODEM keyword for other nodelist flags.
|
|
</p>
|
|
<p>
|
|
The nodelist flag bits in the index files are put in by your
|
|
Version 7 nodelist compiler. You must make sure that the nodelist
|
|
flag definitions in your nodelist compiler setup match those in
|
|
your <name>GoldED+</name> setup.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
NODEV7MODEM <type> <value>
|
|
</head>
|
|
<p>
|
|
The Version 7 nodelist index does not by default define any
|
|
nodelist modem type flags. Unfortunately the V7 index does not
|
|
point to the actual nodelist, it only has some bits which are
|
|
marked "reserved" in the specifications. The NODEV7MODEM keyword
|
|
allows you to define the meaning of each of these bits.
|
|
</p>
|
|
<p>
|
|
The <value> field can be a number or a bit number. Allowed numbers
|
|
are: 1, 2, 4, 8, 16, 32, 64 and 128. Allowed bit numbers are: b0,
|
|
b1, b2, b3, b4, b5, b6 and b7.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
NODEV7MODEM VFC b0
|
|
NODEV7MODEM HST b1
|
|
NODEV7MODEM V34T b2
|
|
NODEV7MODEM V32B b3
|
|
NODEV7MODEM V34 b4
|
|
NODEV7MODEM V42B b5
|
|
NODEV7MODEM ZYX b6
|
|
NODEV7MODEM ISDN b7
|
|
</p>
|
|
<p>
|
|
See also the NODEV7FLAGS keyword for other nodelist flags.
|
|
</p>
|
|
<p>
|
|
The modem type bits in the index files are put in by your Version
|
|
7 nodelist compiler. You must make sure that the modem type
|
|
definitions in your nodelist compiler setup match those in your
|
|
<name>GoldED+</name> setup.
|
|
</p>
|
|
</div2>
|
|
<div2 id=ORGANIZATION>
|
|
<head>
|
|
ORGANIZATION <text>
|
|
</head>
|
|
<p>
|
|
Specifies the content of the RFC Organization header for Internet
|
|
messages.
|
|
</p>
|
|
</div2>
|
|
<div2 id=ORIGIN>
|
|
<head>
|
|
ORIGIN <"string">
|
|
</head>
|
|
<p>
|
|
You can define many different origins for use in <name>GoldED+</name>. You can
|
|
select one of the defined origins from the Origin selection menu
|
|
(the READchangeorigin keyword), which is also available from the
|
|
EDITMENU and the EDITSAVEMENU.
|
|
</p>
|
|
<p>
|
|
Leading and/or trailing spaces can be added by enclosing the
|
|
origin string in quotes.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
<p>
|
|
NOTE: Origins defined in the Random System will always override
|
|
the global origins defined with this keyword, except when they are
|
|
selected from the EDITSAVEMENU.
|
|
</p>
|
|
</div2>
|
|
<div2 id=OUTBOUNDPATH>
|
|
<head>
|
|
OUTBOUNDPATH <path>
|
|
</head>
|
|
<p>
|
|
Defines a Binkley-style outbound path. Currently only used for
|
|
WaZOO .REQ file requests (see FRQWAZOO). This should be the name
|
|
of your primary outbound without extension.
|
|
</p>
|
|
</div2>
|
|
<div2 id=OUTPUTFILE>
|
|
<head>
|
|
OUTPUTFILE <file>
|
|
</head>
|
|
<p>
|
|
This is the default name of the file written using the
|
|
READwritemsg command.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PCBOARDPATH <path>
|
|
</head>
|
|
<p>
|
|
Defines the default path where <name>GoldED+</name> should look for the PCBoard
|
|
setup files if it can't find the PCBOARD environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2 id=PCBOARDUSERNO>
|
|
<head>
|
|
PCBOARDUSERNO <userno>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
Specifies the lastread set used in the PCBoard message base.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PERSONALMAIL <startup,allnames>
|
|
</head>
|
|
<p>
|
|
Specifies options regarding the personal mail scan feature. None
|
|
of them are enabled by default.
|
|
</p>
|
|
<p>
|
|
If the "startup" option is used, <name>GoldED+</name> scans for personal mail
|
|
while doing the startup mail scan.
|
|
</p>
|
|
<p>
|
|
If the "allnames" option is used, <name>GoldED+</name> scans for mail to all the
|
|
USERNAME's instead of only the first. The default is not to scan
|
|
for personal mail at startup and to scan only for the first name.
|
|
This is faster.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
PERSONALMAIL Startup, AllNames
|
|
</p>
|
|
<p>
|
|
The example makes <name>GoldED+</name> scan for personal mail to all your
|
|
USERNAME's at startup.
|
|
</p>
|
|
</div2>
|
|
<div2 id=PLAY>
|
|
<head>
|
|
PLAY <filename.ext/beepnoise>
|
|
</head>
|
|
<p>
|
|
See the EVENT keyword for a definition of the PLAY parameters.
|
|
You may specify <q/@/ before parameter for random noise selection.
|
|
</p>
|
|
<p>
|
|
Bugs: At least one <kw/EVENT/ with file should be defined in order to
|
|
initialize soundcard driver. Otherwise filenames specifyed for the
|
|
<kw/PLAY/ will be ignored.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PRINTDEVICE <devicename>
|
|
</head>
|
|
<p>
|
|
(PRN)
|
|
</p>
|
|
<p>
|
|
Defines the name of the device used for printing. PRN is the
|
|
default, but LPTx can also be used. Printers on COMx ports may
|
|
also work, but this has not been tested.
|
|
</p>
|
|
<p>
|
|
Devices are opened in Write-Only text mode. The function has been
|
|
successfully tested to work with two popular peer-to-peer network
|
|
packages.
|
|
</p>
|
|
<p>
|
|
You should NOT use a filename as devicename. Use the filename
|
|
option in the Write menu instead.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PRINTFORMFEED <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
Used when printing messages. If enabled, it prints a Form Feed
|
|
(12d) character after each message.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PRINTINIT <printstring>
|
|
</head>
|
|
<p>
|
|
This keyword defines the command string sent to your printer to
|
|
initialize it before the actual printing.
|
|
</p>
|
|
<p>
|
|
The <printstring> can contain items like these:
|
|
</p>
|
|
<p>
|
|
$Hex A hexadecimal string.
|
|
#Decimal A decimal (integer) number.
|
|
"String" Text string, enclosed in double quotes.
|
|
'String' Text string, enclosed in single quotes.
|
|
Other chars Ignored.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PRINTLENGTH <lines>
|
|
</head>
|
|
<p>
|
|
(60)
|
|
</p>
|
|
<p>
|
|
Defines the number of lines per page for printing. A formfeed is
|
|
printed when every time PRINTLENGTH lines have been printed.
|
|
</p>
|
|
</div2>
|
|
<div2 id=PRINTMARGIN>
|
|
<head>
|
|
PRINTMARGIN <characters>
|
|
</head>
|
|
<p>
|
|
(80)
|
|
</p>
|
|
<p>
|
|
The right margin to use in printed messages.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PRINTRESET <printstring>
|
|
</head>
|
|
<p>
|
|
This keyword defines the command string sent to your printer to
|
|
reset it after printing.
|
|
</p>
|
|
<p>
|
|
<printstring> See the PRINTINIT keyword.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QUOTEBLANK <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will put the QUOTESTRING on blank lines in the
|
|
quote. Otherwise blank lines are left blank in quotes.
|
|
</p>
|
|
</div2>
|
|
<div2 id=QUOTEBUFFILE>
|
|
<head>
|
|
QUOTEBUFFILE <filename>
|
|
</head>
|
|
<p>
|
|
If used, it sets the default filename for the quotebuffer. If no
|
|
path is specified, the GOLDPATH is used.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
<p>
|
|
NOTE: If this keyword is used in globally (in GOLDED.CFG), it
|
|
effectively disables the automatically named quotebuffers, as
|
|
described in the chapter about the QUOTEBUFMODE keyword.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QUOTEBUFMODE <ask/append/overwrite>
|
|
</head>
|
|
<p>
|
|
(ask)
|
|
</p>
|
|
<p>
|
|
Specifies what <name>GoldED+</name> should do, if the quotebuffer file exists
|
|
already.
|
|
</p>
|
|
<p>
|
|
Ask A menu asks you to select append/overwrite/skip.
|
|
Append Always append, no asking.
|
|
Overwrite Always overwrite, no asking.
|
|
</p>
|
|
<p>
|
|
The "always overwrite" mode is not very useful I guess, but it's
|
|
there if you need it.
|
|
</p>
|
|
<p>
|
|
The quotebuffer feature automatically creates special filenames
|
|
for the buffer file, using these guidelines:
|
|
</p>
|
|
<p>
|
|
FORMAT FILENAME LOCATION
|
|
Fido GOLDED.QBF In the directory with the *.MSG's.
|
|
Hudson GOLDHxxx.QBF In the HUDSONPATH.
|
|
Squish filename.QBF Where the Squish area is.
|
|
Ezycom GLDxxxxx.QBF In the EZYCOMMSGPATH.
|
|
JAM filename.QBF Where the JAM area is.
|
|
Goldbase GOLDGxxx.QBF In the GOLDBASEPATH.
|
|
PCBoard filename.QBF Where the PCBoard area is.
|
|
</p>
|
|
<p>
|
|
Note that they all have extension .QBF so that you can easily find
|
|
them.
|
|
</p>
|
|
</div2>
|
|
<div2 id=QUOTECHARS>
|
|
<head>
|
|
QUOTECHARS ["]<chars>["]
|
|
</head>
|
|
<p>
|
|
Defines up to 10 chars to recognize in addition to '>' as quote
|
|
string chars. This is most useful in gated Internet newsgroups,
|
|
where chars such as '|', ':' and ';' are sometimes used instead of
|
|
the '>'.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
Group Internet:
|
|
Member alt.*, comp.*, net.email
|
|
Quotechars "|:;"
|
|
Username odinn@winboss.dk
|
|
EndGroup
|
|
</p>
|
|
<p>
|
|
The example is similar to the one I use myself (net.email is a
|
|
local netmail area where I import my gated e-mail from
|
|
winboss.dk). The username is my actual Internet address.
|
|
</p>
|
|
<p>
|
|
Note that using additional quotechars such as '|' and ':' may
|
|
cause odd results when quoting in the cases when they are actually
|
|
NOT used in a message as quotechars. Consider for example quoting
|
|
a smiley :-)
|
|
</p>
|
|
</div2>
|
|
<div2 id=QUOTECTRL>
|
|
<head>
|
|
QUOTECTRL <Tearline,Origin,yes/no>
|
|
</head>
|
|
<p>
|
|
Specifies if you want quote tearline and/or origin in your
|
|
messages.
|
|
</p>
|
|
<p>
|
|
This keyword can be used in random system groups.
|
|
</p>
|
|
</div2>
|
|
<div2 id=QUOTEMARGIN>
|
|
<head>
|
|
QUOTEMARGIN <chars>
|
|
</head>
|
|
<p>
|
|
(70)
|
|
</p>
|
|
<p>
|
|
The margin to which quotes are wrapped. A negative value means
|
|
that the negative value is added to the DISPMARGIN (not
|
|
recommended).
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QUOTESPACING <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will automatically add blank lines before and
|
|
after a block of quoted text, if none are present already. This
|
|
improves the readability of some messages.
|
|
</p>
|
|
</div2>
|
|
<div2 id=QUOTESTOPS>
|
|
<head>
|
|
QUOTESTOPS
|
|
</head>
|
|
<list type=gloss>
|
|
<label>
|
|
Synopsis:
|
|
</label>
|
|
<item>
|
|
<kw/QUOTESTOPS/ <ident/<string>/
|
|
</item>
|
|
<label>
|
|
Description:
|
|
</label>
|
|
<item>
|
|
If one of characters defined by this keyword found before quotechar
|
|
then line will be not treated as quote.
|
|
</item>
|
|
<label>
|
|
Default:
|
|
</label>
|
|
<item>
|
|
<![ CDATA ["<\"'-"]]>
|
|
</item>
|
|
</list>
|
|
</div2>
|
|
<div2 id=QUOTESTRING>
|
|
<head>
|
|
QUOTESTRING <quotespec>
|
|
</head>
|
|
<p>
|
|
(" FL> ")
|
|
</p>
|
|
<p>
|
|
With this keyword you define how you want the quotestring to look
|
|
in your quoted replies.
|
|
</p>
|
|
<p>
|
|
The <quotespec> can contain these characters:
|
|
</p>
|
|
<p>
|
|
F Replaced with the first letter of the first name.
|
|
M Replaced with the letters of the middle names.
|
|
L Replaced with the first letter of the last name.
|
|
> Required quote-char.
|
|
Spaces Cosmetics.
|
|
</p>
|
|
<p>
|
|
Other characters are allowed but *not* recommended.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System Groups.
|
|
</p>
|
|
</div2>
|
|
<div2 id=QUOTEWRAPHARD>
|
|
<head>
|
|
QUOTEWRAPHARD <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
This keyword controls behaviour of quoted text (wrap or reflow).
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QWKBADMSGS <echoid>
|
|
</head>
|
|
<p>
|
|
Specifies the area where messages in unknown conferences are put.
|
|
If you get messages tossed here by accident, you must move them
|
|
manually to the correct area. If the badmsgs area is not defined,
|
|
the messages will silently disappear. Messages tossed to the
|
|
badmsgs area will have the control line "AREA:<bbsid>_<confno>" at
|
|
the top of the message.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QWKCONFMAP <bbsid> ["]<confname>["] <echoid>
|
|
</head>
|
|
<p>
|
|
Defines the mapping between the BBSID and conference names in the
|
|
QWK packets and the echoid name of the conference as required by
|
|
<name>GoldED+</name>. You MUST define a mapping for every conference that you
|
|
subscribe to. If you don't, the messages will be tossed to the
|
|
area defined by QWKBADMSGS or disappear. The <bbsid> is the name
|
|
listed on line 5 in CONTROL.DAT after the comma. The <confname> is
|
|
the conference names listed on line 13 and on alternate lines
|
|
onwards in CONTROL.DAT. If a conference name contains embedded
|
|
spaces, the <confname> must be enclosed in double quotes, like
|
|
this: "Main Board". The area <echoid> must be already defined
|
|
either in an AREAFILE or using the AREADEF or AREA keywords.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QWKEXPORTPATH <path>
|
|
</head>
|
|
<p>
|
|
Path where outgoing QWK reply files (BBSID.MSG) can be placed.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QWKIMPORTPATH <path>
|
|
</head>
|
|
<p>
|
|
Path where incoming QWK packet files (CONTROL.DAT and
|
|
MESSAGES.DAT) can be found.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QWKOPTIONS <bbsid> <options>
|
|
</head>
|
|
<p>
|
|
The <bbsid> is the BBSID (same as the name of the QWK packet) for
|
|
which the options will be active. The <options> can be any or a
|
|
combination of the following, separated by commas or spaces:
|
|
</p>
|
|
<p>
|
|
KLUDGES/NOKLUDGES: Defaults to NOKLUDGES. Specifies whether or not
|
|
to include the FidoNet-style kludges at the top of messages when
|
|
exporting to QWK. NOTE: Unless you enable this option, <name>GoldED+</name> will
|
|
*not* include kludges in your QWK packets. You should check if the
|
|
BBS supports kludges in QWK packets. If it does, please enable
|
|
this option.
|
|
</p>
|
|
<p>
|
|
MIXCASE/NOMIXCASE: Defaults to NOMIXCASE. Specifies whether or not
|
|
the BBS allows mixed upper/lower case in the QWK message headers.
|
|
The default is to uppercase the TO and FROM header fields when
|
|
exporting to QWK packets.
|
|
</p>
|
|
<p>
|
|
RECEIPT/NORECEIPT: Defaults to NORECEIPT. Specifies whether or not
|
|
the BBS supports return receipt requests (RRQ). If the RECEIPT
|
|
option is enabled, <name>GoldED+</name> will insert "RRR" at the front of the
|
|
subject field if the RRQ attribute is set on your messages, when
|
|
exporting to QWK packets.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QWKREPLYLINKER <cmd>
|
|
</head>
|
|
<p>
|
|
Commandline for a replylinker program to call after QWK import.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QWKTOSSLOG <file>
|
|
</head>
|
|
<p>
|
|
Name of a file where <name>GoldED+</name> puts the echoids of each area where
|
|
articles have been imported. The tosslog file is intended to be
|
|
used with a replylinker. If no path is given, it defaults to the
|
|
GOLDPATH.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
RA2USERSBBS <yes/no>
|
|
</head>
|
|
<p>
|
|
(detect)
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> supports the two different formats of the Hudson USERS.BBS
|
|
file. With this keyword you can tell <name>GoldED+</name> which format to use.
|
|
</p>
|
|
<p>
|
|
If set to YES, the RA2 format is used. Otherwise if the it is set
|
|
to NO, the Hudson format is used.
|
|
</p>
|
|
<p>
|
|
If this keyword is NOT used, <name>GoldED+</name> tries to detect the format by
|
|
looking at the size of the USERS.BBS file and comparing this to
|
|
the record sizes of the RA2 and Hudson formats.
|
|
</p>
|
|
<p>
|
|
If the size matches one and not the other, the format is detected
|
|
to be of the matching type.
|
|
</p>
|
|
<p>
|
|
If the size matches both (which is quite normal), <name>GoldED+</name> looks for
|
|
the RA environment variable and if found, in the RA config files
|
|
for the RA version.
|
|
</p>
|
|
<p>
|
|
If the size does not match either of them (indicating a possibly
|
|
damaged userfile), <name>GoldED+</name> exits with an error message and writes
|
|
in the log with details of the problem and an advise to run a
|
|
userbase packing utility.
|
|
</p>
|
|
<p>
|
|
If used, this keyword should be placed in the configuration file
|
|
_after_ any AREAFILE keyword.
|
|
</p>
|
|
</div2>
|
|
<div2 id=RCVDISABLESCFM>
|
|
<head>
|
|
RCVDISABLESCFM <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
|
|
If this keyword defined to "no" then GoldEd will recognize RRq
|
|
(receipt request) and/or CFM (confirmation) flag on messages with
|
|
RCV (received) flag set. After that RRq and CFM flags will be
|
|
resetted. It is useful if your netmail tracker sets RCV flag
|
|
before you actually read messages.
|
|
<ptr target=MESSAGEATTRS> chapter,
|
|
<ref target=AREACFMREPLYTO><kw/AREACFMREPLYTO/</ref>,
|
|
<ref target=ATTRIBSCFM><kw/ATTRIBSCFM/</ref>,
|
|
<ref target=CONFIRMFILE><kw/CONFIRMFILE/</ref>,
|
|
<ref target=CONFIRMRESPONSE><kw/CONFIRMRESPONSE/</ref>
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
REGISTERKEY
|
|
</head>
|
|
<p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
REGISTERNAME
|
|
</head>
|
|
<p>
|
|
These keywords do nothing and won't do anything in the future.
|
|
They were used when <name>GoldED+</name> was a Shareware product.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
REM
|
|
</head>
|
|
<p>
|
|
This keyword ignores everything behind it. This is useful to
|
|
comment a single line out.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
REPLYLINK <chain/direct>
|
|
</head>
|
|
<p>
|
|
Defaults to "direct" for JAM and "chain" for everything else.
|
|
</p>
|
|
<p>
|
|
If set to "direct", <name>GoldED+</name> will link your reply directly to the
|
|
original message. If set to "chain", it will link to the last
|
|
message in the reply chain. The default ("chain") is how <name>GoldED+</name>
|
|
has done it in all previous versions.
|
|
</p>
|
|
<p>
|
|
The advantage of the "direct" linking method is that you can
|
|
easily find the the original message the reply was for. Unless of
|
|
course you have later re-linked using a chain-linking replylinker
|
|
utility. I can recommend the utility SQLINK by Serge Terekhov.
|
|
SQLINK links Squish areas using the MSGID/REPLY kludges and makes
|
|
direct links instead of chain-linking on the subject line like
|
|
most other replylinkers do. There are probably also similar
|
|
replylinkers for other msgbase formats, I just don't know them.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
REPLYLINKLIST <fast/full>
|
|
</head>
|
|
<p>
|
|
(fast)
|
|
</p>
|
|
<p>
|
|
When there is more than one reply to a msg in a JAM or Squish
|
|
area, <name>GoldED+</name> pops up a list of the replies. This keyword affects
|
|
the contents of the list.
|
|
</p>
|
|
<p>
|
|
In the "fast" mode, the list data is based solely on what can be
|
|
found by reading the message header, which is quite fast.
|
|
Unfortunately some software does not (or cannot) fill the header
|
|
with the correct origination address. In that case, set this
|
|
keyword to "full", which makes <name>GoldED+</name> read and scan each message
|
|
for control data to get the origination address. That can be very
|
|
slow.
|
|
</p>
|
|
</div2>
|
|
<div2 id=ROBOTNAME>
|
|
<head>
|
|
ROBOTNAME <name>
|
|
</head>
|
|
<p>
|
|
A "robot" is a program on the Boss or Uplink system which responds
|
|
automatically to netmail messages. Usually the robot links or
|
|
unlinks echomail areas or distributed files.
|
|
</p>
|
|
<p>
|
|
The following ROBOTNAME's are defined by default:
|
|
</p>
|
|
<p>
|
|
AreaFix, AreaMgr, FileFix, AreaLink, AllFix, Raid, GEcho.
|
|
</p>
|
|
<p>
|
|
If you write a netmail message where the TO: name is one of the
|
|
robot names, <name>GoldED+</name> will ignore any template definition, and give
|
|
you a blank msg (possibly with a tearline) to edit.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SCREENBLANKER <seconds> [BLACK]
|
|
</head>
|
|
<p>
|
|
(180)
|
|
</p>
|
|
<p>
|
|
If non-zero, <name>GoldED+</name> will blank the screen after the defined number
|
|
of seconds, and put a small moving window up instead. Hitting any
|
|
key (including shiftkeys) will return the screen to normal. If
|
|
zero, no blanking is done.
|
|
</p>
|
|
<p>
|
|
If the additional parameter "BLACK" is given, <name>GoldED+</name> will switch
|
|
the screen completely black instead of showing its own animated
|
|
screenblanker. This is useful if you have a monitor with
|
|
powersaving-features.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
SCREENBLANKER 300 BLACK
|
|
</p>
|
|
<p>
|
|
NOTE: This feature only works if KEYBMODE is set to "poll".
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SCREENMAXCOL <columns>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
On some systems, <name>GoldED+</name> may no detect the correct display size.
|
|
With this keyword you can force a specific size. If zero,
|
|
autodetect is used.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SCREENMAXROW <rows>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
On some systems, <name>GoldED+</name> may not detect the correct display size.
|
|
With this keyword you can force a specific size. If zero,
|
|
autodetect is used.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SCREENPALETTE <reg> <value> OR <reg> (red green blue)
|
|
</head>
|
|
<p>
|
|
You can change the color palette used in <name>GoldED+</name>. The palette has
|
|
16 color registers, corresponding to the 16 colors from black (0)
|
|
to intense white (15). By changing the values in the palette
|
|
registers, it is possible to make any of the 16 colors a
|
|
completely different color. You can even make the background
|
|
colors intense, without using the intense color feature. There are
|
|
64 different colors to chose from.
|
|
</p>
|
|
<p>
|
|
To configure the palette colors in <name>GoldED+</name>, the SCREENPALETTE
|
|
keyword is used. There are two different syntaxes:
|
|
</p>
|
|
<p>
|
|
SCREENPALETTE <reg> <value>
|
|
SCREENPALETTE <reg> (red green blue)
|
|
</p>
|
|
<p>
|
|
So you can either compose the color value using separate red,
|
|
green, blue components, or directly use a precalculated value. The
|
|
red/green/blue values can only be in the range 0-3.
|
|
</p>
|
|
<p>
|
|
These are the original palette values:
|
|
</p>
|
|
<p>
|
|
SCREENPALETTE 0 (0 0 0)
|
|
SCREENPALETTE 1 (0 0 2)
|
|
SCREENPALETTE 2 (0 2 0)
|
|
SCREENPALETTE 3 (0 2 2)
|
|
SCREENPALETTE 4 (2 0 0)
|
|
SCREENPALETTE 5 (2 0 2)
|
|
SCREENPALETTE 6 (2 2 0)
|
|
SCREENPALETTE 7 (2 2 2)
|
|
SCREENPALETTE 8 (1 1 1)
|
|
SCREENPALETTE 9 (1 1 3)
|
|
SCREENPALETTE 10 (1 3 1)
|
|
SCREENPALETTE 11 (1 3 3)
|
|
SCREENPALETTE 12 (3 1 1)
|
|
SCREENPALETTE 13 (3 1 3)
|
|
SCREENPALETTE 14 (3 3 0)
|
|
SCREENPALETTE 15 (3 3 3)
|
|
</p>
|
|
<p>
|
|
Copy these lines into your GOLDED.CFG and start experimenting! :-)
|
|
</p>
|
|
<p>
|
|
If you have written a program to edit the palette and write a
|
|
<name>GoldED+</name> palette setup file, please don't keep it a secret! :-)
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SCREENSHADOWS <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, all relevant windows and menus in <name>GoldED+</name> will have
|
|
shadows.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SCREENSIZE <mode>
|
|
</head>
|
|
<p>
|
|
(Auto)
|
|
</p>
|
|
<p>
|
|
Use this to force <name>GoldED+</name> to use either 25 lines, 43/50 lines on
|
|
EGA/VGA, or even special videomodes supported by your SuperVGA
|
|
adapter (modes like 132x44, 100x40 or 80x60).
|
|
</p>
|
|
<p>
|
|
The <mode> can be one of the following:
|
|
</p>
|
|
<p>
|
|
Auto Use detected size.
|
|
25 Switch to 25 lines.
|
|
28 Switch to 28 lines.
|
|
4350 Switch to 43/50 lines.
|
|
Mode <NN> Switch to videomode NN (a hexadecimal value).
|
|
</p>
|
|
<p>
|
|
Please check your video adapter manual carefully before trying out
|
|
the Mode option. SELECTING A WRONG MODE CAN DAMAGE YOUR MONITOR!!!
|
|
</p>
|
|
<p>
|
|
The Mode option is ignored in the W32 and OS/2 version.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SCREENUSEBIOS <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will use standard BIOS calls for screen
|
|
updates. This is VERY slow, and should only be used if really
|
|
needed. Normally <name>GoldED+</name> uses direct screen writes.
|
|
</p>
|
|
<p>
|
|
This feature is only interpreted in the DOS version.
|
|
</p>
|
|
</div2>
|
|
<div2 id=SEARCHFOR>
|
|
<head>
|
|
SEARCHFOR ["]<string|string|..>["]
|
|
</head>
|
|
<p>
|
|
Defines a set of search strings, separated by the '|' character.
|
|
The search set defined here is the default when using the Alt-F/Z
|
|
search functions or the marking system.
|
|
</p>
|
|
<p>
|
|
The '|' character works like an OR operator. That is, the search
|
|
is successful if one OR more of the strings are matched. The '&'
|
|
character is used as the logical AND operator.
|
|
</p>
|
|
<p>
|
|
Please refer to appropriate section in user's guide for more
|
|
information.
|
|
</p>
|
|
<p>
|
|
Older versions used the ';' semicolon character as a separator,
|
|
but that conflicts with the config reader which treats the
|
|
semicolon in a special way. The semicolon is still accepted as
|
|
separator char like '|', but if semicolons are used, you MUST
|
|
enclose the search strings with quotes or the config reader will
|
|
treat the first semicolon as the start of a comment.
|
|
</p>
|
|
<p>
|
|
Examples:
|
|
</p>
|
|
<p>
|
|
SEARCHFOR string1
|
|
SEARCHFOR string1|string2|stringx
|
|
SEARCHFOR "string1;string2;stringx"
|
|
SEARCHFOR "string 1"|string2&stringx
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in Random System groups.
|
|
</p>
|
|
</div2>
|
|
<div2 id=SEMAPHORE>
|
|
<head>
|
|
SEMAPHORE <type> <file>
|
|
</head>
|
|
<p>
|
|
This keyword defines "semaphore" files, for use with other mailer
|
|
and/or mail processing software.
|
|
</p>
|
|
<p>
|
|
The <type> can be one of the following:
|
|
</p>
|
|
<p>
|
|
NETSCAN Empty netmail scan file (for D'Bridge/FD).
|
|
ECHOSCAN Empty echomail scan file (for D'Bridge).
|
|
EXPORTLIST Echoid-list of your new messages.
|
|
IMPORTLIST Echoid-list of new imported messages.
|
|
</p>
|
|
<p>
|
|
The semaphore files are placed in the AREAPATH, if no path is
|
|
specified.
|
|
</p>
|
|
<p>
|
|
See the example .CFG files for typical semaphore filenames.
|
|
</p>
|
|
<p>
|
|
NOTE: You should not set SEMAPHORE EXPORTLIST to
|
|
%JAMPATH%\ECHOMAIL.JAM. This is incorrect and probably may cause
|
|
your mail processor to malfunction. Use the JAMPATH keyword
|
|
instead.
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> can handle enviroment variables correctly in paths
|
|
specified in connection with this keyword. For example, if a path
|
|
is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in
|
|
AUTOEXEC.BAT (or whatever), then <name>GoldED+</name> translates the path to
|
|
C:\POINT\path\name.
|
|
</p>
|
|
<p>
|
|
NOTE: The translation is done at config compile time, so if you
|
|
change the environment variable and haven't changed anything else
|
|
that would cause <name>GoldED+</name> to recompile it's config, you must force
|
|
it with the -F or -FF command parameter.
|
|
</p>
|
|
<p>
|
|
In addition, <name>GoldED+</name> itself can watch for some semaphore files and
|
|
execute the appropiate function if it is in the arealist screen.
|
|
This can be useful if you have a multitasking system and you want
|
|
to "tell" <name>GoldED+</name> that there is new mail in some areas and <name>GoldED+</name>
|
|
should update its display correctly.
|
|
</p>
|
|
<p>
|
|
In detail, there are
|
|
</p>
|
|
<p>
|
|
EXITNOW <file> Quit immediately.
|
|
SCANALL <file> Scan all areas
|
|
SCANNETMAIL <file> Scan all netmail areas
|
|
SCANTHIS <file> Scan the areas listed in the file
|
|
PMSCANALL <file> PM-scan all areas
|
|
PMSCANNETMAIL <file> PM-scan all netmail areas
|
|
PMSCANTHIS <file> PM-scan the areas listed in the file
|
|
QWKIMPORT <file> Import QWK packets
|
|
QWKEXPORT <file> Export to QWK
|
|
SOUPIMPORT <file> Import SOUP packets
|
|
SOUPEXPORT <file> Export to SOUP
|
|
IDLETIME <seconds> Number of seconds between checks
|
|
</p>
|
|
<p>
|
|
If SEMAPHORE IDLETIME is defined and non-zero, then <name>GoldED+</name> will
|
|
check this list of semaphore files when the user has not pressed a
|
|
key in the specified number of seconds. The semaphores are only
|
|
checked when the arealist screen is active. If a semaphore file is
|
|
found, the file is deleted and then the action is performed. If no
|
|
path is given for the files, the GOLDPATH is assumed.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
SEMAPHORE SCANALL SCANALL.NOW
|
|
SEMAPHORE IDLETIME 30
|
|
</p>
|
|
<p>
|
|
This causes <name>GoldED+</name> to check every 30 seconds for the SCANALL.NOW
|
|
file in the GOLDPATH, and scan all areas if it's found.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SERIALNO
|
|
</head>
|
|
<p>
|
|
Everything mentioned above about REGISTERKEY and REGISTERNAME
|
|
applied to this keyword.
|
|
</p>
|
|
</div2>
|
|
<div2 id=SHAREMODE><head>SHAREMODE <yes/no/mode#></head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> opens all files in a SHARE.EXE compatible mode.
|
|
</p>
|
|
<p>
|
|
The default share-mode is "Share Deny None", but another may be
|
|
specified directly if you give the mode number as the keyword
|
|
parameter (decimal).
|
|
</p>
|
|
<p>
|
|
It is normally not necessary to change the default.
|
|
</p>
|
|
</div2>
|
|
<div2 id=SOUNDPATH>
|
|
<head>
|
|
SOUNDPATH <path>
|
|
</head>
|
|
<p>
|
|
(defaults to the GOLDPATH)
|
|
</p>
|
|
<p>
|
|
Tells <name>GoldED+</name> where to find the sound files for the PLAY and EVENT
|
|
keywords.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPBADMSGS <echoid>
|
|
</head>
|
|
<p>
|
|
Specifies the area where "bad messages" from SOUP packets can be
|
|
tossed. It should be an echomail or newsgroup area.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPEMAIL <echoid>
|
|
</head>
|
|
<p>
|
|
Specifies the area where Internet e-mails can be tossed. It must
|
|
be a netmail or e-mail area.
|
|
</p>
|
|
</div2>
|
|
<div2 id=SOUPEXPORTMARGIN>
|
|
<head>
|
|
SOUPEXPORTMARGIN <margin>
|
|
</head>
|
|
<p>
|
|
(76)
|
|
</p>
|
|
<p>
|
|
This is the margin that <name>GoldED+</name> will hard-wrap to when exporting to
|
|
SOUP packets. If you're getting complaints that your lines are too
|
|
long, you may want to set this to 70 or 60.
|
|
</p>
|
|
<p>
|
|
NOTE: You should NOT enable EDITHARDTERM in email and newsgroups
|
|
that are exported to SOUP. If you do, your messages will probably
|
|
be exported with short line "droppings" after the wrapping margin.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPEXPORTPATH <path>
|
|
</head>
|
|
<p>
|
|
Path where outgoing SOUP reply packet files (REPLIES and
|
|
GOLD*.MSG) can be placed.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPIMPORTPATH <path>
|
|
</head>
|
|
<p>
|
|
Path where the incoming SOUP packet files (AREAS and *.MSG) can be
|
|
found.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPNEWSRCFILE <file>
|
|
</head>
|
|
<p>
|
|
Name with full path of the NEWSRC file which lists the newsgroups
|
|
you are connected to. <name>GoldED+</name> uses the list to mark the matching
|
|
areas as newsgroups. These will then be scanned for outgoing mail
|
|
when starting a SOUP export.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPREPLYLINKER <cmd>
|
|
</head>
|
|
<p>
|
|
Commandline for a replylinker program to call after SOUP import.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPREPLYTO <internet-address>
|
|
</head>
|
|
<p>
|
|
Internet-Address other users should use when they respond to your
|
|
mails (Reply-To Headerline).
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOUPTOSSLOG <file>
|
|
</head>
|
|
<p>
|
|
Name of a file where <name>GoldED+</name> puts the echoids (newsgroup names) of
|
|
each area where articles have been imported. The tosslog file is
|
|
intended to be used with a replylinker. If no path is given, it
|
|
defaults to the GOLDPATH.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SQUISHDIRECT <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, then in Squish areas, if the DIR (direct) attribute is
|
|
set on a message, <name>GoldED+</name> will automatically set both the CRA
|
|
(crash) and HLD (hold) attributes when saving the message.
|
|
</p>
|
|
<p>
|
|
According to the Squish Developers Kit, this is the way to tell
|
|
SquishMail that a message should be routed direct, because
|
|
SquishMail does not recognize the FLAGS kludge where the DIR
|
|
attribute is normally found. This keyword should probably only be
|
|
used with SquishMail (the mail processor) and then only when used
|
|
with Binkley or other so-called "static" mailers. DON'T use it
|
|
with FrontDoor!
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SQUISHSCAN <api/quick>
|
|
</head>
|
|
<p>
|
|
(quick)
|
|
</p>
|
|
<p>
|
|
Specfies whether to use a quick scanning method which only looks
|
|
in the .SQI files. This will normally work fine, but may fail
|
|
slightly in obscure cases, especially when used with Squish 1.0x
|
|
or programs using the old version of the MSGAPI. If you suspect
|
|
problems, try to set this keyword to "api", which tells <name>GoldED+</name> to
|
|
look in the .SQD file for an exact count of active msgs in the
|
|
.SQI file.
|
|
</p>
|
|
<p>
|
|
NOTE: <name>GoldED+</name> does NOT use the original MSGAPI by Scott Dudley.
|
|
Since version 2.50, a completely rewritten implementation is used.
|
|
</p>
|
|
</div2>
|
|
<div2 id=SQUISHUSERNO>
|
|
<head>
|
|
SQUISHUSERNO <index>
|
|
</head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
This sets the lastread index number for the Squish *.SQL lastread
|
|
files. Lowest number is 0 (zero), highest is (in theory) 65534.
|
|
</p>
|
|
<p>
|
|
If used, this disables the use of USER.BBS to find the index
|
|
number, and will in effect also stop <name>GoldED+</name> from creating USER.BBS
|
|
or any new entries in it (useful in a single-user point system).
|
|
If a Squish msgbase is shared between several users, and you don't
|
|
want to have a USER.BBS (recommended in such a case), each user
|
|
must have a unique SQUISHUSERNO in their GOLDED/GOLDAREA.CFG.
|
|
</p>
|
|
</div2>
|
|
<div2 id=SQUISHUSERPATH>
|
|
<head>
|
|
SQUISHUSERPATH <path>[file]
|
|
</head>
|
|
<p>
|
|
This keyword defines the path where <name>GoldED+</name> can find and use/create
|
|
your USER.BBS file, which is used in connection with the Squish
|
|
area lastreads. You can also specify the exact filename if not
|
|
USER.BBS.
|
|
</p>
|
|
<p>
|
|
If this path or filename is not defined, <name>GoldED+</name> will instead take
|
|
the one specified with AREAFILE Squish or AREAFILE Maximus
|
|
(whichever comes first), or failing that, use the MAXIMUS or
|
|
SQUISH environment variables. If even that fails, the AREAPATH or
|
|
GOLDPATH is used. If AREAFILE Maximus is used, <name>GoldED+</name> gets the
|
|
filename from MAX.PRM.
|
|
</p>
|
|
</div2>
|
|
<div2 id=STATUSLINECLOCK>
|
|
<head>
|
|
STATUSLINECLOCK <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will display a clock in HH:MM:SS format in the
|
|
right side of the statusline.
|
|
</p>
|
|
<p>
|
|
You can redefine the clock format with the language keyword
|
|
ST_STATUSLINETIMEFMT in GOLDLANG.CFG. See the Language Definition
|
|
chapter to details about the date/time codes you can use.
|
|
</p>
|
|
<p>
|
|
NOTE: The clock will only run continuously if KEYBMODE is set to
|
|
"poll".
|
|
</p>
|
|
</div2>
|
|
<div2 id=STATUSLINEHELP>
|
|
<head>
|
|
STATUSLINEHELP <yes/no/nologo>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If set to YES, <name>GoldED+</name> will replace the "logo" in the left side of
|
|
the statusline with a text saying "F1 Help". This is for use in
|
|
"point package" setups where the user may be a complete novice,
|
|
maybe even to computers, and who needs to be guided to the help
|
|
screens. The "F1 Help" text is configurable with the
|
|
ST_STATUSLINEHELP language keyword (put it in GOLDLANG.CFG).
|
|
</p>
|
|
<p>
|
|
If set to NO, <name>GoldED+</name> will display it's logo (name and version) in
|
|
the left side of the statusline.
|
|
</p>
|
|
<p>
|
|
If set to NOLOGO, <name>GoldED+</name> will not display anything in the left
|
|
side. The middle part is extended to fill the space on the left
|
|
side.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
STYLECODES <yes/hide/no>
|
|
</head>
|
|
<p>
|
|
(hide)
|
|
</p>
|
|
<p>
|
|
If enabled (yes or hide), <name>GoldED+</name> will highlight text surrounded by
|
|
one of the following characters in a different color: '*' for bold
|
|
text, '/' for italic text, '_' for underlined text and '#' for
|
|
reversed text. These are commonly used "stylecodes" which add
|
|
emphasis to the text, without making it harder to read. Examples:
|
|
*This* will be shown in bold color, /this/ in italic color and
|
|
_this_ in underlined color. It is also possible to combine styles,
|
|
such as */this/*, in bolditalic color.
|
|
</p>
|
|
<p>
|
|
The differ in yes and hide is that hide strips surrounding
|
|
stylecodes.
|
|
</p>
|
|
<p>
|
|
Described values are specific to -asa. Official vesions starting
|
|
at 3.00beta3 has bug in implementation which causes GoldEd to
|
|
ignore this keyword. Realization of this keyword in -asa versions
|
|
compatible with official versions prior to 3.00beta3.
|
|
</p>
|
|
<p>
|
|
To define the highlight colors, use COLOR STYLECODE. See the color
|
|
chapter for details.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
STYLECODEPUNCT <"charlist">
|
|
</head>
|
|
<p>
|
|
(<q>!\"$%&()+,.:;<=>@[\]^`{|}~</q>)
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
STYLECODESTOPS <"charlist">
|
|
</head>
|
|
<p>
|
|
("")
|
|
</p>
|
|
<p>
|
|
The STYLECODEPUNCT keyword specifies all the characters that
|
|
punctuates words. The stylecode line parser scans forward until it
|
|
meets one of these characters and then looks back to see if it
|
|
found a word with stylecodes around it.
|
|
</p>
|
|
<p>
|
|
The STYLECODESTOPS keyword specifies characters which, if found
|
|
within the word to be highlighted, causes the highlight to be
|
|
cancelled.
|
|
</p>
|
|
<p>
|
|
These keywords were added to allow users to experiment with the
|
|
characters for punctuation and stop for stylecode sequences. This
|
|
is mostly to illustrate the point that it is almost impossible to
|
|
make stylecodes work in every case you want without getting a lot
|
|
of false highlights too. Please keep in mind that stylecodes are,
|
|
and always will be, a primitive and very error-prone method for
|
|
adding highlights to message text. The defaults are:
|
|
</p>
|
|
<p>
|
|
STYLECODEPUNCT <q>!\"$%&()+,.:;<=>@[\]^`{|}~</q>
|
|
STYLECODESTOPS <q></q>
|
|
</p>
|
|
<p>
|
|
Note that the double-quote (") must have the backslash (\) in
|
|
front of it - the sequence (\") is translated to a single (").
|
|
</p>
|
|
</div2>
|
|
<div2 id=TAGLINE>
|
|
<head>
|
|
TAGLINE <string or filename>
|
|
</head>
|
|
<p>
|
|
Defines one or more taglines. A tagline collection filename can be
|
|
specified if prepended with an '@' character, like this: TAGLINE
|
|
@TAGLINE.LST. If a tagline collection file is used, <name>GoldED+</name> will
|
|
create an index file for it the first time it is used or any time
|
|
the file is edited. The index file has the same name, but
|
|
extension ".SDX". The index file is an array of 32-bit long
|
|
integers, containing the offset of each line in the tagline
|
|
collection file.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
<p>
|
|
Taglines defined in the Random System *always* overrides the
|
|
default global taglines defined with this keyword.
|
|
</p>
|
|
</div2>
|
|
<div2 id=TAGLINECHAR>
|
|
<head>
|
|
TAGLINECHAR <char>
|
|
</head>
|
|
<p>
|
|
('.')
|
|
</p>
|
|
<p>
|
|
Defines the character <name>GoldED+</name> uses when putting a tagline in your
|
|
message. The default is '.'. You should not change this default.
|
|
<name>GoldED+</name> itself only recognizes taglines with '.' or '_'
|
|
(underscore).
|
|
</p>
|
|
</div2>
|
|
<div2 id=TAGLINESUPPORT>
|
|
<head>
|
|
TAGLINESUPPORT <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
Allows you to turn off the internal tagline support, in case it
|
|
turns out to be too buggy or if you want to use one of the many
|
|
good external tagline utilties out there instead.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TASKTITLE <string>
|
|
</head>
|
|
<p>
|
|
(@longpid)
|
|
</p>
|
|
<p>
|
|
Sets window title in Win32 and OS/2 versions, ignored in other.
|
|
</p>
|
|
</div2>
|
|
<div2 id=TEARLINE>
|
|
<head>
|
|
TEARLINE <string>
|
|
</head>
|
|
<p>
|
|
(@longpid @version)
|
|
</p>
|
|
<p>
|
|
Here you can define your default tearline. The tearline can be up
|
|
to 76 chars long (excluding the leading "--- "), but beware that
|
|
policies (such as FidoNet ECHOPOL1) may set a significantly lower
|
|
limit (around 30).
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
<p>
|
|
Tearlines defined in the Random System *always* overrides the
|
|
default tearline defined with this keyword.
|
|
</p>
|
|
<p>
|
|
If your tearline does not contain at least the string "GoldED" or
|
|
"GED", <name>GoldED+</name> will automatically insert it's PID kludge. See also
|
|
description of USEPID keyword.
|
|
</p>
|
|
</div2>
|
|
<div2 id=TEMPLATE>
|
|
<head>
|
|
TEMPLATE <file> ["desc"] [match-address]
|
|
</head>
|
|
<p>
|
|
(GOLDED.TPL)
|
|
</p>
|
|
<p>
|
|
You can define many different template files. The templates can be
|
|
switched using the READchangetemplate (Ctrl-T) popup menu or the
|
|
EDITMENU.
|
|
</p>
|
|
<p>
|
|
The optional "desc" can be used to give the templates more
|
|
meaningful names like "International template" instead of
|
|
non-obvious names like "GOLDED.TPL". If a description is used, it
|
|
must appear before the match-address. It must always be enclosed
|
|
in quotes, even if it is only one word.
|
|
</p>
|
|
<p>
|
|
The match-address is an address mask (wildcards allowed) which can
|
|
be used to tell <name>GoldED+</name> to select that template if the destination
|
|
address on a message you write matches the match-address. The
|
|
matching will only take place if the TEMPLATEMATCH keyword has
|
|
been enabled.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group. In
|
|
Random System groups, only the <file> parameter can be used.
|
|
</p>
|
|
<p>
|
|
Templates defined in Random System groups always override the
|
|
globally defined templates, except when selected from the EDITMENU
|
|
or when automatic template matching is in effect.
|
|
</p>
|
|
<p>
|
|
To override the automatic template matching, start by selecting a
|
|
template manually using the READchangetemplate (Ctrl-T) command or
|
|
the EDITMENU.
|
|
</p>
|
|
<p>
|
|
Currently only one match-address per template can be specified,
|
|
but you can specify several TEMPLATE keywords for the same file.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
// Use DANSK.TPL for messages to Danish nodes/points.
|
|
TEMPLATE DANSK.TPL "Danish" 2:23/*
|
|
TEMPLATE DANSK.TPL "Danish" 2:234/*
|
|
TEMPLATE DANSK.TPL "Danish" 2:235/*
|
|
TEMPLATE DANSK.TPL "Danish" 2:236/*
|
|
TEMPLATE DANSK.TPL "Danish" 2:237/*
|
|
TEMPLATE DANSK.TPL "Danish" 2:238/*
|
|
</p>
|
|
<p>
|
|
// Use INTERNET.TPL for messages to the WinBoss gateway
|
|
TEMPLATE INTERNET.TPL "Internet" 2:230/9316
|
|
</p>
|
|
<p>
|
|
// Use ENGLISH.TPL for messages to everywhere else
|
|
TEMPLATE ENGLISH.TPL "English" *
|
|
</p>
|
|
</div2>
|
|
<div2 id=TEMPLATEMATCH>
|
|
<head>
|
|
TEMPLATEMATCH <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will select a template which matches the
|
|
destination address on messages that you write. This keyword can
|
|
be used globally or in random system groups.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TEMPLATEPATH <path>
|
|
</head>
|
|
<p>
|
|
(defaults to the GOLDPATH)
|
|
</p>
|
|
<p>
|
|
Defines the default path for msg templates. Use this if you want
|
|
to place templates in a path separate from the GOLDPATH.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TEMPPATH <path>
|
|
</head>
|
|
<p>
|
|
Defines the directory where temporary files are placed by <name>GoldED+</name>
|
|
and GoldNODE.
|
|
</p>
|
|
<p>
|
|
This path should *NOT* point to a RAM disk or other volatile
|
|
media!
|
|
</p>
|
|
<p>
|
|
GoldNODE uses this path to store a temporary file which can become
|
|
as large as the largest index file (GOLDNODE.GXN), so again, don't
|
|
point it to a small RAM disk. If GoldNODE cannot find a TEMPPATH,
|
|
it will use the NODEPATH instead.
|
|
</p>
|
|
</div2>
|
|
<div2 id=TIMEOUT><head>TIMEOUT <seconds></head>
|
|
<p>
|
|
(0)
|
|
</p>
|
|
<p>
|
|
Similar to the screen blanking (SCREENBLANKER) feature, <name>GoldED+</name> can
|
|
auto-exit after a specified period of time. Useful if you are in a
|
|
hurry (or didn't get enough sleep last night ;-), and run <name>GoldED+</name>
|
|
from your mailer shell. The timeout value can be overridden with
|
|
the -T commandline option.
|
|
</p>
|
|
<p>
|
|
NOTE: This feature only works if KEYBMODE is set to "poll".
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TIMEOUTSAVEMSG <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If set to YES, <name>GoldED+</name> behaves as usual: It saves the (perhaps
|
|
partially written) msg text in the internal editor to the msgbase
|
|
and exits. If set to NO, <name>GoldED+</name> will save the msg text in
|
|
GOLDED.MSG just as if EDITAUTOSAVE function was in use and the
|
|
power went out. Next time you started <name>GoldED+</name> and entered a msg, it
|
|
would detect the "lost" msg and ask you if it should be continued.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TITLESTATUS <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled then brief status will be added to title. (Win32 and
|
|
OS/2 versions only)
|
|
</p>
|
|
</div2>
|
|
<div2 id=TWITMODE>
|
|
<head>
|
|
TWITMODE <mode>
|
|
</head>
|
|
<p>
|
|
(Blank)
|
|
</p>
|
|
<p>
|
|
In <name>GoldED+</name> you can define several "Twit" names, addresses or
|
|
subjects. With this keyword you can specify the action taken when
|
|
a Twit message is encountered.
|
|
</p>
|
|
<p>
|
|
The <mode> can be one of the following:
|
|
</p>
|
|
<p>
|
|
Show Show twit messages.
|
|
Blank Blank twit messages.
|
|
Skip Skip twit messages, unless to your USERNAME's.
|
|
Ignore Skip twit messages, always.
|
|
Kill Deletes twit messages, *without* confirmation!
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TWITNAME <name/address>
|
|
</head>
|
|
<p>
|
|
With this keyword, you can specify "Twit" names and/or addresses.
|
|
When a Twit name/address is detected, the TWITMODE setting will
|
|
determine the action taken.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TWITSUBJ <"string">
|
|
</head>
|
|
<p>
|
|
With this keyword, you can specify "Twit" subjects. When a Twit
|
|
subject is detected, the TWITMODE setting will determine the
|
|
action taken. The subject string is searched in the entire subject
|
|
text, so you can specify a partial twit subject. Twit subjects are
|
|
limited to maximum 35 characters.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TWITTO <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> will check both from- and to-names when
|
|
checking for twitnames. By default only the from-names are
|
|
checked.
|
|
</p>
|
|
<p>
|
|
This is a global keyword and won't work as intended if used in a
|
|
random system group.
|
|
</p>
|
|
</div2>
|
|
<div2 id=UNPACKER>
|
|
<head>
|
|
UNPACKER
|
|
</head>
|
|
<p>
|
|
Added ability to READ packed messagebases. You need to add PKD
|
|
attribute to such echo definition and specify UNPACKER for the
|
|
extension defined. You should pack all files from the single
|
|
messagebase to the archive with the same name. For *.msg areas you
|
|
should add the directory as well. When entering to the archived area
|
|
UNPACKER will be executed to unpack files to TEMPPATH. On exit, all
|
|
files will be deleted.
|
|
|
|
New UNPACKER keyword have the following syntax:
|
|
|
|
UNPACKER >extension< ><q/commandline/<
|
|
|
|
The commandline should provide the ability to extract all files from
|
|
@file.<extension> to the current directory. F.e.:
|
|
|
|
UNPACKER zip <q/unzip @file/
|
|
|
|
Note that all changes to the messagebase will be discarded.
|
|
|
|
This feature is not supported for Hudson and GoldBase messagebases.
|
|
</p>
|
|
</div2>
|
|
<div2 id=USEAREA>
|
|
<head>
|
|
USEAREA <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If set to no then GoldEd will not recognize <gi/AREA/ kludge.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
USECHARSET <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If set to no then GoldEd will not generate @CHRS and @CHARSET
|
|
kludges.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
USEFLAGS <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> inserts the FLAGS kludge for certain extended
|
|
attributes, as defined in FSC-0053 by Joaquim H. Homrighausen, and
|
|
supported by FrontDoor, D'Bridge, IMail and other modern software.
|
|
<name>GoldED+</name> uses FLAGS to emulate the Hold and Freq attributes which
|
|
are not defined in the Hudson message format.
|
|
</p>
|
|
</div2>
|
|
<div2 id=USEFWD>
|
|
<head>
|
|
USEFWD <yes/no/ask>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, <name>GoldED+</name> inserts the FSC-0092 kludges introduced by the
|
|
author of FleetStreet, Michael Hohner. These are
|
|
</p>
|
|
<p>
|
|
FWDFROM The original From-Name
|
|
FWDORIG The original From-Aka
|
|
FWDTO The original TO-Field
|
|
FWDDEST The original TO-aka (only in netmails)
|
|
FWDSUBJ The original subject
|
|
FWDAREA The original areatag
|
|
FWDMSGID The original MSGID (useful for reply-linking)
|
|
</p>
|
|
<p>
|
|
When forwarding, <name>GoldED+</name> now adds these kludges, unless the
|
|
original message already contains them, in which case they are
|
|
preserved. When doing a normal reply (Alt-Q or Alt-R) to a message
|
|
with the FWD kludges, <name>GoldED+</name> replies to the forwarder. To reply to
|
|
the from-name in the forwarded message, use the comment-reply
|
|
function (Alt-G). If the message contains the FWDAREA kludge, you
|
|
can reply to the forwarder in the original area (Alt-N) or reply
|
|
to the from-name in the original area (Alt-B). Note that it is not
|
|
possible to reply to the to-name of a message with the FWD
|
|
kludges, and it is also not possible to reply to the to-name of
|
|
the forwarded message (the FWDTO name).
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
USEINTL <type>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
The INTL kludge is normally only inserted in netmail messages, if
|
|
the origination zone is different from the destination zone (the
|
|
"Auto" setting), but on systems with many AKA's in the mailer, it
|
|
might be useful/necessary to add it ALWAYS (the "Yes" setting).
|
|
The "No" option should never be used.
|
|
</p>
|
|
<p>
|
|
The <type> can be one of the following:
|
|
</p>
|
|
<p>
|
|
Auto Only insert in inter-zone netmail.
|
|
Yes Always insert. Recommended and default.
|
|
No Never insert.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
USEMSGID <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
If enabled, the MSGID kludge is inserted in netmail and echomail,
|
|
and the REPLY kludge is inserted when replying to a msg with a
|
|
MSGID.
|
|
</p>
|
|
<p>
|
|
The MSGID kludge is defined in FidoNet document FTS-9.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
USEPID <yes/no>
|
|
</head>
|
|
<p>
|
|
(no if GoldEd mentioned in tearline, yes otherwise)
|
|
</p>
|
|
<p>
|
|
If disabled then @PID kludge will not be used in your messages
|
|
regardless of tearline contents.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
USERLIST <file> [zone/addr]
|
|
</head>
|
|
<p>
|
|
In addition to normal nodelist support, <name>GoldED+</name> also supports the
|
|
"FIDOUSER.LST" style userlist format. The default zone is defined
|
|
by the first ADDRESS or AKA, but can be overridden by adding the
|
|
zone number or a full address after the filename.
|
|
</p>
|
|
<p>
|
|
<file> Userlist file in FIDOUSER.LST format.
|
|
[zone/addr] Default address for the userlist (if no zone info
|
|
is present).
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
USERLISTFILE <file>
|
|
</head>
|
|
<p>
|
|
(GOLDED.LST)
|
|
</p>
|
|
<p>
|
|
<name>GoldED+</name> can generate a list of all users in the current area. This
|
|
keyword defines the default name of the FIDOUSER.LST style
|
|
userlist output file generated with the READmakeuserlist command.
|
|
</p>
|
|
</div2>
|
|
<div2 id=USERNAME>
|
|
<head>
|
|
USERNAME <name>[[,]< >address]
|
|
</head>
|
|
<p>
|
|
You can define many different names/aliases. When <name>GoldED+</name> finds an
|
|
un-received message to one of your USERNAME's, it is marked as
|
|
received. Useful if you use alias names in some conferences. It is
|
|
possible to change the current name using the READchangeusername
|
|
popup menu.
|
|
</p>
|
|
<p>
|
|
For msgbase formats with an associated user database, <name>GoldED+</name> uses
|
|
the *first* defined USERNAME to look in the user database for
|
|
which lastread record to use. If your name is not found, it is
|
|
added and a new lastread record created.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
USERNAME Odinn Sorensen, 2:236/77.999
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2 id=USETZUTC>
|
|
<head>
|
|
USETZUTC <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
Activates usage of TZUTC kludge in your messages. You should
|
|
properly setup timezone information in your OS. For example,
|
|
in DOS you should set environment variable TZ to something
|
|
like this:
|
|
</p>
|
|
<p>
|
|
TZ=MSK-3MSD,M3.5.0/02:00,M10.5.0/03:00
|
|
</p>
|
|
<p>
|
|
This line valid for Moscow, Russia.
|
|
</p>
|
|
<p>
|
|
This option could be used in random system groups.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
UUDECODEPATH <path>
|
|
</head>
|
|
<p>
|
|
Specifies the path where files are placed when using the uudecode
|
|
feature. Files are placed in current directory if a path is not
|
|
specified.
|
|
</p>
|
|
<p>
|
|
The specified path *must* exist !
|
|
</p>
|
|
</div2>
|
|
<div2 id=VIEWHIDDEN>
|
|
<head>
|
|
VIEWHIDDEN <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
Hidden lines are "unknown" kludge lines. If enabled, hidden lines
|
|
will be displayed (in a different color) when reading msgs.
|
|
</p>
|
|
<p>
|
|
A hidden line is defined as a line which has the FidoNet kludge
|
|
char (^a, ASCII 1) as the first char and is not on the list of
|
|
internally or user defined known kludges.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
<p>
|
|
IMPORTANT NOTE:
|
|
</p>
|
|
<p>
|
|
In some conferences the hidden lines are used to give witty
|
|
comment "between the lines" in the plain text, but generally it is
|
|
considered a bad practice and should be avoided because it may
|
|
cause severe technical problems if a witty comment in a hidden
|
|
line happens to match a (perhaps experimentally) defined kludge
|
|
somewhere. It should also be noted that hidden lines are not kept
|
|
in their original places when used in the JAM msgbase. This is due
|
|
to the way the JAM specification stores FidoNet kludges.
|
|
</p>
|
|
</div2>
|
|
<div2 id=VIEWKLUDGE>
|
|
<head>
|
|
VIEWKLUDGE <yes/no>
|
|
</head>
|
|
<p>
|
|
(no)
|
|
</p>
|
|
<p>
|
|
If enabled, known kludge lines will be displayed (in a different
|
|
color) when reading msgs.
|
|
</p>
|
|
<p>
|
|
Known kludges are those defined internally in <name>GoldED+</name> plus those
|
|
defined with the KLUDGE keyword.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2 id=VIEWQUOTE>
|
|
<head>
|
|
VIEWQUOTE <yes/no>
|
|
</head>
|
|
<p>
|
|
(yes)
|
|
</p>
|
|
<p>
|
|
This is an experimental feature. It is similar to the VIEWHIDDEN
|
|
and VIEWKLUDGE keywords, but for quoted text. I implemented it
|
|
because I was annoyed with the excessive quoting often seen in
|
|
Internet newsgroups. When this keyword is set to NO, <name>GoldED+</name>
|
|
attempts to trim down the quotes so that only the first line of
|
|
each quote block is shown. It is not always successful, sometimes
|
|
the result is not so useful.
|
|
</p>
|
|
<p>
|
|
A key command has been added to supplement this feature:
|
|
READtogglequote. Suggested key assignment: Ctrl-V. Example:
|
|
</p>
|
|
<p>
|
|
^V READtogglequote
|
|
</p>
|
|
<p>
|
|
Try it out if you are annoyed with excessive quotes.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2 id=WHOTO>
|
|
<head>
|
|
WHOTO <name>
|
|
</head>
|
|
<p>
|
|
This name is inserted in the TO: name field, when entering new
|
|
messages (not replies) in echomail or local areas.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2 id=WILDCATUSERNO>
|
|
<head>
|
|
WILDCATUSERNO <userno>
|
|
</head>
|
|
<p>
|
|
Defines the lastread set used in the WildCat! 4.x message base.
|
|
</p>
|
|
</div2>
|
|
<div2 id=WRITETEMPLATE>
|
|
<head>
|
|
WRITETEMPLATE
|
|
</head>
|
|
<p></p>
|
|
</div2>
|
|
<div2 id=XLATCHARSET>
|
|
<head>
|
|
XLATCHARSET <importid> <exportid> <file>
|
|
</head>
|
|
<p>
|
|
This keyword defines character set translation table files.
|
|
</p>
|
|
<p>
|
|
<importid> Charset import identifier.
|
|
<exportid> Charset export identifier.
|
|
<file> Charset translation table file.
|
|
</p>
|
|
<p>
|
|
See the Character Translation chapter for details.
|
|
</p>
|
|
</div2>
|
|
<div2 id=XLATESCSET>
|
|
<head>
|
|
XLATESCSET <import> <export> <escfile>
|
|
</head>
|
|
<p>
|
|
This keyword defines escape sequence translation table files.
|
|
</p>
|
|
<p>
|
|
<importid> Escset import identifier.
|
|
<exportid> Escset export identifier.
|
|
<file> Escape sequence translation table file.
|
|
</p>
|
|
<p>
|
|
See the Character Translation chapter for details.
|
|
</p>
|
|
</div2>
|
|
<div2 id=XLATEXPORT>
|
|
<head>
|
|
XLATEXPORT <charsetid>
|
|
</head>
|
|
<p>
|
|
Defines the export charset for your messages. See the Character
|
|
Translation chapter for details.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
<p>
|
|
It can also be used in templates (the @xlatexport token).
|
|
</p>
|
|
</div2>
|
|
<div2 id=XLATIMPORT>
|
|
<head>
|
|
XLATIMPORT <charsetid>
|
|
</head>
|
|
<p>
|
|
(IBMPC)
|
|
</p>
|
|
<p>
|
|
Defines the local charset for your machine. See the Character
|
|
Translation chapter for details.
|
|
</p>
|
|
<p>
|
|
This keyword can be used globally and in a Random System group.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
XLATLOCALSET <charsetid>
|
|
</head>
|
|
<p>
|
|
(IBMPC)
|
|
</p>
|
|
<p>
|
|
Use this keyword to specify the actual physical charset in effect
|
|
for text screen display. This was previously the hardcoded value
|
|
IBMPC, corresponding to the IBM codepage 437 (or the nordic
|
|
edition 865).
|
|
</p>
|
|
<p>
|
|
NOTE: All charset translation files must translate from and to the
|
|
charset identified with the XLATLOCALSET keyword!
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
XLATPATH <path>
|
|
</head>
|
|
<p>
|
|
This is the path where <name>GoldED+</name> tries to find the XLATCHARSET and
|
|
XLATESCSET files.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ZONEGATING <yes/no/ask>
|
|
</head>
|
|
<p>
|
|
(ask)
|
|
</p>
|
|
<p>
|
|
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). <name>GoldED+</name>
|
|
won't ask if Cra or Hld attribute is set.
|
|
</p>
|
|
<p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Obsolete Keywords
|
|
</head>
|
|
<p>
|
|
This is a list of keywords which were used in various older versions.
|
|
These keywords are now obsolete, either because they have been renamed
|
|
or replaced, or if they no longer have any function. Most of the
|
|
keywords are still active and remapped to the new names.
|
|
</p>
|
|
<p>
|
|
To check if you have obsolete keywords in your setup, run <name>GoldED+</name> with
|
|
the -F -D commandline parameters. Then if you get a number of "Unknown
|
|
keyword" warnings, you should replace the old keywords with the new
|
|
ones or remove them.
|
|
</p>
|
|
<p>
|
|
Old keyword: New keyword:
|
|
</p>
|
|
<p>
|
|
AREAAUTOFREQ AREAFREQTO
|
|
AREABADMSGS SOUPBADMSGS
|
|
AREASORT AREALISTSORT
|
|
ASSIGNTO MEMBER
|
|
AUTOATTACH EDITAUTOATTACH
|
|
BLANKTIME SCREENBLANKER
|
|
BOARDNOS (removed)
|
|
CCATTRIB ATTRIBSCC
|
|
CCLIST CARBONCOPYLIST
|
|
CFMATTRIB ATTRIBSCFM
|
|
CHANGEDATE EDITCHANGEDATE
|
|
CHANGEPROMPT (removed)
|
|
CHARSET XLATCHARSET
|
|
CLEARKEYS (removed)
|
|
COLOUR COLOR
|
|
COMMENTNOISE BEEPCOMMENT
|
|
COOKIEFILE (removed)
|
|
CRLFTERM EDITCRLFTERM
|
|
DELORIG ASKDELORIG
|
|
DISPMSGLIST MSGLISTFIRST
|
|
DISPMSGLISTFAST MSGLISTFAST
|
|
DISPSTYLECODES STYLECODES
|
|
DOSSWAP (removed)
|
|
ECHOATTRIB ATTRIBSECHO
|
|
ECHOINFO CTRLINFOECHO
|
|
EDITMARGIN (removed)
|
|
EDITORVERSION (removed)
|
|
ELIMSNOW (removed)
|
|
ESCSET XLATESCSET
|
|
EXCLAREA AREAEXCL
|
|
EXPORTCHARSET XLATEXPORT
|
|
EXTKEYS (removed)
|
|
FIDOLASTREADNO FIDOUSERNO
|
|
FIELDCLEAR EDITFIELDCLEAR
|
|
FILECHECK (removed)
|
|
FILECHECKALL (removed)
|
|
FREEAREA (removed)
|
|
FREETEAR (removed)
|
|
GOLDEDCFM CONFIRMFILE
|
|
GOLDEDLOG LOGFILE
|
|
GOLDEDLST USERLISTFILE
|
|
GOLDEDMSG EDITORFILE
|
|
GOLDEDNAM NAMESFILE
|
|
GOLDEDPRN OUTPUTFILE
|
|
GOLDHELP (no longer documented)
|
|
GOLDKEYS (no longer documented)
|
|
GOLDLANG (no longer documented)
|
|
GOLDRAND (no longer documented)
|
|
GOLDXLAT (no longer documented)
|
|
HARDLINE EDITHARDLINE
|
|
HARDLINES EDITHARDLINES
|
|
HWMARKS (removed)
|
|
INCLAREA AREAINCL
|
|
INTERNALEDITOR EDITINTERNAL
|
|
LASTREAD FIDOLASTREAD
|
|
LASTREADUSER FIDOUSERNO
|
|
LISTWRAP (removed)
|
|
LOCALATTRIB ATTRIBSLOCAL
|
|
LOCALCHARSET XLATIMPORT
|
|
LOCALHIGHLIGHT (removed)
|
|
LOCALINFO CTRLINFOLOCAL
|
|
LOCALNOISE (removed)
|
|
MAPDRIVE MAPPATH
|
|
MATCHAKA AKAMATCH
|
|
MAXCOLS SCREENMAXCOL
|
|
MAXMSGSIZE (removed)
|
|
EDITMSGSIZE (removed)
|
|
MAXROWS SCREENMAXROW
|
|
MIXCASE EDITMIXCASE
|
|
MULTIQBBS (removed)
|
|
NETATTRIB ATTRIBSNET
|
|
NETINFO CTRLINFONET
|
|
NETTEAR CTRLINFONET performs similar function
|
|
NEXTAREA AREANEXT
|
|
NEXTMSGS (removed)
|
|
NODELISTPAGEBAR (removed)
|
|
NOISEFACTOR (removed)
|
|
OVERLAY (removed)
|
|
OVERLAYEMS (removed)
|
|
OVERLAYEXT (removed)
|
|
PAGEBAR (removed)
|
|
QBBSINCRESCAN (removed)
|
|
QBBSPATH HUDSONPATH
|
|
QBBSREBUILD (removed)
|
|
QBBSSCAN (removed)
|
|
QMSGPATH HUDSONPATH
|
|
REALMSGNO (removed)
|
|
REBUILD (removed)
|
|
RENAREA AREARENAME
|
|
REPLYRE EDITREPLYRE
|
|
RIGHTMARGIN DISPMARGIN
|
|
SAVEMENU EDITSAVEMENU
|
|
SAVETIME EDITAUTOSAVE
|
|
SAYBIBI (removed)
|
|
SCANAREA AREASCAN
|
|
SCREENELIMSNOW (removed)
|
|
SCREENUSEANSI (removed)
|
|
SHADOWS (removed)
|
|
SHARE SHAREMODE
|
|
SHOWTWITS TWITMODE
|
|
SIGNALFILE SEMAPHORE
|
|
SOUNDDEVICE (removed)
|
|
SPACEQUOTES (removed)
|
|
SPELLCHECKER EDITSPELLCHECK
|
|
STACKKEYS KEYBSTACK
|
|
STARTECHO AREASTART
|
|
SWAPALL (removed)
|
|
SYSOP USERNAME
|
|
TABSIZE DISPTABSIZE
|
|
TAGLINEFILE (removed)
|
|
TIMESLICE (removed)
|
|
TIMEZONEOFFSET USETZUTC performs similar function
|
|
UNDELETELINES EDITUNDELETE
|
|
USEBIOS SCREENUSEBIOS
|
|
XPLIST CROSSPOSTLIST
|
|
</p>
|
|
<p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Location Dependent Configuration Keywords
|
|
</head>
|
|
<p>
|
|
The following configuration keywords are location dependent and should
|
|
be placed in a particular order in the configuration file(s). Keywords
|
|
that are *not* listed can be placed anywhere you want.
|
|
</p>
|
|
<p>
|
|
The keywords are listed in groups of those that depend on each other.
|
|
They are listed in the recommended order within each group. The order
|
|
between the groups is not important, with one noted exception.
|
|
</p>
|
|
<p>
|
|
Name/Address/Areas:
|
|
USERNAME
|
|
ADDRESS
|
|
AKA
|
|
ATTRIBSNET Specifies default attributes for AREAFILE etc.
|
|
ATTRIBSECHO As above.
|
|
ATTRIBSLOCAL As above.
|
|
FIDOMSGTYPE
|
|
PCBOARDPATH Recommended if you use PCBoard.
|
|
MAPPATH
|
|
AREARENAME Rename occurs before AREAEXCL/INCL.
|
|
AREAEXCL
|
|
AREAINCL
|
|
AREAISEMAIL
|
|
AREAISNEWS
|
|
AREAPATH Default path for the AREAFILE's.
|
|
AREAFILE
|
|
RA2USERSBBS Overrides AREAFILE RemoteAccess.
|
|
AREADESC Add description and more to some AREAFILE's.
|
|
AREA Overrides areas in AREAFILE's.
|
|
AREADEF As above.
|
|
</p>
|
|
<p>
|
|
Paths:
|
|
GOLDPATH
|
|
TEMPPATH MUST be in GOLDED.CFG. Used only by GoldNODE.
|
|
</p>
|
|
<p>
|
|
Nodelists: MUST be below ADDRESS/AKA and ONLY in GOLDED.CFG!
|
|
NODEPATH
|
|
NODELIST
|
|
USERLIST
|
|
EXCLUDENODES Remember to replace "ALL" with '*'.
|
|
INCLUDENODES As above.
|
|
</p>
|
|
<p>
|
|
Colors:
|
|
INTENSECOLORS Selects a default intense colorset if enabled.
|
|
COLORSET Selects a default colorset.
|
|
COLOR
|
|
</p>
|
|
<p>
|
|
External utils:
|
|
EXTERNOPTIONS
|
|
EXTERNUTIL
|
|
</p>
|
|
<p>
|
|
Character translation:
|
|
XLATPATH
|
|
XLATCHARSET
|
|
XLATESCSET
|
|
</p>
|
|
<p>
|
|
Random System:
|
|
GROUP Starts a group.
|
|
MEMBER Defines areas that are members of the group.
|
|
<Group Items> See the Random System chapter for a list.
|
|
ENDGROUP Ends a group.
|
|
</p>
|
|
<p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div1>
|
|
<div1 id=MESSAGEATTRS><head>Message Attributes Reference</head>
|
|
<p>
|
|
This is a list and description of all message attributes that are
|
|
supported by <name>GoldED+</name> in the keywords that accept attribute settings or
|
|
can be displayed in the header.
|
|
</p>
|
|
<p>
|
|
A/S Archive/sent.
|
|
ARQ Audit request.
|
|
ATT File attached.
|
|
CFM Confirmation receipt requested.
|
|
COV Fax cover letter.
|
|
CRA Crash - high priority mail.
|
|
DEL Deleted.
|
|
DIR Direct. Don't route this message.
|
|
FAX Fax image attached.
|
|
FRQ File request.
|
|
GRP Group message.
|
|
HIR Fax hi-resolution image.
|
|
HLD Hold for pickup.
|
|
HUB Host- or Hub-route message.
|
|
IMM Immediate - Send message NOW!
|
|
K/S Kill/sent. Delete message automatically after it is sent.
|
|
KFS Kill/file/sent. Delete attached files after they are sent.
|
|
LET Fax letterhead.
|
|
LOC Local. Message was written on your system.
|
|
LOK Lock. Prevents send/delete/purge/editing.
|
|
ORP Orphan. Could not be sent because destination node is unknown.
|
|
PKD Packed. Used in area definitions to unpack before using.
|
|
PRN Msg has been printed. Specific for Squish (bitvalue 00040000h).
|
|
PVT Private. Message may only be read by the addressee and author.
|
|
R/O Read only. Used in area definitions to prevent writing.
|
|
RCV Received. Read by the addressee.
|
|
RRC Return receipt.
|
|
RRQ Return receipt requested.
|
|
RSV FTS-1 reserved (unused) attribute.
|
|
SIG Fax signature.
|
|
SNT Sent. Message has been sent or exported from the msgbase.
|
|
TFS Truncate/file/sent. Truncate files to zero length when sent.
|
|
TRS Transit. Message passing through, not for you.
|
|
UNS Unsent message.
|
|
URQ Update file request.
|
|
XMA Xmail. Attach does not conform to the ARCmail 0.60 standard.
|
|
ZON Zonegate. Route through zonegate if possible.
|
|
</p>
|
|
<p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div1>
|
|
<div1 id=AREACONFIGURATION><head>Area Configuration</head>
|
|
<p>
|
|
GoldED offers a wide variety of methods for defining message areas.
|
|
You can define each area manually in the GOLDED.CFG file (or an
|
|
INCLUDE'ed GOLDAREA.CFG file), or you can tell <name>GoldED+</name> to read the area
|
|
setup files of many popular BBS/mailer/mail processor packages.
|
|
</p>
|
|
<p>
|
|
For manual definition of areas, use the AREA or AREADEF (recommened)
|
|
keywords.
|
|
</p>
|
|
<p>
|
|
For external area configuration, the general syntax for the AREAFILE
|
|
keyword is:
|
|
</p>
|
|
<p>
|
|
AREAFILE <programname> [path or filename(s)] [-options]
|
|
</p>
|
|
<p>
|
|
Available options:
|
|
</p>
|
|
<p>
|
|
-S<sortspec>
|
|
</p>
|
|
<p>
|
|
If you are *not* using the global AREALISTSORT keyword for sorting
|
|
all the areas, you can sort the areas of each AREAFILE separately.
|
|
See the AREALISTSORT keyword for the definition of <sortspec>.
|
|
</p>
|
|
<p>
|
|
If no path is specified, the appropriate environment variable or the
|
|
AREAPATH is used to find the files.
|
|
</p>
|
|
<p>
|
|
The <programname> can be one of the following:
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
AdeptXBBS
|
|
</head>
|
|
<p>
|
|
Reads the AdeptXBBS configuration files.
|
|
</p>
|
|
<p>
|
|
Looks for the ADEPTXBBS environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
AreasBBS
|
|
</head>
|
|
<p>
|
|
<name>GoldED+</name> is can handle a wide variety of AREAS.BBS type files. It
|
|
can read and distinguish between the old CONFMAIL style with paths
|
|
for *.MSG areas, the Hudson/Goldbase style with board numbers, the
|
|
Squish style with "$basename" and the JAM style with "!basename".
|
|
</p>
|
|
<p>
|
|
The disadvantage of using an AREAS.BBS is that there are no area
|
|
descriptions. The echoid is used as description instead. However,
|
|
<name>GoldED+</name> will use any text behind a semicolon on definition lines as
|
|
description. This may or may not be compatible with mail
|
|
processors, so be careful. A better solution may be to use the
|
|
AREAFILE Echolist to add descriptions from a separate file.
|
|
</p>
|
|
<p>
|
|
One or more AREAS.BBS files may be specified on the same line.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Concord
|
|
</head>
|
|
<p>
|
|
Support is planned but not yet implemented.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Crashmail
|
|
</head>
|
|
<p>
|
|
Reads the CrashMail II configuration file.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
D'Bridge
|
|
</head>
|
|
<p>
|
|
Reads the DBRIDGE.AA1/.AA2 files (for version 1.30) or the
|
|
DBRIDGE.ADF of the later versions.
|
|
</p>
|
|
<p>
|
|
Looks for the "DBRIDGE" and "DB" environment variables.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Dutchie
|
|
</head>
|
|
<p>
|
|
Reads the DUTCHIE.ARE file.
|
|
</p>
|
|
<p>
|
|
Looks for the "DUTCHIE" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2 id=ECHOLIST>
|
|
<head>
|
|
Echolist
|
|
</head>
|
|
<p>
|
|
Reads a simple ascii-text file containing an echolist in this
|
|
format:
|
|
</p>
|
|
<p>
|
|
<echoid> <description>
|
|
</p>
|
|
<p>
|
|
or DZ-format (requires -DZ switch):
|
|
</p>
|
|
<p>
|
|
[Status], Tag, Comment, Moderator's Name, Address,[Flags]
|
|
</p>
|
|
<p>
|
|
This feature adds descriptions to already existing areas in
|
|
<name>GoldED+</name>. Example:
|
|
</p>
|
|
<p>
|
|
AREAFILE AreasBBS AREAS.BBS
|
|
AREAFILE EchoList ECHOLIST.TXT
|
|
AREAFILE EchoList echo5020.lst -dz
|
|
</p>
|
|
<p>
|
|
Descriptions for unknown echoids are ignored. Blank lines and
|
|
lines beginning with characters which are illegal in echoids (such
|
|
as ';') are also ignored.
|
|
</p>
|
|
<p>
|
|
Additional switch -SqaFix could be used to read echolist and groups
|
|
from SqaFix configuration file:
|
|
</p>
|
|
<p>
|
|
AREAFILE Squish C:\SQUISH\
|
|
AREAFILE EchoList C:\SQUISH\SQAFIX.CFG -SqaFix
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Ezycom
|
|
</head>
|
|
<p>
|
|
Reads CONFIG.EZY and MESSAGES.EZY. Supports Ezycom 1.02 and 1.10g,
|
|
but not 1.01.
|
|
</p>
|
|
<p>
|
|
Looks for the "EZY" and "TASK" environment variables.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FastEcho
|
|
</head>
|
|
<p>
|
|
Reads the FASTECHO.CFG file. Supports version 1.10 up to 1.46.
|
|
</p>
|
|
<p>
|
|
Looks for the "FASTECHO" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Fidoconfig
|
|
</head>
|
|
<p>
|
|
Reads fidoconfig (used in Husky Project software). Supports
|
|
version 0.15. Used parser is more powerful than original from
|
|
fidoconfig, due to it strictly follows specification from proposal
|
|
and implements all features from there. Additionaly it implements
|
|
groups not described in proposal but used in in library.
|
|
</p>
|
|
<p>
|
|
Looks for the "FIDOCONFIG" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FidoPCB
|
|
</head>
|
|
<p>
|
|
Reads FIDOPCB.CFG. Supports version 1.x.
|
|
</p>
|
|
<p>
|
|
Looks for the "FIDOPCB" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FMail
|
|
</head>
|
|
<p>
|
|
Reads FMAIL.CFG and FMAIL.AR. Supports versions 0.92, 0.98, 1.0g,
|
|
and 1.20.
|
|
</p>
|
|
<p>
|
|
Looks for the "FMAIL" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FrontDoor
|
|
</head>
|
|
<p>
|
|
Reads the SETUP.FD/FD.SYS and FOLDER.FD/FOLDER.SYS files. If you
|
|
want the real echoid's attached to the areas, you will also need
|
|
to supply the filename of the relevant AREAS.BBS file(s). Supports
|
|
versions 1.99c and 2.xx.
|
|
</p>
|
|
<p>
|
|
Looks for the "FD" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
GEcho
|
|
</head>
|
|
<p>
|
|
Reads SETUP.GE and AREAFILE.GE. Supports versions 1.00, 1.02,
|
|
1.10, 1.11 and 1.20.
|
|
</p>
|
|
<p>
|
|
Looks for the "GE" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
IMAIL
|
|
</head>
|
|
<p>
|
|
Reads the IMAIL.CF and IMAIL.AR files. Supports version 1.60,
|
|
1.7x and 1.8x.
|
|
</p>
|
|
<p>
|
|
Looks for the "IMAIL" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
InterMail
|
|
</head>
|
|
<p>
|
|
Reads the FD.SYS/IMSYS.CFG and FOLDER.CFG/IMFOLDER.CFG files.
|
|
Supports version 2.26 and newer.
|
|
</p>
|
|
<p>
|
|
Looks for the "IM" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
LoraBBS
|
|
</head>
|
|
<p>
|
|
Reads the CONFIG.DAT and SYSMSG.DAT files. Supports version 2.33,
|
|
2.40 and possibly others.
|
|
</p>
|
|
<p>
|
|
Looks for the "LORA" and "LORABBS" environment variables.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Maximus
|
|
</head>
|
|
<p>
|
|
Reads the MAX.PRM and AREA.DAT or MAREA.DAT files. Compatible (or
|
|
should be) with both the old (1.xx) and (2.xx) and new (3.xx)
|
|
formats. If your AREA.DAT is named differently, you must supply
|
|
the correct filename.
|
|
</p>
|
|
<p>
|
|
Looks for the "MAXIMUS" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ME2
|
|
</head>
|
|
<p>
|
|
Reads the old ME2 editor AREADESC.ME2 file and AREAS.BBS file(s).
|
|
You must supply the names of both files.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Opus
|
|
</head>
|
|
<p>
|
|
Reads the Opus 1.1x SYSTEM??.DAT files or the Opus 1.7x SYSMSG.DAT
|
|
file.
|
|
</p>
|
|
<p>
|
|
Looks for the "OPUS" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ParToss
|
|
</head>
|
|
<p>
|
|
Reads the ParToss configuration file.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PCBoard
|
|
</head>
|
|
<p>
|
|
Reads the PCBOARD.DAT, CNAMES.@@@ and CNAMES.ADD files. Supports
|
|
version 14.x and 15.x, up to and including 15.22. Note that,
|
|
depending on the version, echoid's may not be read from this
|
|
format. If the echoid is not available, the description is used as
|
|
echoid, after conversion to uppercase and spaces to underscores.
|
|
</p>
|
|
<p>
|
|
Looks for the "PCBOARD" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Portal
|
|
</head>
|
|
<p>
|
|
Reads the PORTAL*.CFG and PORTAL.ARE files.
|
|
</p>
|
|
<p>
|
|
Looks for the "POPCMDLINE" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ProBoard
|
|
</head>
|
|
<p>
|
|
Reads MSGAREAS.PB. Supports version 2.0.
|
|
</p>
|
|
<p>
|
|
Looks for the "PB" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QEcho
|
|
</head>
|
|
<p>
|
|
Reads /etc/qecho/AreaList. Supports version patched by Eugene
|
|
Sorochinsky for JAM messae base support.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QFront
|
|
</head>
|
|
<p>
|
|
Reads QORIGIN.DAT and QECHOS.DAT. Supports version 1.13b.
|
|
</p>
|
|
<p>
|
|
Looks for the "QFRONT" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
QuickBBS
|
|
</head>
|
|
<p>
|
|
Reads the CONFIG.BBS or QUICKCFG.DAT and MSGCFG.DAT files. To get
|
|
the real echoid's, you must also supply the filename of the
|
|
relevant AREAS.BBS.
|
|
</p>
|
|
<p>
|
|
Looks for the "QUICKBBS" and "QBBS" environment variables.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
RaEcho
|
|
</head>
|
|
<p>
|
|
Reads AREAS.RAE. Supports version 1.00 and 1.01.
|
|
</p>
|
|
<p>
|
|
Looks for the "RAECHO" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
RemoteAccess
|
|
</head>
|
|
<p>
|
|
Reads the MESSAGES.RA file. To get the real echoid's, you must
|
|
also supply the filename of the relevant AREAS.BBS. Supports
|
|
versions 0.xx, 1.xx, 2.0x and 2.5x.
|
|
</p>
|
|
<p>
|
|
Looks for the "RA" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Squish
|
|
</head>
|
|
<p>
|
|
Reads SQUISH.CFG and AREAS.BBS (if used). Supports version 1.0x
|
|
and 1.1x. The "Include <filename>" feature of Squish 1.10 is also
|
|
supported.
|
|
</p>
|
|
<p>
|
|
The optional /G switch specifies the default group of the imported
|
|
areas, i.e. /g=G or /g=#103.
|
|
</p>
|
|
<p>
|
|
Looks for the "SQUISH" and "MAXIMUS" environment variables.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SuperBBS
|
|
</head>
|
|
<p>
|
|
Reads CONFIG.BBS, SCONFIG.BBS and BOARDS.BBS. Supports version
|
|
1.16 and 1.17.
|
|
</p>
|
|
<p>
|
|
Looks for the "SUPERBBS" and "SBBS" environment variables.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
timEd
|
|
</head>
|
|
<p>
|
|
Reads TIMED.CFG and any included file. Also reads the
|
|
configuration from other mail software defined in TIMED.CFG.
|
|
</p>
|
|
<p>
|
|
Looks for the "TIMED" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Termail
|
|
</head>
|
|
<p>
|
|
This is for the Terminate Mail system (Termail). <name>GoldED+</name> does
|
|
currently only support Termail 4.00 und 5.xx style .CFG-files.
|
|
</p>
|
|
<p>
|
|
Reads TM.CFG and any AREAFILE (an AREAS.BBS type file) defined
|
|
there.
|
|
</p>
|
|
<p>
|
|
NOTE: If you use this, you must start <name>GoldED+</name> in the Termail
|
|
directory, because the standard TM configuration files use
|
|
relative paths.
|
|
</p>
|
|
<p>
|
|
Looks for the "TM" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TosScan
|
|
</head>
|
|
<p>
|
|
Reads the FD.SYS/SETUP.FD and AREAFILE.FD files. Supports version
|
|
1.00 and FrontDoor 1.99c and 2.xx.
|
|
</p>
|
|
<p>
|
|
Looks for the "FD" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
WaterGate
|
|
</head>
|
|
<p>
|
|
Reads the WTRCFG.TDB and AREABASE.TDB files. Supports version
|
|
0.93.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
WMail
|
|
</head>
|
|
<p>
|
|
Reads the WMAIL.PRM and AREAS.PRM files. Supports version 2.2.
|
|
</p>
|
|
<p>
|
|
Looks for the "WMAIL" environment variable.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
XMail
|
|
</head>
|
|
<p>
|
|
Reads the AREAS.XM file. Supports version 1.00.
|
|
</p>
|
|
<p>
|
|
Looks for the "XM" environment variable.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1 id=RANDOMSYSTEM><head>The Random System</head>
|
|
<p>
|
|
With the Random System, you can define area-specific sets of origins,
|
|
tearlines, templates, usernames and many other items. If
|
|
more than one item of each type is specified, a random one is picked -
|
|
a Random System. This is a very useful feature when (for example)
|
|
participating in conferences with different languages.
|
|
</p>
|
|
<p>
|
|
The Random System is built on the idea of "groups". A group is a
|
|
collection of "items", belonging to the group. You can assign one or
|
|
more echomail areas, designated by their echoid's to a group. Groups
|
|
can also be specified for just a single echo, and DOS/4DOS-style
|
|
wildcards can be used to simplify the assignment of echoes with common
|
|
strings in their name, such as *.DK, SIG.* and so on. In this way, you
|
|
could for example setup one group for all national echoes, another for
|
|
special local echoes, a third for international echoes etc.
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
Defining Groups
|
|
</head>
|
|
<p>
|
|
The general syntax of a group definition is:
|
|
</p>
|
|
<p>
|
|
GROUP <id>[:]
|
|
; items go here
|
|
[Member <id list>]
|
|
ENDGROUP
|
|
</p>
|
|
<p>
|
|
The Group <id> can be one of three things:
|
|
</p>
|
|
<p>
|
|
1. A group letter or #number, matching the group letters or numbers
|
|
used in the AREAFILE's of D'Bridge, GEcho, IMAIL, TosScan and many
|
|
others. To use this feature, you need to enable the AREAFILEGROUPS
|
|
keyword.
|
|
</p>
|
|
<p>
|
|
2. An individual echoid or echoid mask (wildcards can be used). The
|
|
items are then simply defined below the Group line.
|
|
</p>
|
|
<p>
|
|
3. A group label, terminated by a colon (:). The group items are
|
|
defined below the Group line. Echoes are assigned to the group by
|
|
adding one or more Member statements.
|
|
</p>
|
|
<p>
|
|
You can't assign a group to another group. It will not harm, but it
|
|
also won't work :-)
|
|
</p>
|
|
<p>
|
|
The order of groups is very important. <name>GoldED+</name> scans the groups from
|
|
the top down. This means that the most general groups must be placed
|
|
at the bottom and exceptions (individual areas for example) must be
|
|
placed at the top.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Defining Random Items
|
|
</head>
|
|
<p>
|
|
The random items are defined much like in the main <name>GoldED+</name>
|
|
configuration file.
|
|
</p>
|
|
<p>
|
|
If more than one of each item is defined within a group, those items
|
|
will be picked randomly (hence the name "Random System"), while <name>GoldED+</name>
|
|
collects items when entering an area.
|
|
</p>
|
|
<p>
|
|
Random Item Keywords: <ref target=AKA><kw/AKA/</ref>,
|
|
<ref target=AKAMATCHING><kw/AKAMATCHING/</ref>,
|
|
<ref target=AREACOPYADDID><kw/AREACOPYADDID/</ref>,
|
|
<ref target=AREACOPYDIRECT><kw/AREACOPYDIRECT/</ref>,
|
|
<ref target=AREACOPYTO><kw/AREACOPYTO/</ref>,
|
|
<ref target=AREAFORWARDDIRECT><kw/AREAFORWARDDIRECT/</ref>,
|
|
<ref target=AREAFREQDIRECT><kw/AREAFREQDIRECT/</ref>,
|
|
<ref target=AREAFREQTO><kw/AREAFREQTO/</ref>,
|
|
<ref target=AREAREPLYDIRECT><kw/AREAREPLYDIRECT/</ref>,
|
|
<ref target=AREAREPLYTO><kw/AREAREPLYTO/</ref>,
|
|
<ref target=AREAYOUWROTETO><kw/AREAYOUWROTETO/</ref>,
|
|
<ref target=ATTRIBUTES><kw/ATTRIBUTES/</ref>,
|
|
<ref target=CTRLINFO><kw/CTRLINFO/</ref>,
|
|
<ref target=EDITHARDTERM><kw/EDITHARDTERM/</ref>,
|
|
<ref target=EDITMIXCASE><kw/EDITMIXCASE/</ref>,
|
|
<ref target=EDITREPLYRE><kw/EDITREPLYRE/</ref>,
|
|
<ref target=FORCETEMPLATE><kw/FORCETEMPLATE/</ref>,
|
|
<ref target=INPUTFILE><kw/INPUTFILE/</ref>,
|
|
<ref target=INTERNETADDRESS><kw/INTERNETADDRESS/</ref>,
|
|
<ref target=INTERNETGATE><kw/INTERNETGATE/</ref>,
|
|
<ref target=INTERNETMSGID><kw/INTERNETMSGID/</ref>,
|
|
<ref target=INTERNETRFCBODY><kw/INTERNETRFCBODY/</ref>,
|
|
<ref target=LOADLANGUAGE><kw/LOADLANGUAGE/</ref>,
|
|
<ref target=MEMBER><kw/MEMBER/</ref>,
|
|
<ref target=MSGLISTDATE><kw/MSGLISTDATE/</ref>,
|
|
<ref target=MSGLISTFAST><kw/MSGLISTFAST/</ref>,
|
|
<ref target=MSGLISTFIRST><kw/MSGLISTFIRST/</ref>,
|
|
<ref target=MSGLISTHEADER><kw/MSGLISTHEADER/</ref>,
|
|
<ref target=MSGLISTWIDESUBJ><kw/MSGLISTWIDESUBJ/</ref>,
|
|
<ref target=NICKNAME><kw/NICKNAME/</ref>,
|
|
<ref target=NETNAME><kw/NETNAME/</ref>,
|
|
<ref target=ORGANIZATION><kw/ORGANIZATION/</ref>,
|
|
<ref target=ORIGIN><kw/ORIGIN/</ref>,
|
|
<ref target=OUTPUTFILE><kw/OUTPUTFILE/</ref>,
|
|
<ref target=PLAY><kw/PLAY/</ref>,
|
|
<ref target=QUOTEBUFFILE><kw/QUOTEBUFFILE/</ref>,
|
|
<ref target=QUOTECHARS><kw/QUOTECHARS/</ref>,
|
|
<ref target=QUOTECTRL><kw/QUOTECTRL/</ref>,
|
|
<ref target=QUOTESTRING><kw/QUOTESTRING/</ref>,
|
|
<ref target=QUOTESTOPS><kw/QUOTESTOPS/</ref>,
|
|
<ref target=QUOTEWRAPHARD><kw/QUOTEWRAPHARD/</ref>,
|
|
<ref target=SEARCHFOR><kw/SEARCHFOR/</ref>,
|
|
<ref target=TAGLINE><kw/TAGLINE/</ref>,
|
|
<ref target=TAGLINECHAR><kw/TAGLINECHAR/</ref>,
|
|
<ref target=TAGLINESUPPORT><kw/TAGLINESUPPORT/</ref>,
|
|
<ref target=TEARLINE><kw/TEARLINE/</ref>,
|
|
<ref target=TEMPLATE><kw/TEMPLATE/</ref>,
|
|
<ref target=TEMPLATEMATCH><kw/TEMPLATEMATCH/</ref>,
|
|
<ref target=TWITMODE><kw/TWITMODE/</ref>,
|
|
<ref target=USEAREA><kw/USEAREA/</ref>,
|
|
<ref target=USEFWD><kw/USEFWD/</ref>,
|
|
<ref target=USERNAME><kw/USERNAME/</ref>,
|
|
<ref target=USETZUTC><kw/USETZUTC/</ref>,
|
|
<ref target=VIEWHIDDEN><kw/VIEWHIDDEN/</ref>,
|
|
<ref target=VIEWKLUDGE><kw/VIEWKLUDGE/</ref>,
|
|
<ref target=VIEWQUOTE><kw/VIEWQUOTE/</ref>,
|
|
<ref target=WHOTO><kw/WHOTO/</ref>,
|
|
<ref target=WRITETEMPLATE><kw/WRITETEMPLATE/</ref>,
|
|
<ref target=XLATEXPORT><kw/XLATEXPORT/</ref>,
|
|
<ref target=XLATIMPORT><kw/XLATIMPORT/</ref>.
|
|
</p>
|
|
<p>
|
|
See the Configuration Keyword Reference chapter for details about each
|
|
keyword.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Random System Example
|
|
</head>
|
|
<p>
|
|
Below is an example of how a Random System could be setup. Note how
|
|
the letter group 'D' goes first, followed by the explicit group
|
|
definitions for the NERDS and FOO echoes. Then comes the more general
|
|
groups (those with Label:'s), where the echoes are assigned with one
|
|
or more Member statements. At last there is the catch-all "Group *",
|
|
which works as the default group.
|
|
</p>
|
|
<p>
|
|
=== Cut, GOLDRAND.CFG ===
|
|
</p>
|
|
<p>
|
|
Group NERDS ; For the NERDS echo.
|
|
Origin "I am a Nerd. Take me to your Loser!"
|
|
</p>
|
|
<p>
|
|
Group FOO ; This group is *only* for the FOO echo.
|
|
Tearline FooED @rev
|
|
Origin "Foo-ing my day away"
|
|
</p>
|
|
<p>
|
|
Group FooEchoes:
|
|
Member *FOO* ; Use wildcards to catch any other foo echo.
|
|
Tearline FooED @rev
|
|
Origin "This is a Foo-lish origin"
|
|
</p>
|
|
<p>
|
|
Group FidoNet:
|
|
Member NET_DEV, WORLDPOL, INTERCOOK
|
|
Member GREEN.029, C_ECHO, C_PLUSPLUS
|
|
Origin "Fight-O-Net? Good name..."
|
|
Template FIDONET.TPL
|
|
Whoto Everyone
|
|
</p>
|
|
<p>
|
|
Group SigNet:
|
|
Member SIG.* ; The wildcard is VERY handy here ;-)
|
|
Origin "To SIG or not to SIG..."
|
|
Template SIGNET.TPL
|
|
</p>
|
|
<p>
|
|
Group D ; Letter D for Danish echoes.
|
|
Template DANSK.TPL
|
|
</p>
|
|
<p>
|
|
Group * ; This is default group
|
|
Origin "Yet another forgotten echo"
|
|
</p>
|
|
<p>
|
|
=== Uncut ===
|
|
</p>
|
|
<p>
|
|
See the example GOLDRAND.CFG in the ADVANCED archive for a real-life
|
|
setup similar to the one I use myself.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1 id=COLORCONFIG>
|
|
<head>
|
|
The Color Configuration
|
|
</head>
|
|
<p>
|
|
Color configuration in <name>GoldED+</name> is a bit complicated, and you probably
|
|
have to experiment quite a bit, if you want make your own setup. For
|
|
your convenience, I have added a number of example color setups,
|
|
provided by some of my many good users. I suggest you try them all and
|
|
use the one that suits you best, perhaps tuning it a bit to your
|
|
taste.
|
|
</p>
|
|
<p>
|
|
The COLOR keyword uses the following syntax:
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
COLOR <window> <part> <colors>
|
|
</head>
|
|
<p>
|
|
<window> AREA, ASK, BACKGROUND, BRAG, HEADER, HELP, INFO, MENU,
|
|
READER, SHADOW, STATUS.
|
|
</p>
|
|
<p>
|
|
<part> BLOCK, BORDER, BTYPE, EDIT, HIDDEN, HIGHLIGHT, INPUT,
|
|
KLUDGE, NOSELECT, ORIGIN, QUOTE, SELECTOR, TEARLINE,
|
|
TITLE, WINDOW.
|
|
</p>
|
|
<p>
|
|
The <colors> are composed of [blinking] <ink> [on <paper>].
|
|
</p>
|
|
<p>
|
|
<ink> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey,
|
|
DGrey, LBlue, LGreen, LCyan, LRed, LMagenta, Yellow,
|
|
White.
|
|
</p>
|
|
<p>
|
|
<paper> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey.
|
|
</p>
|
|
<p>
|
|
For monochrome setups we instead have:
|
|
</p>
|
|
<p>
|
|
<ink> Normal, Highlight, Reverse, Underline.
|
|
</p>
|
|
<p>
|
|
The SHADOW color does not need a <part>, because it is global.
|
|
</p>
|
|
<p>
|
|
The paper color always defaults to Black if not specified.
|
|
</p>
|
|
<p>
|
|
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:
|
|
</p>
|
|
<p>
|
|
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.
|
|
</p>
|
|
<p>
|
|
The default border type is always BTYPE 0.
|
|
</p>
|
|
<p>
|
|
The following is a description of the different window parts:
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Various general color items
|
|
</head>
|
|
<p>
|
|
SHADOW Shadow below windows and menus.
|
|
STATUS WINDOW Status line at the bottom.
|
|
BACKGROUND WINDOW Background for the startup window.
|
|
BACKGROUND BORDER Overscan color (currently DOS only).
|
|
</p>
|
|
<p>
|
|
<anything> PAGEBAR Pagebar (scrollbar).
|
|
</p>
|
|
<p>
|
|
The PAGEBAR color specifially sets the color of the pagebars
|
|
(scrollbars) in <name>GoldED+</name>. A pagebar color can currently be set for
|
|
AREA, READER and MENU. Note that BORDER will set both the BORDER and
|
|
PAGEBAR colors, so remember to place the PAGEBAR color below the
|
|
BORDER color.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Startup screen / logo window
|
|
</head>
|
|
<p>
|
|
BRAG WINDOW The Copyright window.
|
|
BRAG BORDER Lines around the Copyright window.
|
|
BRAG TITLE The logo text.
|
|
BRAG HIGHLIGHT The inner logo lines.
|
|
BRAG BLOCK The outer logo lines.
|
|
BRAG BTYPE Copyright window border type.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Area Selection Menu
|
|
</head>
|
|
<p>
|
|
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.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Message Header
|
|
</head>
|
|
<p>
|
|
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.
|
|
HEADER FROM Header From field.
|
|
HEADER TO Header To field.
|
|
HEADER SUBJECT Header Subject field.
|
|
</p>
|
|
<p>
|
|
The FROM/TO/SUBJECT colors supplement the HEADER WINDOW color. Note
|
|
that WINDOW will also set the FROM/TO/SUBJECT colors, so remember to
|
|
place the new colors below it.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Message Text
|
|
</head>
|
|
<p>
|
|
READER WINDOW Normal message text.
|
|
READER BORDER The Pagebar.
|
|
READER QUOTE (Odd) Quoted lines.
|
|
READER QUOTE2 (Even) Quoted lines.
|
|
READER CURSOR Character at cursor pos. (int. editor).
|
|
READER KLUDHIDD Kludges and hidden lines.
|
|
READER TEARORIG Tearline and Origin.
|
|
READER BLOCK Block color (internal editor).
|
|
READER BTYPE Window border type.
|
|
READER HIGHLIGHT Search highlight in the message text.
|
|
READER KLUDGE Known kludges.
|
|
READER HIDDEN Hidden lines. (Unknown kludges).
|
|
READER SIGNATURE Internet-Style signatures ("-- ").
|
|
READER TAGLINE Taglines. (Only the one just above tearline).
|
|
READER TEARLINE Tearline.
|
|
READER ORIGIN Origin.
|
|
</p>
|
|
<p>
|
|
The KLUDGE/HIDDEN colors replaces the old KLUDHIDD color. Note that
|
|
KLUDHIDD will set both the KLUDGE and HIDDEN colors, so remember to
|
|
place the new colors below it if you keep the old definition.
|
|
</p>
|
|
<p>
|
|
The TAGLINE color is the color of taglines. <name>GoldED+</name> detects a tagline
|
|
if it starts with "..." or "___" and is just above the tearline or
|
|
origin.
|
|
</p>
|
|
<p>
|
|
The TEARLINE/ORIGIN colors replaces the old TEARORIG color. Note
|
|
that TEARORIG will set both the TEARLINE and ORIGIN colors, so
|
|
remember to place the new colors below it if you keep the old
|
|
definition.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Miscellaneous Smaller Menus
|
|
</head>
|
|
<p>
|
|
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.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Miscellaneous Larger Menus (Browser Windows)
|
|
</head>
|
|
<p>
|
|
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.
|
|
MENU UNREAD When a msg is unread.
|
|
MENU UNREADHIGH Additional highlight of to/from.
|
|
MENU UNSENT When a msg is unsent.
|
|
MENU UNSENTHIGH Additional highlight of to/from.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Help Screens
|
|
</head>
|
|
<p>
|
|
HELP WINDOW Help text.
|
|
HELP BORDER Lines.
|
|
HELP SELECTOR Current keyword.
|
|
HELP HIGHLIGHT Other keywords.
|
|
HELP BTYPE Window border type.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Pop Up Information Windows
|
|
</head>
|
|
<p>
|
|
INFO WINDOW Window text.
|
|
INFO BORDER Lines.
|
|
INFO TITLE Info title.
|
|
INFO BTYPE Window border type.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Stylecodes
|
|
</head>
|
|
<p>
|
|
STYLECODE ALL All stylecodes at once.
|
|
STYLECODE B *Bold*
|
|
STYLECODE I /Italic/
|
|
STYLECODE BI /*BoldItalic*/
|
|
STYLECODE U _Underline_
|
|
STYLECODE BU _*BoldUnderline*_
|
|
STYLECODE IU /_ItalicUnderline_/
|
|
STYLECODE BIU _/*BoldItalicUnderline*/_
|
|
STYLECODE R #Reverse#
|
|
STYLECODE RB *#ReverseBold#*
|
|
STYLECODE RI /#ReverseItalic#/
|
|
STYLECODE RBI /*#ReverseBoldItalic#*/
|
|
STYLECODE RU _#ReverseUnderline_#
|
|
STYLECODE RBU _*#ReverseBoldUnderline#*_
|
|
STYLECODE RIU _/#ReverseItalicUnderline#/_
|
|
STYLECODE RBIU _/*#ReverseItalicUnderline#*/_
|
|
</p>
|
|
<p>
|
|
Note that stylecode color definitions must be placed below COLOR
|
|
READER WINDOW, because it overrides the COLOR STYLECODE definitions.
|
|
</p>
|
|
<p>
|
|
See the GEDCOL*.CFG and GEDMON*.CFG files for examples of color
|
|
configuration.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1 id=MESSAGETEMPLATE>
|
|
<head>
|
|
The Message Template
|
|
</head>
|
|
<p>
|
|
The message template gives you a ready-made skeleton for writing your
|
|
messages in the editor. The template is one of <name>GoldED+</name>'s many strong
|
|
features. With this, you can eliminate the tedious typing of greetings
|
|
etc etc. <name>GoldED+</name> also provides a number of replacement strings,
|
|
"tokens", to dynamically add message specific information to the
|
|
template.
|
|
</p>
|
|
<p>
|
|
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.
|
|
</p>
|
|
<p>
|
|
The following is a list of the tokens available:
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
Conditional tokens
|
|
</head>
|
|
<p>
|
|
(these are replaced with a null string)
|
|
</p>
|
|
<p>
|
|
@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.
|
|
@moderator Line is only inserted if substring "moderator" appeared in
|
|
from line.
|
|
@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.
|
|
@quotebuf Line is only inserted in Quotebuffered msgs.
|
|
@quoted Line is only inserted in Quoted replies.
|
|
@reply Line is only inserted in Non-Quoted Replies.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Insert tokens
|
|
</head>
|
|
<p>
|
|
(anything else on the line is ignored)
|
|
</p>
|
|
<p>
|
|
@attrib <attributes> - Adds specific message attributes.
|
|
@include <filename> - Inserts the file.
|
|
@forcefrom <"from"> - sets message FROM: field, even if non-empty
|
|
(see @setfrom)
|
|
@forcesubj <"subject"> - sets message SUBJ: field, even if non-empty
|
|
(see @setsubj)
|
|
@forceto <"to"> - sets message TO: field, even if non-empty
|
|
(see @setto)
|
|
@loadlanguage Loads a partial language config file.
|
|
@message Inserts the original message (in Forward & Change).
|
|
@quote Inserts a quote of the original message.
|
|
@random [random.txt] - Inserts random text.
|
|
@setfrom <"from"> - Sets the message FROM: field.
|
|
@setsubj <"subject"> - Sets the message SUBJ: field.
|
|
@setto <"to"> - Sets the message TO: field.
|
|
@xlatexport <charset> - Sets the export charset.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Replacement tokens
|
|
</head>
|
|
<p>
|
|
(replaced with message specific data):
|
|
</p>
|
|
<p>
|
|
@c3daddr Current user 3D (boss) address.
|
|
@caddr Current user address.
|
|
@cdate Current date.
|
|
@cdesc Current area description.
|
|
@cecho Current echoid.
|
|
@cfname Current user first name.
|
|
@clname Current user last name.
|
|
@cname Current user name.
|
|
@cpseudo Current pseudonym given by NICKNAME keyword, or @cfname.
|
|
@ctime Current time.
|
|
@ctzoffset Current timezone offset (if available and enabled).
|
|
@d3daddr Destination 3D (boss) address.
|
|
@daddr Destination address.
|
|
@dfname Destination first name.
|
|
@dlname Destination last name.
|
|
@dname Destination name.
|
|
@dpseudo Destination pseudonym (see addressbook), or @dfname.
|
|
@f3daddr Current from 3D (boss) address.
|
|
@faddr Current from address.
|
|
@ffname Current from first name.
|
|
@flname Current from last name.
|
|
@fname Current from name.
|
|
@fpseudo Current from pseudonym (see addressbook), or @ffname.
|
|
@longpid Long program id. "GoldED", "GoldED/2" or "GoldED/386".
|
|
@o3daddr Original 3D (boss) address.
|
|
@oaddr Original address.
|
|
@odate Original date.
|
|
@odesc Original area description if moved, else current.
|
|
@oecho Original echoid if moved, otherwise current.
|
|
@ofname Original first name.
|
|
@ofrom Original RFC "From" headerline.
|
|
@olname Original last name.
|
|
@omessageid Original RFC "Message-ID" headerline.
|
|
@omsgid Original MSGID kludge content.
|
|
@oname Original name.
|
|
@opseudo Original pseudonym (see addressbook), or @ofname.
|
|
@origin The current global or Random System origin.
|
|
@os2slash "/2" if running <name>GoldED+</name>/2. Empty otherwise.
|
|
@osslash same as above.
|
|
@otime Original time.
|
|
@otzoffset Original timezone offset (if available and enabled).
|
|
@oto Original RFC "To" headerline.
|
|
@pid Short program id. "GED", "GED/2" or "GED386".
|
|
@pseudo pseudonym (see addressbook), or @tfname.
|
|
@rev The revision number (in the form mmdd).
|
|
@serialno Emptiness.
|
|
@subject The message subject line.
|
|
@t3daddr Destination to 3D (boss) address.
|
|
@taddr Destination to address.
|
|
@tagline The current global or Random System tagline.
|
|
@tearline The current global or Random System tearline.
|
|
@tfname Destination to first name.
|
|
@tlname Destination to last name.
|
|
@tname Destination to name.
|
|
@tpseudo Destination to pseudonym (see addressbook), or @tfname.
|
|
@ver The simple version number (in the form x.yy)
|
|
@version The complete release version number of <name>GoldED+</name>.
|
|
@_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).
|
|
</p>
|
|
<p>
|
|
Tokens dealing with names may optionally have two parameters (each
|
|
parameter enclosed in curve brackets): your name and opponent name,
|
|
destination name additionally accepts third parameter - WhoTo name.
|
|
Here is example on how this feature could be used:
|
|
</p>
|
|
<p>
|
|
@oname{I}{You} wrote to @dname{me}{you}{everyone}:
|
|
</p>
|
|
<p>
|
|
The template text begins at the first non-comment line.
|
|
</p>
|
|
<p>
|
|
See the included GOLDED.TPL for example usage.
|
|
</p>
|
|
<p>
|
|
If you need to put some text which contains one of these tokens into a
|
|
template file, use an extra '@' in front of the token.
|
|
</p>
|
|
<p>
|
|
Example:
|
|
</p>
|
|
<p>
|
|
Internet: somebody@veryhot.com
|
|
</p>
|
|
<p>
|
|
would produce
|
|
</p>
|
|
<p>
|
|
Internet: somebody2.51yhot.com (because @ver is a token)
|
|
</p>
|
|
<p>
|
|
so write it like this instead:
|
|
</p>
|
|
<p>
|
|
Internet: somebody@@veryhot.com
|
|
</p>
|
|
<p>
|
|
The double '@' will then be translated to a single, and token
|
|
translation skips past the @token.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
The Online Help System
|
|
</head>
|
|
<p>
|
|
GoldED has a built-in context sensitive help system, tied to the <F1>
|
|
key (one of the very few keys that cannot be reconfigured). It
|
|
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 may be improved in future versions.
|
|
</p>
|
|
<p>
|
|
You can completely redefine the help screens if you wish - the
|
|
GOLDHELP.CFG file is a plain ASCII text file which contains all help
|
|
definitions. The help file is split into several help categories. Here
|
|
is an example of a couple of defined help categories:
|
|
</p>
|
|
<p>
|
|
*B 1,Help Category 1
|
|
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
|
|
*E
|
|
</p>
|
|
<p>
|
|
*B 2,Help Category 2
|
|
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
|
|
See also: ^Help Category 1^
|
|
*E
|
|
</p>
|
|
<p>
|
|
The "*B" indicator specifies the beginning of a help category. The
|
|
format is "*B helpcatnumber[,helpcatname]". In <name>GoldED+</name> 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.
|
|
</p>
|
|
<p>
|
|
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).
|
|
</p>
|
|
<p>
|
|
In the definition of Help Category 2, you will notice the
|
|
crossreference 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 (^^).
|
|
</p>
|
|
<p>
|
|
Any text contained outside of the "*B" and "*E" is treated as
|
|
comments. If an "*E" is not found, then the end-of-file will be
|
|
treated as an "*E".
|
|
</p>
|
|
<p>
|
|
Not all of the help categories in this help file are actually used in
|
|
the current version of <name>GoldED+</name>. The ones not used are empty, except for
|
|
a two-line "header".
|
|
</p>
|
|
<p>
|
|
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.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Character Translation
|
|
</head>
|
|
<p>
|
|
GoldED implements several different proposals for character
|
|
translation in imported and exported messages:
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
FSC-0050 "Charset Identifier"
|
|
</head>
|
|
<p>
|
|
by Thomas Sundblom.
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FSC-0051 "I51"
|
|
</head>
|
|
<p>
|
|
by Thomas Gradin.
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FSC-0054 "CHARSET proposal"
|
|
</head>
|
|
<p>
|
|
by Duncan McNutt.
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
No FSC "Composed Characters"
|
|
</head>
|
|
<p>
|
|
by Andre van de Wijdeven.
|
|
</p>
|
|
<p>
|
|
FSC-0050 is currently known to be implemented in the OPMED 3.xx
|
|
message editor, and in Opus 1.7x. It uses the same identifier as
|
|
FSC-0054 (a ^aCHARSET kludge), but is a lot simpler (but not
|
|
necessarily better).
|
|
</p>
|
|
<p>
|
|
The "I51" and "CHARSET" proposals are in the process of being merged
|
|
to one proposal, which should combine the advantages of both. They are
|
|
both based on using the LATIN-1 (also known as ISO 8859-1) character
|
|
set for extended ASCII. The LATIN-1 set is the same set used by
|
|
Windows 3.xx, Amiga and many other non-PC computers. In addition to
|
|
LATIN-1, I51 defines a set of so-called escape sequences for
|
|
characters not found in the LATIN-1 set.
|
|
</p>
|
|
<p>
|
|
"Composed Characters" became quite popular in Holland, but the author
|
|
decided to drop his proposal because it relied on escape sequences
|
|
using the so called "soft-cr" (141d, 8Dh) character. <name>GoldED+</name> will
|
|
continue to support Composed as long as it seems necessary.
|
|
</p>
|
|
<p>
|
|
If you want to know more about the details, I suggest you read the
|
|
proposals or contact the authors.
|
|
</p>
|
|
<p>
|
|
GoldED currently supports two types of translation tables, the *.ESC
|
|
files and the *.CHS files.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
The ESC translation tables
|
|
</head>
|
|
<p>
|
|
The *.ESC files are used for import translation of the escape
|
|
sequences defined in I51 and Composed Characters.
|
|
</p>
|
|
<p>
|
|
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:
|
|
</p>
|
|
<p>
|
|
<esc1><esc2><space><map chars>[; comment/description]
|
|
</p>
|
|
<p>
|
|
Leading spaces are *not* allowed in ESC files. <esc1> and <esc2> are
|
|
the two characters that define the escape sequence. <space> is ignored
|
|
and can be used to make the table look better. <map chars> defines the
|
|
local representation of the escape sequence, up to three characters.
|
|
Normally you would only map to one extended ascii character. The map
|
|
chars can be either the characters themselves, or decimal or
|
|
hexadecimal numbers of the form "\d<dec>" or "\x<hex>" (like in the C
|
|
programming language).
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
The CHS translation tables
|
|
</head>
|
|
<p>
|
|
The *.CHS files are used for import and export translation of the
|
|
CHARSET type character sets, and export of I51 and Composed escape
|
|
sequences.
|
|
</p>
|
|
<p>
|
|
The CHS files uses the format of the raw text files provided in the
|
|
CHARSET3.ZIP example implementation of FSC-0054. Study some of the
|
|
files provided if you want to know how to define them.
|
|
</p>
|
|
<p>
|
|
The two keywords XLATESCSET and XLATCHARSET are used to define which
|
|
files belong to what import and export set. You can define more than
|
|
one import and export set for each file.
|
|
</p>
|
|
<p>
|
|
The keyword XLATIMPORT defines which charset you have on your own
|
|
machine - this would normally be "IBMPC". It can be useful to change
|
|
this (using the Random System) in areas where another character set
|
|
than IBMPC is the dominant (like Amiga or MacIntosh, whatever).
|
|
</p>
|
|
<p>
|
|
The keyword XLATEXPORT defines the charset your messages should be
|
|
exported to, if any.
|
|
</p>
|
|
<p>
|
|
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. Turn it off completely if you don't understand
|
|
it.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Keyboard Command Reference
|
|
</head>
|
|
<p>
|
|
Most of the <name>GoldED+</name> keyboard commands can be reached with just one
|
|
keystroke. To ease operation for experienced users of other message
|
|
editors, <name>GoldED+</name> comes with 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.
|
|
</p>
|
|
<p>
|
|
The following is a list of all keyboard commands, sorted by type and
|
|
alphabetically, using the format
|
|
</p>
|
|
<p>
|
|
<command> <short description>
|
|
</p>
|
|
<p>
|
|
This list is also available in the context-sensitive help system on
|
|
the <F1> key.
|
|
</p>
|
|
<p>
|
|
It is possible to almost completely redefine the keyboard - this in
|
|
done in the GOLDKEYS.CFG file, which also handles macro definition
|
|
(see later).
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
Arealist Commands
|
|
</head>
|
|
<p>
|
|
AREAabort Abort the arealist.
|
|
AREAaskexit Exit <name>GoldED+</name>, prompt for final decision.
|
|
AREAboardnos Toggle sequential areas vs. board numbers.
|
|
AREAcatchup Point the lastread pointer to the last message
|
|
in the current area.
|
|
AREAdosshell Shell to DOS.
|
|
AREAdropmsgmarks Unmark all msgs in selected areas.
|
|
AREAgotofirst Move selection bar to first area.
|
|
AREAgotolast Move selection bar to last area.
|
|
AREAgotonext Move selection bar to next area.
|
|
AREAgotoprev Move selection bar to previous area.
|
|
AREAheat Heat highwatermarks.
|
|
AREAjump Move selection bar to next marked area.
|
|
AREAjumpnextmatch Move selection bar to next matching area.
|
|
AREAquitnow Exit immediately, no questions asked.
|
|
AREAscan Scan areas.
|
|
AREAscanpm Scan areas for personal mail.
|
|
AREAselect Enter the reader for the selected area.
|
|
AREAselectmarks Select which set of area marks should be used.
|
|
AREAsoundkill Stops currently played sound file.
|
|
AREAtoggle Toggle mark on the selected area.
|
|
AREAtouchnetscan Touches the SEMAPHORE NETSCAN file.
|
|
AREAwritegoldlast Write a fresh copy of GOLDLAST.LST
|
|
AREAzap Zap highwatermarks.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Internal Editor Commands
|
|
</head>
|
|
<p>
|
|
EDITabort Abort editing this message - ask first.
|
|
EDITanchor Set a block "anchor" on the current line.
|
|
EDITaskexit Exit from <name>GoldED+</name> - ask first.
|
|
EDITblockdown Extend block area one line down.
|
|
EDITblockend Extend block area to the end of line.
|
|
EDITblockhome Extend block area to the beginning of line.
|
|
EDITblockleft Extend block area one character left.
|
|
EDITblockpgup Extend block area one screen up.
|
|
EDITblockpgdn Extend block area one screen down.
|
|
EDITblockright Extend block area one character right.
|
|
EDITblockup Extend block area one line up.
|
|
EDITcleardeletebuf Clears the undelete buffer.
|
|
EDITclearpastebuf Clears the cut'n'paste buffer.
|
|
EDITcopy Copies the block to the cut'n'paste buffer.
|
|
EDITcopyabovechar Inserts character same as in the same position
|
|
in previous line.
|
|
EDITcut Cut the block to the cut'n'paste buffer.
|
|
EDITdelchar Delete the char at the cursor position.
|
|
EDITdelete Delete the block.
|
|
EDITdeleteeol Delete from cursor position to end of line.
|
|
EDITdelleft Delete the char to the left of the cursor.
|
|
EDITdelline Delete the current line. (Copied to the
|
|
EDITdelltword Delete the word to the left of the cursor.
|
|
EDITdelrtword Delete the word to the right of the cursor.
|
|
EDITdosshell Shell to DOS.
|
|
EDITdupline Duplicates the current line.
|
|
EDITexitmsg Drop this message - NO ASKING! DANGEROUS!
|
|
EDITexporttext Exports the current block to a file.
|
|
EDITgobegline Move cursor to beginning of line.
|
|
EDITgobotline Move cursor to the bottom line in the display.
|
|
EDITgobotmsg Move cursor to the last line in the message.
|
|
EDITgodown Move cursor down to next line.
|
|
EDITgoeol Move cursor to the end of the line.
|
|
EDITgoleft Move cursor one position left.
|
|
EDITgopgdn Move cursor one page of lines down.
|
|
EDITgopgup Move cursor one page of lines up.
|
|
EDITgoright Move cursor one position right.
|
|
EDITgotopline Move cursor to the top line in the display.
|
|
EDITgotopmsg Move cursor to the first line in the message.
|
|
EDITgoup Move cursor up to the previous line.
|
|
EDITgowordleft Move cursor to the previous word.
|
|
EDITgowordright Move cursor to the next word.
|
|
EDITheader Edit the message header, attributes etc.
|
|
EDITimportquotebuf Imports the current quote buffer.
|
|
EDITimporttext Import text file into this message.
|
|
EDITkillquotes (ignored)
|
|
EDITloadfile Load the message file saved with EDITsavefile.
|
|
EDITlookupcursor Lookup name/node at cursor position.
|
|
EDITlookupdest Lookup TO: node.
|
|
EDITlookuporig Lookup FROM: node.
|
|
EDITnewline Terminate paragraph and/or add a new line.
|
|
EDITpaste Paste a previously cut block at the cursor.
|
|
EDITquitnow Quit <name>GoldED+</name> immediately - no asking.
|
|
EDITreflow Reflows the current text or quote paragraph.
|
|
EDITsavefile Saves the current message as a file.
|
|
EDITsavemsg Save this message.
|
|
EDITsoundkill Stops currently played sound flie.
|
|
EDITspellcheck Calls an external spell checker for the msg.
|
|
EDITtab Add spaces to the next tab-stop.
|
|
EDITtabreverse Remove spaces to the prev tab-stop.
|
|
EDITtogglecase Toggle the case of the cursor character.
|
|
EDITtoggleinsert Toggle insert mode.
|
|
EDITtolower Change the cursor character to lowercase.
|
|
EDITtoupper Change the cursor character to uppercase.
|
|
EDITundelete Undelete previously deleted lines.
|
|
EDITzapquotebelow Deletes quotes below.
|
|
</p>
|
|
</div2>
|
|
<div2 id=FILESELECTION>
|
|
<head>
|
|
File Selection Commands
|
|
</head>
|
|
<p>
|
|
FILEabort Abort file selection.
|
|
FILEaskexit Exit <name>GoldED+</name> - ask first.
|
|
FILEdosshell Shell to DOS.
|
|
FILEgotofirst Go to first file.
|
|
FILEgotolast Go to last file.
|
|
FILEgotonext Go to next file.
|
|
FILEgotoprev Go to previous file.
|
|
FILEmark Mark file.
|
|
FILEmarkall Mark all files.
|
|
FILEquitnow Quit <name>GoldED+</name> immediately.
|
|
FILEselect Select the marked file(s).
|
|
FILEtogglemark Toggle file mark.
|
|
FILEunmark Unmark file.
|
|
FILEunmarkall Unmark all files.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Message Lister Commands
|
|
</head>
|
|
<p>
|
|
LISTabort Abort message lister.
|
|
LISTaskexit Exit <name>GoldED+</name> - ask first.
|
|
LISTdosshell Shell to DOS.
|
|
LISTgotobookmark Go to BookMark message.
|
|
LISTgotofirst Go to first message.
|
|
LISTgotolast Go to last message.
|
|
LISTgotonext Go to next message.
|
|
LISTgotoprev Go to previous message.
|
|
LISTmarkingoptions Marking menu.
|
|
LISTquitnow Quit <name>GoldED+</name> immediately.
|
|
LISTselect Go to reader at the selected message.
|
|
LISTtogglebookmark Toggle BookMark on the selected message.
|
|
LISTtoggledate Toggle date column content.
|
|
LISTtogglemark Toggle Mark on the selected message.
|
|
LISTtogglewidesubj Toggle between wide and short subject.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Nodelist Browser Commands
|
|
</head>
|
|
<p>
|
|
NODEabort Abort nodelist browsing.
|
|
NODEaskexit Exit <name>GoldED+</name> - ask first.
|
|
NODEdosshell Shell to DOS.
|
|
NODEgotofirst Go to first node.
|
|
NODEgotolast Go to last node.
|
|
NODEgotonext Go to next node.
|
|
NODEgotoprev Go to previous node.
|
|
NODEquitnow Quit <name>GoldED+</name> immediately.
|
|
NODEselect Select node.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Message Reader Commands
|
|
</head>
|
|
<p>
|
|
READaddressbookadd Add current/marked mail writer(s) to
|
|
addressbook. Ask first.
|
|
READaskexit Exit <name>GoldED+</name>, prompt for final decision.
|
|
READchangeaka Change default AKA address for current area.
|
|
READchangeattrs Change the attributes of the current message.
|
|
READchangemsg Change current message.
|
|
READchangeorigin Change default origin for the current area.
|
|
READchangetagline Change default tagline.
|
|
READchangetemplate Change default template.
|
|
READchangeusername Change default username.
|
|
READchangexlatimport Change default import charset.
|
|
READcommentmsg Comment-Reply to message. (Reply to TO name).
|
|
READcopymoveforward Enter the Copy/Move/Forward function menu.
|
|
READdecreasemargin Decrease message margin. For test purposes.
|
|
READdeletemsg Delete current/marked message(s). Ask first.
|
|
READdosshell Shell to DOS.
|
|
READfidorenumber Renumber Fido/Opus *.MSG files.
|
|
READfilerequest Generate a filerequest from the current msg.
|
|
READfindall Find string(s) in message header and text.
|
|
READfindheader Find string(s) in message header.
|
|
READgotobookmark Go to the "BookMark" message.
|
|
READgotofirstmsg Go to the first message in the area.
|
|
READgotolastmsg Go to the last message in the area.
|
|
READgotomsgno Go to a specific message number.
|
|
READgotonextarea Go directly to the next area.
|
|
READgotonextmsg Go to the next message.
|
|
READgotonextunread Go to the next unread message.
|
|
READgotoprevarea Go directly to the previous area.
|
|
READgotoprevmsg Go to the previous message.
|
|
READgotoprevunread Go to the previous unread message.
|
|
READgotoreplies Choose from the next messages in the replylink.
|
|
READgotoreply1st Go to the first reply to this message.
|
|
READgotoreplynext Go to the next reply to this message.
|
|
READgotoreplyprev Go to the parent message in the replylink.
|
|
READincreasemargin Increase message margin. For test purposes.
|
|
READlookupdest Lookup TO: node.
|
|
READlookuporig Lookup FROM: node.
|
|
READmakeuserlist Generate FIDOUSER.LST of users in the area.
|
|
READmakepathreport Added "path report" feature. The output file
|
|
can be processed by a RDDT (Route Diagram
|
|
Drawing Tool) utility.
|
|
READmarkingoptions Enter the marking menu.
|
|
READmessagelist Enter the message lister.
|
|
READmovecommentmsg Comment-Reply in another area.
|
|
READmovequotemsg Quote-Reply in another area.
|
|
READmsgcontinue Page down or go to next message.
|
|
READmsgend Display last part of current message.
|
|
READmsghome Display first part of current message.
|
|
READmsglinedown Scroll message display.
|
|
READmsglineup Scroll message display.
|
|
READmsgpgdn Page message display.
|
|
READmsgpgup Page message display.
|
|
READnewarea Enter the area selection screen.
|
|
READnewmsg Start a new message.
|
|
READquitnow Exit <name>GoldED+</name> immediately, no questions asked.
|
|
READquotebuf Append quote of the msg to the quotebuffer.
|
|
READquotemsg Quote-Reply to message. (Reply to FROM name).
|
|
READreplymsg Reply to the current message, without quoting.
|
|
READsearch Launches the search engine.
|
|
READsoundkill Stops currently played sound file.
|
|
READthreadtree Enter the Message Threading lister.
|
|
READtogglebookmark Toggle a "BookMark" on the current message.
|
|
READtogglehexdump Toggle hexdump mode. For debugging purposes.
|
|
READtogglehiddklud Toggle display of Hidden and Kludge lines.
|
|
READtogglehidden Toggle display of Hidden lines.
|
|
READtogglekludge Toggle display of Kludge lines.
|
|
READtogglemark Toggle a message mark on the current message.
|
|
READtogglemarkread Toggle "Read Marked" mode.
|
|
READtogglepagebar Toggle the "PageBar" feature.
|
|
READtogglequote Toggle display of quoted lines. Experimental.
|
|
READtogglerot13 Toggle ROT13 encryption for the current msg.
|
|
READtogglerealmsgno Toggle between seq. or real message numbers.
|
|
READtogglestyles Toggle Disable/Show/Show+Strip of STYLECODES.
|
|
READtoggletwits Toggle Twit display - Show/Blank/Skip/Ignore.
|
|
READtouchnetscan Touches the SEMAPHORE NETSCAN file.
|
|
READtouchsemaphore Popup touch a manually entered semaphore file.
|
|
READuserbase Launches the addressbook.
|
|
READuudecode UUdecodes the current message.
|
|
READwritemsg Write message(s) to file or printer.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Key Undefine Commands
|
|
</head>
|
|
<p>
|
|
AREAundefine
|
|
EDITundefine
|
|
FILEundefine
|
|
LISTundefine
|
|
NODEundefine
|
|
READundefine
|
|
</p>
|
|
<p>
|
|
The undefine commands can used to undefine any of the built-in default
|
|
keyboard definitions.
|
|
</p>
|
|
<p>
|
|
See the Key Reference below for a list of the key symbols you can use
|
|
in keyboard redefinition.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1 id=MACROSANDKEYSTACKING><head>Macros and Keystacking</head>
|
|
<p>
|
|
GoldED has a simple keyboard macro facility, which you can use to
|
|
automate certain common operations. In addition, a "keystacking"
|
|
facility allows you to create simple automatic macros on the fly.
|
|
</p>
|
|
<p>
|
|
The macro definition syntax is modelled after the syntax used in the
|
|
QEdit text editor:
|
|
</p>
|
|
<p>
|
|
<assignment-key> Macro <commands or keys>
|
|
<assignment-key> AreaMacro <commands or keys>
|
|
<assignment-key> EditMacro <commands or keys>
|
|
<assignment-key> FileMacro <commands or keys>
|
|
<assignment-key> ListMacro <commands or keys>
|
|
<assignment-key> NodeMacro <commands or keys>
|
|
<assignment-key> ReadMacro <commands or keys>
|
|
</p>
|
|
<p>
|
|
Macros are defined in the GOLDKEYS.CFG file, where you can also find
|
|
several examples.
|
|
</p>
|
|
<p>
|
|
By using the word "Auto" as <assignment-key>, you can even define a
|
|
special macro which will be automatically executed when you start
|
|
GoldED.
|
|
</p>
|
|
<p>
|
|
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.
|
|
</p>
|
|
<p>
|
|
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 <name>GoldED+</name> commandline or the GEDCMD
|
|
environment variable.
|
|
</p>
|
|
<p>
|
|
See the Key Reference chapter for a list of the key symbols you can
|
|
use in macros and keystacking.
|
|
</p>
|
|
<p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Key Reference
|
|
</head>
|
|
<p>
|
|
Below is the list of key symbols recognized by <name>GoldED+</name> for
|
|
keyboard/macro definition and keystacking.
|
|
</p>
|
|
<p>
|
|
Unshifted function keys
|
|
</p>
|
|
<p>
|
|
F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12
|
|
</p>
|
|
<p>
|
|
Shift-function keys
|
|
</p>
|
|
<p>
|
|
#F1 #F2 #F3 #F4 #F5 #F6 #F7 #F8 #F9 #F10 #F11 #F12
|
|
</p>
|
|
<p>
|
|
Alt-function keys
|
|
</p>
|
|
<p>
|
|
@F1 @F2 @F3 @F4 @F5 @F6 @F7 @F8 @F9 @F10 @F11 @F12
|
|
</p>
|
|
<p>
|
|
Ctrl-function keys
|
|
</p>
|
|
<p>
|
|
^F1 ^F2 ^F3 ^F4 ^F5 ^F6 ^F7 ^F8 ^F9 ^F10 ^F11 ^F12
|
|
</p>
|
|
<p>
|
|
Alt-Numbers
|
|
</p>
|
|
<p>
|
|
@0 @1 @2 @3 @4 @5 @6 @7 @8 @9
|
|
</p>
|
|
<p>
|
|
Alt-Letters
|
|
</p>
|
|
<p>
|
|
@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
|
|
</p>
|
|
<p>
|
|
Ctrl-Letters
|
|
</p>
|
|
<p>
|
|
^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
|
|
</p>
|
|
<p>
|
|
Insert/Delete
|
|
</p>
|
|
<p>
|
|
Ins ^Ins @Ins
|
|
Del ^Del @Del
|
|
</p>
|
|
<p>
|
|
Home/End
|
|
</p>
|
|
<p>
|
|
Home ^Home @Home
|
|
End ^End @End
|
|
</p>
|
|
<p>
|
|
Page up/down
|
|
</p>
|
|
<p>
|
|
PgUp ^PgUp @PgUp
|
|
PgDn ^PgDn @PgDn
|
|
</p>
|
|
<p>
|
|
Cursor left/right
|
|
</p>
|
|
<p>
|
|
Left ^Left @Left
|
|
Right ^Right @Right
|
|
</p>
|
|
<p>
|
|
Cursor up/down
|
|
</p>
|
|
<p>
|
|
Up ^Up @Up
|
|
Down ^Down @Down
|
|
</p>
|
|
<p>
|
|
Misc other keys
|
|
</p>
|
|
<p>
|
|
Esc ^Grey* Key5 Space Tab #Tab @Tab BackSpace ^BackSpace
|
|
@BackSpace Enter ^Enter @Enter
|
|
</p>
|
|
<p>
|
|
Note that some of the Alt-keys, especially the cursor-related keys and
|
|
the F11/F12 keys, are "extended" keys normally only available on
|
|
systems with an extended keyboard bios. However, <name>GoldED+</name> uses a few
|
|
tricks to make some the extended keys available on non-extended
|
|
systems.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Language Definition
|
|
</head>
|
|
<p>
|
|
GoldED allows you to almost completely redefine the language dependent
|
|
text in the program.
|
|
</p>
|
|
<p>
|
|
The language dependent text in <name>GoldED+</name> is defined in the plain ASCII
|
|
text GOLDLANG.CFG file.
|
|
</p>
|
|
<p>
|
|
See the example language file for the actual method and format of
|
|
language redefinition.
|
|
</p>
|
|
<p>
|
|
If you are planning to translate the text in <name>GoldED+</name>, you should also
|
|
look into the definition of the help screens.
|
|
</p>
|
|
<p>
|
|
You do not need permission from the author before announcing or
|
|
distributing your own modified language files.
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
Date/Time Substitution Codes
|
|
</head>
|
|
<p>
|
|
A few of the language texts can contain special date/time substitution
|
|
codes. The keywords for those are: MS_DateTimeFmt, MS_DateFmt,
|
|
MS_TimeFmt and ST_StatuslineTimeFmt.
|
|
</p>
|
|
<p>
|
|
Here are the valid substitution codes:
|
|
</p>
|
|
<p>
|
|
%a Abbreviated weekday name (Mon, Tue, Wed, ...).
|
|
%A Full weekday name (Monday, Tuesday, Wednesday, ...).
|
|
%b Abbreviated month name (Jan, Feb, Mar, ...).
|
|
%B Full month name (January, February, March, ...).
|
|
%d Day of month (01-31).
|
|
%e Day of month, with leading space for single digits (1-31).
|
|
%E Day of month (1-31).
|
|
%H Hour (00-23) (24-hour clock).
|
|
%I Hour (01-12) (12-hour clock).
|
|
%j Day of the year (001-366).
|
|
%m Month (01-12).
|
|
%M Minute (00-59).
|
|
%p AM or PM according to 12-hour clock.
|
|
%S Second (00-59).
|
|
%U Week number (00-52) where sunday is first day of the week.
|
|
%w Weekday (0-6) where 0 is sunday.
|
|
%W Week number (01-53) where monday is first day of the week.
|
|
%y Year without century (00-99).
|
|
%Y Year with century.
|
|
%% Character '%'.
|
|
</p>
|
|
<p>
|
|
The %a, %A, %b and %B codes substitute to the current language setup
|
|
loaded using the LOADLANGUAGE keyword.
|
|
</p>
|
|
<p>
|
|
*** NOTE ***
|
|
</p>
|
|
<p>
|
|
In the continuing development of <name>GoldED+</name>, it is impossible to
|
|
completely maintain backward compatibility of the language format or
|
|
the text defined there. New features may add and/or obsolete some
|
|
definitions, or may change the format of others.
|
|
</p>
|
|
<p>
|
|
The existing language file may contain definitions which are already
|
|
obsolete, but which I haven't had time to search for and remove, as
|
|
well as there may be some texts in <name>GoldED+</name> which are not yet definable.
|
|
All this will of course be corrected in future versions. If you find
|
|
inconsistencies, please report them, because I may have overlooked
|
|
them.
|
|
</p>
|
|
<!-- page -->
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</div2>
|
|
</div1>
|
|
<div1>
|
|
<head>
|
|
Message Kludge Lines
|
|
</head>
|
|
<p>
|
|
Kludge lines are special control lines, that begin with a ^a (ASCII 1)
|
|
as the first character of the line, followed by a unique identifying
|
|
name and the relevant control information.
|
|
</p>
|
|
<p>
|
|
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.
|
|
</p>
|
|
<p>
|
|
Some kludges are useless junk and more or less commercials for this
|
|
and that software, but a few are useful for miscellaneous purposes. In
|
|
the following, I will list (some of) the known and supported kludges,
|
|
and a short description of what they are used for.
|
|
</p>
|
|
<div2>
|
|
<head>
|
|
ACUPDATE:
|
|
</head>
|
|
<p>
|
|
This kludge is a feature of Squish 1.10: Message Broadcast
|
|
Modify/Delete. Read the docs for Squish 1.10 for details.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
AREA:<echoname>
|
|
</head>
|
|
<p>
|
|
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.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
CC: <name> <address>
|
|
</head>
|
|
<p>
|
|
When <name>GoldED+</name> 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.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
CHARSET:<charset identifier>
|
|
</head>
|
|
<p>
|
|
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.
|
|
<name>GoldED+</name> can recognize, use and generate this kludge.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
CHRC:<font change id>
|
|
</head>
|
|
<p>
|
|
Proposed in FSC-0054, this is a kludge for changing fonts,
|
|
underlining and other stuff.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
CHRS:<charset identifier>
|
|
</head>
|
|
<p>
|
|
Alternative FSC-0054 version of the CHARSET kludge.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
DESTADDR:<destaddress>
|
|
</head>
|
|
<p>
|
|
This one is not proposed anywhere, but it looks like it gives the
|
|
address of the intended recipient. <name>GoldED+</name> takes the address for
|
|
the dest field.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
DOMAIN <destdomain> <destaddress> <origdomain> <origaddress>
|
|
</head>
|
|
<p>
|
|
Proposed in FSC-0038, this tries to solve the problem of mail
|
|
crossing domain boundaries. <name>GoldED+</name> takes both addresses.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EID:<crc16> <stamp> [replycrc16] <replystamp>
|
|
</head>
|
|
<p>
|
|
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.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ENC:
|
|
</head>
|
|
<p>
|
|
Signifies that the message contains encrypted data. <name>GoldED+</name> will
|
|
add this kludge if it detects that the message has been encrypted
|
|
with PGP.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
EOT:
|
|
</head>
|
|
<p>
|
|
End Of Text. See SOT.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FLAGS <special attributes>
|
|
</head>
|
|
<p>
|
|
Proposed in FSC-0053, this is a special netmail kludge used by the
|
|
FrontDoor and D'Bridge mailers and the IMail mail processor. It
|
|
provides extra attributes not found among the standard attributes
|
|
in the normal message/packet headers. <name>GoldED+</name> uses and generates
|
|
this kludge, if you set the attributes.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FMPT <from point>
|
|
</head>
|
|
<p>
|
|
Defined in <name>FTS-0001</name>, this tells the point number of the
|
|
originator. Netmail only. <name>GoldED+</name> can generate this line.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FWDAREA <original area>
|
|
</head>
|
|
<p>
|
|
<name>FSC-0092</name>: The original area in forwards. See
|
|
<kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed
|
|
description.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FWDDEST <aka>
|
|
</head>
|
|
<p>
|
|
<name>FSC-0092</name>: The original <gi>To:</gi> address in forwards.
|
|
See <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed
|
|
description.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FWDFROM <name>
|
|
</head>
|
|
<p>
|
|
<name>FSC-0092</name>: The original <gi>From:</gi> name in forwards.
|
|
See <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed
|
|
description.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FWDMSGID <aka serial#>
|
|
</head>
|
|
<p>
|
|
<name>FSC-0092</name>: The original <gi>MSGID</gi> in forwards.
|
|
See <kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed
|
|
description.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FWDORIG <aka>
|
|
</head>
|
|
<p>
|
|
<name>FSC-0092</name>: The original from-aka in forwards. See
|
|
<kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed
|
|
description.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FWDSUBJ <original subject>
|
|
</head>
|
|
<p>
|
|
<name>FSC-0092</name>: The original subject in forwards. See
|
|
<kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed
|
|
description.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
FWDTO <name>
|
|
</head>
|
|
<p>
|
|
<name>FSC-0092</name>: The original <q>To:</q> field in forwards. See
|
|
<kw>USEFWD</kw> and <name>FSC-0092</name> for a more detailed
|
|
description.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
GATECHK:<???>
|
|
</head>
|
|
<p>
|
|
Some sort of gating kludge? Don't know what it's for.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
GIF:<filename>
|
|
</head>
|
|
<p>
|
|
Invented by <name>Henk Wever</name> and used in his
|
|
<name>Dutchie</name> software. The filename (which does not have an
|
|
extension) indicates a <abbr>GIF</abbr> picture of the author of the
|
|
message.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
GROUP:<echoname>
|
|
</head>
|
|
<p>
|
|
I think this one comes from stray Groupmail messages. Similar to the
|
|
<gi>AREA</gi> kludge.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
I51 (no parameters)
|
|
</head>
|
|
<p>
|
|
Proposed in <name>FSC-0051</name>, this indicates that the message text
|
|
conforms to the <name>ISO-8859-1</name> (<name>LATIN-1</name>)
|
|
character set, and may contain certain escape codes. The
|
|
<name>ISO-8859-1</name> set is used in <name>Amiga</name> and
|
|
<name>Windows</name> 3.xx. <name>GoldED+</name> can recognize, use and
|
|
generate this kludge.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
INTL <destaddress> <origaddress>
|
|
</head>
|
|
<p>
|
|
Defined in <name>FTS-0001</name>, this one solves the problem of
|
|
crossing zone boundaries. Netmail only. <name>GoldED+</name> can
|
|
generate this line.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MSGID: <origaddress> <serialno>
|
|
</head>
|
|
<p>
|
|
Defined in <name>FTS-0009</name>, this is a method for unique
|
|
identification of a message. It can be used for dupe checking and
|
|
replylinking. <name>GoldED+</name> can generate this line.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
MSGTO: <destaddress>
|
|
</head>
|
|
<p>
|
|
This one is not proposed anywhere, but it looks like it gives the
|
|
address of the intended recipient. <name>GoldED+</name> takes the
|
|
address for the dest field.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Original: <Carbon copy, original name>
|
|
</head>
|
|
<p>
|
|
Generated by the <name>FrontDoor</name> <name>FM</name> editor when it
|
|
produces carbon copies.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PATH: <list of nodes>
|
|
</head>
|
|
<p>
|
|
Defined in <name>FTS-0004</name>, 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.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PTH: <list of nodes>
|
|
</head>
|
|
<p>
|
|
Not yet a <name>FSC</name> (or is it?), this is a 5D-version of the
|
|
<gi>PATH</gi> kludge, which sticks to the top of the msg.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
PID: <identifier> <version> [serialno]
|
|
</head>
|
|
<p>
|
|
Proposed in <name>FSC-0046</name>, this takes a stab at the tearline
|
|
abuse, and puts <q>safe</q> information about the first mail processing
|
|
software in the line. This could be message editors, mail scanners and
|
|
other stuff.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Realname: <Name>
|
|
</head>
|
|
<p>
|
|
This kludge was probably born in Russia because of some software was
|
|
not able to properly handle non-<abbr>ASCII</abbr> characters in
|
|
the header lines. Name should be written in national codepage.
|
|
Otherwise I don't see any reason for this kludge. I don't know any
|
|
software that generate this kludge.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
RFD: <id>
|
|
</head>
|
|
<p>
|
|
Received For Distribution. A kludge inserted by one of the file
|
|
announcement programs.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
REPLY: <replyaddress> <replyserialno>
|
|
</head>
|
|
<p>
|
|
Defined in <name>FTS-0009</name>, this is the <gi>MSGID</gi>
|
|
counterpart. When replying to a message with a <gi>MSGID</gi>, the
|
|
<gi>MSGID</gi> of the original is renamed to <gi>REPLY</gi>.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
RID:<stuff>
|
|
</head>
|
|
<p>
|
|
Unknown kludge which looks suspiciously like the <gi>EID</gi>.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
ROUTE <list of nodes and points>
|
|
</head>
|
|
<p>
|
|
Specifies route path. Currently supported by <name>Unimail</name> and
|
|
<name>S\Tosser</name>.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SEEN-BY: <list of nodes>
|
|
</head>
|
|
<p>
|
|
Defined in <name>FTS-0004</name>, this is a tool for finding dupe links
|
|
and other structural faults in the net structures. Depending on the
|
|
mail tosser, the seen-by's may or may not have a preceding ^a
|
|
character. Unfortunately the list of nodes is 2D (net/node), and this
|
|
can create problems when exporting echomail across zones.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SN:<serialno>
|
|
</head>
|
|
<p>
|
|
Serial number inserted by the <name>Dutchie</name> message editor.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SOT:
|
|
</head>
|
|
<p>
|
|
Start Of Text. See <gi>EOT</gi>.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
SPLIT:
|
|
</head>
|
|
<p>
|
|
Defined in <name>FSC-0047</name>. A method for splitting large msgs so
|
|
that some mail processors don't choke on them.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TCL1:, TCL2: <long hex string>
|
|
</head>
|
|
<p>
|
|
Old obsolete swedish dupecheck/replylink kludge.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TID:
|
|
</head>
|
|
<p>
|
|
Tosser <abbr>ID</abbr>. Similar to the <gi>PID</gi>, but specifically
|
|
for mail processors.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TOPT <to point>
|
|
</head>
|
|
<p>
|
|
Defined in <name>FTS-0001</name>, this tells the point number of the
|
|
destination. Netmail only. <name>GoldED+</name> can generate this line.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TZ <offset from UTC>
|
|
</head>
|
|
<p>
|
|
Specifies the time to <hi>add</hi> to the header time to get the
|
|
<abbr>UTC</abbr> (Universal Time Coordinated) time. Generated by newer
|
|
versions of the <name>TrackMail</name> netmail processor.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
TZUTC
|
|
</head>
|
|
<p>
|
|
See <gi>TZ</gi>. <name>GoldED+</name> can generate this line.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
Via: <netmail tossing info>
|
|
</head>
|
|
<p>
|
|
Routed netmail messages usually gets a <gi>Via</gi> line for each node
|
|
it passes through. This can be used for tracing faults in the netmail
|
|
routing structure.
|
|
</p>
|
|
</div2>
|
|
<div2>
|
|
<head>
|
|
XID:<stuff>
|
|
</head>
|
|
<p>
|
|
Unknown kludge which looks suspiciously like the EID.
|
|
</p>
|
|
</div2>
|
|
</div1>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</body>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</text>
|
|
<!-- --------------------------------------------------------------------- -->
|
|
</TEI.2>
|