You'll notice
Useful3 Signal0
Importing Gemini commands containing a plain exclamation mark no longer fails validation.
What's wrong with this entry?
Anonymous. No account, no email.
What
Importing a Gemini command that used an exclamation mark as prose or negation could fail validation even when nothing shell-like was involved.
Details
- Previously any command mixing argument placeholders with a '!' anywhere outside its shell blocks was rejected.
- The importer now masks
$-prefixed tokens first. - It only flags a '!' whose preceding character is not an ordinary word or punctuation character.
- The dangling-marker and shell-block checks are unchanged.
Evidence
Mixes argument placeholders with backticks or '!' outside its shell blocks
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command