Hello Vincent,
Tuesday January 18 2022 17:26, you wrote to All:
How can I get hatch to accept multiple lines of descriptions for
a specific file as one liners are not cutting it ?
Add additional "DESC" lines to the "hatch" script. What I'd do is
read in the FILE_ID.DIZ and split it into the standard 10 45-char
lines as per the FILE_ID.DIZ specification.
How can I get hatch to accept multiple lines of descriptions for a
specific file as one liners are not cutting it ?
Add additional "DESC" lines to the "hatch" script. What I'd do is read in the FILE_ID.DIZ and split it into the standard 10 45-char lines as per the FILE_ID.DIZ specification.
Hello Vincent,
Tuesday January 18 2022 17:26, you wrote to All:
How can I get hatch to accept multiple lines of descriptions for
a specific file as one liners are not cutting it ?
Add additional "DESC" lines to the "hatch" script. What I'd do is
read in the FILE_ID.DIZ and split it into the standard 10 45-char
lines as per the FILE_ID.DIZ specification.
So you can have a single DESC with multiple LDESC lines in a TIC?
There should only be one "Desc" line in a tic file, it doesn't need to
be a short one liner, but it should all be on one line.
There can be multiple "LDesc" lines but that is different.
Thank you for that very important clarification.
So you can have a single DESC with multiple LDESC lines in a TIC?
mark lewis wrote to Sean Dennis <=-
http://ftsc.org/docs/fts-5006.001
http://ftsc.org/docs/fts-5006.001
Thank you very much for the clarification!
Hello Vincent,
Tuesday January 18 2022 20:00, you wrote to me:
The hatch program as near as I can tell does NOT read the
FILE_ID.DIZ but accepts a line for the description.
Let me look into this. I should be able to write a bash script to do
this.
Clearly using automation is best for them and myself - being a bit of
a lazy git :)
Hello Vincent,
Wednesday January 19 2022 15:23, you wrote to me:
Clearly using automation is best for them and myself - being a
bit of a lazy git :)
I wouldn't call it lazy but being more efficient.
I was looking into things last night but I am surprisingly busy right
now. I finally have MBSE running under FreeBSD and am working on
switching over to running MBSE again full-time. I have my OS/2 BBS
fairly automated and that makes it very easy for me so no reason not
to try to build that functionality into MBSE also.
I did have a look at the hatch.c code but realised yesterday it is NOT
to run the independent hatch operation but within the mbsebsb system.
A script called hatch is run and I could not work how to change it.
Hello Vincent,
Thursday January 20 2022 01:20, you wrote to me:
I did have a look at the hatch.c code but realised yesterday it
is NOT to run the independent hatch operation but within the
mbsebsb system. A script called hatch is run and I could not work
how to change it.
The "hatch" script itself isn't too bad. I could write a program that
could extract FILE_ID.DIZ from an archive and arrange it in both a
short DESC line then build LDESC lines from that.
Vincent Coen wrote to Sean Dennis <=-
That would be great if you can spare the time and with your permission
and after testing I would add it to the mbse sources for others to use.
Funny enough there is NO documentation regarding this hatch script and
I really
tried hard to find any so the current one must have been from a contributor that Micheal never used.
The original code looks like this :
--
for (i = 0; i < strlen(hatch.Desc); i++) {
if (hatch.Desc[i] != '%') {
fprintf(Tf, "%c", hatch.Desc[i]);
} else {
i++;
memset(&tmp, 0, sizeof(tmp));
if (isdigit(hatch.Desc[i]))
tmp[0] = hatch.Desc[i];
if (isdigit(hatch.Desc[i+1])) {
tmp[1] = hatch.Desc[i+1];
i++;
}
fprintf(Tf, "%c", de->d_name[atoi(tmp) -1]);
}
}
--
Vincent
--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 140:32:19 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,239 |