 -ReMove_file(1)

NAME
-ReMove_file - add files to be deleted to a change

SYNOPSIS
-ReMove_file file-name... [ option... ]
-ReMove_file -List [ option... ]
-ReMove_file -Help

DESCRIPTION
The -ReMove_file command is used to add files to be deleted to a change. The file will be added to the list of files in the change, and will be removed from the baseline at integration time.

This command may be used to remove tests, not just source files. Tests are treated just like any other source file, and are subject to the same process.

A file will be created in the development directory containing 1KB of random text. The random text is sufficiently revolting that most compilers will give error messages, should the file be referenced accidentally. This is often very helpful when removing include files.

You may specify a directory name to remove all files in the named directory tree. It is an error if there are no relevant files.

  Process Side Effects
This command will cancel any build or test registrations, because adding a file logically invalidates them.

When the change files are listed ( -List Change_Files -TERse) the removed files will not appear in the terse listing. Similarly, when the project files are listed with an explicit change number ( -List Project_Files -TERse -Change N) none of the change's files, including the the removed files, will not appear in the terse listing. These two features are very helpful when calling from within a DMT to generate the list of source files.

  Notification
The remove_file_command in the project config file is run, if set. The project_file_command is also run, if set, and if there has been an integration recently. See aepconf(5) for more information.

OPTIONS
The following options are understood:

RECOMMENDED ALIAS
The recommended alias for this command is
csh%	alias aerm ' -rm \!* -v'
sh$	aerm(){ -rm "$@" -v}

ERRORS
It is an error if the change is not in the being developed state.
It is an error if the change is not assigned to the current user.
It is an error if the file does not exist in the baseline.
It is an error if the file is already part of the change.

SEE ALSO

aecp(1)
    copy files into a change

aedb(1)
    begin development of a change

aemv(1)
    rename a file as part of a change

aenf(1)
    add files to be created to a change

aermu(1)
    remove files to be deleted from a change

aeuconf(5)
    user configuration file format