Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title>Simple Image Slider</title> | |
| <style> | |
| .gallery { position: relative; width: 400px; height: 200px; } | |
| .gallery figure { | |
| top: 0; | |
| left: 0; |
| $(".event").each(function() { | |
| // get the ID of the event element | |
| var the_date = $(this).attr("id"); | |
| // find the tabel cell with that same ID and append the div | |
| $(this).clone().appendTo('.calendar td#' + the_date); | |
| }); |
JavaScript Code
var str = "hi";Memory allocation:
| Address | Value | Description |
|---|---|---|
...... |
... |
| title: Fieldset Kitchen Sink | |
| fields: | |
| status: | |
| type: status | |
| _template: | |
| type: templates |
Revised date: 07/11/2012
Between us [company name] and you [customer name]
We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.
| <div id="payment-errors"> | |
| {{ bison:checkout_form_errors }} | |
| {{ if missing }} | |
| <p>You are missing the following fields.</p> | |
| <ul> | |
| {{ missing }} | |
| <li>The {{ field_label }} field {{ message }}</li> | |
| {{ /missing }} | |
| </ul> | |
| {{ endif }} |
Here are a few common tasks you might do in your templates, as they would be written in ExpressionEngine vs. Craft CMS.
| module.exports = function(grunt) { | |
| grunt.initConfig({ | |
| concat: { | |
| // js stuff | |
| }, | |
| uglify: { | |
| // more js stuff |