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
Based on previous experience, I would strongly suggest changing your repo's name to something like logcat-sublime. The problem with naming it with an extension that's used by Sublime (.tmLanguage, .tmTheme, etc.) is that some versions of Sublime may process the directory name, thinking it's a file name, and mess things up internally.
When I first started work on Neon, I named the repo Neon.tmTheme, and only later learned about the issues some users were having, so I changed the name to Neon-color-scheme (Github will still follow links to the old repo name, no problem), and in Package Control changed the name of the package (and hence the directory it's installed in) to Neon Color Scheme, which it's been ever since. If/when you ever submit this to Package Control (it's actually a very easy process, only taking a couple of days, max), you can name the package simply Logcat if you wish.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion.
I intended to start a new repo for uploading to Package Control as I wanted to keep the log and screenshot away from it (possibly by putting them in gh-pages branch).
I'll keep this in mind when I start the work.
Based on previous experience, I would strongly suggest changing your repo's name to something like
logcat-sublime
. The problem with naming it with an extension that's used by Sublime (.tmLanguage
,.tmTheme
, etc.) is that some versions of Sublime may process the directory name, thinking it's a file name, and mess things up internally.When I first started work on Neon, I named the repo
Neon.tmTheme
, and only later learned about the issues some users were having, so I changed the name toNeon-color-scheme
(Github will still follow links to the old repo name, no problem), and in Package Control changed the name of the package (and hence the directory it's installed in) toNeon Color Scheme
, which it's been ever since. If/when you ever submit this to Package Control (it's actually a very easy process, only taking a couple of days, max), you can name the package simplyLogcat
if you wish.The text was updated successfully, but these errors were encountered: