with this double quoting, look at PS1 after assignment:
Your variables are expanded inside of a double-quote before assignment. If you escape the $ then it will be stored inside of PS1. You can also use single quotes to avoid expansion, but you have some in there so those are the 1 character you need to treat special inside single quotes:
Having a command execute for each prompt is a bit much. Also maybe you'd like to make it a function and handle those fatal errors in case you leave a git branch.
et voila!?
This User Gave Thanks to neutronscott For This Post:
I am having a hard time figuring out how to change the command prompt in my UNIX shell.
I am using the bash shell, and I would like to set the prompt to show me the full path of the current working directory along with my username, I suppose... The main thing I want is the full path of the... (2 Replies)
Hello there !
I am new in this Unix world and just start learning Unix. I have very simple question about changing PS1 variable (Shell Prompt)
i have local.profile file in my working directory, i open in vi edit mode and add this line PS1="Hello:>" and i save that file.
I disconnected from... (2 Replies)
Hi,
I want to change my command prompt to contain the current username and the current directory in it, instead of just the '$' symbol.
I tried the command:-
export PS1="$(echo \\n$) "
But whenever I switch the user or change the directory, the changes are not reflected in the command... (10 Replies)
would someone please explain in detail, how does the code below change the color or bash prompt
$ echo $PS1
:\033
are there other tricks like above? (3 Replies)
please advise what's wrong with this command ?
PS1="`hostname`:`who am i | cut -d " " -f1`:>>"
trying to make the PS1 prompt look like :
machine_name:username:>>
thank you (4 Replies)
Hi,
I'm trying to find out if there is a way to get a timestamp on my Solaris root shell prompt using /sbin/sh?
I'm trying to archive something in line with the following:
12:34:26 root@server #
12:34:28 root@server #
12:34:28 root@server # ls
...
12:34:30 root@server #
I know there... (1 Reply)
Dear Members,
I have an variable by name dir.If i do echo $dir i will get the path (/usr/bin/).
I am writing a shell script which will prompt to enter the variable name if run.Suppose the script name is test.sh.
If run test.sh it will prompt for entering variable name which is dir.Suppose... (9 Replies)
So, this is strange... I created this prompt:
PS1='\n\e
You can see that it's a pretty minor modification of the default Debian prompt. And, if it matters, I'm using Putty to SSH to my server. The following strange symptoms appear when I use that prompt, and disappear when I change and... (2 Replies)
I have given as:
PS1="Karthick>" in linux.
Now the prompt changed as:
Karthick>
Now I need to get back the default prompt .
How to achieve this?
Thanks in advance (13 Replies)
Hi, I need help changing PS1 in Solaris. I tried this:
MYPROMPT="> "
PS1=$LOGNAME@$HOSTNAME:${PWD}$MYPROMPT (NOT SURE WHY IT'S HIGHLIGHTED HERE)
export PS1
My problem is that $PWD is not working, when I get the prompt and I change directories, the prompt is not displaying the current... (17 Replies)
Discussion started by: curiousmal
17 Replies
LEARN ABOUT DEBIAN
git-sh
GIT-SH(1)GIT-SH(1)NAME
git-sh -- a git shell
SYNOPSIS
git-sh
DESCRIPTION
git-sh starts an interactive bash(1) session modified for git-heavy workflows. Typical usage is to change into the directory of a git work
tree or bare repository and run the git-sh command to start an interactive shell session.
Top-level command aliases are created for all core git(1) subcommands, git-sh builtin aliases (see BUILTIN ALIASES), and git command
aliases defined in ~/.gitconfig.
BUILTIN ALIASES
git-sh loads a set of standard aliases in addition to all core git commands. The builtin aliases are overridden by aliases defined in the
user or system gitconfig files.
a git add
b git branch
c git checkout
d git diff
f git fetch --prune
k git cherry-pick
l git log --pretty=oneline --abbrev-commit
n git commit --verbose --amend
r git remote
s git commit --dry-run --short
t git diff --cached
The Staging Area
a git add
aa git add --update (mnemonic: "add all")
stage git add
ap git add --patch
p git diff --cached (mnemonic: "patch")
ps git diff --cached --stat (mnemonic: "patch stat")
unstage
git reset HEAD
Commits and Commit History
ci git commit --verbose
ca git commit --verbose --all
amend git commit --verbose --amend
n git commit --verbose --amend
k git cherry-pick
re git rebase --interactive
pop git reset --soft HEAD^
peek git log -p --max-count=1
Fetching and Pulling
f git fetch
pm git pull (mnemonic: "pull merge")
pr git pull --rebase (mnemonic: "pull rebase")
Miscellaneous Commands
d git diff
ds git diff --stat (mnemonic: "diff stat")
hard git reset --hard
soft git reset --soft
scrap git checkout HEAD
CUSTOM ALIASES
Anything defined in the [alias] section of the repository, user, or system git config files are also available as top-level shell commands.
Assuming a ~/.gitconfig that looked like this:
[alias]
ci = commit --verbose
ca = commit -a
d = diff
s = status
thanks = !git-thanks
... you might then have the following shell session:
master!something> echo "stuff" >somefile
master!something*> s
M somefile
master!something*> d
diff --git a/somefile b/somefile
-- a/somefile
++ b/somefile
@@ -0,0 +1 @@
+ stuff
master!something*> ca -m "add stuff"
master!something> thanks HEAD
PROMPT
The default prompt shows the current branch, a bang (!), and then the relative path to the current working directory from the root of the
work tree. If the work tree includes modified files that have not yet been staged, a dirty status indicator (*) is also displayed.
The git-sh prompt includes ANSI colors when the git color.ui option is set and enabled. To enable git-sh's prompt colors explicitly, set
the color.sh config value to auto:
$ git config --global color.sh auto
Customize prompt colors by setting the color.sh.branch, color.sh.workdir, and color.sh.dirty git config values:
$ git config --global color.sh.branch 'yellow reverse'
$ git config --global color.sh.workdir 'blue bold'
$ git config --global color.sh.dirty 'red'
See colors in git for information.
COMPLETION
Bash completion support is automatically enabled for all git built-in commands and also for aliases defined in the user ~/.gitconfig file.
The auto-completion logic is smart enough to know an alias d that expands to git-diff should use the same completion configuration as the
git-diff command.
The completion code is a slightly modified version of the git bash completion script shipped with the core git distribution. The script is
built into thegit-sh executable at compile time and need not be obtained or installed separately.
CUSTOMIZING
Most git-sh behavior can be configured by editing the user or system gitconfig files (~/.gitconfig and /etc/gitconfig) either by hand or
using git-config(1). The [alias] section is used to create basic command aliases.
The /etc/gitshrc and ~/.gitshrc files are sourced (in that order) immediately before the shell becomes interactive.
The ~/.bashrc file is sourced before either /etc/gitshrc or ~/.gitshrc. Any bash customizations defined there and not explicitly overrid-
den by git-sh are also available.
ENVIRONMENT
PS1 Set to the dynamic git-sh prompt. This can be customized in the ~/.gitshrc or /etc/gitshrc files.
GIT_DIR
Explicitly set the path to the git repository instead of assuming the nearest .git path.
GIT_WORK_TREE
Explicitly set the path to the root of the work tree instead of assuming the nearest parent directory with a .git repository.
SEE ALSO bash(1), git(1), git-config(1),http://github.com/rtomayko/git-sh
Ryan Tomayko March 2010 GIT-SH(1)