[BUG] Unexpected behavior with subcommand in quotes

[creamsan]

Environment

📱 Termux

System

Mull 125.3.0

Version

SillyTavern 1.12.0-preview 'staging' (517da9f)

Desktop Information

No response

Describe the problem

The exection goes through despite using /abort with quotes. {: ... :} works fine though.

Additional info

Please tick the boxes

• I have explained the issue clearly, and I included all relevant info
• I have checked that this issue hasn't already been raised
• I have checked the docs

[Cohee1207]

@LenAnderson does the abort not immediately stop the execution in the new parser when encountered in a subcommand?

[LenAnderson]

My guess would be that subcommands are called with handleExecutionErrors set to true. Should be false so that the exception gets rethrown and reaches the proper scope. I can take a look tonight.

…

________________________________ From: Cohee ***@***.***> Sent: Thursday, May 16, 2024 1:00:39 PM To: SillyTavern/SillyTavern ***@***.***> Cc: Len ***@***.***>; Mention ***@***.***> Subject: Re: [SillyTavern/SillyTavern] [BUG] Unexpected behavior with subcommand in quotes (Issue #2254) @LenAnderson<https://github.com/LenAnderson> does the abort not immediately stop the execution in the new parser when encountered in a subcommand? — Reply to this email directly, view it on GitHub<#2254 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABWRMQB4D5WYQYOGXLITFKLZCTQ3PAVCNFSM6AAAAABH2SDEVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVG43TINJUGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Cohee1207]

Should be false so that the exception gets rethrown and reaches the proper scope.

I believe that's all to it.