 -Make_Transparent_Undo(1)

NAME
-Make_Transparent_Undo - no longer make branch file transparent

SYNOPSIS
-Make_Transparent_Undo [ option... ] filename...
-Make_Transparent_Undo -List
-Make_Transparent_Undo -Help

DESCRIPTION
The -Make_Transparent_Undo command is used to reverse the effects of the -Make_Transparent command. The named files will be removed from the list of files in the change.

The file is deleted from the development directory unless the -Keep option is specified. The -Keep option should be used with great care, as you can confuse tools such as make(1) by leaving these files in place.

You may name a directory to delete from the change all files in that directory tree previously copied into the change, other files in the tree will be ignored. It is an error if there are no relevant files.

  Process Side Effects
This command will cancel any build or test registrations, because deleting a file logically invalidates them. If the project config file was deleted, any diff registration will also be canceled.

The difference file (,D) will also be removed, however any DMT derived files (e.g a .o file from a .c file) will not be removed. This is because is decoupled from the DMT, and cannot know what these derived file may be called. You may need to delete derived files manually.

  Notification
The make_transparent_undo_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 aemtu ' -mtu \!* -v'
sh$	aemtu(){ -mtu "$@" -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.

SEE ALSO

aecpu(1)
    no longer modify a file

aemt(1)
    make branch files transparent

aeuconf(5)
    user configuration file format