Next: Source Comparison, Previous: Managing Large Systems, Up: Managing Large Systems [Contents][Index]
A file group is a set of files, upon which various editing operations can be performed. The files in a group are specified by a file in the following format:
This syntax is used for historical reasons. Although any number of file groups may be read into Hemlock, there is only one active group, which is the file group implicitly used by all of the file group commands. Page compile-group-command describes the Compile Group command.
This command prompts for the name of a file group to make the active group. If the name entered is not the name of a group whose definition has been read, then the user is prompted for the name of a file to read the group definition from. The name of the default pathname is the name of the group, and the type is "upd".
This command prompts for target and replacement strings and then executes an interactive string replace on each file in the active group. This reads in each file as if Find File were used and processes it as if Query Replace were executing.
This is like Group Query Replace except that it executes a non-interactive replacement, similar to Replace String.
This command prompts for a string and then searches for it in each file in the active group. This reads in each file as if Find File were used. When it finds an occurrence, it prompts the user for a key-event indicating what action to take. The following commands are defined:
Exit Group Search.
Continue searching for the next occurrence of the string.
Continue the search at the beginning of the next file, skipping the remainder of the current file.
Go into a recursive edit at the current location, and continue the search when it is exited.
The group searching and replacing commands read each file into its own buffer using Find File. Since this may result in large amounts of memory being consumed by unwanted buffers, this variable controls whether to delete the buffer after processing it. When this variable is false, the default, the commands delete the buffer if it did not previously exist; however, regardless of this variable, if the user leaves the buffer modified, the commands will not delete it.
If this variable is true, the group searching and replacing commands ask for confirmation before saving any modified file. The commands attempt to save each file processed before going on to the next one in the group.
Next: Source Comparison, Previous: Managing Large Systems, Up: Managing Large Systems [Contents][Index]