[LANG] Missing shell, bash, zsh, tsh, etc As Valid Potential New Gists -- Why Define Language First?

[zudsniper]

⚠ Summary

This editor seems very well-implemented, but I was unfortunately immediately stopped from making use of it by the fact that the language (I'm assuming for LSP reasons) is selected before creation of the actual gist file(s). Due to the fact that shell & bash -- as well as other system shells -- are not included in the supported language list, I was unable to use the site to create the gist that I intended to.

💡 Proposed Solution

^{may or may not work or be easy to implement... YMMV}

Don't Assign A Language to a gist Strictly!

Apologies if that reads harshly, but I think that your editor is very cool and has a lot of potential, and I feel it is a shame to miss out on this due to this relatively small issue.
My suggestion to fix the problem is to simply do as github does currently with the (sort of very bad) web gist editor: **determine the language of a file within a gist based on the file extension of that file. This would also handle multi-language gists, which certainly exist[^1].

Again I do want to say -- very cool little editor. I will be looking forward to a fix for this, and would attempt one myself if time permitted. But it never seems to.

Good luck & good day to you.

[^1]: not sure why they aren't repos, but there are probably valid reasons...

[zudsniper]

Wow, I didn't realize you were so prolific! those contributions...
very impressive. Thank you for keeping the web running smoothly C: