daves Posted June 13, 2014 Share Posted June 13, 2014 If I have a variable called Bam5 and accidentally type bam5=5 in the terminal it sets m5 to 5! This could be nasty if m5 started a crushing move, say. I know there should be other safety limits. I know it is hard for the terminal to know if you are concatenating valid commands but I think some thought is required here, maybe ; delimiters? I see from another post a new IDE is coming, maybe this is addressed. I also hope it is Visual Studio Shell 2013. Is it? We were promised the 2010 shell 3 years ago... Link to comment Share on other sites More sharing options...
curtwilson Posted June 13, 2014 Share Posted June 13, 2014 Try setting Sys.NoShortCmds to 1. This disables most single-letter commands so that they cannot be confused with user names. (e.g. you must use "begin" for "b", "abort" for "a") Link to comment Share on other sites More sharing options...
MClement Posted June 14, 2014 Share Posted June 14, 2014 Or typing something with an "r" like "rabbit" and it runs whatever program is loaded. Seems like the noshort should be the default for safety? Link to comment Share on other sites More sharing options...
curtwilson Posted June 16, 2014 Share Posted June 16, 2014 Unfortunately, changing the default would create major backward incompatibilities for users "right out of the box". Link to comment Share on other sites More sharing options...
Recommended Posts