From owner-freebsd-hackers Thu Dec 22 00:12:05 1994 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA20236 for hackers-outgoing; Thu, 22 Dec 1994 00:12:05 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA20226 for ; Thu, 22 Dec 1994 08:11:59 GMT Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA00269; Thu, 22 Dec 1994 19:11:05 +1100 Date: Thu, 22 Dec 1994 19:11:05 +1100 From: Bruce Evans Message-Id: <199412220811.TAA00269@godzilla.zeta.org.au> To: freebsd-hackers@freefall.cdrom.com, rivers%ponds@ncren.net Subject: Re: Small problem in nvi. Sender: hackers-owner@freebsd.org Precedence: bulk >I've noticed that previous versions of nvi would not "edit" >directories. nvi seems to read ufsdirectories OK in 1.1.5. Elvis refuses to read them. nvi has interestingly different behaviour depending on the path used to reach the directory: for the directory /tmp~ and the symlink /tmp -> /var/tmp/tmp (all on the same ufs file system), after cd /: In both 1.1.5 and 2.0: /usr/bin/vi tmp~: works, reads the dir /usr/bin/vi /tmp~: works, reads the dir /usr/bin/vi tmp: works, reads the dir /usr/bin/vi /tmp: fails, reads the new file /tmp/vi.00 In 2.0, with /tmp~ renamed to /tmp: Same behaviour as for /tmp above. Renaming the file changed nvi's behaviour! Bruce