Upon entering an unknown command TCC9 outputs error message 'TCC: Unknown command "rxyz"' and makes no beep, while TCC13 outputs no error message and makes a beep. How can I make TCC13 act like TCC9, please?
Upon entering an unknown command TCC9 outputs error message 'TCC: Unknown command "rxyz"' and makes no beep, while TCC13 outputs no error message and makes a beep. How can I make TCC13 act like TCC9, please?
|Upon entering an unknown command TCC9 outputs error message 'TCC: Unknown command "rxyz"' and makes no beep, while TCC13 outputs no error message and makes a beep. How can I make TCC13 act like TCC9, please?
That may be in the plugin I sent you (but I wouldn't expect that plugin to work
with v9). I was experimenting with UNKNOWN_CMD (and BEEP). I'll send another
one.
|Upon entering an unknown command TCC9 outputs error message 'TCC: Unknown command "rxyz"' and makes no beep, while TCC13 outputs no error message and makes a beep. How can I make TCC13 act like TCC9, please?
That may be in the plugin I sent you (but I wouldn't expect that plugin to work
with v9). I was experimenting with UNKNOWN_CMD (and BEEP). I'll send another
one.
Indeed it is. I'm not using it with v9 just v13, and that's where I had this issue.
Fyi, this command sequence reverts v13 to v9-like behavior:
plugin /u * & for i in (plugins\*.dll) plugin /l %i
but this one doesn't:
plugin /u * & plugin /l *
One would think both commands would accomplish the same thing, but no...
|Fyi, this command sequence reverts v13 to v9-like behavior:
What's "v9-like behavior"?
| plugin /u * & for i in (plugins\*.dll) plugin /l %i
|but this one doesn't:
| plugin /u * & plugin /l *
|One would think both commands would accomplish the same thing, but no...
They seem to do the same thing for me (as long as I'm in d:\tc13).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.