Date: Sun, 12 Sep 1999 18:08:27 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Tim Vanderhoek <vanderh@ecf.utoronto.ca> Cc: current@freebsd.org Subject: Re: more Message-ID: <19990912180827.A83446@daemon.ninth-circle.org> In-Reply-To: <19990912103801.C7124@mad> References: <19990912152002.D81750@daemon.ninth-circle.org> <19990912103801.C7124@mad>
next in thread | previous in thread | raw e-mail | index | archive | help
* Tim Vanderhoek (vanderh@ecf.utoronto.ca) [990912 17:50]: >On Sun, Sep 12, 1999 at 03:20:02PM +0200, Jeroen Ruigrok/Asmodai wrote: >> >> 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. > >Accidentally. I didn't notice that particular (mis?)-feature when >reading the older code. I'll re-add it. You can, of course, also use >"n" in the meantime. *nod* That's ok. I was merely curious as to the why. I am used to using it, but I can easily adopt myself to using `n'. Just wonder who else wants this behaviour to stay away and come back. It's not like I am emotionally attached to it =) >Of course, one really wonders why we need "/\n" to be a synonym for >"n", but I hadn't meant to change this behaviour. That's ok =) Cheers, -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>; Network/Security Specialist BSD: Technical excellence at its best Millions for defense but not one cent for tribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990912180827.A83446>