mbuild help request should support internal mbuild info residing in more than one .info segment

[Gary Dixon]

The mbuild help (h) request currently expects all mbuild internal info blocks to reside is a single mbuild.info segment. That segment has grown to almost 1800 lines in length. Also, enhancement ticket #329 proposes adding many additional info segments to mbuild's documentation set. This extra documentation would definitely cause the mbuild help request to fail in parsing such a large info segment (usually because of "record quota overflow" on temporary storage used by help_ to parse the lines of a single info segment).

This ticket proposes that mbuild_help_.pl1 be enhanced as follows.

• The mbuild help request should look for mbuild-related info blocks in several info segments.

• The mbuild help request should accept a -section (-scn) control argument to permit selection of info blocks which include a section title matching the -section STR operand. Display of selected info blocks should begin that that matching section.

• mbuild should include a list_help (lh) request which provides the user with a list of help TOPICs available via the mbuild help (h) request.

• The mbuild list_requests (lr) request should list available requests in a more useful order. Requests needed to advance work within a build_directory should appear first, followed by less-important mbuild-specific requests, followed by ssu_-provided subsystem-support requests (like list_requests, ?, ., .., etc.).

[Eric Swenson]

​https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10142.pdf

MR12.9-1004