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
if a line in a bash code snippet is not started with $ (so the javascript adds the $), the command export GH_TOKEN=github_path_11AAPO<snip> will have the space between the export and GH removed. If the post explicitly includes the $ in front of the command, it works as expected.
if a bash code snippet is multi-line and uses the \ at the end of the line, the js code will add a $ to each line but it is all part of the same command. The more I've thought about this, I wonder if there will be so many edge cases with pre-pending the $ that we might want to just remove that. Either the post add the $ explicitly or it's not present? For long commands, I like how Huge Clarity handles it with the ability to "Toggle line wrap". Thoughts?
would like to experiment with making the webpage take up the entire browser space as a lot of the code snippets have scrollbars now which is aesthetically annoying, imo. :-)
If you are able to add the Matomo support you have at a config.toml level like in Hugo Clarity, I won't have to override to add the js in layouts/_default/baseof.html (that's just a nice to have!)
The text was updated successfully, but these errors were encountered:
There are minor items I noticed:
export GH_TOKEN=github_path_11AAPO<snip>
will have the space between the export and GH removed. If the post explicitly includes the $ in front of the command, it works as expected.\
at the end of the line, the js code will add a $ to each line but it is all part of the same command. The more I've thought about this, I wonder if there will be so many edge cases with pre-pending the $ that we might want to just remove that. Either the post add the $ explicitly or it's not present? For long commands, I like how Huge Clarity handles it with the ability to "Toggle line wrap". Thoughts?The text was updated successfully, but these errors were encountered: