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
And sometimes, characters in the file name are prohibiting the bash script from executing. Spaces in the name caused this issue. I believe numbers also were a problem. I am not exactly sure.
The temporary solution I came up with is to use lookalike Unicode characters. However, this causes another issue, as the API cannot interpret the characters to mean what they are supposed to mean, and the coloring is ruined.
Therefore, I am currently left with a script that succeeds 50% of the time yet still produces wrong previews.
The specific characters that causes issues for me are:
{
}
"
'
(
)
/
If I had found all of the characters, my script would be executing with a higher successful rate. As I am not educated about using bash, I was unable to identify the additional characters that were causing issues.
In addition, as I am reading the content of my code, the actual typed out newlines '\n' are getting mixed up with the interpreted newlines (actually pressing enter).
The text was updated successfully, but these errors were encountered:
I am reading the content of my code files and storing it inside a variable. Then, I am using the variable inside the bash script to create a preview with the code.
However, as I am manually executing the bash script from inside of my script, specific characters included in my code files are hindering the bash script to execute/complete. This is resulting in corrupted, unopenable .png files.
And sometimes, characters in the file name are prohibiting the bash script from executing. Spaces in the name caused this issue. I believe numbers also were a problem. I am not exactly sure.
The temporary solution I came up with is to use lookalike Unicode characters. However, this causes another issue, as the API cannot interpret the characters to mean what they are supposed to mean, and the coloring is ruined.
Therefore, I am currently left with a script that succeeds 50% of the time yet still produces wrong previews.
The specific characters that causes issues for me are:
If I had found all of the characters, my script would be executing with a higher successful rate. As I am not educated about using bash, I was unable to identify the additional characters that were causing issues.
In addition, as I am reading the content of my code, the actual typed out newlines '
\n
' are getting mixed up with the interpreted newlines (actually pressing enter).The text was updated successfully, but these errors were encountered: