| 😄 | 😆 | 😊 | 😃 |
😩 | 😔 | 😞 | 😖 | 😨 | 😰 | 😣 | 😢 | 😭 | 😂 | 😲 | 😱 |
| 😫 | 😠 | 😡 | 😤 | 😪 | 😋 | 😷
😎 | 😵 | 👿 | 😈 | 😐 | 😶 | 😇 | 👽 | 💛 | 💙 | 💜 | ❤️ | 💚 | 💔 | 💓 | 💗 | 💕 | 💞 | 💘 | ✨
| /* | |
| * twitter-entities.js | |
| * This function converts a tweet with "entity" metadata | |
| * from plain text to linkified HTML. | |
| * | |
| * See the documentation here: http://dev.twitter.com/pages/tweet_entities | |
| * Basically, add ?include_entities=true to your timeline call | |
| * | |
| * Copyright 2010, Wade Simmons | |
| * Licensed under the MIT license |
| 😄 | 😆 | 😊 | 😃 |
😩 | 😔 | 😞 | 😖 | 😨 | 😰 | 😣 | 😢 | 😭 | 😂 | 😲 | 😱 |
| 😫 | 😠 | 😡 | 😤 | 😪 | 😋 | 😷
😎 | 😵 | 👿 | 😈 | 😐 | 😶 | 😇 | 👽 | 💛 | 💙 | 💜 | ❤️ | 💚 | 💔 | 💓 | 💗 | 💕 | 💞 | 💘 | ✨
| /* | |
| In the node.js intro tutorial (http://nodejs.org/), they show a basic tcp | |
| server, but for some reason omit a client connecting to it. I added an | |
| example at the bottom. | |
| Save the following server in example.js: | |
| */ | |
| var net = require('net'); |
| var path = require('path'); | |
| var _invalidateRequireCacheForFile = function(filePath){ | |
| delete require.cache[path.resolve(filePath)]; | |
| }; | |
| var requireNoCache = function(filePath){ | |
| _invalidateRequireCacheForFile(filePath); | |
| return require(filePath); | |
| }; |
| Step 1. Install homebrew from here: http://brew.sh | |
| Step 1.1. Run export PATH=/usr/local/bin:$PATH | |
| Step 2. Run brew update | |
| Step 3. Run brew install vim && brew install macvim | |
| Step 4. Run brew link macvim | |
| # http://stackoverflow.com/questions/21012203/gvim-or-macvim-in-mac-os-x/21012284#21012284 | |
| Adv: | |
| - copy & paste between tabs |
| #lang racket | |
| (require racket/gui) | |
| ; | |
| ; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
| ; I wrote this code five years ago while learning functional programming. | |
| ; It is an example of what you should NOT do in a functional language (or in software writing in general). | |
| ; | |
| ; THIS IS NOT A GOOD EXAMPLE OF RACKET CODE. | |
| ; |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParentThis is unmaintained, please visit Ben-PH/spacemacs-cheatsheet
SPC q q - quitSPC w / - split window verticallySPC w - - split window horizontallySPC 1 - switch to window 1SPC 2 - switch to window 2SPC w c - delete current window