You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have "Trigger with trailing space" turned on, but I can not trigger at the start of a new line. This makes logical sense given the wording, but does not make sense with a typical workflow: there is a whitespace separation from the previous content, which is more in line with the conceptual intent of this feature, At least in my mind; opinions certainly would vary, which leads to two different proposals, one appealing to a conceptual fix and one to a more programmer/technically minded use case:
In a simple solution, a grouped option (that is disabled until the above option is turned on) that reads: "Allow at start of line" would be helpful.
As an advanced solution: "Allow after the following characters" would allow something like "]\n:" to allow after a bracket, a new line, and a colon (for consecutive shortcodes). This opens up the ability to tailor for individual workflow, or be ignored in favor of the more user friendly options listed above.
The text was updated successfully, but these errors were encountered:
I have "Trigger with trailing space" turned on, but I can not trigger at the start of a new line. This makes logical sense given the wording, but does not make sense with a typical workflow: there is a whitespace separation from the previous content, which is more in line with the conceptual intent of this feature, At least in my mind; opinions certainly would vary, which leads to two different proposals, one appealing to a conceptual fix and one to a more programmer/technically minded use case:
In a simple solution, a grouped option (that is disabled until the above option is turned on) that reads: "Allow at start of line" would be helpful.
As an advanced solution: "Allow after the following characters" would allow something like "]\n:" to allow after a bracket, a new line, and a colon (for consecutive shortcodes). This opens up the ability to tailor for individual workflow, or be ignored in favor of the more user friendly options listed above.
The text was updated successfully, but these errors were encountered: