TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:PROBLEMS WITH DOCS From:Gregg Roberts <gregg -dot- roberts -at- TPOINT -dot- COM> Date:Sat, 4 Feb 1995 10:08:08 -0600
> I've been struggling with how to present commands in the ascii
> version of the
> documentation. I've checked several other university gopher sites
> for ideas,
> but none that I've found use a consistent method: some use both
> all-caps and
> double quotes in the same document. All-caps wouldn't be bad, but it
> won't work for our Unix docs, because Unix commands are case
What about including the prompt in front of any commands? I have not used UNIX
extensively, but it seems as though there was always a command line prompt of
one kind or another.