Created
November 9, 2013 19:25
-
-
Save poseidonrage/7388854 to your computer and use it in GitHub Desktop.
detect internet explorer
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Package Control Messages | |
======================== | |
Emmet: | |
----- | |
Thank you for installing Emmet -- a toolkit that can greatly improve your workflow. Note that this plugin automatically downloads and installs PyV8 binary (see status bar message). | |
****************************** | |
Please restart editor | |
to finish installation process | |
after PyV8 was downloaded. | |
****************************** | |
Tab key handler | |
========================== | |
By default, Emmet allows you to expand abbreviations with Tab key in HTML, XML, HAML and CSS/SASS/LESS/Stylus documents. As a side effect, you can’t use some of your ST2 snippets. | |
Please read https://github.com/sergeche/emmet-sublime#tab-key-handler about how Tab handler works and how to tweak its behavior to match your needs. | |
Enter key | |
========================== | |
In HTML and XML documents, Emmet overrides Enter key to insert formatted line breaks between opening and closing tags. In some cases it will break character input (for example, in Japanese language). | |
To disable Enter key handler, simply add the following option in your user's Preferences file: | |
"disable_formatted_linebreak": true | |
Actions shortcuts | |
========================== | |
Emmet has a number of actions with keyboard shortcuts that may override ones you're using commonly (for example, Ctrl-E or Ctrl-Down). Please read the project main page to get list of available actions and keyboard shortcuts and how to disable them: | |
https://github.com/sergeche/emmet-sublime | |
Documentation and examples: | |
http://emmet.io | |
------------------------------ | |
Follow me on Twitter: @emmetio | |
------------------------------ | |
AdvancedNewFile: | |
--------------- | |
Thank you for installing the AdvancedNewFile plugin. | |
For more information please visit https://github.com/skuroda/Sublime-AdvancedNewFile. | |
Note you may need to restart Sublime Text after installing this plugin. | |
If you have any questions, comments, or run into issues, please let me know! Hope you enjoy the plugin. | |
Thank you! | |
SublimeLinter: | |
------------- | |
SublimeLinter | |
============= | |
SublimeLinter is a plugin that supports "lint" programs (known as "linters"). SublimeLinter highlights | |
lines of code the linter deems to contain (potential) errors. It also | |
supports highlighting special annotations (for example: TODO) so that they | |
can be quickly located. | |
SublimeLinter has built in linters for the following languages: | |
* C/C++ - lint via `cppcheck` | |
* CoffeeScript - lint via `coffee -s -l` | |
* CSS - lint via built-in [csslint](http://csslint.net) | |
* Git Commit Messages - lint via built-in module based on [A Note About Git Commit Messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). | |
* Haml - syntax check via `haml -c` | |
* HTML - lint via `tidy` (actually [tidy for HTML5](http://w3c.github.com/tidy-html5/)) | |
* Java - lint via `javac -Xlint` | |
* JavaScript - lint via built in [jshint](http://jshint.org), [jslint](http://jslint.com), or the [closure linter (gjslint)](https://developers.google.com/closure/utilities/docs/linter_howto) (if installed) | |
* Lua - syntax check via `luac` | |
* Objective-J - lint via built-in [capp_lint](https://github.com/aparajita/capp_lint) | |
* Perl - lint via [Perl:Critic](http://perlcritic.com/) or syntax+deprecation check via `perl -c` | |
* PHP - syntax check via `php -l` | |
* Puppet - syntax check via `puppet parser validate` | |
* Python - native, moderately-complete lint | |
* Ruby - syntax check via `ruby -wc` | |
* XML - lint via `xmllint` | |
For more information: | |
--------------------- | |
Please take the time to read the documentation: | |
* Online - https://github.com/SublimeLinter/SublimeLinter | |
* Sublime Text - Select Preferences->Package Settings->SublimeLinter->README | |
IMPORTANT | |
Do NOT edit the default SublimeLinter settings. Your changes will be lost | |
when SublimeLinter is updated. ALWAYS edit the user SublimeLinter settings | |
by selecting "Preferences->Package Settings->SublimeLinter->Settings - User". | |
Note that individual settings you include in your user settings will **completely** | |
replace the corresponding default setting, so you must provide that setting in its entirety. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment