Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML entities with markdown and automatically publishing gists when edited #27

Closed
f97-26082023 opened this issue May 6, 2023 · 3 comments · Fixed by #29
Closed

HTML entities with markdown and automatically publishing gists when edited #27

f97-26082023 opened this issue May 6, 2023 · 3 comments · Fixed by #29

Comments

@f97-26082023
Copy link

Hi @thomiceli, I love opengist! However, I have some issues:

  • Markdown code tag will show HTML entities
cat /dev/null > /etc/profile.d/linux-login.sh && touch ~/.hushlogin

image

Expected result: The code will display correctly, same as on GitHub

  • With Unlisted gists, after I save changes, they are automatically published

Expected result: With Unlisted gists, saving changes will not automatically publish them.

Thanks ❤️

@thomiceli
Copy link
Owner

Hi and thank you :)

For your second issue I'm not sure to follow, what do you mean by changes published ? Changes committed to the git repository ?

@f97-26082023
Copy link
Author

For your second issue I'm not sure to follow, what do you mean by changes published ? Changes committed to the git repository ?

I changed them from web GUI.

@thomiceli
Copy link
Owner

For your second issue I'm not sure to follow, what do you mean by changes published ? Changes committed to the git repository ?

I changed them from web GUI.

Unlisted gists just means you have to get the url to access them, they are not "public". Now when you make changes from the web GUI there is no such concept like a draft, they are committed directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants