home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
gem250.zip
/
NOTE.DOC
< prev
next >
Wrap
Text File
|
1995-10-08
|
63KB
|
1,444 lines
----------------------------------------------------------------------
TECHNICAL NOTES
----------------------------------------------------------------------
This file contains detailed and often highly technical notes about the
news/fixes/changes of each version.
Symbols used: - Bugfix. ! Changed feature.
+ New feature. * Information/clarification.
----------------------------------------------------------------------
Notes for GoldED 2.50 Public Release, October 8th 1995.
----------------------------------------------------------------------
- The Write-to-file function now no longer uses the PRINTMARGIN, but
instead uses a fixed 80 chars margin. In a later release I will
add a keyword to set the margin specifically for Write-to-file.
- The arealist groupid column is now only shown if there is at least
one area with a groupid.
- Corrected several (but probably not all) bugs in the IBM_*.CHS
(and a few other) character translation tables, most notably
regarding the characters with ASCII codes 149, 150, 151, 161, 162
and 163. Also corrected a bug in the translation code which caused
GoldED to output kludges without the '^a' kludge character in some
situations.
The IBM_IQP.CHS file now uses the new ID 100000 which allows the
full 256 characters to be translated. This is done in order to
properly translate the '=' character to the q-p code "=3D".
Thanks to Rene Kreisbeck for pointing out bugs in the .CHS files.
Also added several new .CHS files for translation to and from
codepage 850. These files are named 850_???.CHS and ???_850.CHS.
+ The kludge "NOTE:" is now recognized as a known kludge, but is
otherwise ignored. This kludge is used by some programs as an
alternative free-form PID (product id).
- The EDITmacro's now allow single letters (highbit or not) to be
used to trigger a macro. This could be used to convert commonly
used local highbit letters to their ASCII equivalents. Example:
Æ EDITmacro "AE"
¥ EDITmacro "OE"
Å EDITmacro "AA"
æ EDITmacro "ae"
¢ EDITmacro "oe"
å EDITmacro "aa"
TIP: See also the new chapter "Converting your highbit characters
to ASCII" in the users guide manual for a couple of other ways of
doing this.
- In the adjusted file attach dialog, the window scrolled part of
the middle vertical border. Also, when the window wasn't filled
with files, the terminating was too short in wide screen modes.
- If no other file than GOLDLANG.CFG was edited, GoldED would crash
after compiling the configuration.
+ New key command READtouchsemaphore. There is no default key
assignment. This command will pop up an input window and allow you
to enter the name of a semaphore file, which will then be touched.
The command is meant to be used in macros, like this one:
F12 READmacro READtouchsemaphore "R:\FD\FDXIT1.117" Enter
This example macro touches a semaphore file which causes FrontDoor
task 1 to exit with errorlevel 117.
+ New keyword APP <programname> [keyword or parameters]. This was
added to enable other programs to use GOLDED.CFG as a place to
read their own configuration data. GoldED itself ignores the APP
keyword.
- Messages entered in Squish areas with Maximus v3 showed a lonely
kludge character at the top of the message.
+ New keyword AREASCANSORT <sortspec>. Defaults to XZBE. Specifies
the sort order used during area scanning. The default optimizes
speed.
+ New keyword CTRLINFO. Same as CTRLINFOECHO etc, but for use in
random system groups. This should help those who use the QWK and
Internet features and don't want tearline and origin in their
messages.
- The sound support in GoldED/2 now releases the sound device after
a sound file has played to the end.
+ At last, the language configuration in GOLDLANG.CFG has been made
up-to-date. The new example GOLDLANG.CFG contains *all* available
language keywords, with the newest separated out, plus a list of a
number of language keywords which are now obsolete. If you want to
keep your old GOLDLANG.CFG, but want to remove the obsolete
keywords, run GoldED with parameters -FF -D, which will cause
GoldED to show warnings about the obsolete keywords. Now almost
all text which is displayed on the screen can be translated.
Logging and error messages cannot be translated and either can the
registration info text in the startup screen. If you find some
text that you believe should be translatable, please let me know
and I will consider it.
NOTE: You will probably have to edit your GEDLNG*.CFG files too,
if you have them, because there are a few language keyword
commonly used in them, which are no longer supported.
- In the random system there was indeed a bug concerning groupid
letter groups, despite my information to the contrary for A0918.
Somehow the bug didn't turn up in my own test setup. Thanks to
Thomas Fisker who provided full input data per the instructions
given recently (subject REPORT.BUG).
- A word wrap bug in the internal editor has been fixed. It showed
when editing on the last positions of a line inside a paragraph.
The result was that words were split in two then the message was
saved.
! The -X debug commandline parameter now, in addition to showing
function tracking in the statusline, checks all memory allocations
for under/overruns every time function tracking is called, which
is at the entry and exit of many functions in GoldED. Using -X
will dramatically slow down GoldED, but it may finally pinpoint
the code which occasionally causes pointer under+overruns.
! The -Y debug commandline parameter now write all function tracking
continuously to the logfile and also writes additional debug
information, especially about area scanning. Note that the logfile
may grow quite large!
- The ELSEIF/ELIF configuration control keywords did not work
properly.
! The default for the AREAFILEGROUPS keyword is now YES. The change
was made to prevent support questions about "why doesn't my
groupid groups work?"
- The message list date column always showed "n/a" when switched to
show the "received" date.
- In GoldNODE index lookups, GoldED refused to access the index if
the original nodelists were missing.
+ The groupid numbers can now be in the range 1 to 999.
- Apparently groupid's in GEcho 1.20 are numbered 1-256 in the setup
and 0-255 in the configuration file. GoldED will now read them as
1-256.
- In FD/IM nodelist lookups, if the nodelist contained a zero-length
field (",,"), the entry would not be interpreted correctly.
- The message list now automatically switches the date column to the
date written, for messagebase formats that don't support the other
dates (arrived or received).
----------------------------------------------------------------------
Notes for GoldED 2.50.A0918 * Open Alpha * Public Pre-Release *
----------------------------------------------------------------------
* INFORMATION: Despite what you may think, the random system does in
fact still work in Beta6 and this Alpha. The "problem" is that it
has been fixed with regard to handling of GROUP's based on
groupid's (letters or numbers). It has been the practice in older
config examples to put these groups at the top, but now they
should be moved below most other groups, because otherwise they
will override them. Note however, that the Beta6 bug with messed
up descriptions and/or echoids *could* in some cases be the reason
for your problems. If that was the case, this Alpha should fix it.
If you still can't seem to get the random system to work as you
expect, send me (in netmail as a file attach) the files GOLDED.DMP
and GOLDAREA.INC after you run GoldED with these parameters: "-FF
-VV -W >GOLDED.DMP".
+ The character translation files (.CHS) can now define all
characters from 0 to 255 for level 2 sets if the ID is set to
65536 or higher. This is only of concern for anyone who wishes to
create new .CHS files.
- This macro now works:
@R Macro READmarkingoptions "R" READtogglemarkread.
- The file attach selection window has been modified to better
support long names on HPFS drives. The list of files is now sorted
without case sensitivity. The file size, date and time columns
were compacted to leave more space for the filename column. The
filename column now shows the actual filename instead of splitting
it up into name and extension.
- GoldED/2 required the file MDM.DLL to be in the LIBPATH, even when
the sound support was not used and MMPM/2 was not installed. A
dummy MDM.DLL was distributed to solve this problem for Beta6. In
this release there is no longer a need for the dummy MDM.DLL and
you can and should delete it.
+ Added a warning menu which comes up when you are to about change
an already sent message.
+ Added another menu item to the arealist scanning menu: "Scan
Group". This scans all areas which have the same groupid as the
current area.
+ Added a menu asking "Really exit?" which comes up if you press ESC
when GoldED is waiting for access to a locked messagebase.
- The default for STYLECODESTOPS has been changed back to the way it
was before Beta6 (nothing).
- When required nodelist or nodelist index files were missing,
GoldED would crash when trying to do a lookup. Now it will warn
that it is unable to access the files.
- In areas marked as Internet email, an extra "To:" line was added
at the top of the message body.
- There was an unfree'd pointer in gxmax2.cpp.
- The INTL/FMPT/TOPT kludges were messed up when copy/moving
messages to JAM netmail areas.
- GoldED/2 would seem to hang at exit when sound support was
enabled. It was in fact not hanged - pressing ESC at that point
would make it exit. This was due to an incomplete sound support
implementation. New sound support code was kindly provided by
Nicolai Dufva and this problem has been solved.
+ The arealist groupid column is now able to show numeric groupid's.
- The -t commandline option was not working. Actually it was removed
over a year ago because at that time it could not be supported. I
forgot to put it back when it could be supported again.
- When replying to a message in the Hudson msgbase, it linked back
but not forward.
- The palette is now restored during shells if you have redefined
it using SCREENPALETTE. This fix is not tested.
- GoldED would pause at the end of config reading when the -v
commandline option was used.
- Descriptions and/or echoids were messed up if they were not
defined. This would happen with AREAFILE Squish, AREAS.BBS and
several others.
- The config reader did not report unknown keywords if they didn't
have any parameters.
- The IF/ELIF/ENDIF logic was not solid. Now it works as expected
and warns if you make a mistake (such as putting ENDIF before IF
or try to nest IF/ENDIF's). Also, an ELSE keyword was added.
! The SCREENUSEANSI keyword is obsolete and has been for quite some
time, I just didn't bother to document it here.
----------------------------------------------------------------------
Notes for GoldED 2.50.Beta6, released september 1st, 1995.
----------------------------------------------------------------------
+ A new template token has been added: "@xlatexport <charset>". If
this token is used on a line in a template, the message will be
saved using the specified charset. This is particularly useful
when FidoNet netmail and Internet e-mail is mixed in a netmail
area and you want to use ISO-8859-1 quoted-printable for the
replies to the Internet e-mail. Then you just need to switch
template before replying. Example:
@xlatexport latin1qp
NOTE: A known problem with this feature is that it only works then
saving the message the first time. If the message is later
changed, the charset will revert to the default for the area. This
problem will be solved in a later version.
- The Random System GROUP behaviour has been changed with regard to
handling of groupid letter or number groups. Previously it was not
possible to specify exceptions to these groups. Now you can put
the exception groups before the groupid letter or number groups.
The rule is now: Specific groups first, general groups last. Here
is an example what should make it all clear:
GROUP GOLDED_R23.PNT ; A specific group
ORIGIN Danish support area
GROUP GOLDED: ; A general group
MEMBER *GOLDED*
ORIGIN All other GoldED areas
GROUP G ; A general groupid letter group
ORIGIN All areas belonging to group letter 'G'
GROUP #117 ; A general groupid number group
ORIGIN All areas belonging to group number 117
GROUP * ; Final catch-all group
ORIGIN Any area not taken care of above
ENDGROUP
+ When replying to messages in Squish or JAM areas, GoldED now
correctly updates the replylinks on the original message. For
Squish, it uses the first free link field, if any. For JAM, it
runs down the entire chain and updates the last link's replynext
field.
+ The JAM hexdump now also shows information about and from the
lastread record.
+ AREAFILE Maximus now supports Maximus 3.00. Detection of the
version is done by looking for a file named "MAREA.DAT". If that
file is found, version 3.00 is assumed.
+ The "MSGSEQ" kludge is now a known kludge and treated as such.
+ The "MOOD" kludge (invented by Terminate author Bo Bendtsen) is
now a known kludge and treated as such.
+ Soup export now exports from any area listed as EMail or News.
- Forward of messages to Internet e-mail areas with a To: line at
the top wasn't working as expected. Please let me know if there
are still problems.
- When forwarding from Internet areas, the From: name in the
original message was unintentionally used as from-name in the
forwarded message.
- In Internet e-mail, it was practically impossible to change the
To: name.
- The FD and V7 nodelist index lookups have been changed so that
they no longer pick the last of several matching names instead of
popping up the browser. This was a problem which came up in some,
not all, cases. NOTE: This fix has not been tested (because of
course I couldn't find any of the special cases when I needed
them..), but should work.
- In SOUP exports, long References headers were not exported
correctly.
- When importing SOUP packets, GoldED will now only put in *one*
REPLY kludge, using the last reference in the References header.
This has been done because some MSGID/REPLY-based replylinkers
will only look for one REPLY kludge, and the one it finds is
typically the first one. Unfortunately it is the last one which is
the most significant. Reversing the order of REPLY kludges
generated from the References header would help in this case, but
then there might be replylinkers that were using the last REPLY
kludge, and they would stop working correctly. So the best
compromise seems to be to keep only the most significant reference
and put it in the single REPLY kludge.
- Fixed a bug that caused GoldED/386 to crash on certain messages
when run in a DOS session under Windows.
+ In the arealist, if you have entered a "fuzzy" string, then the
scanning menus (Alt-S/Alt-P) will default to "Scan Matching".
- Fixed undesirable behavior in aka matching: The aka is now not
changed if the current aka already matches. (Not tested much!)
- Leading and trailing spaces are now trimmed from the @oname,
@dname and @tname tokens in templates. (Not tested!)
+ AREAFILE GEcho now supports version 1.20, including Squish and
PCBoard areas and numeric groups. I have tested that it still
works with GEcho 1.11, but I don't have 1.20 (beta) yet, so
testers will have to tell me if it works with that version.
+ Soundcards are now again supported in GoldED. In the DOS and 386
versions, sound is supported via the Goldware Sound API. Read
about the Goldware Sound API in the reference manual. For a sample
implementation of the Goldware Sound API, get GCTV100.ZIP. The
OS/2 version also supports sound, through MMPM/2. There are still
some minor problems with the sound support in OS/2.
- The Ctrl-M pulldown menus didn't accept left/right cursor keys.
- The AUTO macro keyword was not recognized in GOLDKEYS.CFG.
- The Alt-W(rite) output in wide screen modes was also wide. Write
output is now adjusted to the PRINTMARGIN.
- In wide modes like 100x25, there is was leftover junk after the
to-address field when replying to msgs with domain.
- Help screen: When switching from a topic with a long title to one
with a short title, there were junk left over from the long title.
! AREAFILE FastEcho now only supports major struct versions 4
(v1.10-1.40), 5 (v1.41) and 6 (v1.42 and up).
! AREAFILE IMAIL now only supports major struct version 4 (v1.6x)
and 5 (v1.7x), following advice from the IMAIL author.
+ Groupids in the range 1-255 are now supported. AREAFILE IMAIL
(for v1.7x and up) and AREAFILE GEcho (for 1.2x and up) now read
groupid numbers instead of letters.
If you want to use numeric groupids in AREADEF's, use the syntax
#nnn. Example:
AREADEF MYECHO "mydesc" #117 ...
If you want to specify numeric random system GROUP's, use the #nnn
syntax:
GROUP #117
ORIGIN "My 117th origin"
ENDGROUP
+ JAM netmail areas will now show INTL/TOPT/FMPT kludges in
netmails. Note that this is cosmetics only. All kludges shown in
JAM areas area actually reconstructed from the JAM subfield for
your viewing convenience.
+ New keyword: MSGLISTDATE <written/arrived/received/no>.
Defaults to "written". 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.
+ New key command: LISTtoggledate. Default assignment: Ctrl-D.
Toggles the content of the date column in the message list.
+ Added a new stylecode: #REVERSE#. A bunch of additional stylecode
colors have been added to support it:
COLOR STYLECODE R <colors>
COLOR STYLECODE RB <colors>
COLOR STYLECODE RI <colors>
COLOR STYLECODE RBI <colors>
COLOR STYLECODE RU <colors>
COLOR STYLECODE RBU <colors>
COLOR STYLECODE RIU <colors>
COLOR STYLECODE RBIU <colors>
Or you could simply use COLOR STYLECODE ALL <colors> to use the
same color for all combinations of stylecodes.
+ New keywords: STYLECODEPUNCT <"charlist">, and STYLECODESTOPS
<"charlist">. 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. The
STYLECODESTOPS keyword specifies characters which, if found within
the word to be highlighted, causes the highlight to be cancelled.
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:
STYLECODEPUNCT " !\"$%&()+,.:;<=>@[\]^`{|}~"
STYLECODESTOPS "/#*"
Note that the double-quote (") must have the backslash (\) in
front of it - the sequence (\") is translated to a single (").
! The DISPSTYLECODES keyword has been renamed to STYlECODES in order
to match the other new stylecode keywords. The old name is now
on the list of obsolete keywords.
* Further optimization of memory usage and overlays have been made
in this version. Even the OS/2 version seems snappier now! :-)
Note that the startup configuration compile is still somewhat
slower than you might be used to. Subsequent startups are faster.
! The content of the PID kludge for GoldED has now been revised to
conform 100% to the specification in FSC-0046.005. The PID for
GoldED will from now on have the following form:
GED[2,3] <major>.<minor>.<a,b,g><number> <serialno or UNREG>
Examples:
Tearline: PID:
GoldED 2.50 GED 2.5
GoldED/2 2.50.Beta6 GED2 2.5.b6
GoldED/386 2.50.A0812 GED3 2.5.a812
GoldED/386 2.51.Gamma1 GED3 2.51.g1 (note: fictional!)
The rule for inserting the PID or not has also been changed and
is now as follows:
The PID will be inserted if the token-expanded substring
"@longpid @version" is not found anywhere in the tearline.
The recommended (and default) tearline for GoldED is "@longpid
@version". If you use that as the whole or part of a tearline,
then the PID will not be inserted.
NOTE: The responsibility is entirely YOURS if you decide to break
the PID specification on purpose. YOU will break the PID
spec if YOU setup GoldED so that it generates both a PID and
a non-empty tearline.
+ NODEV7FLAGS <flag> <value>. 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.
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.
Example:
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
See also the NODEV7MODEM keyword for other nodelist flags.
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 GoldED setup.
+ NODEV7MODEM <type> <value>. 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.
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.
Example:
NODEV7MODEM VFC b0
NODEV7MODEM HST b1
NODEV7MODEM V34T b2
NODEV7MODEM V32B b3
NODEV7MODEM V34 b4
NODEV7MODEM V42B b5
NODEV7MODEM ZYX b6
NODEV7MODEM ISDN b7
See also the NODEV7FLAGS keyword for other nodelist flags.
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
GoldED setup.
- The nodelist browser only showed the first nodelist flag when
using FrontDoor indexes.
- If an empty name was entered in the to-field in a netmail area,
the nodelist browser did not pop up.
- The carbon copy function truncated the address, if it encountered
a CC entry with a name and address longer than 35 characters.
- Fixed a serious bug in the character translation function.
Messages you wrote were assumed to be in another charset than
expected. This would manifest itself prominently when using IBMPC
to LATIN-1 translation with characters with values above A0h, such
as 'ß' (225d).
+ New keyword: XLATLOCALSET <charsetid>. Defaults to IBMPC. 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).
All charset translation files must translate from and to the
charset identified with the XLATLOCALSET keyword.
This keyword was added so that it could, for example, be possible
to create charset translation files which translate between IBM
codepage 850 (CP850) and the LATIN-1 charset. These two charsets
can be converted almost loss-less to each other. The charset files
850_850.CHS, 850_ISO.CHS and ISO_850.CHS are now included. These
are for translation to/from the charset named CP850. Actually
several additional charset files should be added to complete the
set for CP850, but there wasn't time.
- The address mask "*" was expanded to "akazone:akanet/*.*" and not
"*:*/*.*" as intended.
+ New keyword TEMPLATEMATCH <yes/no>. Defaults to NO. If enabled,
GoldED 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. See below for more details
about template matching.
+ Added template matching feature. The TEMPLATE keyword now has the
following syntax (when used globally - not in groups):
TEMPLATE <file> ["desc"] [match-address]
The match-address is an address mask (wildcards allowed) which can
be used to tell GoldED 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.
Currently only one match-address per template can be specified,
but you can specify several TEMPLATE keywords for the same file.
Example:
// 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/*
// Use INTERNET.TPL for messages to the WinBoss gateway
TEMPLATE INTERNET.TPL "Internet" 2:230/9316
// Use ENGLISH.TPL for messages to everywhere else
TEMPLATE ENGLISH.TPL "English" *
NOTE: The description ["desc"] is optional, but if used, it must
appear before the match-address. It must always be enclosed in
quotes, even if it is only one word.
NOTE: To override the automatic template matching, start by
selecting a template manually using the READchangetemplate
(Ctrl-T) command or the EDITMENU.
- Fixed a bug in the FD index support for nodelists with no comma
and flags after the baud rate. This messed up the detail lines in
the browser.
! Removed the EDITMARGIN keyword which was introduced in A0715. It
was an attempt to solve a problem which occurs when using wide
screen modes and msgbases such as Ezycom and PCBoard which require
messages to have lines that are maximum 80 chars wide. EDITMARGIN
did not solve this problem properly. For now, you should run
GoldED in a 80 chars mode or set DISPMARGIN to 80 if you have
Ezycom or PCBoard msgbases.
+ The EDITHEADERFIRST keyword (introduced in A0715, see below) has
been changed to accept several new values. It now accepts:
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.
The New, Changes, Replies and Forwards values can be combined. YES
is equivalent to enabling all four of these.
For example, we want to edit the header only when entering a new
message or when changing a message:
EDITHEADERFIRST New, Changes
! The GIF kludge is now only inserted in your messages if the
specified GIF file is actually present in the GIFPATH. This
restriction has been implemented to prevent abuse of this feature.
After all, the intention of the GIF kludge is to specify a
filename that others can file request from you (or your bossnode).
+ New keyword: AREALISTSCAN <"L menu text"> [path]<filename>. This
keyword allows you to define additional menu items for the
arealist scanning menus (Alt-S or Alt-P).
The filename specifies a plain ASCII 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 GOLDPATH.
Example:
AREALISTSCAN "g Scan Newsgroups" NEWSGRPS.LST
=== Cut, NEWSGRPS.LST ===
ALT.*, COMP.*, MISC.*, NEWS.*
REC.*, SOC.*, SCI.*, TALK.*
=== Cut ===
+ It is now possible to undefine any built-in key command, using one
of these new key commands:
AREAundefine
EDITundefine
FILEundefine
LISTundefine
NODEundefine
READundefine
For example, if you want to undefine the right-arrow in the
arealist, put this in your GOLDKEYS.CFG:
Right AREAundefine
+ Added mode-specific keyboard macros. This means that you can now
define keyboard macros that work only in the internal editor, or
in the reader etc. These are the new macro key commands:
AREAmacro
EDITmacro
FILEmacro
LISTmacro
NODEmacro
READmacro
Examples:
@G AREAmacro "GOLDED"
^N EDITmacro EDITnewline EDITgoup
@F1 READmacro READcopymoveforward "C" "THE_SAFE" Enter
NOTE: The old global macro key command still works as normal.
+ AREAFILE IMAIL now supports version 1.70 or newer, provided that
it is backwards compatible with 1.6x. Not tested.
- The Internet Organization RFC line disappeared after changing a
message.
+ The file request function now always adds FILES to the list of
requestable files, unless FRQOPTIONS NOFILES is specified.
- In the internal editor, the line number in the statusline was not
updated after an automatic wordwrap.
+ New keyword EDITHEADERATTRS <yes/no>. Defaults to YES. 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.
+ You can now manually toggle the attributes window on and off by
pressing Alt-F1 during header edit. This is a help if you are
trying to enter a name or address based on information in the
message text which might be covered by the attributes window.
- In wide screen modes, such as 132x45, and when the header and
reader colors are different, the reader colors would show through
in non-updated blocks to the left of the date fields.
----------------------------------------------------------------------
Notes for A0715:
----------------------------------------------------------------------
* The regular DOS version now uses a bit less memory than before,
due to various memory saving code changes:
1. Code rearrangements which reduced the overlay buffer size.
2. Removal of the function tracking debug code.
3. Reduction of the max echoid size from 80 to 50 chars.
4. Nodelist lookup doesn't have to load the entire .GXA any more.
In my tests I found that the memory meter in the statusline now
shows at least 20k more than A0611. The reduction of the max
echoid size will also have a positive effect on the memory meter,
especially if you have a large number of message areas.
The startup (configuration reading) is now a bit slower, because
the configuration interpreting code was spread over more overlays.
Due to the smaller overlay buffer, there may be a slight overall
slowdown or it may seem a bit sluggish. If you have plenty of DOS
memory available and the statusline memory meter typically shows
more than 150k, you might want to use the commandline option -o to
increase the overlay buffer size for more speed.
I have my eye on several things in GoldED that uses a lot of
memory, and I will continue working on reducing the memory usage
in future releases.
NOTE: For the 386 and OS/2 versions, the function tracking debug
code is still present, and the max echoid size is still 80.
! The nodelist lookup and browser is now fully functional for
Version 7, FrontDoor/InterMail(*), FIDOUSER.LST and GoldED
nodelist indexes. Please see the notes for A0611 regarding the
setup for V7/FD/IM/FIDOUSER. It is still only possible to use one
of the different types of indexes.
(*) The nodelist browser for FrontDoor/InterMail indexes is
currently not working 100% correctly. A straight lookup should
work fine, and the browser will typically work pretty well when
scrolling/paging downward, but upward scrolling/pageing and screen
update will mess up (but not fatally) after a while. This will be
corrected in a later release.
In the browser, the Tab key will now toggle between name and
address lookup and browsing.
NOTE: I have decided to continue supporting my own GoldED nodelist
index and GoldNODE, even now that Version 7 and FrontDoor index
support is in place. This is due to the fact that not all software
supports one of these formats, and a set of Version 7 indexes is
substantially larger than GoldED's own. GoldNODE will now be
distributed in a separate archive, to reduce costs for those to
don't need it. However, I can recommend Marius Ellens FASTV7,
which can produce GoldED indexes and often does it faster than
GoldNODE, especially in low-memory setups.
- The nodelist lookup now again works as expected when looking up
the string ".?". This works like looking up ".0", except that the
browser will come up for further selection.
- Under some circumstances, such as after a search, the pagedown or
enter key would fail to work as expected.
- The EDITzapquotebelow command now leaves a blank line after doing
its thing.
- For Internet messages, GoldED did not parse addresses with commas
in quotes correctly. Example: "Name, Name" <what@where>. This is
now correctly parsed.
- When the EDITreflow command was used on a single line, the line
was not updated.
- If F1 was pressed while the screenblanker was running, the help
window would come up and start moving around the screen :-)
+ New keyword EDITCOMPLETION <"abbreviation"> <"completion">. This
new feature allows you to define abbreviations which will be
automatically expanded to full words or sentences when typed in
the internal editor. Examples:
EDITCOMPLETION "Odin" "Odinn"
EDITCOMPLETION "GED" "GoldED"
EDITCOMPLETION "V7" "Version 7"
EDITCOMPLETION "FD" "FrontDoor"
NOTE! The abbreviation is case-sensitive. If "XX" is defined as
an abbreviation, completion will NOT be triggered if "xx" is
typed.
+ New keyword AREALISTGROUPID <yes/no>. Defaults to YES. If enabled,
the arealist screen will display the group id letters, if any, in
a column to the right of the EchoID column.
- AREAFILE FastEcho did not get the group letter from versions 1.41g
and 1.45 (structure revision 6).
- If INTERNETADDRESS was defined globally, it was used as the From
name instead of the current USERNAME.
- The domain (if any was defined) on the address in the MSGID kludge
was missing.
- The EDITdupline key command (F4) didn't leave the cursor on the
correct line.
- The stylecodes feature was broken in the regular DOS version and
could cause strange behavior and crashes.
- The READquotebuf key command (Ctrl-W) caused a crash when used in
an empry area.
- The internal editor would fail to display lines correctly if empty
quotes were used with the EDITCHARPARA or EDITCHARSPACE keywords.
+ New keyword EDITMARGIN <margin>. Defaults to 80. Specifies the
margin used when editing messages. Previously this margin was
controlled using the DISPMARGIN keyword. The addition of
EDITMARGIN allows the possibility of viewing messages on the full
width of, say, a 100x40 or 132x44 screen, but still only edit
messages 80 chars wide. This is mostly relevant for those
messagebases that must have lines that are hard-terminated at max
80 chars per line.
+ New keyword NODEPATHIM <path>. 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.
+ AREAFILE LoraBBS now sets the PVT attribute on areas that are
marked as "Private only". It now also sets the GOLDBASEPATH if it
is not defined.
- IMPORTANT! The Hudson/Goldbase NETMAIL/ECHOMAIL.BBS/.DAT files
were not updated correctly. Because of this, it is possible that
some messages that you have written have not been scanned out. To
scan out the unscanned messages, you should force your mail
scanner to scan the entire Hudson/Goldbase messagebase. Here are
some typical "force complete Hudson scan" commandlines for a few
of the popular mail processors:
FastEcho: Scan -N -HMB
FMail: Scan /S
GEcho: Scan -Force
IMAIL: Scan /F /H
+ New keyword EDITHEADERFIRST <yes/no>. Defaults to YES (work as
usual). If set to NO, the header edit will be bypassed and you
will start directly in the EDITMENU (if enabled) or in the
internal or external editor. A new menu item has been added in the
EDITSAVEMENU, "Edit Header", which allows you to edit the header
after you have written your message, but before it is finally
saved. If you set EDITHEADERFIRST to NO, you must either have the
EDITSAVEMENU enabled, or use the internal editor, because
otherwise it is not possible to edit the header at all.
- GoldED put uppercased names in the userlist produced with the
READmakeuserlist command. The case is now left unchanged.
+ New keyword ORGANIZATION <text>. Defaults to nothing. Specifies
the content of the RFC Organization header for Internet messages.
GoldED will no longer use the ORIGIN text in the Organization
header.
+ The RFC header X-FTN-To is now supported. It supplies the to-name
from FTN (FidoNet) headers.
+ New keyword TIMEZONEOFFSET [+/-]<hhmm>. Defaults to zero.
Specifies the difference in hours and minutes from GMT/UT. Note
that the sign must be correct. Zones west of Greenwich have
negative offsets. Some examples:
-1000 Alaska-Hawaii Standard Time
-0900 Hawaii Daylight Time
-0800 Pacific Standard Time
-0700 Pacific Daylight Time
-0700 Mountain Standard Time
-0600 Mountain Daylight Time
-0600 Central Standard Time
-0500 Central Daylight Time
-0500 Eastern Standard Time
-0400 Eastern Daylight Time
-0100 West Africa Time
+0000 Greenwich Mean Time
+0100 Central European Time
+0100 British Summer Time
+0200 Central European Summer Time
+0200 Eastern European Time
+0700 West Australian Time
+0800 West Australian Daylight Time
+0800 China Coast Time
+0900 Japan Standard Time
+0900 Central Australian Standard Time
+1000 East Australian Standard Time
+1000 Central Australian Daylight Time
+1100 East Australian Daylight Time
+1200 New Zealand Standard Time
+1300 New Zealand Daylight Time
Note that the hh in a timezone offset can go up to about 14; it is
not limited to 12. This is because the International Date Line
does not run exactly along the boundary between zone -1200 and
+1200.
The timezone offset is currently only used for the RFC Date header
in Internet messages.
----------------------------------------------------------------------
Notes for A0611:
----------------------------------------------------------------------
+ Added FrontDoor, Version 7 and FIDOUSER.LST lookup capability!
This release contains the first *very* *rough* implementation of
FD/V7 nodelist index support. At this time, it only supports a
direct lookup of the first match, no browsing. The nodelist
browser may come up, but it will not display anything useful.
Three new keywords have been added to support the new feature:
FIDOUSERLIST <file> Path and name of a sorted FIDOUSER.LST file.
NODEPATHFD <path> Path to the FrontDoor nodelist index files.
NODEPATHV7 <path> Path to the NODEX.* and SYSOP.NDX files.
Currently lookup is only supported for one of these three. If all
three are defined, GoldED will only lookup the Version 7 index. In
a later release, it is planned that GoldED will try them in
sequence until a match is found.
For the FIDOUSERLIST, the list file is expected to be sorted in
ascending alphabetical order using 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 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).
NOTE: GoldED's own nodelist index files are still supported in
this release, in case the FD/V7 support is too buggy. As soon as
it is debugged, and full browsing has been implemented, I intend
to remove the support for GoldED's own index files (reducing the
GoldED EXE size) and drop the GoldNODE program. GoldED will use
it's own index if none of the three new keywords are defined.
+ Enhanced the functionality of some keywords which previously
accepted only one parameter. Here is a list of the keywords which
will now accept more than one parameter, separated by spaces or
commas:
AREAEXCL
AREAINCL
AREAISEMAIL
AREAISNEWS
AREAPMSCAN
AREAPMSCANEXCL
AREAPMSCANINCL
AREASCAN
AREASCANEXCL
AREASCANINCL
FRQEXT
ROBOTNAME
This means that you can now write:
AREAISNEWS alt.*, comp.*, misc.*
Instead of:
AREAISNEWS alt.*
AREAISNEWS comp.*
AREAISNEWS misc.*
So now you can make a more elegant configuration :-)
- With FRQWAZOO YES, spaces in the subject were transformed into LF
characters.
+ New keyword: QWKOPTIONS <bbsid> <options>. 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:
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, GoldED 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.
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.
RECEIPT/NORECEIPT: Defaults to NORECEIPT. Specifies whether or not
the BBS supports return receipt requests (RRQ). If the RECEIPT
option is enabled, GoldED will insert "RRR" at the front of the
subject field if the RRQ attribute is set on your messages, when
exporting to QWK packets.
- QWKCONFMAP did not work correctly when conferences names were
enclosed in double quotes.
- Unknown kludges with a colon were not recognized as hidden lines.
- In the arealist, you could type a fuzzy string so that that it
wrapped down on the next line.
- The uudecode function did not work when there was a table at the
beginning of the uuencoded data.
+ For those who are not interested in setting up different colors
for each stylecode combination, it is now possible to specify a
single highlight color for all the stylecode combinations:
COLOR STYLECODE ALL <color>
Remember to place this definition *below* COLOR READER WINDOW.
+ The FILEALIAS definitions now also work in the internal editor
import function.
+ GoldED now adds the "Sender:" RFC header in your Internet e-mail
and newsgroup articles.
! In Internet newsgroups, GoldED now uses "X-To:" instead of "To:"
in newsgroups for safety. It turned out that some software would
send an e-mail copy to the To: address if found in a newsgroup.
+ New keyword: UUDECODEPATH <path>. Specifies the path where files
are placed when using the uudecode feature. Files are placed in
current directory if a path is not specified.
- When in personal mail mode, after the "delete original?" menu,
GoldED was locked into the area at msg 1.
- In Hudson/Goldbase, netmails with the DEL attribute were deleted
on-the-fly if encountered.
- Character translation of character ASCII 255 was not performed
correctly.
- The internal editor in A0525 painted some strange colors when
moving around with the cursor.
----------------------------------------------------------------------
Notes for A0525:
----------------------------------------------------------------------
- In SOUP import, an internal buffer was too small (2k) to handle
some obscenely long RFC headers. The buffer has now been increased
to 16k (crossing fingers that it is enough).
+ New keyword and feature: DISPSTYLECODES <yes/no>. Defaults to NO.
If enabled, GoldED will highlight text surrounded by one of the
following characters in a different color: '*' for bold text, '/'
for italic text and '_' for underlined 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.
There are 7 new color keyword combinations which are used to
define the colors of the stylecodes. By default, GoldED assigns
the COLOR READER WINDOW to all 7 stylecode colors. Therefore you
must define these 7 colors specifically if you enable
DISPSTYLECODES, otherwise you will not see any difference. Here is
an example:
COLOR STYLECODE B Red on LGrey ; *Bold*
COLOR STYLECODE I Blue on LGrey ; /Italic/
COLOR STYLECODE BI LMagenta on LGrey ; /*BoldItalic*/
COLOR STYLECODE U Green on LGrey ; _Underline_
COLOR STYLECODE BU Yellow on LGrey ; _*BoldUnderline*_
COLOR STYLECODE IU LCyan on LGrey ; /_ItalicUnderline_/
COLOR STYLECODE BIU Black on LGrey ; _/*BoldItalicUnderline*/_
These definitions must be placed after COLOR READER WINDOW,
because it overrides the COLOR STYLECODE definitions.
- QWK export set the line length to the DISPMARGIN instead of the
maximum allowed 80 chars.
+ AREAFILE PCBoard now reads the PCBFIDO.CFG file to get FidoNet
addresses/akas and the true echoids for conferences. GoldED finds
the location and name of the file at line 246 in PCBOARD.DAT. The
docs for v15.21 lists line 246 as "reserved", but I assume that
this is an oversight.
- Fixed two bugs in the PCBoard support: The lastreads in boards
above #39 were not read from and written to the correct file
offsets. Messages deleted with GoldED incorrectly showed up again
with the DEL attribute.
+ New keywords: AREAISEMAIL <echoid> and AREAISNEWS <echoid>. One or
more of each can be used, but only one echoid per line. Wildcards
* and ? are allowed. These keywords are designed to mark areas
which are read from an AREAFILE as Internet e-mail or newsgroups.
This may be necessary in some cases to enable the Internet
specific features without having to manually define all Internet
areas. Examples:
AREAISNEWS alt.*
AREAISNEWS rec.*
AREAISNEWS sci.*
- If INTERNETADDRESS was defined globally, GoldED would insert a
^aFrom: kludge (RFC headerline) in all messages, including FidoNet
messages. GoldED will now only use the Internet address in areas
that are marked as e-mail or newsgroups, either with
AREAISEMAIL/AREAISNEWS, manually with AREADEF, with SOUPEMAIL or
in the SOUPNEWSRCFILE.
- The QWK export function did not uppercase the to/from names.
- The uudecoder would hang if a uuencoded msg was not terminated
correctly.
- It was not possible to change the destination Internet address on
e-mails.
- The destination Internet address could not be set using
addressmacros for e-mails.
- AREAFILE FMail did not get the recovery board.
- The CC: function did not work with Internet addresses.
- The new keywords CTRLINFOEMAIL and CTRLINFONEWS were not
recognized by the config reader.
----------------------------------------------------------------------
Notes for A0517:
----------------------------------------------------------------------
+ Added QWK packet support! New keywords:
QWKIMPORTPATH Path where unpacked QWK packets can be found.
QWKEXPORTPATH Path where QWK packet files can be placed.
QWKBADMSGS Area where bad QWK msgs can be placed.
QWKCONFMAP Conference<->echoid mapping setup.
QWKTOSSLOG Name of a logfile for areas with imported msgs.
QWKREPLYLINKER Commandline for an external replylinker.
For more details about the QWK support, please read the Alpha
edition of the "Using the QWK features" chapter in the file
GOLDQWK.DOC.
The QWK import/export feature is accessed via a submenu in the
arealist Alt-S menu.
+ New and changed Internet SOUP features:
SOUP packet export has now been implemented! The export is
started from the Alt-S menu in the arealist. The SOUP import menu
entry has been changed to a "SOUP Packet" entry which leads to a
submenu where import or export is selected.
To support the SOUP packet export and to improve SOUP packet
import and Internet compatibility in general, a number of new
keywords were added. Below is a brief list. For more detail,
please read the Alpha edition of the "Using the SOUP features"
chapter in the file GOLDSOUP.DOC.
SOUPEXPORTPATH Path for exported SOUP packet files.
SOUPNEWSRCFILE Name of the .newsrc file.
SOUPTOSSLOG Name of a logfile for areas with imported news.
SOUPREPLYLINKER Commandline for an external replylinker.
MAILINGLIST Mailing list participation setup.
INTERNETRFCBODY Gets/puts RFC headerlines at the msg body top.
+ Support of character translations for MIME ISO-8859-1, 8bit and
quoted-printable encoding, plus RFC1345 character mnemonics
(X-Charset) have been added. The new or updated charset table
files ISO_IBM.CHS, IQP_IBM.CHS, IBM_IQP.CHS, IBM_MNE.CHS and
MNE_IBM.ESC are included with this release. For examples of usage
and details of character translation on Internet, see
GOLDSOUP.DOC.
+ Updated the charset file MAC_IBM.CHS, because the old edition
didn't correctly translate some of the Danish characters from the
MAC charset to the IBMPC (CP865) charset.
+ Added three new template tokens:
@oto Original RFC "To" headerline.
@ofrom Original RFC "From" headerline.
@omessageid Original RFC "Message-ID" headerline.
These only work for messages which contain the RFC headerlines,
otherwise they are replaced with a zero-length string.
They were added so that templates can be created with attribution
lines that look like the main defacto standard types.
For an example template for use in Internet newsgroups, see
GOLDSOUP.DOC.
- Fixed the bug that caused the log entry "Detected 1 unfree'd
memory allocation [..] at [gemsgs.cpp,nnn]. This was just a
harmless memory leak. It occurred when doing a carbon copy which
was aborted because there were nobody else to carbon copy to.
+ Added new keycommand: READchangexlatimport. Default key assignment
is Ctrl-J. This command is used to manually select the import
charset. The import charset is the one that messages are assumed
to be written with, if there is no control information in the
message that specifically sets the charset. When the command is
given, GoldED will display a menu of all the XLATCHARSET lines
that convert to the IBMPC charset. It is recommended to sort the
XLATCHARSET lines so that the most commonly used charsets are
listed first. See the chapter about Internet and SOUP in the
manual for examples of suggested sorting.
+ Added two keywords: "CTRLINFOEMAIL <tearline,origin,yes,no>".
Defaults to "no". And "CTRLINFONEWS <tearline,origin,yes,no>".
Defaults to "no". These specify what, if any, FTN control lines
that will be added at the bottom of the Internet e-mails and news
articles that you write. Typically you should not have to use
these keywords. They were only added for completeness.
+ The AREADEF keyword now accepts "EMail" and "News" as area types
along with "Net", "Echo" and "Local". Areas defined as EMail or
News will be scanned when starting a SOUP export.
- Fixed two different causes of the dreaded internal editor "Range
Check (_length > (maxcol+1))" problem.
- The message lister could cause NULL pointers to be found or
failure to find msgnos in internal indexes.
- There was a long-standing problem with very long kludge lines
being wrapped wrongly so that parts of them showed even when
kludges are hidden. This was mostly a problem when using GoldED in
Internet areas.
- The new Squish PRN attribute bit (introduced in Beta5) was not
properly implemented.
- Fixed the problem that caused MBUTIL Index to report "Invalid JAM
signature in xxxx.JHR after Msg# yyy".
----------------------------------------------------------------------
Notes for A0307:
----------------------------------------------------------------------
* If the Alpha archive contains a .BDF file, use the BUPDATE utility
to update your copy of the original Beta5 .EXE.
- The new HUDSONSYSPATH keyword was supposed to default to the
HUDSONPATH, but instead it defaulted to the GOLDPATH. Check if you
have some NETMAIL.BBS and/or ECHOMAIL.BBS files in the GOLDPATH.
If you have, delete them.
PLEASE NOTE! You may have some mail which is not scanned out
because of this bug. You should make your mail processor scan the
entire Hudson msgbase for unsent mail.
! When the FRQWAZOO feature was enabled, the request netmail was not
saved. The request netmail is now by default saved. If this is not
desired, add the new NOWAZOOMSG parameter to the FRQOPTIONS
keyword.
- The FRQWAZOO feature had a few problems: It did not make a .HLO
file, and it did not handle requests with passwords correctly. The
fixes have not been tested.
One remaining problem have not yet been dealt with: Different
outbounds for different domains is not supported.
+ New keyword: "MENUMARKED <marked/current/previous/default>".
Defaults to DEFAULT. Specifies the position of the selection bar
in the Marked/Current menu.
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.
Note that older versions (before 2.50) used the equivalent of the
"previous" setting.
+ New keyword: "INTERNETADDRESS <address>". Can be used globally or
in Random System groups. Specifies your Internet address.
Currently only used by the INTERNETMSGID feature, but later it
will be used with other Internet features.
+ New keyword: "INTERNETMSGID <yes/no>". Defaults to NO. Can be used
globally or in Random System groups. If enabled, GoldED will use a
different format in the MSGID kludge, compatible with the Internet
Message-ID header line. Well-written replylinkers and dupe
detectors should still be able to handle the MSGID in the new
format. This feature is only meant to be used together with the
Internet SOUP packet feature. Note that the new format in
principle violates the FTS-0009.001 specification, so please don't
use it in FidoNet net- or echomail. This keyword requires that an
Internet address is specified with the new INTERNETADDRESS
keyword.
+ New keyword: "AREACOPYADDID <yes/no>". Defaults to NO. If enabled,
GoldED will insert the control line "AREA:<originalechoid>" at the
top of each message that is copied or moved. This can be a help
when regularly copying messages to a "THE_SAFE" type area.
+ The EDITMIXCASE keyword can now also be specified in Random System
groups. This is useful if you prefer mixcase enabled in FidoNet
areas, but don't want it in Internet areas.
+ The TAGLINESUPPORT keyword can now also be specified in Random
System groups. This will be most useful to when you specify
taglines globally, but need to disable them for areas where they
are not allowed or desired.
- AREAFILE FMail did not get the netmail board descriptions. It also
did not get the group id letter.
- The subject was character translated on file request or attach
messages. This could produce undesirable results.
- The "^aENC: PGP" kludge was added even on clearsigned messages.
- The Forward feature asked about marked/current message, but it is
only designed to work on the current message.
- Squish personal mail scan: GoldED did not check the received bit
in the hash value.
- If "PERSONALMAIL Startup" was specified and no AREAPMSCAN keywords
were found, GoldED would not scan any areas on startup. Now GoldED
will use the AREASCAN keywords if no AREAPMSCAN keywords are
found.
+ AREAFILE FrontDoor now recognizes JAM folders. Untested.
+ The AREA:<echoid> line in messages is now also recognized when it
is a kludge (^aAREA:).
+ For SOUP packet import, the binary formats 'b' and 'B' are now
supported. Private mail in the 'u' format ('unm') is now treated
as e-mail. Still not supported yet is the 'M' format. Can anyone
give me some packets in that format?
+ Added new search string options to the Alt-F/Alt-Z find functions
and the Alt-S Header/Text marking functions. The new search string
options are: '<', '>', '=', '*' and '!'. Here is the complete list
of all search string options:
- Search backward.
+ Search forward.
< Search the From: field.
> Search the To: field.
: Search the Subj: field.
= Case-sensitive search.
! Reverse - Stop/mark when the search string(s) are NOT found.
By default, '<', '>' and ':' are enabled, so that GoldEd searches
all header fields. When one of the from/to/subj options are used,
the search is limited to those only.
Examples:
"<Odinn Sorensen"
Searches for "Odinn Sorensen" in the From: field only.
"<>Odinn"
Searches for "Odinn" in both From: and To: fields.
":tagline"
Search for "tagline" in the Subj: field only.
! Changed a default option in FRQOPTIONS. The "FromTop" option is
now default. A new "NotFromTop" option has been added if you want
the previous behavior, where GoldED started the filename search
from the top of the screen instead of the top of the message.
----------------------------------------------------------------------
Previous notes were for GoldED 2.50.Beta5 and older.
----------------------------------------------------------------------