From owner-freebsd-bugs  Wed Sep 27 05:30:02 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id FAA29265
          for bugs-outgoing; Wed, 27 Sep 1995 05:30:02 -0700
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id FAA29259
          ; Wed, 27 Sep 1995 05:30:01 -0700
Date: Wed, 27 Sep 1995 05:30:01 -0700
Message-Id: <199509271230.FAA29259@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: J Wunsch <j@ida.interface-business.de>
Subject: Re: bin/743: vi cannot edit a file where the name starts with +
Reply-To: J Wunsch <j@ida.interface-business.de>
Sender: owner-bugs@FreeBSD.org
Precedence: bulk

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

From: J Wunsch <j@ida.interface-business.de>
To: mpp@mpp.minn.net (Mike Pritchard)
Cc: joerg_wunsch@interface-business.de, FreeBSD-gnats-submit@freebsd.org,
        bostic@cs.berkeley.edu
Subject: Re: bin/743: vi cannot edit a file where the name starts with +
Date: Wed, 27 Sep 1995 12:50:08 +0100 (MET)

 As Mike Pritchard wrote:
 > 
 > > vi +foo
 > > ~
 > > ...
 > > ~
 > > /tmp/vi.014780: new file: line 1;  The foo command is unknown.
 
 > As for the "vi +foo" problem, note the "+cmd" syntax above.
 
 Of course, this has been quite clear to me.
 
 >  I don't 
 > think that I would consider this a real "bug".  It seems to fall into 
 > the same category as trying to use rm to remove a file that starts with 
 > a dash (-) (and please, lets not get into a long discussion on that...).
 
 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.
 
 -- 
 cheers,
 
 J"org Wunsch