Hi DM,
I'm trying to use the Default.src file as a reference to build my own command shell and I have a couple of questions:
# Get key (with / extended commands allowed)
compare_user_misc UM_COLDKEYS
if_false
getkeye
else
getstrupr 60
endif <---
1. Is that endif a typo? Is it supposed to be end_if or does it matter?
I'm trying to use the Default.src file as a reference to build my own
command shell and I have a couple of questions:
# Get key (with / extended commands allowed)
compare_user_misc UM_COLDKEYS
if_false
getkeye
else
getstrupr 60
endif <---
1. Is that endif a typo? Is it supposed to be end_if or does it
matter?
should probably be end_if but that works
Re: Default.src
By: MRO to Uatu13 on Sun Sep 24 2017 13:27:36
I'm trying to use the Default.src file as a reference to build my own
command shell and I have a couple of questions:
# Get key (with / extended commands allowed)
compare_user_misc UM_COLDKEYS
if_false
getkeye
else
getstrupr 60
endif <---
1. Is that endif a typo? Is it supposed to be end_if or does it
matter?
should probably be end_if but that works
Thanks Mro, that puts me one step closer to debuging my command shell.
-=U13=-
Hi DM,
I'm trying to use the Default.src file as a reference to build my own command shell and I have a couple of questions:
# Get key (with / extended commands allowed)
compare_user_misc UM_COLDKEYS
if_false
getkeye
else
getstrupr 60
endif <---
1. Is that endif a typo? Is it supposed to be end_if or does it matter?
------------
# Do nothing for control keys and space
cmdkey ^@
cmd_cmd
cmdkey ^M
end_cmd
cmdkey ^S
end_cmd
cmdkey " <---
end_cmd
2. Is that last cmdkey supposed to only be one double quote (') ?
cmdkey " <---
end_cmd
2. Is that last cmdkey supposed to only be one double quote (') ?
No, it's correct. It just means a blank command key (a space character).
digital man
Re: Default.src
By: Digital Man to Uatu13 on Mon Sep 25 2017 15:44:46
cmdkey " <---
end_cmd
2. Is that last cmdkey supposed to only be one double quote (') ?
No, it's correct. It just means a blank command key (a space character).
digital man
Thanks, my experience was telling me it needed two double quotes with a space in the middle.. Would that work too?
Also, is there any reason why adding a folder path to MENU xferinfo in the File Info Section, for example: MENU darkside\xferinfo
When I add the folder path none of the options on the File Info Section menu work except for 'Q'.
Note: Adding the folder path to all the other MENU statments within Default.src works as expected.
Also, is there any reason why adding a folder path to MENU xferinfo in
the File Info Section, for example: MENU darkside\xferinfo
No, I see no reason why that would be. The "menu" function is just for displaying the menu (e.g. ANSI) file to the user and has nothing to do with the command key parsing/processing. If an option/command doesn't work, I suspect something else is the matter.
digital man
Re: Default.src
By: Digital Man to Uatu13 on Tue Sep 26 2017 11:33:23
Also, is there any reason why adding a folder path to MENU xferinfo in
the File Info Section, for example: MENU darkside\xferinfo
No, I see no reason why that would be. The "menu" function is just for displaying the menu (e.g. ANSI) file to the user and has nothing to do with the command key parsing/processing. If an option/command doesn't work, I suspect something else is the matter.
digital man
Thanks. I suspected this, but just had to check because nothing else makes sense. I copied the Default.src to Darkside.src then added the path darkside\menufile to all the MENU functions. The Darkside folder resides in the text\menu folder and all the custom menu files display, but none of the info_ functions are working when that command shell is used; I discovered last night that it's not just the File Info, it's also the Main Info not working as well.
I guess I'll have to start over and test after I add each path to the .src file to hunt this down.
darkside\menufile to all the MENU functions. The Darkside folder resides in the text\menu folder and all the custom menu files display, but none of the info_ functions are working when that command shell is used; I discovered last night that it's not just the File Info, it's also the Main Info not working as well.
I guess I'll have to start over and test after I add each path to the .src file to hunt this down.
Thanks for help as always! :)
matter.Re: Default.src
By: Digital Man to Uatu13 on Tue Sep 26 2017 11:33:23
Also, is there any reason why adding a folder path to MENU xferinfo
in the File Info Section, for example: MENU darkside\xferinfo
No, I see no reason why that would be. The "menu" function is just
for displaying the menu (e.g. ANSI) file to the user and has
nothing to do with the command key parsing/processing. If an
option/command doesn't work, I suspect something else is the
digital man
Thanks. I suspected this, but just had to check because nothing else
makes sense. I copied the Default.src to Darkside.src then added the
path darkside\menufile to all the MENU functions. The Darkside folder
resides in the text\menu folder and all the custom menu files display,
but none of the info_ functions are working when that command shell is
used; I discovered last night that it's not just the File Info, it's
also the Main Info not working as well.
But the other menu files work okay?
I guess I'll have to start over and test after I add each path to the
.src file to hunt this down.
You might want to use a forward-slash instead of a backslash. Forward-slashes are cross-platform (work in both Windows and *nix) and they don't need escaping (e.g. "\\") in any context.
digital man
Re: Default.src
By: Uatu13 to Digital Man on Tue Sep 26 2017 09:43 pm
darkside\menufile to all the MENU functions. The Darkside folder
resides in the text\menu folder and all the custom menu files display,
but none of the info_ functions are working when that command shell is
used; I discovered last night that it's not just the File Info, it's
also the Main Info not working as well.
I guess I'll have to start over and test after I add each path to the
.src file to hunt this down.
Thanks for help as always! :)
go to my bbs, bbs.eob-bbs.com and send me an email with your email address. also if you want to at this point, zip up your menus and the .src file and send it to me and i will look it over and run it on my test system and fix it up if i can.
i'm also on irc at irc.bbses.info user mro. you can pm be the info but i dont take file xfers.
---
■ Synchronet ■ ::: BBSES.info - free BBS services :::
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,043 |
Nodes: | 16 (0 / 16) |
Uptime: | 44:35:58 |
Calls: | 500,941 |
Calls today: | 4 |
Files: | 109,374 |
D/L today: |
4,322 files (919M bytes) |
Messages: | 304,043 |