Mark Pruitt
03-06-2005, 14:48
Hey Eros, I have a question about using ThinBASIC from the command prompt.
I prefer to do a lot of mundane things from the command prompt. I've been using ThinBASIC mostly that way. After entering something like, "C:\thinbasicC.exe ...", I've found that I need to type in the complete extension (.tbasic) to run a script.
As it is now, it seems ThinBASIC expects you to enter the entire extension before it will run a script. Do you think there would be any value to having it assume the operator is looking for a .tbasic script, so that you could enter something like the below and run a script?
"c:\thinbasicC script1" as opposed to "c:\thinbasicC script1.tBasic"
Have you tried adding ThinBASIC to the PATH directory, so you could do something like "script1.tbasic" and have a script run?
This is not necessarily a feature request. I'm more curious. I don't know how many like the command prompt as much as I do. Thanks.
I prefer to do a lot of mundane things from the command prompt. I've been using ThinBASIC mostly that way. After entering something like, "C:\thinbasicC.exe ...", I've found that I need to type in the complete extension (.tbasic) to run a script.
As it is now, it seems ThinBASIC expects you to enter the entire extension before it will run a script. Do you think there would be any value to having it assume the operator is looking for a .tbasic script, so that you could enter something like the below and run a script?
"c:\thinbasicC script1" as opposed to "c:\thinbasicC script1.tBasic"
Have you tried adding ThinBASIC to the PATH directory, so you could do something like "script1.tbasic" and have a script run?
This is not necessarily a feature request. I'm more curious. I don't know how many like the command prompt as much as I do. Thanks.