Article View: gnu.bash.bug
Article #507completion on command arguments and switches
From: Ray Nickson
Date: Wed, 23 Aug 1989 21:59
Date: Wed, 23 Aug 1989 21:59
26 lines
1639 bytes
1639 bytes
Some time ago, during a discussion on what the switches to the `type' command should be, Brian wrote something like: I don't know why you're complaining that these switches are too long. You should be complaining that you cannot do completion on them. (sorry, I've junked the message containing the exact quote; from memory, this was the general idea though). I awaited some reaction to this, before commenting myself, but none forthcame. Was it just a throwaway line or do you really have plans in this direction? Something like VMS's (horror!) command description language so the shell can know about what sort of arguments each command expects and can do completion (and globbing!) appropriately? Such a thought has brought groans of derision from nearly every un*x hacker I've spoken to, yet I've never heard a good argument against it. Is there anything in the back (or the front!) of your mind(s)(*) in this direction? (*) BTW, is bash entirely bfox's baby, or do others (rms?) have continuing major input? -rgn -- Ray Nickson, Dept. Comp. Sci., Victoria University of Wellington, New Zealand. nickson@comp.vuw.ac.nz ...!uunet!vuwcomp!nickson + 64 4 721000x8593
Technical Details
Message-ID:
<8908232203.AA15814@comp.vuw.ac.nz>Path:
arc1-ca.pugleaf.net!utzoo!telly!philmtl!uunet!tut.cis.ohio-state.edu!comp.vuw.ac.nz!nicksonShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!telly!philmtl!uunet!tut.cis.ohio-state.edu!comp.vuw.ac.nz!nickson From: nickson@comp.vuw.ac.nz (Ray Nickson) Newsgroups: gnu.bash.bug Subject: completion on command arguments and switches Message-ID: <8908232203.AA15814@comp.vuw.ac.nz> Date: 23 Aug 89 21:59:08 GMT Article-I.D.: comp.8908232203.AA15814 Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 26