Abstract: Methods and apparati including computer program products link compiler error messages to information relevant to an error causing the compiler to generate the error message by adding link information to the compiler error messages. The error messages are displayed to the user without the link information. Portions of the visible error messages pertaining to the link information are highlighted, and upon selection by the user of the highlighted portion of the error message, information relevant to the highlighted error message is automatically displayed, for example, by running an editor, loading the source file which generated the error message, and displaying the relevant portion of the source file, or by running a help facility and displaying help information relevant to the error.

Abstract: Methods, apparatti and computer program products allow one or more editors to provide integrated functionality with one or more applications. The methods, systems and computer program products allow a user to select from among several editors which are not integrated with an application, yet interact with the editor and application as though the editor and application were integrated. One or more editors are assigned to each application and commands sent from each application are transformed into a command readable by the editor associated with the application. The command is sent to the editor, which is then able to display files to provide an appearance that the editor and the application are integrated. User generated commands from the editors may be sent to all of the applications or only a subset of the applications to allow the user to control one or more applications from the editor user interface.

Abstract: A method for the stateless propagation of rename's between hierarchial file name spaces is provided. Under the method any standard rename command may be used on a filename located in a local file system name space (FSNS). Thereafter, when a file is renamed, that rename may be propagated through the use of three steps. First, when files have been renamed in either the local, remote or both FSNS, the filenames in the local FSNS must be matched with the corresponding file names in the remote FSNS. Then, after a match has been made, the current rename state is determined to see if the file was renamed in either, both or neither FSNS, or to see of the filename describes a new file not found in the other FSNS. Finally, after the name history for each file in both the local and remote FSNS's are updated, a propagation can occur which updates any changed file names in the remote FSNS, and also updates the entries in the remote FSNS name table and the local FSNS name table to reflect any such changes.

Abstract: A rename tracking and propagation facility propagates renames, executed in multiple isolated file system name spaces (FSNS), to a remote FSNS on a per object basis without corruption of the remote FSNS names. In propagating an object's rename, the smallest set of additional object's renames which must be applied in the remote FSNS in order to apply the object's rename in the remote FSNS is determined. The set of renames is applied in the correct order, in the remote FSNS, accounting for those renames already propagated to the remote FSNS. A record of renames executed in a FSNS is utilized to determine which renames are to propagated. To accommodate parallel development (multiple users modifying part of the fill system all the time without explicit locking), name collisions in the remote FSNS are detected and resolved. These sets of renames are constructed such that they can be applied to the remote FSNS in any order.