Also note that there are some special variables which are also introduced by "$":
$$ = process number of the currently running process
$* = all the arguments passed to a process (or subfunction of a script)
$@ = same as above*)
$# = number of all the arguments passed to a process (or subfunction of a script)
$! = process number of the background process invoked by the current process
$? = the return code of the last process executed
$1 ($2, $3, ...) = the first (second, third, ...) positional parameter passed to that process
I hope this helps.
bakunin
____________
*) "$*" and "$@" are basically the same, except when quoted. "$*" gives all arguments surrounded by spaces, "$@" gives all arguments surrounded by quotes. For instance, you call a script this way:
Code:
myscript.sh "one arg" "two arg" "three arg"
Inside the script you use "$*" and you get a single string: "one arg two arg three arg", whereas when you use "$@" you get three strings: "one arg" "two arg" "three arg".
hey there
im a bit stuck on executing commands that include the special character '?'. can someone recommend a way on how i would be able to execute it?? i thought the glob function could be useful (still mite be) but upon entering the command
'ls pars?' it listed all the files in the... (1 Reply)
Hello,
I've had a daemon go a little bit mental and create directories using somments from a config file. The end result is I've ended up with directories with names such as #, 5625), (5725 etc etc etc...
However, when I try and delete them I get syntax errors, ( not expected,
rmdir #... (2 Replies)
Hi,
I am trying to unload file from a database. Which contains few lines with the character below. Rest of the data was unloaded appropriately.
a) What does this below character means?
b) How can i remove it,
I already have sed '/^$/d'
c) Will this effect the file by any means... (4 Replies)
Hi
I am comparing 2 files (using diff command) with numerical data in them. In the output file I want only the differences which are in file2 but not in file1. Although I am getting the diffences i am also getting special characters in the output file which i do not want. Can somebody help me
For... (3 Replies)
Hi,
In the shell script, i need to remove the special charater "\" with "\\". For example, i need to replace "D:\FXT\ABC.TXT" with "D:\\FXT\\ABC.TXT".
However, when trying to do something like , i get the below error :-
-->echo "D:\FXT\ABC.TXT" | sed -e 's#\#\\#g'
sed: 0602-404 Function... (7 Replies)
I have below line in a unix file, I want to delete one character after "Â".
20091020.Non-Agency CMO Daily Trade Recap Â~V Hybrids
The result should be :
20091020.Non-Agency CMO Daily Trade Recap  Hybrids
i dont want to use "~V" anywhere in the sed command or any other command, just remove... (1 Reply)
When editing a file, vi displays a special character as ^L. Can you tell me the escaped character to be used in awk? And can that escaped character be used in a regexp in both sed and awk? (7 Replies)
a='CASH$$A'
/usr/xpg4/bin/grep -F "$a" *.txt
It is not able to grep CASH$$A string as it contains special character $$.
I also tried with
/usr/xpg4/bin/grep -F '$a' *.txt
but still not working.
I have to assign CASH$$A to a variable and serach that variable..i dont want to search the... (8 Replies)
Hi,
on ksh
What does the following do?
grep -v "toolbox" $home_oracle/.profile >$home_oracle/.profile.$$ Thanks.
Please use CODE tags as required by forum rules! (3 Replies)
Discussion started by: big123456
3 Replies
LEARN ABOUT DEBIAN
aepromptcmd
aepromptcmd(1)aepromptcmd(1)NAME
aepromptcmd - change prompt color by change state
SYNOPSIS
PROMPT_COMMAND="aepromptcmd"
DESCRIPTION
The bash(1) shell has an interesting property: If the PROMPT_COMMAND vaiable is set, the value is executed as a command prior to issuing
each primary prompt. (Actually, it can be a seties of semicolon separated commands.)
In order to change the text back to normal, the PS1 variable needs to have "33[0m" somewhere near the end, otherwise things can get a
little difficult to read. If you are using bash(1), you need to let it know these are unprintable (like this: "[33[0m]") or it messes
up command line editing.
The aepromptcmd command is used to set the color of the prompt, based on the state of the current change. This is an idea taken from Kent
Beck's Test Driven Development book. If the change is in the being developed or being integrated state and it needs to be built, the
prompt is red; if it is built but it needs to be tested, the prompt is magenta, otherwise it is green.
Example
Here is a short script you can put in your .bashrc file to turn on prompt coloring:
if [ "$PS1" ] then
case "$PROMPT_COMMAND" in
"" ) PROMPT_COMMAND="aepromptcmd" PS1="$PS1^[[0m" ;;
*aepromptcmd*) ;;
*) PROMPT_COMMAND="$PROMPT_COMMAND;aepromptcmd" PS1="$PS1[33[0m]" ;;
esac
export PROMPT_COMMAND
export PS1 fi
Note that this usually leaves your prompt default (black) when you are not somewhere inside a development directory.
Limitations
The aepromptcmd command uses the ANSI color escape sequences. It really should to use the tigetstr(3) function from terminfo(3) to do
this in a terminal independent way. Code contributions welcome.
OPTIONS
The following options are understood:
-Change number
This option may be used to specify a particular change within a project. See aegis(1) for a complete description of this option.
-Project name
This option may be used to select the project of interest. When no -Project option is specified, the AEGIS_PROJECT environment
variable is consulted. If that does not exist, the user's $HOME/.aegisrc file is examined for a default project field (see aeu-
conf(5) for more information). If that does not exist, when the user is only working on changes within a single project, the
project name defaults to that project. Otherwise, it is an error.
-Help
This option may be used to obtain more information about how to use the aepromptcmd program.
-Verbose
By default error messages are supressed, so that the prompt will be normal when you are outside an Aegis work area. Use this
option to tuen error messages back on.
See also aegis(1) for options common to all aegis commands.
All options may be abbreviated; the abbreviation is documented as the upper case letters, all lower case letters and underscores (_) are
optional. You must use consecutive sequences of optional letters.
All options are case insensitive, you may type them in upper case or lower case or a combination of both, case is not important.
For example: the arguments "-project, "-PROJ" and "-p" are all interpreted to mean the -Project option. The argument "-prj" will not be
understood, because consecutive optional characters were not supplied.
Options and other command line arguments may be mixed arbitrarily on the command line, after the function selectors.
The GNU long option names are understood. Since all option names for aepromptcmd are long, this means ignoring the extra leading '-'.
The "--option=value" convention is also understood.
EXIT STATUS
The aepromptcmd command will exit with a status of 1 on any error. The aepromptcmd command will only exit with a status of 0 if there are
no errors.
ENVIRONMENT VARIABLES
See aegis(1) for a list of environment variables which may affect this command. See aepconf(5) for the project configuration file's
project_specific field for how to set environment variables for all commands executed by Aegis.
COPYRIGHT
aepromptcmd version 4.24.3.D001
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Peter
Miller
The aepromptcmd program comes with ABSOLUTELY NO WARRANTY; for details use the 'aepromptcmd -VERSion License' command. This is free soft-
ware and you are welcome to redistribute it under certain conditions; for details use the 'aepromptcmd -VERSion License' command.
AUTHOR
Peter Miller E-Mail: millerp@canb.auug.org.au
//* WWW: http://www.canb.auug.org.au/~millerp/
Reference Manual Aegis aepromptcmd(1)