When someone discovers these little "glitches", the PowerGlove always pops up.
Haha. Yeah. I... will avoid unpacking my feelings and just say that I appreciated your post.

The changes don't seem to break anything, and in fact, it works really well. This is going to be quite handy for designing signatures.

Thanks for testing it!
This is especially useful when you want to add a [ quote ] tag but accidentally click [ code ] instead.
I see that you're using spaces to write BBCode tags in a way that doesn't "activate" them. Maybe you already know this, but, just in case you don't: that's what
[nobbc] is for (so that, for example, you can write
[quote] rather than
[ quote],
[quote ], or
[ quote ]).
(Hmm... I wonder if it's worth adding [nobbc] to the toolbar and/or the help? It might be a nice "starter patch" for someone looking to get their feet wet! Though, just as I say that, I think, "Please, please don't some AI-using wally now decide to take a run at a task that would ordinarily have stymied them. I'm getting really, really tired of digesting output that's clearly mysterious to the person presenting it.")Even more off-topic: I recently noticed that someone had their display name changed to a BBCode tag ([btc]), and I thought, "Ah, jeez. Now people need to mangle the name, or use
[nobbc] or a zero-width joiner or something each time they want to mention that user? Sigh."

@theymos: Maybe you should place a zero-width joiner after the opening bracket of that user's display name, so that copy-pasting the name can become a reasonably convenient way to mention them? (Probably I would undo the name-change if it were up to me; I'd probably also add some logic to prevent any future BBCode-colliding display names.)
