10 More Discussions You Might Find Interesting
1. Red Hat
Hi
I need to install expect in redhat.
through net I came to know that I must install tcl too in order to make expect work.
I have downloaded both packages but not able to install
# ls -lrt
total 3720
18:33 tcl8.4.20-src.tar.gz
18:33 expect5.45.3.tar.gz
18:40 expect5.45.3... (7 Replies)
Discussion started by: scriptor
7 Replies
2. Shell Programming and Scripting
hi experts,
how will i convert the first part of my script into expect or tcl since shell script cannot be embedded into expect script ? i have 100+ servers in my serverlist. how will i call or declare it in expect or tcl ?
#!/usr/sbin/expect -f
serverlist=`cat $1`
for i in serverlist... (2 Replies)
Discussion started by: linuxgeek
2 Replies
3. Shell Programming and Scripting
Hello,
I write a TCL script for Expect/ Telnet.
I want to send command to the telnet server.
But I want to close after the command is sent.
Anybody know which command can flush the expect so I can sure the command is sent to the telnet server???
EX:
send "./command1\r"
close... (0 Replies)
Discussion started by: linboco
0 Replies
4. UNIX for Dummies Questions & Answers
hi, I am new in Expect.
I have a question about expect timeout.
suppose I have a structure of
expect { ".."{
send"............"}
timeout{
...............
}
}
The silly question is if I reach timeout, how can I store the error message showing on the screen to... (2 Replies)
Discussion started by: allenxiao7
2 Replies
5. Shell Programming and Scripting
I am having an issue with TCL\Expect; I am passing arguments via the commandline that are read in via "lrange $argv". One of those var's is a password with characters that need to be escapaed, after escaping them an hitting enter expect is placing curly braces around my password... why?!
... (4 Replies)
Discussion started by: RiSk
4 Replies
6. Shell Programming and Scripting
I'm having this problem with a very simple tcl expect script that is running on Solaris 5.3 with TCL version 8.4.7 and expect version 5.0.
below is the simplified version of the code snippet, which I think has everything to illustrate the problem, the full version is at the very bottom in... (0 Replies)
Discussion started by: pinchharmonic
0 Replies
7. Shell Programming and Scripting
Can someone identify what is the problem here?.
no children
while executing
"exp_wait -nowait -i -1"
(procedure "logOptions" line 45)
invoked from within
"logOptions"
(procedure "doExecute" line 98)
invoked from within
"doExecute"
(procedure "main" line 32)
... (7 Replies)
Discussion started by: calsum
7 Replies
8. Shell Programming and Scripting
In the following "for" loop I assume the the script will expect "anyway", "first" NOT in any paticular order and send "yes" when there found, breaking out of the loop when "$prompt" is found. The way it is working is like 3 individual expect lines, and they MUST be in cronological order. ANY help... (0 Replies)
Discussion started by: dave_m
0 Replies
9. UNIX for Dummies Questions & Answers
Does anyone know of an expect/tcl forum that is as helpful as this one is for shell scripting?
Or if anyone has any expect knowledge, can you please provide some guidance on how to write to a local error log based on output from a ssh session?
I have something like this:
foreach host... (2 Replies)
Discussion started by: earnstaf
2 Replies
10. Shell Programming and Scripting
I am rewriting the first big script project I ever coded to clean up some issues, mainly my really clumsy bash code, and to migrate to TCL/Expect. I have a couple of questions that I could use some help with.
1.) The script needs to know where it is located. I realize that I could use "find /... (1 Reply)
Discussion started by: thumper
1 Replies
doctools::tcl::parse(n) Documentation tools doctools::tcl::parse(n)
__________________________________________________________________________________________________________________________________________________
NAME
doctools::tcl::parse - Processing text in 'subst -novariables' format
SYNOPSIS
package require Tcl 8.4
package require snit
package require fileutil
package require logger
package require struct::list
package require struct::stack
package require struct::set
package require treeql
::doctools::tcl::parse text tree text ?root?
::doctools::tcl::parse file tree path ?root?
_________________________________________________________________
DESCRIPTION
This package provides commands for parsing text with embedded Tcl commands as accepted by the Tcl builtin command subst -novariables. The
result of the parsing is an abstract syntax tree.
This is an internal package of doctools, for use by the higher level parsers processing the docidx, doctoc, and doctools markup languages.
API
::doctools::tcl::parse text tree text ?root?
The command takes the text and parses it under the assumption that it contains a string acceptable to the Tcl builtin command subst
-novariables. Errors are thrown otherwise during the parsing. The format used for these errors in described in section Error format.
The command returns the empty string as it result. The actual result of the parsing is entered into the tree structure tree, under
the node root. If root is not specified the root of tree is used. The tree has to exist and be the command of a tree object which
supports the same methods as trees created by the package struct::tree.
In case of errors tree will be left in an undefined state.
::doctools::tcl::parse file tree path ?root?
The same as text, except that the text to parse is read from the file specified by path.
ERROR FORMAT
When the parser encounters a problem in the input it will throw an error using the format described here.
[1] The message will contain the reason for the problem (unexpected character or end of input in input), the character in question, if
any, and the line and column the problem was found at, in a human readable form. This part is not documented further as its format
may change as we see fit. It is intended for human consumption, not machine.
[2] The error code however will contain a machine-readable representation of the problem, in the form of a 5-element list containing, in
the order listed below
[1] the constant string doctools::tcl::parse
[2] the cause of the problem, one of
char Unexpected character in input
eof Unexpected end of the input
[3] The location of the problem as offset from the beginning of the input, counted in characters. Note: Line markers count as one
character.
[4] The line the problem was found on (counted from 1 (one)),
[5] The column the problem was found at (counted from 0 (zero))
TREE STRUCTURE
After successfully parsing a string the generated tree will have the following structure:
[1] In the following items the word 'root' refers to the node which was specified as the root of the tree when invoking either text or
file. This may be the actual root of the tree.
[2] All the following items further ignore the possibility of pre-existing attributes in the pre-existing nodes. If attributes exists
with the same names as the attributes used by the parser the pre-existing values are written over. Attributes with names not clash-
ing with the parser's attributes are not touched.
[3] The root node has no attributes.
[4] All other nodes have the attributes
type The value is a string from the set { Command , Text , Word }
range The value is either empty or a 2-element list containing integer numbers. The numbers are the offsets of the first and last
character in the input text, of the token described by the node,.
line The value is an integer, it describes the line in the input the token described by the node ends on. Lines are counted from 1
(one).
col The value is an integer, it describes the column in the line in the input the token described by the node ends on. Columns
are counted from 0 (zero).
[5] The children of the root, if any, are of type Command and Text, in semi-alternation. This means: After a Text node a Command node
has to follow, and anything can follow a Command node, a Text or other Command node.
[6] The children of a Command node, if any, are of type Command, and Text, and Word, they describe the arguments of the command.
[7] The children of a Word node, if any, are of type Command, Text, in semi-alternation. This means: After a Text node a Command node
has to follow, and anything can follow a Command node, a Text or other Command node.
[8] A Word node without children represents the empty string.
[9] All Text nodes are leaves of the tree.
[10] All leaves of the tree are either Text or Command nodes. Word nodes cannot be leaves.
BUGS, IDEAS, FEEDBACK
This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category doctools
of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for
either package and/or documentation.
KEYWORDS
Tcl syntax, command, doctools, parser, subst, word
CATEGORY
Documentation tools
COPYRIGHT
Copyright (c) 2009 Andreas Kupries <andreas_kupries@users.sourceforge.net>
doctools2base 1 doctools::tcl::parse(n)