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
Using this snippet as an example: "<ul>\n<li>$|$</li>\n</ul>"
When I add double quotes in the replace field in espanso-gui, it prints the quotes and the escape characters literally.
When I add the quotes directly in the config file, the snippet is printed as expected:
<ul>
<li></li>
</ul>
The text was updated successfully, but these errors were encountered:
Having added the string via the GUI, how does it appear in the .yml file?
The output you're describing suggests you'll see the replace: value has single, or no quotes.
How would espanso-gui know you're not wanting the literal string?
I've attached a couple of screenshots.
When I add a new item with double quotes in the GUI it looks like this:
And in the config file it looks like this; it has single quotes around the code:
If I go and edit the config file, remove the single quotes and save, the GUI respects the change, and shows the item as follows:
The line feeds are not shown in the GUI, but it doesn't touch the replace value.
This is fine, and is working as expected/designed.
To answer your second question: espanso-gui can't know the intentions of the user, but perhaps you can add a checkbox labeled "Escape chars" (or similar) that indicates that the user wants to maintain the double quotes as-is.
Hi there,
I have a couple of snippets that include escape characters, such as \n and \t. According to the espanso docs: "Note that strings using \n as the line terminator character, or \t for tab-spacing, or beginning with a YAML special character [...], must be quoted.".
Using this snippet as an example: "
<ul>\n<li>$|$</li>\n</ul>
"When I add double quotes in the replace field in espanso-gui, it prints the quotes and the escape characters literally.
When I add the quotes directly in the config file, the snippet is printed as expected:
The text was updated successfully, but these errors were encountered: