home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 2362 
 Vincent Coen to Andrew Leary 
 mbse v..4 and hatch and 
 16 Jul 23 22:55:57 
 
REPLY: 1:320/119 64b36b5e
MSGID: 2:250/1@fidonet 64b4676e
CHRS: UTF-8 2
TZUTC: 0100
TID: MBSE-FIDO 1.0.8.4 (Linux-x86_64)
Hello Andrew!

Saturday July 15 2023 23:54, you wrote to me:

 > 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
 VC>> 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
 VC>> if you use *.* it will scrap the lot so any s/w must check that
 VC>> such a 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.

That's a shame but I will have to live with it.
The trouble is I get new additions to one area i.e., PDNBASIC as a file
without any TIC details including description so I have to do a unzip -z
filename.ZIP just to get the one liner to use when running hatch - that then
gets the full description via file_id.diz but if I just use a one word detail,
that get passed on to all downlinks instead.

I have now asked him to specify the previous fn.

Can I assume that if I specify old fn to REPLACE it is NOT case sensitive ?

He does NOT run a BBS.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
 * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
SEEN-BY: 1/19 120 123 15/0 16/0 18/0 200 19/37 25/0 80/1 90/1 103/705
SEEN-BY: 105/81 106/201 123/0 10 25 130 131 180 200 755 3001 124/5016
SEEN-BY: 129/305 135/115 300 142/104 153/757 7715 154/10 30 40 50
SEEN-BY: 154/700 203/0 218/700 220/90 221/0 6 222/2 226/18 30 227/114
SEEN-BY: 227/201 229/110 112 113 206 307 317 400 426 428 452 470 550
SEEN-BY: 229/664 700 240/1120 5411 5413 5824 5832 5853 6309 250/0
SEEN-BY: 250/1 2 3 4 5 6 7 8 11 12 13 14 263/0 266/512 275/1000 280/464
SEEN-BY: 280/5003 282/1038 291/111 292/854 8125 299/6 301/1 310/31
SEEN-BY: 317/3 320/119 219 319 2119 322/0 757 341/66 234 342/200 396/45
SEEN-BY: 423/120 460/58 467/4 633/280 712/848 1321 770/1 2320/105
SEEN-BY: 3634/0 12 27 57 119 5020/400 1042 5075/35
PATH: 250/1 3634/12 154/10 280/464 240/5832 320/219 229/426


<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca