since you can customize text.dat colors, how do you customize the sbbsecho colors?
Re: sbbsechosbbsecho colors?
By: The Millionaire to digital man on Sat Aug 03 2019 02:48 pm
since you can customize text.dat colors, how do you customize the
You don't. Unless you are willing and able to modify sbbsecho.c. I'll add itto the todo list though. Reading/using strings from
sbbsecho.ini should be doable.
digital man
Synchronet/BBS Terminology Definition #63:
SMB = Synchronet Message Base (e.g. smblib)
Norco, CA WX: 71.5øF, 64.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs
So yeah, I could help you to do that, but if you ever used echocfg to edityour sbbsecho.ini, it'd be all merged together into one
giant file and likely not what you were hoping for.
Hey DM,
Would you consider sbbsecho.ini supporting a wildcard include?
eg: in sbbsecho.ini you have "include sbbsecho/*.ini"
Then, the placement of "abc.ini" in the dir sbbsecho/, which would present a new node "abc", could automatically be included when sbbsecho does its processing.
Much the same way other linux wildcard includes work..
I was thinking that would be useful for hubs where an external process could add the required ini file relatively easily and drop it in that dir for a new node.
Re: sbbsecho
By: Digital Man to alterego on Fri Apr 03 2020 12:41 am
So yeah, I could help you to do that, but if you ever used echocfg to edit your sbbsecho.ini, it'd be all merged together into one
giant file and likely not what you were hoping for.
Your right, this probably wouldnt be ideal. But for the other reason, I think it would be great.
A step further might be a !include fsx/* - where the could be node ini files, with also domain and echolist ini files (they dont have to be in order do they?) - then config packs could be provided by othernets (if they desired).
If you do implement it (I would still use it), can you make echocfg "warn" when it is invoked, if it detects that the config has been created with included files - just in case somebody goes to use it (out of habit) and the result would be as you say a giant file. (Or by default echocfg ignores included files?)
If you do implement it (I would still use it), can you make echocfg "warn" when it is invoked, if it detects that the config has been created with included files - just in case somebody goes to use it (out of habit) and the result would be as you say a giant file. (Or by default echocfg ignores included files?)
Yeah, probably.
Re: sbbsechocreated
By: Digital Man to alterego on Fri Apr 03 2020 08:52 am
If you do implement it (I would still use it), can you make echocfg "warn" when it is invoked, if it detects that the config has been
habit)with included files - just in case somebody goes to use it (out of
requests (e.g. changing archive type). This will also expand the sbbsecho.ini to include all the !include'd files, currently. That will also have to be addressed.and the result would be as you say a giant file. (Or by default echocfg ignores included files?)
Yeah, probably.
So here's another issue:
SBBSecho itself can update the sbbsecho.ini file in response to AreaFix
Also, assuming that first problem is addressed, if the updated nodeconfiguration was *within* one of those !include'd files, that node couldn't be
digital man[vert/cvs/bbs].synchro.net
Synchronet/BBS Terminology Definition #52:
NUP = New User Password
Norco, CA WX: 61.1�F, 66.0% humidity, 3 mph E wind, 0.00 inches rain/24hrs ---
� Synchronet � Vertrauen � Home of Synchronet �
Interesting topic.
I admit that like that feature because i am used to "debian.d" includes.
You can easy manage the ini file via the *crudini* tool
The problem are that echocfg generate indents for the options/values
pairs, and raise error for this tool to parse the file.
See: https://github.com/pixelb/crudini/issues/30
[node:4:90/1@fidonet]
<TAB>Name = Momia BBS
<TAB>Comment = Manuel Adorni
<TAB>Archive = ZIP
<TAB>PacketType = 2+
If you can add option that echocfg to generate the file without these
tab, just work
you can add a node:
crudini --set sbbsecho.ini "node:4:9/9@fidonet" name "FErnando Toledo" crudini --set sbbsecho.ini "node:4:9/9@fidonet" Archive ZIP
Re: sbbsecho
By: Digital Man to alterego on Fri Apr 03 2020 11:14 am
Also, assuming that first problem is addressed, if the updated node configuration was *within* one of those !include'd files, that node couldn't be updated via AreaFix or bad things would happen.
Ahh, OK, that goes against my goal of automation and self service. I agree that is not desirable, so perhaps this is not a good idea after all.
Thanks for going through it though...
Re: sbbsecho
By: The Millionaire to digital man on Sat Aug 03 2019 02:48 pm
You don't. Unless you are willing and able to modify sbbsecho.c. I'll add it to the todo list though. Reading/using strings from sbbsecho.ini should be doable.
digital man
Synchronet/BBS Terminology Definition #63:
SMB = Synchronet Message Base (e.g. smblib)
Norco, CA WX: 71.5°F, 64.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs
Also, assuming that first problem is addressed, if the updated node configuration was *within* one of those !include'd files, that node couldn't be updated via AreaFix or bad things would happen.
Re: sbbsecho
By: The Millionaire to digital man on Sat Aug 03 2019 02:48 pm
You don't. Unless you are willing and able to modify sbbsecho.c. I'll add it to the todo list though. Reading/using strings from sbbsecho.ini should be doable.
Why not add the lines to text.dat instead?
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (1 / 7) |
| Uptime: | 190:38:19 |
| Calls: | 2,006 |
| Calls today: | 3 |
| Files: | 11,114 |
| Messages: | 942,286 |