Closed nyankers closed 1 year ago
Thanks, I added it to my todo list. Thought I had fixed it a while ago, but apparently not.
Should be fixed in yesterday's release. It goes through the generic escaping routine now, so ;
and some other characters are escaped as well.
Using
#CURSOR GET
has some odd behavior with curly braces. It basically seems like it's not escaping them, so when the variable is later used, they're treated as code braces rather than characters.For example:
This throw error messages if the buffer contains
{
but will work if it contains other stuff, such asblah{
.The error message:
#ERROR: GET BRACED ARGUMENT: UNMATCHED BRACE.
However, using it as an index to another variable (whether using
$
or&
), evenblah{
will spam the above error message: