Alberto De Lucca adeluccar

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.

Prerequisities

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

Using git-submodules to version-control Vim plugins

If you work across many computers (and even otherwise!), it's a good idea to keep a copy of your setup on the cloud, preferably in a git repository, and clone it on another machine when you need. Thus, you should keep the .vim directory along with your .vimrc version-controlled.

But when you have plugins installed inside .vim/bundle (if you use pathogen), or inside .vim/pack (if you use Vim 8's packages), keeping a copy where you want to be able to update the plugins (individual git repositories), as well as your vim-configuration as a whole, requires you to use git submodules.

Creating the repository

Initialize a git repository inside your .vim directory, add everything (including the vimrc), commit and push to a GitHub/BitBucket/GitLab repository:

cd ~/.vim

Creating your own ag.vim

Vim provides built-in mechanisms to search through projects in the form of the grep command. However, on large projects, grep is known to be slow; and hence people have been switching to simpler searchers like ack, and faster, parallel (metal?) searchers like ag and pt. Correspondingly, several plugins have been created that integrate these tools in vim: ack.vim, ag.vim, etc.

However, it's actually very easy to get the functionalities these plugins provide (faster search, results in quickfix-window, jumps, previews, and so on) in vanilla Vim itself; in fact, Vim already populates the grep-search results in a quickfix window. We just need to tell Vim to do the following things (use-case: ag):

Use ag as the default grep program
Open quickfix window by default
Create mappin

	@font-face {
	font-family: junicode;
	src: url('_junicode.ttf');
	}
	.card, table {
	font-family: Helvetica, sans-serif, junicode;
	font-size: 20px;
	text-align: center;
	color: #d03030;
	background-color: #fafaf5;

	# Credit to http://www.iarp.ca/hobby/computing/36-git-committed-and-pushed-to-the-incorrect-branch

	# Ensure you're in the branch that you commited to by accident.
	git checkout master

	# Reset the branch back one commit.
	git reset --soft HEAD^

	# Stash the changes
	git stash

	#!/usr/bin/env ruby
	# Remove all gems EXCEPT defaults :)

	`gem list -d`.split(/\n\n^(?=\w)/).each do \|data\|
	match = data.match(/(?<name>([^\s]+)) \((?<versions>.*)\)/)
	name = match[:name]
	versions = match[:versions].split(', ')

	if match = data.match(/^.\(([\d\.]),? ?default\): .*$/)
	next if match[1].empty? # it's the only version if this match is empty

	#!/usr/bin/env bash

	(set -x; brew update;)

	(set -x; brew cleanup;)
	(set -x; brew cask cleanup;)

	red=`tput setaf 1`
	green=`tput setaf 2`
	reset=`tput sgr0`

	#!/bin/bash -e

	# Ideas, Drawbacks, and Suggestions: https://davidlaietta.com/bash-scripting-to-automate-site-builds-with-wp-cli/

	# Set up some defaults
	wpuser='USERNAME'
	email='[email protected]'
	blueprint='BLUEPRINT-NAME'

	clear

	#!/bin/bash -e
	clear
	echo "============================================"
	echo "WordPress Install Script"
	echo "============================================"
	echo "Database Name: "
	read -e dbname
	echo "Database User: "
	read -e dbuser
	echo "Database Password: "