Simulate "Enter" Key in script

[Dick Fischer]

We use RCS as our program configuration management software in unix. I'm attempting to create a unix script to automate the checkin process of 100+ programs that are modified every time there's a timechange.

Typically one keys text into RCS, and RCS waits for the "Enter" key before going on to the next command. The checkin process does not complete until a period (.) is entered on the final step. The unix script would have a series of RCS commands for each of the 100+ modules. Is there a way of coding the "Enter" key into the script? I've tried a few things, but the script just hangs after the first command.

A typical series of commands would be:

ci -l filename <== checkin and lock filename

??? <== Hit Enter

Time change <== text keyed in explaining what the modification was

??? <== Hit Enter

Changed by yours truly <== second line of text keyed in

??? <== Hit Enter

. <== Period (.) to indicate that I'm done entering text

??? <== Hit Enter

The last "Enter" will indicate that I'm done with the checkin, and RCS will be exited.

[Geoff Wild]

You can do this with an expect script...

http://hpux.ee.ualberta.ca/hppd/hpux/Tcl/expect-5.41/

Rgds...Geoff

[Victor Fridyev]

Hi

Try the following:
echo "\n\n\n...\n"| your_script
or this:
your_script<<$$END_OF_INPUT




$$END_OF_INPUT

Each empty string is ENTER

HTH

[Rodney Hills]

So doing something like-
echo "\n\n\n\n" | ci -l filename

Doesn't work?

Hmmm... Maybe ci reads from STDERR. Try-
echo "\n\n\n\n" | ci -l filename 2<&0

See if that works...

-- Rod Hills

[Dick Fischer]

The ci -l filename command will execute whether I stick an echo statement in front of it or not.

Beyond that point the process is hanging no matter what variations of echo or END_OF_DATA statements I try.

[Rodney Hills]

If "ci" is like "passwd" command, then as stated before, "expect" utility is the best way to drive the input.

-- Rod Hills

[Sundar_7]

I am not sure if I fuly understand your requirement

I will give it a try :-)

ci -l filename <echo "Time Change"
echo "Changed by yours truly"
echo "."
EOF

will this work for you ?

[Tom Danzig · Accepted solution]

I would think that a "here doc" would work in a script:


A typical series of commands would be:


################################
ci -l filename <
text explaining what the mod was
second line of text
.

EOD
################################


The blank lines above should feed in as "Enter" to the ci program.

[Dick Fischer]

The EOD solution did the trick. Thank you all for your suggestions.

[Dick Fischer]

Thread is closed. Thanks again for taking the time to give suggestions.