neulab/tldr huggingface dataset:
The -re flag forces the string to be interpreted as a regexp-style pattern.  In this case, matching substrings are stored in the variable interact_out similarly to the way expect stores its output in the variable expect_out.  The -indices flag is similarly supported.
The pattern eof introduces an action that is executed upon end-of- file.  A separate eof pattern may also follow the -output flag in which case it is matched if an eof is detected while writing output.  The default eof action is "return", so that interact simply returns upon any EOF.
The pattern timeout introduces a timeout (in seconds) and action that is executed after no characters have been read for a given time.  The timeout pattern applies to the most recently specified process.  There is no default timeout.  The special variable "timeout" (used by the expect command) has no affect on this timeout.
For example, the following statement could be used to autologout users who have not typed anything for an hour but who still get frequent system messages:
interact -input $user_spawn_id timeout 3600 return -output \ $spawn_id
If the pattern is the keyword null, and nulls are allowed (via the remove_nulls command), the corresponding body is executed if a single ASCII 0 is matched.  It is not possible to match 0 bytes via glob or regexp patterns.
Prefacing a pattern with the flag -iwrite causes the variable interact_out(spawn_id) to be set to the spawn_id which matched the pattern (or eof).
Actions such as break and continue cause control structures (i.e., for, proc) to behave in the usual way.  However return causes interact to return to its caller, while inter_return causes interact to cause a return in its caller.  For example, if "proc foo" called interact which then executed the action inter_return, proc foo would return.  (This means that if interact calls interpreter interactively typing return will cause the interact to continue, while inter_return will cause the interact to return to its caller.)
During interact, raw mode is used so that all characters may be passed to the current process.  If the current process does not catch job control signals, it will stop if sent a stop signal (by default ^Z).  To restart it, send a continue signal (such as by "kill -CONT <pid>").  If you really want to send a SIGSTOP to such a process (by ^Z), consider spawning csh first and then running your program.  On the other hand, if you want to send a SIGSTOP to Expect itself, first call interpreter (perhaps by using an escape character), and then press ^Z.
String-body pairs can be used as a shorthand for avoiding having to enter the interpreter and execute commands interactively.  The previous terminal mode is used while the body of a string-body pair is being executed.
For speed, actions execute in raw mode by default.  The -reset flag resets the terminal to the mode it had before interact was executed (invariably, cooked mode).  Note that characters entered when the mode is being switched may be lost (an unfortunate feature of the terminal driver on some systems).  The only reason to use -reset is if your action depends on running in cooked mode.
The -echo flag sends characters that match the following pattern back to the process that generated them as each character is read. This may be useful when the user needs to see feedback from partially typed patterns.
If a pattern is being echoed but eventually fails to match, the characters are sent to the spawned process.  If the spawned process then echoes them, the user will see the characters twice.  -echo is probably only appropriate in situations where the user is unlikely to not complete the pattern.  For example, the following excerpt is from rftp, the recursive-ftp script, where the user is prompted to enter ~g, ~p, or ~l, to get, put, or list the current directory recursively.  These are so far away from the normal ftp commands, that the user is unlikely to type ~ followed by anything else, except mistakenly, in which case, they'll probably just ignore the result anyway.
interact { -echo ~g {getcurdirectory 1} -echo ~l {getcurdirectory 0} -echo ~p {putcurdirectory} }
The -nobuffer flag sends characters that match the following pattern on to the output process as characters are read.
This is useful when you wish to let a program echo back the pattern.  For example, the following might be used to monitor where a person is dialing (a Hayes-style modem).  Each time "atd" is seen the script logs the rest of the line.
proc lognumber {} { interact -nobuffer -re "(.*)\r" return puts $log "[clock format [clock seconds]]: dialed $interact_out(1,string)" }
interact -nobuffer "atd" lognumber
During interact, previous use of log_user is ignored.  In particular, interact will force its output to be logged (sent to the standard output) since it is presumed the user doesn't wish to interact blindly.
The -o flag causes any following key-body pairs to be applied to the output of the current process.  This can be useful, for example, when dealing with hosts that send unwanted characters during a telnet session.
By default, interact expects the user to be writing stdin and reading stdout of the Expect process itself.  The -u flag (for "user") makes interact look for the user as the process named by its argument (which must be a spawned id).
This allows two unrelated processes to be joined together without using an explicit loop.  To aid in debugging, Expect diagnostics always go to stderr (or stdout for certain logging and debugging information).  For the same reason, the interpreter command will read interactively from stdin.
For example, the following fragment creates a login process.  Then it dials the user (not shown), and finally connects the two together.  Of course, any process may be substituted for login.  A shell, for example, would allow the user to work without supplying an account and password.
spawn login set login $spawn_id spawn tip modem # dial back out to user # connect user to login interact -u $login
To send output to multiple processes, list each spawn id list prefaced by a -output flag.  Input for a group of output spawn ids may be determined by a spawn id list prefaced by a -input flag. (Both -input and -output may take lists in the same form as the -i flag in the expect command, except that any_spawn_id is not meaningful in interact.)  All following flags and strings (or patterns) apply to this input until another -input flag appears. If no -input appears, -output implies "-input $user_spawn_id -output".  (Similarly, with patterns that do not have -input.)  If one -input is specified, it overrides $user_spawn_id.  If a second -input is specified, it overrides $spawn_id.  Additional -input flags may be specified.
The two implied input processes default to having their outputs specified as $spawn_id and $user_spawn_id (in reverse).  If a -input flag appears with no -output flag, characters from that process are discarded.
The -i flag introduces a replacement for the current spawn_id when no other -input or -output flags are used.  A -i flag implies a -o flag.
It is possible to change the processes that are being interacted with by using indirect spawn ids.  (Indirect spawn ids are described in the section on the expect command.)  Indirect spawn ids may be specified with the -i, -u, -input, or -output flags.
interpreter  [args] causes the user to be interactively prompted for Expect and Tcl commands.  The result of each command is printed.
Actions such as break and continue cause control structures (i.e., for, proc) to behave in the usual way.  However return causes interpreter to return to its caller, while inter_return causes interpreter to cause a return in its caller.  For example, if "proc foo" called interpreter which then executed the action inter_return, proc foo would return.  Any other command causes interpreter to continue prompting for new commands.
By default, the prompt contains two integers.  The first integer describes the depth of the evaluation stack (i.e., how many times Tcl_Eval has been called).  The second integer is the Tcl history identifier.  The prompt can be set by defining a procedure called "prompt1" whose return value becomes the next prompt.  If a statement has open quotes, parens, braces, or brackets, a secondary prompt (by default "+> ") is issued upon newline.  The secondary prompt may be set by defining a procedure called "prompt2".
During interpreter, cooked mode is used, even if the its caller was using raw mode.
If stdin is closed, interpreter will return unless the -eof flag is used, in which case the subsequent argument is invoked.
log_file [args] [[-a] file] If a filename is provided, log_file will record a transcript of the session (beginning at that point) in the file.  log_file will stop recording if no argument is given.  Any previous log file is closed.
Instead of a filename, a Tcl file identifier may be provided by using the -open or -leaveopen flags.  This is similar to the spawn command.  (See spawn for more info.)
The -a flag forces output to be logged that was suppressed by the log_user command.
By default, the log_file command appends to old files rather than truncating them, for the convenience of being able to turn logging off and on multiple times in one session.  To truncate files, use the -noappend flag.
The -info flag causes log_file to return a description of the most recent non-info arguments given.
log_user -info|0|1 By default, the send/expect dialogue is logged to stdout (and a logfile if open).  The logging to stdout is disabled by the command "log_user 0" and reenabled by "log_user 1".  Logging to the logfile is unchanged.
The -info flag causes log_user to return a description of the most recent non-info arguments given.
match_max [-d] [-i spawn_id] [size] defines the size of the buffer (in bytes) used internally by expect.  With no size argument, the current size is returned.
With the -d flag, the default size is set.  (The initial default is 2000.)  With the -i flag, the size is set for the named spawn id, otherwise it is set for the current process.
overlay [-# spawn_id] [-# spawn_id] [...] program [args] executes program args in place of the current Expect program, which terminates.  A bare hyphen argument forces a hyphen in front of the command name as if it was a login shell.  All spawn_ids are closed except for those named as arguments.  These are mapped onto the named file identifiers.
Spawn_ids are mapped to file identifiers for the new program to inherit.  For example, the following line runs chess and allows it to be controlled by the current process - say, a chess master.
overlay -0 $spawn_id -1 $spawn_id -2 $spawn_id chess
This is more efficient than "interact -u", however, it sacrifices the ability to do programmed interaction since the Expect process is no longer in control.
Note that no controlling terminal is provided.  Thus, if you disconnect or remap standard input, programs that do job control (shells, login, etc) will not function properly.
parity [-d] [-i spawn_id] [value] defines whether parity should be retained or stripped from the output of spawned processes.  If value is zero, parity is stripped, otherwise it is not stripped.  With no value argument, the current value is returned.
With the -d flag, the default parity value is set.  (The initial default is 1, i.e., parity is not stripped.)  With the -i flag, the parity value is set for the named spawn id, otherwise it is set for the current process.
remove_nulls [-d] [-i spawn_id] [value] defines whether nulls are retained or removed from the output of spawned processes before pattern matching or storing in the variable expect_out or interact_out.  If value is 1, nulls are removed.  If value is 0, nulls are not removed.  With no value argument, the current value is returned.
With the -d flag, the default value is set.  (The initial default is 1, i.e., nulls are removed.)  With the -i flag, the value is set for the named spawn id, otherwise it is set for the current process.
Whether or not nulls are removed, Expect will record null bytes to the log and stdout.
send [-flags] string Sends string to the current process.  For example, the command
send "hello world\r"
sends the characters, h e l l o <blank> w o r l d <return> to the current process.  (Tcl includes a printf-like command (called format) which can build arbitrarily complex strings.)
Characters are sent immediately although programs with line- buffered input will not read the characters until a return character is sent.  A return character is denoted "\r".
The -- flag forces the next argument to be interpreted as a string rather than a flag.  Any string can be preceded by "--" whether or not it actually looks like a flag.  This provides a reliable mechanism to specify variable strings without being tripped up by those that accidentally look like flags.  (All strings starting with "-" are reserved for future options.)
The -i flag declares that the string be sent to the named spawn_id. If the spawn_id is user_spawn_id, and the terminal is in raw mode, newlines in the string are translated to return-newline sequences so that they appear as if the terminal was in cooked mode.  The -raw flag disables this translation.
The -null flag sends null characters (0 bytes).  By default, one null is sent.  An integer may follow the -null to indicate how many nulls to send.
The -break flag generates a break condition.  This only makes sense if the spawn id refers to a tty device opened via "spawn -open". If you have spawned a process such as tip, you should use tip's convention for generating a break.
The -s flag forces output to be sent "slowly", thus avoid the common situation where a computer outtypes an input buffer that was designed for a human who would never outtype the same buffer.  This output is controlled by the value of the variable "send_slow" which takes a two element list.  The first element is an integer that describes the number of bytes to send atomically.  The second element is a real number that describes the number of seconds by which the atomic sends must be separated.  For example, "set send_slow {10 .001}" would force "send -s" to send strings with 1 millisecond in between each 10 characters sent.
The -h flag forces output to be sent (somewhat) like a human actually typing.  Human-like delays appear between the characters. (The algorithm is based upon a Weibull distribution, with modifications to suit this particular application.)  This output is controlled by the value of the variable "send_human" which takes a five element list.  The first two elements are average interarrival time of characters in seconds.  The first is used by default.  The second is used at word endings, to simulate the subtle pauses that occasionally occur at such transitions.  The third parameter is a measure of variability where .1 is quite variable, 1 is reasonably variable, and 10 is quite invariable.  The extremes are 0 to infinity.  The last two parameters are, respectively, a minimum and maximum interarrival time.  The minimum and maximum are used last and "clip" the final time.  The ultimate average can be quite different from the given average if the minimum and maximum clip enough values.
As an example, the following command emulates a fast and consistent typist:
set send_human {.1 .3 1 .05 2} send -h "I'm hungry.  Let's do lunch."
while the following might be more suitable after a hangover:
set send_human {.4 .4 .2 .5 100} send -h "Goodd party lash night!"
Note that errors are not simulated, although you can set up error correction situations yourself by embedding mistakes and corrections in a send argument.
The flags for sending null characters, for sending breaks, for forcing slow output and for human-style output are mutually exclusive. Only the one specified last will be used. Furthermore, no string argument can be specified with the flags for sending null characters or breaks.
It is a good idea to precede the first send to a process by an expect.  expect will wait for the process to start, while send cannot.  In particular, if the first send completes before the process starts running, you run the risk of having your data ignored.  In situations where interactive programs offer no initial prompt, you can precede send by a delay as in:
# To avoid giving hackers hints on how to break in, # this system does not prompt for an external password. # Wait for 5 seconds for exec to complete spawn telnet very.secure.gov sleep 5 send password\r
exp_send is an alias for send.  If you are using Expectk or some other variant of Expect in the Tk environment, send is defined by Tk for an entirely different purpose.  exp_send is provided for compatibility between environments.  Similar aliases are provided for other Expect's other send commands.
send_error [-flags] string is like send, except that the output is sent to stderr rather than the current process.
send_log [--] string is like send, except that the string is only sent to the log file (see log_file.)  The arguments are ignored if no log file is open.
send_tty [-flags] string is like send, except that the output is sent to /dev/tty rather than the current process.
send_user [-flags] string is like send, except that the output is sent to stdout rather than the current process.
sleep seconds causes the script to sleep for the given number of seconds. Seconds may be a decimal number.  Interrupts (and Tk events if you are using Expectk) are processed while Expect sleeps.
spawn [args] program [args] creates a new process running program args.  Its stdin, stdout and stderr are connected to Expect, so that they may be read and written by other Expect commands.  The connection is broken by close or if the process itself closes any of the file identifiers.
When a process is started by spawn, the variable spawn_id is set to a descriptor referring to that process.  The process described by spawn_id is considered the current process.  spawn_id may be read or written, in effect providing job control.
user_spawn_id is a global variable containing a descriptor which refers to the user.  For example, when spawn_id is set to this value, expect behaves like expect_user.
error_spawn_id is a global variable containing a descriptor which refers to the standard error.  For example, when spawn_id is set to this value, send behaves like send_error.
tty_spawn_id is a global variable containing a descriptor which refers to /dev/tty.  If /dev/tty does not exist (such as in a cron, at, or batch script), then tty_spawn_id is not defined.  This may be tested as:
if {[info vars tty_spawn_id]} { # /dev/tty exists } else { # /dev/tty doesn't exist # probably in cron, batch, or at script }
spawn returns the UNIX process id.  If no process is spawned, 0 is returned.  The variable spawn_out(slave,name) is set to the name of the pty slave device.
By default, spawn echoes the command name and arguments.  The -noecho flag stops spawn from doing this.
The -console flag causes console output to be redirected to the spawned process.  This is not supported on all systems.
Internally, spawn uses a pty, initialized the same way as the user's tty.  This is further initialized so that all settings are "sane" (according to stty(1)).  If the variable stty_init is defined, it is interpreted in the style of stty arguments as further configuration.  For example, "set stty_init raw" will cause further spawned processes's terminals to start in raw mode. -nottycopy skips the initialization based on the user's tty. -nottyinit skips the "sane" initialization.
Normally, spawn takes little time to execute.  If you notice spawn taking a significant amount of time, it is probably encountering ptys that are wedged.  A number of tests are run on ptys to avoid entanglements with errant processes.  (These take 10 seconds per wedged pty.)  Running Expect with the -d option will show if Expect is encountering many ptys in odd states.  If you cannot kill the processes to which these ptys are attached, your only recourse may be to reboot.
If program cannot be spawned successfully because exec(2) fails (e.g. when program doesn't exist), an error message will be returned by the next interact or expect command as if program had run and produced the error message as output.  This behavior is a natural consequence of the implementation of spawn.  Internally, spawn forks, after which the spawned process has no way to communicate with the original Expect process except by communication via the spawn_id.
The -open flag causes the next argument to be interpreted as a Tcl file identifier (i.e., returned by open.)  The spawn id can then be used as if it were a spawned process.  (The file identifier should no longer be used.)  This lets you treat raw devices, files, and pipelines as spawned processes without using a pty.  0 is returned to indicate there is no associated process.  When the connection to the spawned process is closed, so is the Tcl file identifier.  The -leaveopen flag is similar to -open except that -leaveopen causes the file identifier to be left open even after the spawn id is closed.
The -pty flag causes a pty to be opened but no process spawned.  0 is returned to indicate there is no associated process.  Spawn_id is set as usual.
The variable spawn_out(slave,fd) is set to a file identifier corresponding to the pty slave.  It can be closed using "close -slave".
The -ignore flag names a signal to be ignored in the spawned process.  Otherwise, signals get the default behavior.  Signals are named as in the trap command, except that each signal requires a separate flag.
strace level causes following statements to be printed before being executed. (Tcl's trace command traces variables.)  level indicates how far down in the call stack to trace.  For example, the following command runs Expect while tracing the first 4 levels of calls, but none below that.
expect -c "strace 4" script.exp
The -info flag causes strace to return a description of the most recent non-info arguments given.
stty args changes terminal modes similarly to the external stty command.
By default, the controlling terminal is accessed.  Other terminals can be accessed by appending "< /dev/tty..." to the command.  (Note that the arguments should not be grouped into a single argument.)
Requests for status return it as the result of the command.  If no status is requested and the controlling terminal is accessed, the previous status of the raw and echo attributes are returned in a form which can later be used by the command.
For example, the arguments raw or -cooked put the terminal into raw mode.  The arguments -raw or cooked put the terminal into cooked mode.  The arguments echo and -echo put the terminal into echo and noecho mode respectively.
The following example illustrates how to temporarily disable echoing.  This could be used in otherwise-automatic scripts to avoid embedding passwords in them.  (See more discussion on this under EXPECT HINTS below.)
stty -echo send_user "Password: " expect_user -re "(.*)\n" set password $expect_out(1,string) stty echo
system args gives args to sh(1) as input, just as if it had been typed as a command from a terminal.  Expect waits until the shell terminates. The return status from sh is handled the same way that exec handles its return status.
In contrast to exec which redirects stdin and stdout to the script, system performs no redirection (other than that indicated by the string itself).  Thus, it is possible to use programs which must talk directly to /dev/tty.  For the same reason, the results of system are not recorded in the log.
timestamp [args] returns a timestamp.  With no arguments, the number of seconds since the epoch is returned.
The -format flag introduces a string which is returned but with substitutions made according to the POSIX rules for strftime.  For example %a is replaced by an abbreviated weekday name (i.e., Sat). Others are: %a      abbreviated weekday name %A      full weekday name %b      abbreviated month name %B      full month name %c      date-time as in: Wed Oct  6 11:45:56 1993 %d      day of the month (01-31) %H      hour (00-23) %I      hour (01-12) %j      day (001-366) %m      month (01-12) %M      minute (00-59) %p      am or pm %S      second (00-61) %u      day (1-7, Monday is first day of week) %U      week (00-53, first Sunday is first day of week one) %V      week (01-53, ISO 8601 style) %w      day (0-6) %W      week (00-53, first Monday is first day of week one) %x      date-time as in: Wed Oct  6 1993 %X      time as in: 23:59:59 %y      year (00-99) %Y      year as in: 1993 %Z      timezone (or nothing if not determinable) %%      a bare percent sign
Other % specifications are undefined.  Other characters will be passed through untouched.  Only the C locale is supported.
The -seconds flag introduces a number of seconds since the epoch to be used as a source from which to format.  Otherwise, the current time is used.
The -gmt flag forces timestamp output to use the GMT timezone. With no flag, the local timezone is used.
trap [[command] signals] causes the given command to be executed upon future receipt of any of the given signals.  The command is executed in the global scope. If command is absent, the signal action is returned.  If command is the string SIG_IGN, the signals are ignored.  If command is the string SIG_DFL, the signals are result to the system default. signals is either a single signal or a list of signals.  Signals may be specified numerically or symbolically as per signal(3).  The "SIG" prefix may be omitted.
With no arguments (or the argument -number), trap returns the signal number of the trap command currently being executed.
The -code flag uses the return code of the command in place of whatever code Tcl was about to return when the command originally started running.
The -interp flag causes the command to be evaluated using the interpreter active at the time the command started running rather than when the trap was declared.
The -name flag causes the trap command to return the signal name of the trap command currently being executed.
The -max flag causes the trap command to return the largest signal number that can be set.
For example, the command "trap {send_user "Ouch!"} SIGINT" will print "Ouch!"  each time the user presses ^C.
By default, SIGINT (which can usually be generated by pressing ^C) and SIGTERM cause Expect to exit.  This is due to the following trap, created by default when Expect starts.
trap exit {SIGINT SIGTERM}
If you use the -D flag to start the debugger, SIGINT is redefined to start the interactive debugger.  This is due to the following trap:
trap {exp_debug 1} SIGINT
The debugger trap can be changed by setting the environment variable EXPECT_DEBUG_INIT to a new trap command.
You can, of course, override both of these just by adding trap commands to your script.  In particular, if you have your own "trap exit SIGINT", this will override the debugger trap.  This is useful if you want to prevent users from getting to the debugger at all.
If you want to define your own trap on SIGINT but still trap to the debugger when it is running, use:
if {![exp_debug]} {trap mystuff SIGINT}
Alternatively, you can trap to the debugger using some other signal.
trap will not let you override the action for SIGALRM as this is used internally to Expect.  The disconnect command sets SIGALRM to SIG_IGN (ignore).  You can reenable this as long as you disable it during subsequent spawn commands.
See signal(3) for more info.
wait [args] delays until a spawned process (or the current process if none is named) terminates.
wait normally returns a list of four integers.  The first integer is the pid of the process that was waited upon.  The second integer is the corresponding spawn id.  The third integer is -1 if an operating system error occurred, or 0 otherwise.  If the third integer was 0, the fourth integer is the status returned by the spawned process.  If the third integer was -1, the fourth integer is the value of errno set by the operating system.  The global variable errorCode is also set.
Additional elements may appear at the end of the return value from wait.  An optional fifth element identifies a class of information. Currently, the only possible value for this element is CHILDKILLED in which case the next two values are the C-style signal name and a short textual description.
The -i flag declares the process to wait corresponding to the named spawn_id (NOT the process id).  Inside a SIGCHLD handler, it is possible to wait for any spawned process by using the spawn id -1.
The -nowait flag causes the wait to return immediately with the indication of a successful wait.  When the process exits (later), it will automatically disappear without the need for an explicit wait.
The wait command may also be used wait for a forked process using the arguments "-i -1".  Unlike its use with spawned processes, this command can be executed at any time.  There is no control over which process is reaped.  However, the return value can be checked for the process id.
Expect automatically knows about two built-in libraries for Expect scripts.  These are defined by the directories named in the variables exp_library and exp_exec_library.  Both are meant to contain utility files that can be used by other scripts.
exp_library contains architecture-independent files.  exp_exec_library contains architecture-dependent files.  Depending on your system, both directories may be totally empty.  The existence of the file $exp_exec_library/cat-buffers describes whether your /bin/cat buffers by default.
PRETTY-PRINTING A vgrind definition is available for pretty-printing Expect scripts. Assuming the vgrind definition supplied with the Expect distribution is correctly installed, you can use it as:
vgrind -lexpect file
It many not be apparent how to put everything together that the man page describes.  I encourage you to read and try out the examples in the example directory of the Expect distribution.  Some of them are real programs.  Others are simply illustrative of certain techniques, and of course, a couple are just quick hacks.  The INSTALL file has a quick overview of these programs.
The Expect papers (see SEE ALSO) are also useful.  While some papers use syntax corresponding to earlier versions of Expect, the accompanying rationales are still valid and go into a lot more detail than this man page.
Extensions may collide with Expect's command names.  For example, send is defined by Tk for an entirely different purpose.  For this reason, most of the Expect commands are also available as "exp_XXXX".  Commands and variables beginning with "exp", "inter", "spawn", and "timeout" do not have aliases.  Use the extended command names if you need this compatibility between environments.
Expect takes a rather liberal view of scoping.  In particular, variables read by commands specific to the Expect program will be sought first from the local scope, and if not found, in the global scope.  For example, this obviates the need to place "global timeout" in every procedure you write that uses expect.  On the other hand, variables written are always in the local scope (unless a "global" command has been issued).  The most common problem this causes is when spawn is executed in a procedure. Outside the procedure, spawn_id no longer exists, so the spawned process is no longer accessible simply because of scoping.  Add a "global spawn_id" to such a procedure.
If you cannot enable the multispawning capability (i.e., your system supports neither select (BSD *.*), poll (SVR>2), nor something equivalent), Expect will only be able to control a single process at a time.  In this case, do not attempt to set spawn_id, nor should you execute processes via exec while a spawned process is running. Furthermore, you will not be able to expect from multiple processes (including the user as one) at the same time.
Terminal parameters can have a big effect on scripts.  For example, if a script is written to look for echoing, it will misbehave if echoing is turned off.  For this reason, Expect forces sane terminal parameters by default.  Unfortunately, this can make things unpleasant for other programs.  As an example, the emacs shell wants to change the "usual" mappings: newlines get mapped to newlines instead of carriage-return newlines, and echoing is disabled.  This allows one to use emacs to edit the input line.  Unfortunately, Expect cannot possibly guess this.
You can request that Expect not override its default setting of terminal parameters, but you must then be very careful when writing scripts for such environments.  In the case of emacs, avoid depending upon things like echoing and end-of-line mappings.
The commands that accepted arguments braced into a single list (the expect variants and interact) use a heuristic to decide if the list is actually one argument or many.  The heuristic can fail only in the case when the list actually does represent a single argument which has multiple embedded \n's with non-whitespace characters between them.  This seems sufficiently improbable, however the argument "-nobrace" can be used to force a single argument to be handled as a single argument.  This could conceivably be used with machine-generated Expect code.  Similarly, -brace forces a single argument to be handle as multiple patterns/actions.
It was really tempting to name the program "sex" (for either "Smart EXec" or "Send-EXpect"), but good sense (or perhaps just Puritanism) prevailed.
On some systems, when a shell is spawned, it complains about not being able to access the tty but runs anyway.  This means your system has a mechanism for gaining the controlling tty that Expect doesn't know about. Please find out what it is, and send this information back to me.
Ultrix 4.1 (at least the latest versions around here) considers timeouts of above 1000000 to be equivalent to 0.
Digital UNIX 4.0A (and probably other versions) refuses to allocate ptys if you define a SIGCHLD handler.  See grantpt page for more info.
IRIX 6.0 does not handle pty permissions correctly so that if Expect attempts to allocate a pty previously used by someone else, it fails. Upgrade to IRIX 6.1.
Telnet (verified only under SunOS 4.1.2) hangs if TERM is not set.  This is a problem under cron, at and in cgi scripts, which do not define TERM. Thus, you must set it explicitly - to what type is usually irrelevant. It just has to be set to something!  The following probably suffices for most cases.
set env(TERM) vt100
Tip (verified only under BSDI BSD/OS 3.1 i386) hangs if SHELL and HOME are not set.  This is a problem under cron, at and in cgi scripts, which do not define these environment variables.  Thus, you must set them explicitly - to what type is usually irrelevant.  It just has to be set to something!  The following probably suffices for most cases.
set env(SHELL) /bin/sh set env(HOME) /usr/local/bin
Some implementations of ptys are designed so that the kernel throws away any unread output after 10 to 15 seconds (actual number is implementation-dependent) after the process has closed the file descriptor.  Thus Expect programs such as
spawn date sleep 20 expect
will fail.  To avoid this, invoke non-interactive programs with exec rather than spawn.  While such situations are conceivable, in practice I have never encountered a situation in which the final output of a truly interactive program would be lost due to this behavior.
On the other hand, Cray UNICOS ptys throw away any unread output immediately after the process has closed the file descriptor.  I have reported this to Cray and they are working on a fix.
Sometimes a delay is required between a prompt and a response, such as when a tty interface is changing UART settings or matching baud rates by looking for start/stop bits.  Usually, all this is require is to sleep for a second or two.  A more robust technique is to retry until the hardware is ready to receive input.  The following example uses both strategies:
send "speed 9600\r"; sleep 1 expect { timeout {send "\r"; exp_continue} $prompt }
trap -code will not work with any command that sits in Tcl's event loop, such as sleep.  The problem is that in the event loop, Tcl discards the return codes from async event handlers.  A workaround is to set a flag in the trap code.  Then check the flag immediately after the command (i.e., sleep).
The expect_background command ignores -timeout arguments and has no concept of timeouts in general.
There are a couple of things about Expect that may be non-intuitive. This section attempts to address some of these things with a couple of suggestions.
A common expect problem is how to recognize shell prompts.  Since these are customized differently by differently people and different shells, portably automating rlogin can be difficult without knowing the prompt. A reasonable convention is to have users store a regular expression describing their prompt (in particular, the end of it) in the environment variable EXPECT_PROMPT.  Code like the following can be used.  If EXPECT_PROMPT doesn't exist, the code still has a good chance of functioning correctly.
set prompt "(%|#|\\$) $"          ;# default prompt catch {set prompt $env(EXPECT_PROMPT)}
expect -re $prompt
I encourage you to write expect patterns that include the end of whatever you expect to see.  This avoids the possibility of answering a question before seeing the entire thing.  In addition, while you may well be able to answer questions before seeing them entirely, if you answer early, your answer may appear echoed back in the middle of the question.  In other words, the resulting dialogue will be correct but look scrambled.
Most prompts include a space character at the end.  For example, the prompt from ftp is 'f', 't', 'p', '>' and <blank>.  To match this prompt, you must account for each of these characters.  It is a common mistake not to include the blank.  Put the blank in explicitly.
If you use a pattern of the form X*, the * will match all the output received from the end of X to the last thing received.  This sounds intuitive but can be somewhat confusing because the phrase "last thing received" can vary depending upon the speed of the computer and the processing of I/O both by the kernel and the device driver.
In particular, humans tend to see program output arriving in huge chunks (atomically) when in reality most programs produce output one line at a time.  Assuming this is the case, the * in the pattern of the previous paragraph may only match the end of the current line even though there seems to be more, because at the time of the match that was all the output that had been received.
expect has no way of knowing that further output is coming unless your pattern specifically accounts for it.
Even depending on line-oriented buffering is unwise.  Not only do programs rarely make promises about the type of buffering they do, but system indigestion can break output lines up so that lines break at seemingly random places.  Thus, if you can express the last few characters of a prompt when writing patterns, it is wise to do so.
If you are waiting for a pattern in the last output of a program and the program emits something else instead, you will not be able to detect that with the timeout keyword.  The reason is that expect will not timeout - instead it will get an eof indication.  Use that instead.  Even better, use both.  That way if that line is ever moved around, you won't have to edit the line itself.
Newlines are usually converted to carriage return, linefeed sequences when output by the terminal driver.  Thus, if you want a pattern that explicitly matches the two lines, from, say, printf("foo\nbar"), you should use the pattern "foo\r\nbar".
A similar translation occurs when reading from the user, via expect_user. In this case, when you press return, it will be translated to a newline. If Expect then passes that to a program which sets its terminal to raw mode (like telnet), there is going to be a problem, as the program expects a true return.  (Some programs are actually forgiving in that they will automatically translate newlines to returns, but most don't.) Unfortunately, there is no way to find out that a program put its terminal into raw mode.
Rather than manually replacing newlines with returns, the solution is to use the command "stty raw", which will stop the translation.  Note, however, that this means that you will no longer get the cooked line- editing features.
interact implicitly sets your terminal to raw mode so this problem will not arise then.
It is often useful to store passwords (or other private information) in Expect scripts.  This is not recommended since anything that is stored on a computer is susceptible to being accessed by anyone.  Thus, interactively prompting for passwords from a script is a smarter idea than embedding them literally.  Nonetheless, sometimes such embedding is the only possibility.
Unfortunately, the UNIX file system has no direct way of creating scripts which are executable but unreadable.  Systems which support setgid shell scripts may indirectly simulate this as follows:
Create the Expect script (that contains the secret data) as usual.  Make its permissions be 750 (-rwxr-x---) and owned by a trusted group, i.e., a group which is allowed to read it.  If necessary, create a new group for this purpose.  Next, create a /bin/sh script with permissions 2751 (-rwxr-s--x) owned by the same group as before.
The result is a script which may be executed (and read) by anyone.  When invoked, it runs the Expect script.
Tcl(3), libexpect(3) "Exploring Expect: A Tcl-Based Toolkit for Automating Interactive Programs" by Don Libes, pp. 602, ISBN 1-56592-090-2, O'Reilly and Associates, 1995. "expect: Curing Those Uncontrollable Fits of Interactivity" by Don Libes, Proceedings of the Summer 1990 USENIX Conference, Anaheim, California, June 11-15, 1990. "Using expect to Automate System Administration Tasks" by Don Libes, Proceedings of the 1990 USENIX Large Installation Systems Administration Conference, Colorado Springs, Colorado, October 17-19, 1990. "Tcl: An Embeddable Command Language" by John Ousterhout, Proceedings of the Winter 1990 USENIX Conference, Washington, D.C., January 22-26, 1990. "expect: Scripts for Controlling Interactive Programs" by Don Libes, Computing Systems, Vol. 4, No. 2, University of California Press Journals, November 1991. "Regression Testing and Conformance Testing Interactive Programs", by Don Libes, Proceedings of the Summer 1992 USENIX Conference, pp. 135-144, San Antonio, TX, June 12-15, 1992. "Kibitz - Connecting Multiple Interactive Programs Together", by Don Libes, Software - Practice & Experience, John Wiley & Sons, West Sussex, England, Vol. 23, No. 5, May, 1993. "A Debugger for Tcl Applications", by Don Libes, Proceedings of the 1993 Tcl/Tk Workshop, Berkeley, CA, June 10-11, 1993.
Don Libes, National Institute of Standards and Technology
Thanks to John Ousterhout for Tcl, and Scott Paisley for inspiration. Thanks to Rob Savoye for Expect's autoconfiguration code.
The HISTORY file documents much of the evolution of expect.  It makes interesting reading and might give you further insight to this software. Thanks to the people mentioned in it who sent me bug fixes and gave other assistance.
Design and implementation of Expect was paid for in part by the U.S. government and is therefore in the public domain.  However the author and NIST would like credit if this program and documentation or portions of them are used.
GOBUSTER(1)                       User Commands                      GOBUSTER(1)
gobuster - Directory/file & DNS busting tool
-P string
Password for Basic Auth (dir mode only)
-U string
Username for Basic Auth (dir mode only)
-a string
Set the User-Agent string (dir mode only)
-c string
Cookies to use for the requests (dir mode only)
Show CNAME records (dns mode only, cannot be used with '-i' option)
-e     Expanded mode, print full URLs
-f     Append a forward-slash to each directory request (dir mode only)
Force continued operation when wildcard found
-i     Show IP addresses (dns mode only)
-k     Skip SSL certificate verification
-l     Include the length of the body in the output (dir mode only)
-m string
Directory/File mode (dir) or DNS mode (dns) (default "dir")
-n     Don't print status codes
-o string
Output file to write results to (defaults to stdout)
-p string
Proxy to use for requests [http(s)://host:port] (dir mode only)
-q     Don't print the banner and other noise
-r     Follow redirects
-s string
Positive status codes (dir mode only) (default "200,204,301,302,307")
-t int
Number of concurrent threads (default 10)
-u string
The target URL or Domain
-v     Verbose output (errors)
-w string
Path to the wordlist
-x string
File extension(s) to search for (dir mode only)
XARGS(1)                     General Commands Manual                    XARGS(1)
xargs - build and execute command lines from standard input
xargs [options] [command [initial-arguments]]
This manual page documents the GNU version of xargs.  xargs reads items from the standard input, delimited by blanks (which can be protected with double or single quotes or a backslash) or newlines, and executes the command (default is /bin/echo) one or more times with any initial- arguments followed by items read from standard input.  Blank lines on the standard input are ignored.
The command line for command is built up until it reaches a system- defined limit (unless the -n and -L options are used).  The specified command will be invoked as many times as necessary to use up the list of input items.  In general, there will be many fewer invocations of command than there were items in the input.  This will normally have significant performance benefits.  Some commands can usefully be executed in parallel too; see the -P option.
Because Unix filenames can contain blanks and newlines, this default behaviour is often problematic; filenames containing blanks and/or newlines are incorrectly processed by xargs.  In these situations it is better to use the -0 option, which prevents such problems.   When using this option you will need to ensure that the program which produces the input for xargs also uses a null character as a separator.  If that program is GNU find for example, the -print0 option does this for you.
If any invocation of the command exits with a status of 255, xargs will stop immediately without reading any further input.  An error message is issued on stderr when this happens.
-0, --null Input items are terminated by a null character instead of by whitespace, and the quotes and backslash are not special (every character is taken literally).  Disables the end of file string, which is treated like any other argument.  Useful when input items might contain white space, quote marks, or backslashes.  The GNU find -print0 option produces input suitable for this mode.
-a file, --arg-file=file Read items from file instead of standard input.  If you use this option, stdin remains unchanged when commands are run.  Otherwise, stdin is redirected from /dev/null.
--delimiter=delim, -d delim Input items are terminated by the specified character.  The specified delimiter may be a single character, a C-style character escape such as \n, or an octal or hexadecimal escape code.  Octal and hexadecimal escape codes are understood as for the printf command.   Multibyte characters are not supported.  When processing the input, quotes and backslash are not special; every character in the input is taken literally.  The -d option disables any end-of-file string, which is treated like any other argument. You can use this option when the input consists of simply newline- separated items, although it is almost always better to design your program to use --null where this is possible.
-E eof-str Set the end of file string to eof-str.  If the end of file string occurs as a line of input, the rest of the input is ignored.  If neither -E nor -e is used, no end of file string is used.
-e[eof-str], --eof[=eof-str] This option is a synonym for the -E option.  Use -E instead, because it is POSIX compliant while this option is not.  If eof- str is omitted, there is no end of file string.  If neither -E nor -e is used, no end of file string is used.
-I replace-str Replace occurrences of replace-str in the initial-arguments with names read from standard input.  Also, unquoted blanks do not terminate input items; instead the separator is the newline character.  Implies -x and -L 1.
-i[replace-str], --replace[=replace-str] This option is a synonym for -Ireplace-str if replace-str is specified.  If the replace-str argument is missing, the effect is the same as -I{}.  This option is deprecated; use -I instead.