From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3/2) with ESMTP id AAA09308 for ; Fri, 7 Jun 1996 00:59:48 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id KAA20137; Thu, 6 Jun 1996 10:52:34 -0400 (EDT) Resent-Date: Thu, 6 Jun 1996 10:52:09 -0400 (EDT) Message-Id: <199606061451.AA003572668@hpbs2245.boi.hp.com> To: zsh-users@math.gatech.edu (Zsh Users Mailing List) Subject: Auto-created completion. Date: Thu, 06 Jun 1996 08:51:07 -0600 From: Rodger Anderson Resent-Message-ID: <"gXl7q3.0.Dw4.O2ljn"@euclid> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/236 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Since folks are talking about what a future zsh might have, here is my idea: Zsh would be able to automatically figure out what each program might need for options/arguments and do completion accordingly. This would require that every program have some way to tell zsh what its options are, so this idea is pretty far-fetched. GNU programs have the --help option. The output format of "find --help" is meant to be viewed by a person, not parsed by a program, so perhaps if there were a --synopsis option or something. The first time a zsh user runs the "find" program, zsh would run "find --sysopsis" and parse the output to create a completion map for that command and cache the results. Auto-created completion. Rodger Anderson