This is just a quick poll for a consensus of opinion. Every time I run vagrant up I normally forget that it is running and when it comes time to shutdown or reboot I have forgotten that I have vagrant running. How many of you also suffer from this problem?
If there’s enough call for one then I shall write a shell script to suspend all instances of vagrant on shutdown or reboot. Let me know what you think.
Please leave your comments below or reply on Twitter
Many people know that you can add the Git branch name you are currently working in to the end of your command prompt but did you know that you can also have the command prompt notify you if you have any untracked of modified files?
I have created this post with linux in mind but I’m sure you can Google what to do if you have a different OS
First place the following in ~/.bashrc so that .bashrc can read my script.
# Include my very own git parse type function :-)
source ~/.GitParseStatus.sh
Then I update the PS1 variable (the command prompt text) to output the result of the script
# What do you want to show when everything is up to date
# Your options are…
TICK=$’\u2714′
OK=’OK’
CUSTOM_OK=”
# Now set the all ok message
ALL_OK=$TICK
# What do you want to display when there git needs updating in some way?
# I have used “M” for files have been modified
UPDATE_TEXT=’ M’
# What do you want to display when there are untracked files in the repo?
# I have used “U” but you can use whatever you want
UNTRACKED_TEXT=” U”
# How do you want to display the repo branch
# I have used square brackets
BRANCH_PRE_TEXT=”[”
BRANCH_POST_TEXT=”]”
# What colour do you want the git section of you command line to be when
# everything is ok?
# I have it as green
# Set some colours #
# Some examples are…
GIT_RESET=”17″
GIT_NORMAL=”33[0m”
GIT_RED_1=”33[31;1m”
GIT_YELLOW_1=”33[33;1m”
GIT_WHITE=”33[37;1m”
GIT_RED=”33[0;31m”
GIT_YELLOW=”33[01;33m”
GIT_GREEN=”33[0;32m”
GIT_BLUE=”33[01;034m”
BRANCH_COLOUR_ALL_OK=$GIT_GREEN
BRANCH_COLOUR_NOT_OK=$GIT_GREEN
# If we fail to get a branch name then simply return empty handed 🙁
#IN=$(git symbolic-ref HEAD 2> /dev/null) || echo “You are not in a Git repo”
IN=$(git symbolic-ref HEAD 2> /dev/null) || return
#echo $IN
BRANCH_NAME=`echo $IN | sed ‘s/refs\/heads\///’`
#log ‘Branch Name=”‘$BRANCH_NAME'”‘
# get a list of files to run through
FILES=$(git status -z 2> /dev/null)
#log ‘Git Status=”‘”$FILES”‘”‘
#echo
if [[ -z “$FILES” ]]; then
#log “All the files in your Git repo are up to date”
UPDATES=`echo -e ${TEXT_CODES_COLOUR_ALL_OK}`${ALL_OK}
A Tutorial that will walk you though the ins and out of running XBMC fullscreen in your second monitor. It can also be used for many other programs and in either primary or secondary monitor using the techniques that are demonstrated in this post.
Step 2:
Type gvim in your terminal and it will not hog it until you close gvim i.e
john@John-Tosh-Lin 10:31 ~
$ gvim
[1] 10381
john@John-Tosh-Lin 10:31 ~
$
As a bonus, if you start gvim in the directory that you are working in then NERDTree’s root will be the directory you are in. That in itself saves a lot of time 🙂
Tada!
Enjoy your newly reclaimed terminal people 🙂