Daniel D. Rodrigues

Wow! Could you share your source code with these changes? I have created a GitHub repository and uploaded all available versions one by one there, for historical purposes. In addition to making it easier to compare changes, using diff. Take a look, you may like it. I made a mistake in my GitHub repository and made your version 3.20f available in the Releases section as if it were version 3.20 of Howard S. Wulf (a.k.a. AF5NE). I know that Howard S. Wulf was working on a 3.30 version, but never released....

Hey Howard, can you share the code for bwbasic 3.30? Also, FYI, I have created a GitHub repository: https://github.com/nerun/bwbasic. If you want access, let me know.

@KenUnix, Have you changed anything in the code? What are the differences from 3.20 in Files section (2017) tô yours 3.20f? What you have changed in renum2? There's any changelog.gz?

New and updated bwbasic package for Linux Debian Amd64

@KenUnix, worked like a charm! I've dug around in the guts of bwBASIC enough to know stuff about it. The simple answer is that bwBASIC is not a "shell" in the sense that "BASH" or just plain "SH" are. Its a BASIC interpreter. It runs BASIC programs. You can execute shell commands from it with the "SHELL" function. So you would do something like this: bwBASIC: shell "ls" Or if you want to capture the exit code and do something with it, you use the SHELL() function, like this: x = shell("ls") I've...

Why shell commands are not working? In bwbasic 2.20 i can use ls -l *.bas: bwBASIC: ls bwbasic bwbasic-3.20.zip renum2 In 3.20f i can't: bwBASIC: ls ILLEGAL COMMAND AFTER LINE NUMBER: 1 ls bwBASIC: ls -l *.bas ILLEGAL COMMAND AFTER LINE NUMBER: 1 ls -l *.bas

DELETED

Why shell commands are not working? In bwbasic 2.20 i can use ls -l *.bas: bwBASIC: ls bwbasic bwbasic-3.20.zip renum2 In 3.20f i can't: bwBASIC: ls ILLEGAL COMMAND AFTER LINE NUMBER: 1 ls bwBASIC: ls -l *.bas ILLEGAL COMMAND AFTER LINE NUMBER: 1 ls -l *.bas