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:Re: word of the day From:Janice Gelb <Janice -dot- Gelb -at- Sun -dot- COM> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Sat, 05 Dec 2009 03:50:22 +1100
McLauchlan, Kevin wrote:
> I don't know what that word is, nor even if it exists.
>
> I just have this nagging suspicion that there's a word that would serve...
>
> Say you have a shell or command-line environment. Um, a command-line window in Windoze for example.
>
> You are at the standard command-line prompt (for that shell/environment/whatever).
> You have some executable utility binary files in the current directory.
>
> You type the name of an executable possibly followed by some arguments or parameters, possibly not.
>
> In one case, the command does something, finishes, and goes away.
>
> In the other case, the command puts up a command-line menu and waits for you to type one of the permissible... um.... subcommands, with attendant options and parameters, and that subcommand does its thing and stops, but you are still at the prompt for the main command, not the prompt for your shell.
> You can either issue another of the special-purpose commands of this lingering utility, or you can say "exit" and find yourself back at (say) the Windoze command-line prompt (DOS prompt).
>
> The word "menu-driven" floats around, but is somehow not satisfactory.
> Someone mumbled "TSR?", but the utility doesn't terminate - you can't actually run anything else in that "DOS" window until you actively terminate the utility, in which case it's entirely gone.
>
> I thought there was another term that nicely indicated a style of command-driven utility that started, accepted multiple commands, or just sat there, until actively dismissed - versus one that you call with all the parameters it's going to need, and it goes entirely away as soon as it completes the one task.
>
Not sure this is relevant in this case but I've
seen commands that initiate scripts that require
this sort of interaction, and that's what we
usually call them. ("Type bozo.exe to start the
Bozo script.")
-- Janice
***********************************************************
Janice Gelb | The only connection Sun has with
janice -dot- gelb -at- sun -dot- com | this message is the return address
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
generate 8 different formats and as many different versions as you need
from just one project. Fast and intuitive. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
