-
Notifications
You must be signed in to change notification settings - Fork 20
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
The very basics of the Documentation sucks #5
Comments
While I agree there is assumed knowledge (since the JSON format is standard for prefs in ST2/3) with the instructions of configuring the preferences file, the issue title isn't going to get anyone hustling to fix it. |
Added configuration file example to Readme.md per issue spadgos#5
I'm shocked that a user who able to file an issue on github doesn't know ST2/3 use JSON format for almost all the ST2/3 configuration files. I think you really should RTFM for SublimeText to understand how powerful editor is. |
I'm not sure what relevance someone's ability to use GitHub has in regards to magically already having in-depth knowledge of what formatting/extension types a particular program uses, so please try to keep your comments relevant. On topic, since this particular issue is relevant to mine, are there any known quirks with this plugin? I've created the default files, filled the formatting out correctly, and can't seem to make it change the default file type. The plugin itself does work, because files are now default-opening into Java, but the rather large project I'm working on currently is html, and for the life of me I can not figure out why it's not taking the new configs. (ST2, don't particularly like ST3) meh I'll just make a new one. |
If someone is able to use GitHub issue to complain README sucks, then why he didn't read SublimeText's Manual? I reply so, because the answer is already in ST's manual. Almost every config file in ST use same JSON format. He really need to read the manual of ST. reply to leeber, |
being a non programmer, tho i like to hack around other folks scripts, i agree with OP, not flaming, just saying, thanks for this superb editor. |
Perhaps you should make it obvious atleast SOMEWHERE that the settings need to be formatted like this:
and not like this:
and also, not like this:
You could even include an example settings file!
The text was updated successfully, but these errors were encountered: