From owner-freebsd-bugs  Wed Sep 27 19:20:05 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id TAA23348
          for bugs-outgoing; Wed, 27 Sep 1995 19:20:05 -0700
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id TAA23341
          ; Wed, 27 Sep 1995 19:20:02 -0700
Date: Wed, 27 Sep 1995 19:20:02 -0700
Message-Id: <199509280220.TAA23341@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Keith Bostic <bostic@BSDI.COM>
Subject: Re: bin/743: vi cannot edit a file where the name starts with +
Reply-To: Keith Bostic <bostic@BSDI.COM>
Sender: owner-bugs@FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/743; it has been noted by GNATS.

From: Keith Bostic <bostic@BSDI.COM>
To: j@ida.interface-business.de
Cc: FreeBSD-gnats-submit@freebsd.org, mpp@mpp.minn.net
Subject: Re: bin/743: vi cannot edit a file where the name starts with +
Date: Wed, 27 Sep 1995 20:18:07 -0600

 > But for removing a file starting with a dash, there's a well-known
 > interface to work around it (--).  I'd rather suggest for vi to also
 > accept a ``--'' to end scanning the command line for options.
 
 I agree.  Since nvi uses getopt(3), "--" does, in general, work.
 exactly as it does in rm.
 
 Unfortunately, +cmd arguments are translated into -c cmd before
 getopt is called, so the result in the case of a leading + sign
 in an argument is not what the user wanted.
 
 I'll fix this in the next version of nvi.
 
 --keith