I wonder how wise that is, I believe I have seen installer scripts use C:Edit, for altering startup-sequence and other things.
Because I made a mistake when I wrote the Roadshow installation script I thought I could put the "Edit" command to good use in order to fix the problem I had created. The "Installer" tool has only very limited string/file manipulation functions, so "Edit" seemed like an option to try. However, it turned out that the V36 "Edit" command could not be used because the editing commands I needed either did not work at all, or crashed the command.
The "Edit" command which shipped with Workbench 2.0-3.1 suffered from several bugs and limitations which rendered it mostly unsafe for use. For example, the DTA, SA and SB commands never worked at all, the WIDTH and PREVIOUS arguments didn't work either, lines longer than 120 characters could cause Edit to slip up badly and path names longer than 120 characters would trash memory before even loading the respective file.
When I got curious after I ran into the "Edit" bugs I took the plunge and fixed the bugs, using the original BCPL implementation as a reference. The updated version is available in a form usable within the context of Workbench 3.1.4. As far as I can tell it's now on the same level as the Workbench 1.3 version (last updated in 1985) and "only" suffers from the same design limitations.
However, this is a Catch-22 situation bordering on satire: if "Edit" saw limited use because it was rarely safe to use in the first place, replacing it with a version which actually does what it's supposed to will accomplish exactly what?
