Use without caution
while :; do echo "I will kill you later" | say -v Whisper; sleep 50; done &| # Mounts FTP server | |
| open -a Finder ftp://login:password@ftp_host/path | |
| # Rsync from there (add --dry-run option to simulate transfer) | |
| rsync -arvz --no-o --no-g /Volumes/ftp_host/path/ ./ | |
| # WIN! |
| { | |
| "dbHost": "localhost", | |
| "dbUser": "root", | |
| "dbPass": "root", | |
| "git": true, | |
| "installTheme": true, | |
| "themeDir": "mkt-virtual-theme", | |
| "themeType": "git", | |
| "themeUser": "mktvirtual", | |
| "themeRepo": "mkt-virtual-theme", |
| # Run it in the root of your wordpress project | |
| # Create .zip from project, without node_modules and bower_components | |
| projectname=${PWD##*/}; zip -x '*.git*' -x 'wp-content/uploads*' -x '*node_modules*' -x '*bower_components*' -r $projectname.zip . |
Use without caution
while :; do echo "I will kill you later" | say -v Whisper; sleep 50; done &Serviços bem simples baseados em API públicas que tenham como objetivo facilitar a vida na cidade.
Algumas ideias do que é possível fazer:
| { | |
| "caret_extra_width": 2, | |
| "caret_style": "phase", | |
| "color_scheme": "Packages/User/base16-ocean.dark (SL).tmTheme", | |
| "dictionary": "Packages/Dictionaries/Portuguese (Brazilian).dic", | |
| "ensure_newline_at_eof_on_save": true, | |
| "folder_exclude_patterns": | |
| [ | |
| ".svn", | |
| ".git", |
Source: https://crashingdaily.wordpress.com/2008/03/06/diff-two-stdout-streams/
You can diff two commands stdout without creating two files. <( ... ) command creates a temporary file with the stdout of the command inside it.
Example:
diff -B <( ls -1 / ) <( ls -1 ~ )| (ns ^:figwheel-always om-tut.core | |
| (:require-macros [cljs.core.async.macros :refer [go]]) | |
| (:require [om.core :as om :include-macros true] | |
| [om.dom :as dom :include-macros true] | |
| [cljs.core.async :refer [put! chan <!]] | |
| [clojure.data :as data] | |
| [clojure.string :as string])) | |
| (enable-console-print!) |
CSS Wizardry recently wrote a great post about styling: Contextual Styling: UI Components, Nesting, and Implementation Detail. He showed three ways to solve the problem of implementation details in a component's styles. I want to propose another way to solve this problem, one that uses composition.
The original styles of a .nav-primary component are:
.nav-primary {
/* This is how the nav should always look: */
margin: 0;| node -e "require('repl').start({ignoreUndefined: true})" |