Things your website should clearly state / make accessible:
- The core focus of your conf
- Your core values
- The (precise) location
- The dates
- Your programme, complete with speakers and their bios/pics
# Put this in your ~/.gitconfig or ~/.config/git/config | |
# Windows users: "~" is your profile's home directory, e.g. C:\Users\<YourName> | |
[user] | |
name = Your Full Name | |
email = your@email.tld | |
[color] | |
# Enable colors in color-supporting terminals | |
ui = auto | |
[alias] | |
# List available aliases |
# STEP 1: ENSURE COMPLETION AND PROMPT FUNCTION ARE LOADED | |
# ======================================================== | |
# OPTION 1: If on OSX using Homebrew: | |
# | |
# source $(brew --prefix)/etc/bash_completion.d/git-prompt.sh | |
# source $(brew --prefix)/etc/bash_completion.d/git-completion.bash | |
# OPTION 2: If on OSX using built-in Git (also works on ZSH): | |
# |
// Assumes http://brian.io/lawnchair/ and http://backbonejs.org/ | |
var collection = new MyCollection(); | |
var localStore = new Lawnchair({ name: 'my-cache' }, $.noop); | |
// First load from the cache, then fetch | |
function initialLoad() { | |
localStore.all(function(items) { | |
collection.reset(items, function() { | |
collection.fetch(); |
Function.prototype.throttle = function(/* … */) { | |
var f = this; | |
// … | |
return function() { | |
// … | |
return f.apply(this, arguments); | |
}; | |
}; |
Pour le LULZ ce soir, je teste le site marchand de la filiale FR d'une grande enseigne internationale. J'ai été tellement ébahi par le degré de fail que je me suis senti obligé de faire un compte-rendu, un tweet n'aurait pas rendu justice à un tel niveau de moisitude…
"ensure_newline_at_eof_on_save": true, | |
"tab_size": 2, | |
"translate_tabs_to_spaces": true, | |
"trim_trailing_white_space_on_save": true, |
Par exemple pour être à l'aise avant un JS Total ou un Node.js.
On parle ici du langage pur dans ses versions « traditionnelles » (ES3/ES5).
Le cours JavaScript de Codecademy (hors "Objects I/II") : http://www.codecademy.com/fr/tracks/javascript
Le guide JavaScript du MDN : https://developer.mozilla.org/fr/docs/JavaScript/Guide
export PS1='\[\e[0;36m\][\A] \u@\h:\[\e[0m\e[0;32m\]\W\[\e[1;33m\]$(__git_ps1 " (%s)")\[\e[0;37m\] \$\[\e[0m\]' |
We extract our test repos from this small Zip file.
main
is a "container" repository with its working copy,plugin
is a "shared" repository with its working copy,remotes
emulates remote bare repos for both, to better resemble regular usage.The idea is to use plugin
as a subtree of main
in a vendor/plugins/demo
path, and allow maintenance both ways: