Sponsored Content
Top Forums UNIX for Dummies Questions & Answers RCS register a file without the prompt Post 302499676 by js8765 on Friday 25th of February 2011 04:52:38 AM
Old 02-25-2011
RCS register a file without the prompt

Hi there,

I'm very new to UNIX. I'm writing a script (tcsh / Solaris) in which a file is created and then it needs to be registered using RCS. The problem is that on running the command "ci -u myfile" I keep getting prompted to "enter description, terminated with single '.' or end of file:"

Is there any way to run this command in a script without having to input the description manually? The -m option only seems to work after the file has been initially registered and does not seem to work the first time you try to check in a file.

Thanks for any help!
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

RCS, what is it? how do i install it...

One of our DBAs is requesting RCS be installed on one of our boxes...what is it? Where do I get it from? Thanks. (2 Replies)
Discussion started by: debaire
2 Replies

2. UNIX for Dummies Questions & Answers

RCS Question

I am a new user. Can anyone tell me where I can get documentation on the RCS feature? Thanks (1 Reply)
Discussion started by: Terry
1 Replies

3. UNIX for Advanced & Expert Users

rcs,sccs

I am not really sure whether i am posting this question in the right forum.....Can someone tell me why I should go for a rational Clearcase version controller when I can use the version controllers 'rcs' or 'sccs' available in UNIX. I want to know the advantage of Rational over these two. Also, I... (2 Replies)
Discussion started by: Abhishek Ghose
2 Replies

4. UNIX for Dummies Questions & Answers

Rcs

does anyone know if RCS is part of UNIX? Does a copy come with all UNIX systesm? Is it a seperate program? Is it purchased? Or is RSC a freeware program downloaded for everyone to use? (3 Replies)
Discussion started by: rtoba
3 Replies

5. UNIX for Advanced & Expert Users

RCS - Find difference between 2 different versions of a file

Hi, I have a c file in my repository. We are using RCS(Revision Control System) to control and manage the versions. I need to find 1. Difference between the current version with a different version 2. Difference between any two different versions of a file. Ex Difference between 1.14 and... (1 Reply)
Discussion started by: kelangovan
1 Replies

6. Shell Programming and Scripting

creating an RCS archive in /etc

Hi Why is creating an RCS archive in /etc a "good thing"? Hi Why is creating an RCS archive in /etc a "good thing"? (2 Replies)
Discussion started by: scofiled83
2 Replies

7. Shell Programming and Scripting

RCS archive in /etc

Well it is not a bad idea. I have worked for one place that did that. It wasn't my idea but I did not object. The reason it is done is to put critical files like nsswitch.conf, hosts, and so on under RCS control. Previous versions are then available to see how stuff changed over the years. ... (0 Replies)
Discussion started by: Perderabo
0 Replies

8. UNIX for Dummies Questions & Answers

RCS Register a file without the "This is NOT the log" prompt

Hi, I was wondering if anyone knows the command (using Solaris) to register a file in RCS without getting the prompt to enter a description. Thanks for any help! js (0 Replies)
Discussion started by: js8765
0 Replies

9. UNIX for Dummies Questions & Answers

RCS Issue

Hi there, I am trying to utalise RCS on unix. I am including the following tags in my source code for RCS to populate based on rlog. #$Author:$ #$Log:$ Everything i have read on the "co" man page of RCS indicates that the lines from the Log will be populated in the source file using the same... (0 Replies)
Discussion started by: cdoyle
0 Replies
after(n)						       Tcl Built-In Commands							  after(n)

__________________________________________________________________________________________________________________________________________________

NAME
after - Execute a command after a time delay SYNOPSIS
after ms after ms ?script script script ...? after cancel id after cancel script script script ... after idle ?script script script ...? after info ?id? _________________________________________________________________ DESCRIPTION
This command is used to delay execution of the program or to execute a command in background sometime in the future. It has several forms, depending on the first argument to the command: after ms Ms must be an integer giving a time in milliseconds. The command sleeps for ms milliseconds and then returns. While the command is sleeping the application does not respond to events. after ms ?script script script ...? In this form the command returns immediately, but it arranges for a Tcl command to be executed ms milliseconds later as an event handler. The command will be executed exactly once, at the given time. The delayed command is formed by concatenating all the script arguments in the same fashion as the concat command. The command will be executed at global level (outside the context of any Tcl procedure). If an error occurs while executing the delayed command then the background error will be reported by the com- mand registered with interp bgerror. The after command returns an identifier that can be used to cancel the delayed command using after cancel. after cancel id Cancels the execution of a delayed command that was previously scheduled. Id indicates which command should be canceled; it must have been the return value from a previous after command. If the command given by id has already been executed then the after can- cel command has no effect. after cancel script script ... This command also cancels the execution of a delayed command. The script arguments are concatenated together with space separators (just as in the concat command). If there is a pending command that matches the string, it is cancelled and will never be executed; if no such command is currently pending then the after cancel command has no effect. after idle script ?script script ...? Concatenates the script arguments together with space separators (just as in the concat command), and arranges for the resulting script to be evaluated later as an idle callback. The script will be run exactly once, the next time the event loop is entered and there are no events to process. The command returns an identifier that can be used to cancel the delayed command using after can- cel. If an error occurs while executing the script then the background error will be reported by the command registered with interp bgerror. after info ?id? This command returns information about existing event handlers. If no id argument is supplied, the command returns a list of the identifiers for all existing event handlers created by the after command for this interpreter. If id is supplied, it specifies an existing handler; id must have been the return value from some previous call to after and it must not have triggered yet or been cancelled. In this case the command returns a list with two elements. The first element of the list is the script associated with id, and the second element is either idle or timer to indicate what kind of event handler it is. The after ms and after idle forms of the command assume that the application is event driven: the delayed commands will not be executed unless the application enters the event loop. In applications that are not normally event-driven, such as tclsh, the event loop can be entered with the vwait and update commands. EXAMPLES
This defines a command to make Tcl do nothing at all for N seconds: proc sleep {N} { after [expr {int($N * 1000)}] } This arranges for the command wake_up to be run in eight hours (providing the event loop is active at that time): after [expr {1000 * 60 * 60 * 8}] wake_up The following command can be used to do long-running calculations (as represented here by ::my_calc::one_step, which is assumed to return a boolean indicating whether another step should be performed) in a step-by-step fashion, though the calculation itself needs to be arranged so it can work step-wise. This technique is extra careful to ensure that the event loop is not starved by the rescheduling of processing steps (arranging for the next step to be done using an already-triggered timer event only when the event queue has been drained) and is useful when you want to ensure that a Tk GUI remains responsive during a slow task. proc doOneStep {} { if {[::my_calc::one_step]} { after idle [list after 0 doOneStep] } } doOneStep SEE ALSO
concat(n), interp(n), update(n), vwait(n) KEYWORDS
cancel, delay, idle callback, sleep, time Tcl 7.5 after(n)
All times are GMT -4. The time now is 03:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy