hi guys, i have a question related to quoting but i am not sure how to formulate it...
lets say we want to simulate the following shell actions
so i make the following script
buidtags.sh
but it doesn't work...
i think the reason is that it skips file globbing, and considers *.sh to be a file, that (of course) can't be found! How can i make file globbing and double quotes coexist? in other words how can i make this example work?
thanks in advance for your time,
nicolas
PS: in quoting as a reference i use chap7 from "learning the bash shell 3rd edition" but i am relatively new to shell scripting.Is there any other good reference for bash?
Hi All
In a script, I want a user to enter 4 characters, these can be a mix of letters (uppercase and lowercase) and numbers.
In this example $var represents what the user has entered.
eg $var can be A9xZ, 3DDL, bbHp .........etc
I need to check that the user has only entered characters... (2 Replies)
Hi,
I have trouble with quotations of the M4 preprocessor.
I want to write a basic makro that removes all spaces and newlines at the end and at the beginning of a string.
I tried this:
define(`TRIM_END', `patsubst(`$1', `\(\\n\| \)*$', `')')
define(`TRIM', `patsubst(`TRIM_END(`$1')',... (0 Replies)
I'm trying to take the command `date` giving me:
Fri Feb 22 09:23:52 EST 2008
and using some command take out the rest of the string leaving me with
"Fri Feb 22"
any help appreciated hopefully thanks in advance (3 Replies)
The block below isn't a surprise:$ ls
file1 file2 file3
$ x=*
$ echo $x
file1 file2 file3
$ echo '$x'
$x
$ echo "$x"
*
$But I found this block a bit bewildering:$ echo $x'
>'
*
$I'm wondering why substitution wasn't performed on the $x, since it was unquoted (as far as I can tell).... (5 Replies)
I think this has to do with the quoting, I just feel I've been looking at it too long. Thanks ~T
prompt> cat my.awk
BEGIN{"date +%d%b%Y.%H%M%S" | getline sDate}
{
if (substr($0,151,1) ~ /6/ )
print >> sDate".NEW_ORDER.dat"
# print >> sDate # note this works to output the contents to sDate,... (2 Replies)
Hi all,
i have a file that looks like:
one:two:three:four:five
six:seven:eight:nine:ten
and i'd like to quote the fourth column, getting:
one:two:three:"four":five
six:seven:eight:"nine":ten
i was thinking something like:
awk 'BEGIN{FS=":"}{print $1 FS $2 FS $3 FS \"$4\" FS $5}'... (5 Replies)
Hi,
My first shell script is one that prints the five largest directories in a given directory. My current effort is as follows, it gives me the output I'd like, but I have to quote a globbed pathname, which seems wrong:
#!/bin/sh
du -hs $1 | sort -rn | head -n 5
And I must invoke... (2 Replies)
I have some data files that I can identify by a certain pattern in the names using find.
Every one of those data files has an XML file associated with it (can be multiple data files per XML file).
The XML file is always up one directory from the data file(s) in a folder calledRun##### -... (12 Replies)
I am trying to write a BASH script that will prompt a user to enter a number of days, then calculate the date.
My problem is the date command uses single or double quotes. For Example..
date -d "7 days"
Here is an example of some same code I am trying to work through.
echo "when do you... (4 Replies)
Discussion started by: javajockey
4 Replies
LEARN ABOUT SUNOS
readonly
readonly(1) User Commands readonly(1)NAME
readonly - shell built-in function to protect the value of the given variable from reassignment
SYNOPSIS
sh
readonly [name...]
ksh
**readonly [ name [ = value]...]
**readonly -p
DESCRIPTION
sh
The given names are marked readonly and the values of the these names may not be changed by subsequent assignment. If no arguments are
given, a list of all readonly names is printed.
ksh
The given names are marked readonly and these names cannot be changed by subsequent assignment.
When -p is specified, readonly writes to the standard output the names and values of all read-only variables, in the following format:
"readonly %s=%s
", name, value
if name is set, and:
"readonly $s
", name
if name is unset.
The shell formats the output, including the proper use of quoting, so that it is suitable for reinput to the shell as commands that achieve
the same value and readonly attribute-setting results in a shell execution environment in which:
1. Variables with values set at the time they were output do not have the readonly attribute set.
2. Variables that were unset at the time they were output do not have a value at the time at which the saved output is reinput to the
shell.
On this man page, ksh(1) commands that are preceded by one or two ** (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO ksh(1), sh(1), typeset(1), attributes(5)SunOS 5.10 17 Jul 2002 readonly(1)