From rwsys!hammy!gordon@lerami.lerctr.org  Thu Jul  6 18:22:51 1995
Received: from news.onramp.net (news.onramp.net [199.1.11.7])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA11702
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 6 Jul 1995 18:22:50 -0700
Received: from rwsys!hammy.UUCP (uucp@localhost) 
	by news.onramp.net (8.6.12/8.6.9) with UUCP id UAA29034 for FreeBSD-gnats-submit@freebsd.org; Thu, 6 Jul 1995 20:22:48 -0500
Received: by lerami.lerctr.org (/\oo/\ Smail3.1.29.1 #29.2)
	id <m0sU1dz-0000XcC@lerami.lerctr.org>; Thu, 6 Jul 95 19:51 CDT
Received: from hammy by rwsys.lonestar.org with uucp
	(Smail3.1.27.1 #1) id m0sTzh1-0001IdC; Thu, 6 Jul 95 17:46 CDT
Received: by hammy.lonestar.org (Smail3.1.29.0 #1)
	id m0sTzTL-0001hkC; Thu, 6 Jul 95 17:32 CDT
Message-Id: <m0sTzTL-0001hkC@hammy.lonestar.org>
Date: Thu, 6 Jul 95 17:32 CDT
From: gordon@sneaky.lonestar.org
Reply-To: gordon@sneaky.lonestar.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: csh 'imported path' warning makes it unusable with vi
X-Send-Pr-Version: 3.2

>Number:         598
>Category:       bin
>Synopsis:       csh 'imported path' warning makes it unusable with vi
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul  6 18:30:01 1995
>Closed-Date:    Fri Jul 7 15:45:34 PDT 1995
>Last-Modified:
>Originator:     Gordon Burditt
>Release:        FreeBSD 2.0-BUILT-19950603 i386
>Organization:
what organization? 
>Environment:
	FreeBSD 2.0.5

>Description:
	While csh's warning 'warning:  imported path contains 
	relative components' is accurate (when you su to root
	and inherit a path containing '.' as the last component,
	and yes, I'll grant this has security problems, but many
	package makefiles won't work without it, and you have to be
	root to install), it cripples use of vi due to the message 
	getting into filename expansions and edit buffers.

	How about making this warning apply only to INTERACTIVE shells?
	If that's a bad idea, how about turning the warning into a
	fatal error (it might as well be anyway, for all the work
	you can get done using it).

>How-To-Repeat:
	su to root
	set PATH to something including "." at the end.
	setenv SHELL /bin/csh
	Invoke vi.
	Attempt a ":e ~/.login"
	Get usage message, because expanded filename starts with "Warning: 
	imported path"

>Fix:
	
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: ache 
State-Changed-When: Fri Jul 7 15:45:34 PDT 1995 
State-Changed-Why:  
Fixed in csh.c v1.4 
>Unformatted:



