When I execute following shell script I am getting the following error
syntax error at line 50 : `<<' unmatched
What am I doing wrong :confused:
Script begins here
----------------
MPAN_FILE=$1
exec 3<$MPAN_FILE ... (2 Replies)
Does anyone see anything wrong with this.
#getInfraFiles()
#{
# cd Infra/$DAY
# rm *
# /usr/bin/ftp -i -n $LINE << cmd
# user "$USER" "$PASSWD"
# cd $INFRAPATH
# binary
# mget *
# bye
#}
besides that its commented out (4 Replies)
Hello,
I have a simple script such as
-----------------------------
#! /bin/sh
YEAR=`date -u +%Y`;
MONTH=`date -u +%m`;
DAY=`date -u +%d`;
DATE=$MONTH$DAY$YEAR
LOGFILES=auditTrail-$DATE
LOGMATCH=$LOGFILES\*
ARGUM=''
# find all files and write them to a file
find . -name... (7 Replies)
I really just mess around in UNIX, for the most part, when I want to get something done. I can usually piece things together by searching for brief how-to's on Google, but the syntax errors in my following .sh file are really confusing me. I've got lots of programming experience in other places, so... (7 Replies)
when user select option 2 nothing happen.for testing purpose I put
echo command but is not executing .
basically when user prompt for option 2,I want to get list of database name from user separeted by space (TEST DEVL)
and put into the file seprated by new line
TEST
DEVL
after that stay on... (1 Reply)
For one of my script, I want one extra parameter needs to be added to one of the Usage option. Below its given
#Check Input parameters are valid
if ; then
function usage() {
echo
echo "*******************************************"
echo " !!! USAGE... (2 Replies)
I am working on a simple login ID check shell script that should prompt for a user ID then check to see if this user is logged on. Trying to get the hang of this stuff so I am thinking of my own little projects.
#! /bin/sh
echo "please enter a user name"
read user
if user=$user
then... (3 Replies)
Hi ! all I am just trying to check range in my datafile
pls tell me why its resulting wrong
admin@IEEE:~/Desktop$ cat test.txt
0 28.4
5 28.4
10 28.4
15 28.5
20 28.5
25 28.6
30 28.6
35 28.7
40 28.7
45 28.7
50 28.8
55 28.8
60 28.8
65 28.1... (2 Replies)
Discussion started by: Akshay Hegde
2 Replies
LEARN ABOUT OSX
tklib_history
history(n) Provides a history for Entry widgets history(n)
__________________________________________________________________________________________________________________________________________________NAME
history - Provides a history for Entry widgets
SYNOPSIS
package require Tcl 8.4
package require Tk 8.4
package require history ?0.1?
::history::init pathName ?length?
::history::remove pathName
::history::add pathName text
::history::get pathName
::history::clear pathName
::history::configure pathName option ?value?
bell
_________________________________________________________________DESCRIPTION
This package provides a convenient history mechanism for Entry widgets. The history may be accessed with the up and down arrow keys.
::history::init pathName ?length?
Arranges to remember the history of the named Entry widget. An optional length determines the number of history entries to keep.
This may be changed later with ::history::configure. History entries must be added with the ::history::add command before they can
be seen.
::history::remove pathName
Forgets all history entries for the Entry pathName and removes the history bindings.
::history::add pathName text
This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be
called from your Entry handler with the contents of the entry (or whatever you wish to add to the history).
::history::get pathName
This command returns a list containing the history entries for the Entry pathName
::history::clear pathName
This command clears the history list for the named Entry.
::history::configure pathName option ?value?
This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter-
mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of
the history, it defaults to
bell
entry .e
bind .e <Return> [list ProcessEntry %W]
::history::init .e
pack .e
proc ProcessEntry {w} {
set text [$w get]
if {$text == ""} { return }
::history::add $w $text
puts $text
$w delete 0 end
}
KEYWORDS
entry, history
history 0.1 history(n)