From owner-freebsd-current Sun Sep 12 6:19:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id EFF6B1533E for ; Sun, 12 Sep 1999 06:19:12 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.148]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA24E8 for ; Sun, 12 Sep 1999 15:19:11 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id PAA82904 for current@freebsd.org; Sun, 12 Sep 1999 15:20:02 +0200 (CEST) (envelope-from asmodai) Date: Sun, 12 Sep 1999 15:20:02 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: more Message-ID: <19990912152002.D81750@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a question, who changed more's behaviour? On this CURRENT of 3-4 weeks old I can do /blah and then use / to find the next occurance of blah in the same file. With the `new' more this behaviour has been barfed. Wonder why and who... -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best There is no greater sorrow than to recall, in misery, the time when we were happy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message