[14.0.92 Pro] - BUG: Formatted Comments

[14.0.92 Pro] - BUG: Formatted Comments

Sometimes the action for Formatted Comments does not trigger. It seems that if the comment is 'behind' a single line `--` comment, the action skips, unless the single line comment is 'blocked' by a block comment first.

Check out this short video >>>here<<<.

The attached video is demonstrating an abstract scenario that doesn't seem to be aligned with the use case for the specially formatted comments designed as value placeholders for INSERT, UPDATE, and CALL statements to help with a faster data entry and code completion, and column-value pairs matching. Can this be reproduced with a use case more like what's in the example below?

INSERT INTO ... ( bunch of columns here)
VALUES (bunch of comment formatted value placeholders here)

I don't think this has anything to do with the use case this feature was originally intended for. The User's Guide (page 99, One-Click Actions for Specially Formatted Comments) discusses this feature, saying these comments are specially formatted comments that are treated as placeholders for entry fields. It also mentions that SA generates these when completing INSERT, UPDATE, and CALL statements; it does not state that those cannot be used in other parts of the code.
Since SA lacks the feature of post-snippet-insertion placeholders that could be traversed after inserting the snippet contents, eg. using Tab / Shift+Tab, I've been using these Specially Formatted Comments as a crude replacement for years.

The behavior suggests this is more likely related to how SA recognizes what is a comment (or what is not), and what it should or should not do when inside a comment. Some things work inside a comment, while others do not: for example, the above mentioned statements INSERT, UPDATE etc., are not completed when you type them inside a comment. On the other hand, last-key-triggered snippets are triggered.

If you check this code:

	Code:
	INSERT INTO `information_schema`.`ENGINES` ( `ENGINE`, `SUPPORT`, `COMMENT`, `TRANSACTIONS`, `XA`, `SAVEPOINTS` ) VALUES ( -- /{ ENGINE }/, /{ SUPPORT }/, /{ COMMENT }/, /{ TRANSACTIONS }/, /{ XA }/, /{ SAVEPOINTS }/ )

in this short video >>>here<<< you'll see that the specially formatted comment for ENGINE does not trigger its select action when it is hidden behind a single-line comment.

And a bonus funny thing: if I 'close' the single line comment with */ (which, by the way, should not close a single line comment), it magically starts working again.