REPLY: 1:105/81@fidonet 65517dd3
MSGID: 1:16/101 6551917d
CHRS: LATIN-1 2
TZUTC: -0500
TID: hpt/lnx 1.9.0-cur 14-08-16
Hello, Rick!
Sunday November 12 2023 17:33, from Rick Smith -> All, in URL @OFGHIUrl:
RS> I have fidonet area F and MicroNet area M can golded display area M
RS> ahead of area F (or group I suppose).
From the GoldED Reference Manual, see below
===Begin===
AREALISTSORT (FYTUE)
This keyword defines how the area list should be sorted. You can
override the default setting from the commandline with the -S
switch.
The can be composed of the following types:
A Sort by aka.
B Sort by board number.
D Sort by description.
E Sort by echoid.
F Sorts all "fuzzy search" matches first.
G Sort by group (if any).
M Sorts all marked areas first.
O Sort by original order.
P Sort by personal mail.
T Sort by type (in the order net, echo, local).
U Sort by unread messages (try it!).
X Sort by msgbase type.
Y Sorts all areas with "new" mail first.
Z Sort by msgbase path.
- Descending sort (largest first).
+ Ascending sort (smallest first) (default).
In practice 'M' and 'Y' will usually give the same result, because
GoldED automatically marks scanned areas if they contain new mail.
Example:
AREALISTSORT T-U+E
This sorts ascending by Type, descending by Unread (that is, areas
with the most unread messages comes first) and ascending by Echoid
(in case two areas have the same number of unread msgs).
By default no sorting is done, and all areas are listed in the
order they were found (unless sorting was specified with an
AREAFILE keyword). However, the configuration examples all make
use of the Unread sorting type. This is a very useful way of
sorting areas, because it keeps all the areas with mail together.
Personally I now sort my areas like this: "AREALISTSORT FYTUE".
This puts all areas with new mail first, then sorts these into
type (net/echo/local), then into number of new msgs and finally
into echoid. The 'F' at the start enables fuzzy match sorting,
which is very handy when looking for an echoid containing a
particular word. Let's say I want a list of all GOLDED echoes. I
can now simply type "GOLDED" and then the arealist automatically
sorts itself so that all echoes with an echoid containing "GOLDED"
comes first :-)
The 'X' sort type sorts areas according to msgbase type, in the
following order:
Hudson
Goldbase
JAM
Squish
OPUS *.MSG
FTS-1 *.MSG
Ezycom
PCBoard
The 'X' and 'Z' sort types were implemented for internal use, to
optimize area scanning speed. When scanning areas, GoldED starts
by sorting the arealist using the sortspec defined with the
AREASCANSORT keyword.
===End===
RS> Second, I am using fastecho with proboard, if I write a message on
RS> proboard fastecho sees it and packs it for outbound. If I write the
RS> message using my golded fastecho does not see it and pack it, however
RS> that message can be viewed on the BBS? I must have something wrong
RS> wondering if anything pops to mind with anyone?
You have not mentioned whether a message written on proboard will be seen by
on BBS.
Fastecho will pack it for outbound, means subscribed links, if it sees new
messages in configured area. If proboard and fastecho are configured with the
same area location then the last will pack new messages. If you write a
message and fastecho will not pack it then it means that they point to a
different area location or there are no links to pack on.
Best Regards, Nil
--- GoldED+/LNX 1.1.5
* Origin: -=NIL BBS=- (1:16/101)
SEEN-BY: 1/123 15/0 18/200 90/1 105/81 106/201 123/131 129/305 153/7715
SEEN-BY: 218/700 226/30 227/114 229/110 112 113 206 307 317 400 426
SEEN-BY: 229/428 452 470 664 700 266/512 280/464 282/1038 291/111
SEEN-BY: 292/854 301/1 305/3 317/3 320/219 322/757 342/200 396/45
SEEN-BY: 460/58 633/267 280 712/620 848 770/1
PATH: 16/101 261/38 153/7715 3634/12 5020/1042 5030/49 5080/102
PATH: 712/848 229/426
|
