REPLY: 2:250/1@fidonet 64b1b4d8
MSGID: 1:320/119 64b36b5e
PID: GED+2 1.1.5-b20230304
CHRS: CP437 2
TZUTC: -0400
TID: FastEcho 1.46.1 10045
Hello Vincent!

Friday July 14 2023 21:46, Vincent Coen wrote to Sean Dennis:

 >> I don't think you can use a wildcard.  I believe it has to be an
 >> actual filename.  I am no expert on this but many years ago I
 >> talked to the Allfix developer about this.

 VC> Found the TIC spec in doc FTS-5006.001 which states :

 VC>  Replaces

 VC>      This specifies that the file replaces one or more files that
 VC>      were sent previously. It is up to the receiving system if it
 VC>      honours this keyword.
 VC>      The wildcard characters '?' and '*' may be used with the usual
 VC>      meaning as in MS-DOS.
 VC>      Some tic processors do not support wild cards and use of
 VC>      wild cards with this keyword may cause unexpected results.


 VC> With the proviso of unexpected results which I assume means that if
 VC> you use *.* it will scrap the lot so any s/w must check that such a
 VC> first '*' is not less than the 5 chars etc.

 VC> So the question is what does mbse do and more importantly in what
 VC> program ?

MBSE does NOT support wildcards in the .TIC Replaces directive.  The
processing of the Replaces directive is done in addbbs.c which handles adding
the file to the BBS file database.

Andrew

---
 * Origin: Bits & Bytes BBS * V.Everything! * 860/503-8857 (1:320/119)
SEEN-BY: 1/19 123 15/0 16/0 18/200 19/37 80/1 90/1 105/81 106/201
SEEN-BY: 123/130 131 129/305 142/73 104 153/7715 203/0 218/700 221/0
SEEN-BY: 226/30 227/114 229/110 112 113 206 307 317 400 426 428 452
SEEN-BY: 229/470 550 664 700 240/5832 266/512 282/1038 291/111 292/854
SEEN-BY: 317/3 320/119 219 319 2119 322/0 757 342/200 396/45 460/58
SEEN-BY: 633/280 712/848 5020/400 5075/35
PATH: 320/119 219 229/426