33.3.2 Specifying which files to delete from the project folder
To specify which files Mif2Go should delete from the project folder before conversion:
; EmptyOutputFiles = list of files to delete, separated by spaces,
; wildcards allowed but not paths, no spaces within an item
EmptyOutputFiles = *.htm *.ref *.grx
If you do not include a setting for EmptyOutputFiles, depending on the value of EmptyOutputDir (see §33.3.1 Specifying when to delete old files from the project folder), by default Mif2Go deletes the following old files from the project folder before conversion:
![[spacer]](1p.gif){kind=small}
Use wildcards; do not use paths
The file specifications you assign to EmptyOutputFiles must be separated by spaces, and no spaces are allowed within a file specification. You can use wildcards in file specifications, but you cannot include paths.
Do not specify *.* or *.ini, or you will lose your configuration file(s); and for Help systems, you might lose a great deal more. |
Depending on the value of EmptyOutputDir (see §33.3.1 Specifying when to delete old files from the project folder), Mif2Go deletes the specified files before conversion begins, immediately after executing any system commands listed in your configuration file for BookFileStart, in section [BookFileCommands]; see §32.4.2 Executing system commands before and after conversion.
Files get deleted on compiling and indexing, also
EmptyOutputFiles takes effect not only when WrapAndShip=Yes, but also when either of the following is true:
See §33.8 Gathering and compiling Help-system files.
§33.3.1 Specifying when to delete old files from the project folder
§33.3.3 Understanding when not to delete .ref and .htm files
§33.3.4 Deleting MIF files from the project folder
> 33 Producing deliverable results > 33.3 Clearing out old files before converting > 33.3.2 Specifying which files to delete from the project folder