| .gform_wrapper ul { | |
| padding-left: 0; | |
| list-style: none; } | |
| .gform_wrapper li { | |
| margin-bottom: 15px; } | |
| .gform_wrapper form { | |
| margin-bottom: 0; } |
import urllib2,os; pf='Package Control.sublime-package'; ipp = sublime.installed_packages_path(); os.makedirs( ipp ) if not os.path.exists(ipp) else None; urllib2.install_opener( urllib2.build_opener( urllib2.ProxyHandler( ))); open( os.path.join( ipp, pf), 'wb' ).write( urllib2.urlopen( 'http://sublime.wbond.net/' +pf.replace( ' ','%20' )).read()); print( 'Please restart Sublime Text to finish installation')
From here on out, use Package Control to install everything. ⌘+Shift+P, then type Install to get a list of installable packages you can 'livesearch through. After installing plugins, they should be running.
mix3d asked for some help using this guide with windows so here we go. This was tested with Windows 10. Run all commands in Git Bash once it's installed.
Github will be the main account and bitbucket the secondary.
| alias nginx.start='sudo launchctl load /Library/LaunchDaemons/homebrew.mxcl.nginx.plist' | |
| alias nginx.stop='sudo launchctl unload /Library/LaunchDaemons/homebrew.mxcl.nginx.plist' | |
| alias nginx.restart='nginx.stop && nginx.start' | |
| alias php-fpm.start="launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.php56.plist" | |
| alias php-fpm.stop="launchctl unload -w ~/Library/LaunchAgents/homebrew.mxcl.php56.plist" | |
| alias php-fpm.restart='php-fpm.stop && php-fpm.start' | |
| alias mysql.start="launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist" | |
| alias mysql.stop="launchctl unload -w ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist" | |
| alias mysql.restart='mysql.stop && mysql.start' | |
| alias nginx.logs.error='tail -250f /usr/local/etc/nginx/logs/error.log' |
#Error management in gulp
Sucking at something is the first step to becoming sorta good at something
No one can assure you, that plugins will run smooth in any circumstances (except for tests - they could), so neither should you convince anyone, that your plugin will never break. Only thing, that you could possibly do (if something gone wrong) - is gracefully inform your plugin user, that something went wrong and die.
We are will use this plugin from beginning to demonstrate error management. Suppose you have a task in gulpfile.js that contains this code (we modified it a little bit to be closer to real-usage):
var coffee = require('gulp-coffee');
| <?php | |
| //* Do NOT include the opening php tag | |
| //* Remove the link 'SEO' from admin bar. It's placed there by the plugin WordPress SEO by Yoast. | |
| add_action( 'wp_before_admin_bar_render', 'wlwp_admin_bar' ); | |
| function wlwp_admin_bar(){ | |
| global $wp_admin_bar; | |
| $wp_admin_bar->remove_menu('wpseo-menu'); | |
| } |
| <html> | |
| <head> | |
| <style type="text/css"> | |
| table table { | |
| width: 600px !important; | |
| } | |
| table div + div { /* main content */ | |
| width: 65%; | |
| float: left; | |
| } |
| # WORDPRESS WP Query Taxonomy and Meta query | |
| This shows the two alternate methods to running taxonomy and post meta paramaters within WP Query. | |
| * Shorthand version only accepts one postmeta key | |
| * Longhand version is the full method and has much more flexiblity for complex queries |