From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4779 invoked from network); 26 Sep 1997 17:13:29 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 26 Sep 1997 17:13:29 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id MAA22500; Fri, 26 Sep 1997 12:42:11 -0400 (EDT) Resent-Date: Fri, 26 Sep 1997 12:42:11 -0400 (EDT) From: "Bart Schaefer" Message-Id: <970926094237.ZM28275@candle.brasslantern.com> Date: Fri, 26 Sep 1997 09:42:37 -0700 X-Mailer: Z-Mail (4.0b.820 20aug96) To: zsh-workers@math.gatech.edu Subject: Bug in info (yodl?) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"E8flQ2.0.RV5.YN-Aq"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3532 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu I don't know if this is yodl-induced because I'm using the 3.0.x sources, but capitalization is messed up in the extended completion section: `S[STRING] ...' Matches if the current word on the command line starts with one of the strings given in brackets. The STRING is not removed and is not part of the completion. `S[STRING] ...' Like S[STRING] except that the STRING is part of the completion. Uhh, yeah ... one of those is supposed to be a lower case S. Every pair of upper/lower completion options has this problem, and not all of them can be easily deduced from context like that one. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com