I can't tell why code I can't see isn't working. Please show your code.
I doubt that the dollar sign causes the problem, though. Shell is quite careful not to interpret dollar signs in strings as variables -- only in the shell's code itself is the value special.
Variables inside single quotes don't work, variables inside double quotes are expanded. This might be the issue.
Last edited by Corona688; 09-20-2017 at 07:32 PM..
Hi,
How can I get this to work?
#!/bin/ksh
if ; then
direction=">>"
else
direction=">"
fi
cat some_file_name $direction temp.txt
exit
This shell script is not happy with using "$direction" opposed to ">" or ">>".
Thanks. (5 Replies)
Hi,
I have a data file delimited by Ω symbol, I would like to use this in grep and cut command. but How to type this Omega symbol.
Thanks
Murugesan (1 Reply)
Hi
Thanks for this amazing forum first, I've been searching answers in it for problems that I've encountered at work.
The only problem I haven't been able to find a fix for, is a ever waiting for prompt problem in Expect when encounter a $ prompt.
I usually set the timeout to -1 cause the... (2 Replies)
Dear All,
we have a command output which looks like :
Total 200 queues in 30000 Kbytes
and we're going to get "200" and "30000" for further process. currently, i'm using :
numA=echo $OUTPUT | awk '{print $2}'
numB=echo $OUTPUT | awk '{print $5}'
my question is : can I use just one... (4 Replies)
I have a target directory, there are some files and directories in "target_dir".
I have a symbol link: my_link -> <target_dir>
The target directory name is NOT known to the script (because it is varying), while the link name is always fixed.
In a shell script, how to remove both the... (1 Reply)
hi,
I have been trying to acheive the following task for a while now, but failed.. Need help, experts please help!
This is what I am trying to do:
- I am writing to a flat file the name of the source to be copied and the destination path as to where it is to be copied to.
Sample flat file:... (7 Replies)
Hi Team,
Can you please help me to resolve this issue.
Am unable to use this $ symbol in sql query in the shell script.
For Example:
# !/bin/sh
export USER_NAME=XXX
export PASSWORD=YYY
export ORACLE_SID=xamdb
echo $ORACLE_SID
echo " Session Details ..."
... (1 Reply)
I have a shell script (.sh) and I want to pass a parameter value to the awk command but I am getting exception, please assist.
diff=$1$2.diff
id=$2 new=new_$diff
echo "My id is $1"
echo "I want to sync for user account $id"
##awk command I am using is as below
cat $diff | awk... (2 Replies)
I have the following script, and I want to assign the output ($10 and $5) from awk to N and L:
grdinfo data.grd | awk '{print $10,$5}'| read N L
output from gridinfo data.grd is: data.grd 50 100 41 82 -2796 6944 0.016 0.016 3001 2461. where N and L is suppose to be 3001 and 100. I use... (8 Replies)
Discussion started by: geomarine
8 Replies
LEARN ABOUT BSD
unifdef
UNIFDEF(1) General Commands Manual UNIFDEF(1)NAME
unifdef - remove ifdef'ed lines
SYNOPSIS
unifdef [ -t -l -c -Dsym -Usym -idsym -iusym ] ... [ file ]
DESCRIPTION
Unifdef is useful for removing ifdef'ed lines from a file while otherwise leaving the file alone. Unifdef is like a stripped-down C pre-
processor: it is smart enough to deal with the nested ifdefs, comments, single and double quotes of C syntax so that it can do its job, but
it doesn't do any including or interpretation of macros. Neither does it strip out comments, though it recognizes and ignores them. You
specify which symbols you want defined -Dsym or undefined -Usym and the lines inside those ifdefs will be copied to the output or removed
as appropriate. The ifdef, ifndef, else, and endif lines associated with sym will also be removed. Ifdefs involving symbols you don't
specify are untouched and copied out along with their associated ifdef, else, and endif lines. If an ifdef X occurs nested inside another
ifdef X, then the inside ifdef is treated as if it were an unrecognized symbol. If the same symbol appears in more than one argument, only
the first occurrence is significant.
The -l option causes unifdef to replace removed lines with blank lines instead of deleting them.
If you use ifdefs to delimit non-C lines, such as comments or code which is under construction, then you must tell unifdef which symbols
are used for that purpose so that it won't try to parse for quotes and comments in those ifdef'ed lines. You specify that you want the
lines inside certain ifdefs to be ignored but copied out with -idsym and -iusym similar to -Dsym and -Usym above.
If you want to use unifdef for plain text (not C code), use the -t option. This makes unifdef refrain from attempting to recognize com-
ments and single and double quotes.
Unifdef copies its output to stdout and will take its input from stdin if no file argument is given. If the -c argument is specified, then
the operation of unifdef is complemented, i.e. the lines that would have been removed or blanked are retained and vice versa.
SEE ALSO diff(1)DIAGNOSTICS
Premature EOF, inappropriate else or endif.
Exit status is 0 if output is exact copy of input, 1 if not, 2 if trouble.
BUGS
Does not know how to deal with cpp consructs such as
#if defined(X) || defined(Y)
AUTHOR
Dave Yost
4.3 Berkeley Distribution April 29, 1985 UNIFDEF(1)