Sponsored Content
Full Discussion: How to make Alias?
Top Forums UNIX for Dummies Questions & Answers How to make Alias? Post 302580607 by aish11 on Friday 9th of December 2011 02:57:04 AM
Old 12-09-2011
hi,

1)where i will get this files .If i am not getting this file the how to find the path?

2)Generally i make my shellscript in bash.then in which .profile or .bashrc or .kshrc i should add the code of alias?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

make and make install commands

Hi there, I am installing a package at the moment on to my Solaris version 8 and I have run into a problem with the 'make' command. I have installed the package using the 'pkgadd' command and I am now at the stage where I have to use the 'make' command followed by the 'make install'... (4 Replies)
Discussion started by: gerwhelan
4 Replies

2. Shell Programming and Scripting

How to make Alias

Dear all, I'm new in unix systm , I try to write alias script: alias hr= cd/home/hmi/bin/Log and this work, but when i quit from unix and login again, this can't work again. how to create alias that can work anytime thank you Regards Heru (1 Reply)
Discussion started by: heru_90
1 Replies

3. Linux

Error in issuing a make and make install

Hi, Recently I install a package and try to do a make and make install. However, in the make it gives me below error:- make:Nothing to be done for 'install-exec-am' make:Nothing to be done for 'install-data-am' Can anyone please explain to me what does this mean? I have been trying... (1 Reply)
Discussion started by: ahjiefreak
1 Replies

4. UNIX for Dummies Questions & Answers

How to make alias for start of next sessiones

Good morning Dear Friends Please tell me how can be don't alias which is not Temporary.I mean in next log it to be there specially for AIX and HP UNIX.Thanks in advance. (0 Replies)
Discussion started by: papa1980
0 Replies

5. Solaris

Gani Network Driver Won't Install - make: Fatal error: Don't know how to make targ...

I attached a README file that I will refer to. I successfully completed everything in the README file until step 4. # pwd /gani/gani-2.4.4 # ls COPYING Makefile.macros gem.c Makefile Makefile.sparc_gcc gem.h Makefile.amd64_gcc ... (1 Reply)
Discussion started by: Bradj47
1 Replies

6. UNIX for Dummies Questions & Answers

How to make a make from other folder

Hi, Sorry for my English. I want Execute a make from other folder but no it's a normal make. The comand is: make telosb install,3 And for example if i have to execute this comand in /tmp and i am in /$HOME how he would be now the comand? thx (7 Replies)
Discussion started by: Grobix
7 Replies

7. UNIX for Dummies Questions & Answers

Difference between configure/make/make install.

Hi, While installation of apache on linux, we perform the below tasks. 1) Untar 2) configure 3) make 4) make install. I wanted to understand the difference and working of configure/make/make install. Can any one help me understanding this? Thanks in advance. (1 Reply)
Discussion started by: praveen_b744
1 Replies

8. UNIX for Dummies Questions & Answers

How to make delays between multiple commands in an alias (ircII)?

Okay so I have an alias that looks like this: ALIAS gscn { MSG gscn Test1 MSG gscn Test2 MSG gscn Test3 MSG gscn Test4 MSG gscn Test5 } How do I make it wait 5 seconds between each command before it executes the next one after that in order from top to bottom? I tried the TIMER... (1 Reply)
Discussion started by: guitarscn
1 Replies

9. Programming

Issue with make, no rule to make target etc.

I have been trying to split up my src directory to clear out files that are not re-compiled very often. Now I have the following setup in my trunk, trunk/bld trunk/src/ trunk/src/src_server trunk/makefile.linux In the make file, I have compile rules SOURCELOC = src # compile src c++... (4 Replies)
Discussion started by: LMHmedchem
4 Replies

10. UNIX for Dummies Questions & Answers

Create alias files (not alias commands)

If one: $ find -name 'some expression' -type f > newfile and then subsequently wants to create an alias file from each pathname the find command retrieved and the > placed within 'newfile', how would one do this? Ideally, the newly created alias files would all be in one directory. I am... (3 Replies)
Discussion started by: Alexander4444
3 Replies
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)
All times are GMT -4. The time now is 12:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy