I just hit a problem and tried to find a solution, and I think I have one.

I have a modified default.src in my mods directory, because I use the DDMsgReader instead of the built in. However this means I have to manually update my default.src each time there's a change.

What if all the commands in default.src were includes?

Take this for example


cmdkey R
msg_read
end_cmd

This uses the built in reader, but I changed it to

cmdkey R
exec "?../xtrn/DDMsgReader/DDMsgReader.js -startMode=read"
end_cmd

So now I'm using the DDMsgReader instead.

But what if...

cmdkey R
!include ../text/msg_read.menu
end_cmd

text/msg_read.menu could contain just

msg_read

or it could contain

exec "?../xtrn/DDMsgReader/DDMsgReader.js -startMode=read"

That means I could update default.src any time I wanted and still retain my specific settings.


Now..apply the same !include principal to all the shells, and you only have
to change one file for all your shells (wildcat.src wwiv.src etc)

And the good thing is that since baja is compiled, it'll read in the incldes
at compile time (at least you'd assume?) so no extra i/o.

Digitalman, does this make sense? If I did the work would it be worth it to commit for everyone to use?

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: Changing the structure of default.src
By: Nelgin to DOVE-Net.DOVE-Net_Sysops on Fri Mar 06 2020 03:39 pm

I just hit a problem and tried to find a solution, and I think I have one.

I have a modified default.src in my mods directory, because I use the DDMsgReader instead of the built in. However this means I have to manually update my default.src each time there's a change.

What if all the commands in default.src were includes?

Take this for example

cmdkey R
msg_read
end_cmd

This uses the built in reader, but I changed it to

cmdkey R
exec "?../xtrn/DDMsgReader/DDMsgReader.js -startMode=read"
end_cmd

So now I'm using the DDMsgReader instead.

But what if...

cmdkey R
!include ../text/msg_read.menu
end_cmd

text/msg_read.menu could contain just

msg_read

or it could contain

exec "?../xtrn/DDMsgReader/DDMsgReader.js -startMode=read"

That means I could update default.src any time I wanted and still retain my specific settings.

Now..apply the same !include principal to all the shells, and you only have to change one file for all your shells (wildcat.src wwiv.src etc)

And the good thing is that since baja is compiled, it'll read in the incldes at compile time (at least you'd assume?) so no extra i/o.

Yup.

Digitalman, does this make sense? If I did the work would it be worth it to commit for everyone to use?

Sure, but notice that "all the shells" aren't identical.

I'm not too hip on the ".menu" filenames though. Why not .src or .inc, the existing Baja "standards"?

digital man

This Is Spinal Tap quote #2:
Nigel Tufnel: Well, this piece is called "Lick My Love Pump".
Norco, CA WX: 62.1øF, 71.0% humidity, 9 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Digital wrote:

[Snip a load of stuff[

Digitalman, does this make sense? If I did the work would it be worth it to
commit for everyone to use?

Sure, but notice that "all the shells" aren't identical.

I'm not too hip on the ".menu" filenames though. Why not .src or .inc, the existing Baja "standards"?

That's fine. I just used that to make it stand out from something else. I
hate to fill exec with .src or .inc files Where would you suggest is the
best place for them? Should I name them something like menu_msg_read.inc
or whatever ?

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: Re: Changing the structure of default.src
By: Nelgin to Digital Man on Fri Mar 06 2020 08:59 pm

Digital wrote:

[Snip a load of stuff[

Digitalman, does this make sense? If I did the work would it be worth it to
commit for everyone to use?

Sure, but notice that "all the shells" aren't identical.

I'm not too hip on the ".menu" filenames though. Why not .src or .inc, the existing Baja "standards"?

That's fine. I just used that to make it stand out from something else. I hate to fill exec with .src or .inc files Where would you suggest is the best place for them? Should I name them something like menu_msg_read.inc
or whatever ?

exec dir seems the right place. Or maybe exec/menu/* ?

digital man

This Is Spinal Tap quote #46:
"Not an Exit" - we don't want an exit. Well that's true.
Norco, CA WX: 60.4øF, 63.0% humidity, 6 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net