Skip to content

Instantly share code, notes, and snippets.

Last active October 3, 2023 12:53
Show Gist options
  • Save davidpustai/9282314 to your computer and use it in GitHub Desktop.
Save davidpustai/9282314 to your computer and use it in GitHub Desktop.
My workflow dotfiles
My workflow dotfiles
### Aliases
# Enable aliases to be sudo’ed
alias sudo='sudo '
# Git
# You must install Git first - ""
alias g='git status'
alias ga='git add .'
alias gd='git diff'
alias gc='git commit -m' # requires you to type a commit message
alias gca='git commit -am' # requires you to type a commit message
alias gp='git push'
### Prompt Colors
# Modified version of @gf3’s Sexy Bash Prompt
# (
if [[ $COLORTERM = gnome-* && $TERM = xterm ]] && infocmp gnome-256color >/dev/null 2>&1; then
export TERM=gnome-256color
elif infocmp xterm-256color >/dev/null 2>&1; then
export TERM=xterm-256color
if tput setaf 1 &> /dev/null; then
tput sgr0
if [[ $(tput colors) -ge 256 ]] 2>/dev/null; then
BLACK=$(tput setaf 190)
MAGENTA=$(tput setaf 9)
ORANGE=$(tput setaf 172)
GREEN=$(tput setaf 190)
PURPLE=$(tput setaf 141)
WHITE=$(tput setaf 255)
BLACK=$(tput setaf 190)
MAGENTA=$(tput setaf 5)
ORANGE=$(tput setaf 4)
GREEN=$(tput setaf 2)
PURPLE=$(tput setaf 1)
WHITE=$(tput setaf 7)
BOLD=$(tput bold)
RESET=$(tput sgr0)
export BLACK
export MAGENTA
export ORANGE
export GREEN
export PURPLE
export WHITE
export BOLD
export RESET
# Git branch details
function parse_git_dirty() {
[[ $(git status 2> /dev/null | tail -n1) != *"working tree clean"* ]] && echo "*"
function parse_git_branch() {
git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e "s/* \(.*\)/\1$(parse_git_dirty)/"
# Change this symbol to something sweet.
# (
symbol="$ "
export PS1="\[$GREEN\]\w\[$WHITE\]\$([[ -n \$(git branch 2> /dev/null) ]] && echo \" on \")\[$PURPLE\]\$(parse_git_branch)\[$WHITE\] $symbol\[$RESET\]"
export PS2="\[$ORANGE\]→ \[$RESET\]"
# init z! (
. ~/
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar
# make less more friendly for non-text input files, see lesspipe(1)
#[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
#alias grep='grep --color=auto'
#alias fgrep='fgrep --color=auto'
#alias egrep='egrep --color=auto'
# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'
# some more ls aliases
alias ll='ls -l'
alias la='ls -A'
alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
# Nothing else to see here — Everything's in .bash_profile
[ -n "$PS1" ] && source ~/.bash_profile
# EditorConfig is awesome:
# top-most EditorConfig file
root = true
# File encoding
charset = utf-8
# 1 tab (4 space) indentation
indent_style = tab
indent_size = 4
# Trailing whitespace (UNIX style with no trailing whitespace)
end_of_line = lf
trim_trailing_whitespace = true
insert_final_newline = false
name = David Pustai
email =
editor = subl -nw
excludesFiles = ~/.gitignore_global
excludesFile = ~/.gitignore_global
name = David Pustai
email =
defaultBranch = main
co = checkout
{ "keys": ["ctrl+alt+w"], "command": "prompt_select_workspace" },
// insert nbsp shortcut
{ "keys": ["shift+space"], "command": "insert", "args": {"characters": " "} },
"bootstrapped": true,
"Package Control",
"font_size": 15,
"color_scheme": "Monokai.sublime-color-scheme",
"fade_fold_buttons": true,
"highlight_line": true,
"highlight_modified_tabs": false,
"trim_trailing_white_space_on_save": true,
"word_wrap": false,
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment