Skip to content

Instantly share code, notes, and snippets.

View tisseurdetoile's full-sized avatar
🏠
confiné

tisseurdetoile tisseurdetoile

🏠
confiné
View GitHub Profile
#
# Example of a user's .screenrc file
#
# This is how one can set a reattach password:
# password ODSJQf.4IJN7E # "1234"
# no annoying audible bell, please
vbell on
"Set Mapleader
let mapleader = ","
let g:mapleader = ","
"Theme
colo zenburn
"NERDTree
map <Leader>, :NERDTreeToggle<cr>
#!/bin/sh
# btsync service
# Replace with linux users you want to run BTSync clients for
BTSYNC_USERS="mendel"
DAEMON=/usr/bin/btsync
start() {
for btsuser in $BTSYNC_USERS; do
HOMEDIR=`getent passwd $btsuser | cut -d: -f6`
config=$HOMEDIR/.sync/config.json
@tisseurdetoile
tisseurdetoile / vimdiff.md
Created October 24, 2017 12:39 — forked from mattratleph/vimdiff.md
vimdiff cheat sheet

vimdiff cheat sheet

##git mergetool

In the middle file (future merged file), you can navigate between conflicts with ]c and [c.

Choose which version you want to keep with :diffget //2 or :diffget //3 (the //2 and //3 are unique identifiers for the target/master copy and the merge/branch copy file names).

:diffupdate (to remove leftover spacing issues)

:only (once you’re done reviewing all conflicts, this shows only the middle/merged file)

@tisseurdetoile
tisseurdetoile / README-Template.md
Created January 23, 2018 01:05 — forked from PurpleBooth/README-Template.md
A template to make good README.md

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Pull Request Process

  1. Ensure any install or build dependencies are removed before the end of the layer when doing a
@tisseurdetoile
tisseurdetoile / readme.md
Created March 9, 2018 09:33 — forked from mattliuoz/readme.md
User_story

EPIC = Group of user stories
RMP = Rate My Photographer
Vister is a user doesn’t have login to RMP website

EPIC - Vister

  • As a visiter,
    when I visit RMP homepage,
    then I should be able to see: -Top 5 photographers in a list -Newest added 5 photographers in a list
@tisseurdetoile
tisseurdetoile / .git-commit-template-simple.txt
Created May 26, 2018 16:02 — forked from adeekshith/.git-commit-template.txt
This commit message template helps you write great commit messages and enforce it across teams.
# S'il est appliqué ce chagement fera...
# Expliquer pourquoi ce changement est intervenue ?
Avant ce changement,
# Comment cela regle le problème ?
Ce changement
# Fournir les liens et les ids de tous les tickets, articles ressources utiles
@tisseurdetoile
tisseurdetoile / hsqldb.cmd
Created May 31, 2018 13:11 — forked from kdabir/hsqldb.cmd
Windows cmd script to run HSQLDB server and client GUI
@echo off
REM set these variables
SET HSQLDB_HOME=c:\path\to\hsqldb
SET DB_NAME=mydb
REM start the server in new window ( prompt visible, so that you can CTRL+C )
REM database files are created in current directory/data
start java -cp %HSQLDB_HOME%\lib\hsqldb.jar org.hsqldb.server.Server --database.0 file:data/%DB_NAME% --dbname.0 %DB_NAME%
REM start the client GUI and connect to server ( no new cmd window opens because of javaw )
@tisseurdetoile
tisseurdetoile / .git-commit-template
Last active May 26, 2020 19:34 — forked from zakkak/.git-commit-template
This commit message template that helps you write great commit messages and enforce it across your team.
# <type(scope)> (Si appliqué, ce commit fera...) <sujet> (Max 72 char)
# |<---- C'est mieux en 50 charactères --->|<------------------->|
# Exemples:
# feat: automatisation des messages de commits
# feat(commit): automatisation des messages
# (Optionnel) Expliquer pourquoi ce changement est fait
# |<---- Essayer de vous limiter à un maximum de 72 characteres ---->|
# (Optionnel) Fournissez les liens/référence vers les tickets et autres resources