| # 0 is too far from ` ;) | |
| set -g base-index 1 | |
| # Automatically set window title | |
| set-window-option -g automatic-rename on | |
| set-option -g set-titles on | |
| #set -g default-terminal screen-256color | |
| set -g status-keys vi | |
| set -g history-limit 10000 |
(The below text is licensed with CC0, which means that if you want to use or translate it, that is OK by me.)
Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺
Locally, I'm at this commit:
$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <jnthn@jnthn.net>
Date: Sun Apr 15 16:35:03 2012 +0200
| \ProvidesFile{absender.lco} | |
| \KOMAoptions{% | |
| % fromemail=true, % Email wird im Briefkopf angezeigt | |
| % fromphone=true, % Telefonnumer wird im Briefkopf angezeigt | |
| % fromfax=true, % Faxnummer wird im Briefkopf angezeit | |
| % fromurl=true, % URL wird im Briefkopf angezeigt | |
| % fromlogo=true, % Logo wird im Briefkopf angezeigt | |
| % subject=titled, % Druckt "Betrifft: " vor dem Betreff | |
| locfield=wide, % Breite Absenderergänzung (location) |
Most of programs will not accept an email using just @localhost as domain.
So, edit /etc/hosts file to make the domain localhost.com point to your machine, including this content to the file:
127.0.0.1 localhost.com
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
| $ ffmpeg -i input.mp4 -vcodec h264 -acodec mp2 output.mp4 |
| /* | |
| Simple HTTP proxy in Rust. Hard coded to proxy rust-lang.org. | |
| */ | |
| extern crate hyper; | |
| use std::io::Read; | |
| use hyper::Client; | |
| use hyper::header::Connection; |
| Links: | |
| A Visual Introduction to Machine Learning | |
| http://www.r2d3.us/visual-intro-to-machine-learning-part-1/ | |
| UC Berkeley CS188 Intro to AI -- Course Materials | |
| http://ai.berkeley.edu/home.html | |
| Eyeo 2016 – Gene Kogan | |
| https://vimeo.com/180044029 |
