09-29-2009
That wouldn't be part of your script environment though. Are you using these aliases for something else or mainly this? You could source your .bashrc or keep the definitions in a separate file and source that whenever you have a script that needs to access the definitions.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a question about expanding shell variables. Given the following piece of script:
a="Some text"
b="Other text"
for i in a b
do
string1=$i
echo $string1 --> returns 'a'
string2=EXPRESSION_WITH_$i
echo $string2 --> returns 'Some text'
done
... (2 Replies)
Discussion started by: lonar
2 Replies
2. UNIX for Dummies Questions & Answers
I'm new to UNIX. I have to run executables often, and they all have a common prefix "prefix_". Now I'm wondering if I can make an alias where I can type run xyz that will then execute "./prefix_xyz" ?
Thanks in advance. (1 Reply)
Discussion started by: JustinT
1 Replies
3. Solaris
I'm having a little trouble with a Solaris package build/install.
I have the following entries in my prototype file...
# Interfaces file - all versions installed and auto linked to installation type...
f none $OPTDIR/config/interfaces.DEV 0444 $OWNER $GROUP
f none... (0 Replies)
Discussion started by: JerryHone
0 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
I have a series of directories which i open regularly. I want create an alias so that i can pass the direcotry name to alias and then this commands makes Cd to the path i need. COuld you please help on how to create an alias
ex of what i am trying but couldn't succeeded
#alias... (1 Reply)
Discussion started by: firestar
1 Replies
5. UNIX for Dummies Questions & Answers
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
6. Shell Programming and Scripting
I am trying to turn this into an alias with no luck. I would then like to put the alias into my bashrc file. I know awk is very picky about quotes. I have tried every version of quotes, single quotes, double quotes, and backslashes that I can think of.
VAR=$(xrandr | awk '$2=="connected"{s=$1}... (3 Replies)
Discussion started by: cokedude
3 Replies
7. Shell Programming and Scripting
Hi Guys,
aliase uniq get ut=XXX anistr|availyStus|oratate|uniqueid
I want to create aliase but i want xxx as variable.....
run like this
uniq ak123
uniq ak324
uniq ak123
End of the story i want to use variable in aliase command (5 Replies)
Discussion started by: asavaliya
5 Replies
8. Shell Programming and Scripting
s=`awk '{ print $0}' /Applications/Relink.app/z_cloudline.txt`
sed -n '"$s"' /var/mobile/Library/iFile/Bookmarks.plist > /var/mobile/originalip.txt
What is the problem with that code ?
With variable it only outputs:
sed: -e expression #1, char 1: unknown command: `"'
If I use the... (3 Replies)
Discussion started by: pasc
3 Replies
9. Shell Programming and Scripting
Heyas
I'm trying to give some information on used variables.
While the first two work fine, the ones starting with a glob (is that the proper term?) fail.
echo ${!TUI_*} ${!RET_*} ${!*_CLI} ${!*\_GUI}
bash: ${!*_CLI}: bad substitution
Same with @ or have them escaped.
I found no... (2 Replies)
Discussion started by: sea
2 Replies
10. UNIX for Beginners Questions & Answers
I have also some difficulty calling sed to change a word in a file.
sed -i 's/docTitl/Outline ${docTitl}/g' $ofln
Moved to new thread, since it is a different question (3 Replies)
Discussion started by: Danette
3 Replies
catch(n) Tcl Built-In Commands catch(n)
__________________________________________________________________________________________________________________________________________________
NAME
catch - Evaluate script and trap exceptional returns
SYNOPSIS
catch script ?varName?
_________________________________________________________________
DESCRIPTION
The catch command may be used to prevent errors from aborting command interpretation. Catch calls the Tcl interpreter recursively to exe-
cute script, and always returns without raising an error, regardless of any errors that might occur while executing script.
If script raises an error, catch will return a non-zero integer value corresponding to one of the exceptional return codes (see tcl.h for
the definitions of code values). If the varName argument is given, then the variable it names is set to the error message from interpret-
ing script.
If script does not raise an error, catch will return 0 (TCL_OK) and set the variable to the value returned from script.
Note that catch catches all exceptions, including those generated by break and continue as well as errors. The only errors that are not
caught are syntax errors found when the script is compiled. This is because the catch command only catches errors during runtime. When
the catch statement is compiled, the script is compiled as well and any syntax errors will generate a Tcl error.
EXAMPLES
The catch command may be used in an if to branch based on the success of a script.
if { [catch {open $someFile w} fid] } {
puts stderr "Could not open $someFile for writing
$fid"
exit 1
}
The catch command will not catch compiled syntax errors. The first time proc foo is called, the body will be compiled and a Tcl error will
be generated.
proc foo {} {
catch {expr {1 +- }}
}
KEYWORDS
catch, error
Tcl 8.0 catch(n)