Create a git repo directly in your home folder, .g. ~/dotfiles
In this directory, you create a folder with a "package name" and in it the exact folder structure this app has it's config files in your home folder.
Let's take i3 for example, which has its config file in ~/.config/i3/config
Move this file into ~/dotfiles/i3/.config/i3/config. Now you can git add and git commit it, like usual.
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
#Quick Guide
sudo atsutil databases -remove
atsutil server -shutdown
atsutil server -ping
#Extended Guide from http://doc.extensis.com/Font-Management-in-OSX-Best-Practices-Guide.pdf
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
| /* Compile with: g++ -Wall –Werror -o shell shell.c */ | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <string.h> | |
| #include <ctype.h> | |
| #include <unistd.h> | |
| #include <sys/types.h> | |
| #include <sys/wait.h> |
| /** | |
| * @file fsm.c | |
| * @brief an implementation for a FSM in C, this file contains | |
| * implementation of definations. | |
| * License GPLv3+ | |
| * @author Ankur Shrivastava | |
| */ | |
| #include "fsm.h" | |
| #include<stdlib.h> |
