Date: Sat, 04 Sep 1999 12:35:52 -0500 From: "Jeffrey J. Mountin" <jeff-ml@mountin.net> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, hoek@FreeBSD.ORG Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/usr.bin/more default.morerc less.morerc macro.c most.morerc ncommand.c Makefile command.c input.c less.h line.c main.c more.1 more.help option.c output.c pathnames.h prim.c screen.c signal.c ttyin.c decode.c Message-ID: <3.0.3.32.19990904123552.01522520@207.227.119.2> In-Reply-To: <19990903224600.51536@hydrogen.fircrest.net> References: <19990904012751.A30517@mad> <199909032231.PAA60938@freefall.freebsd.org> <19990903214400.29996@hydrogen.fircrest.net> <19990904012751.A30517@mad>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:46 PM 9/3/99 -0700, John-Mark Gurney wrote: >Tim Vanderhoek scribbled this message on Sep 4: >> On Fri, Sep 03, 1999 at 09:44:00PM -0700, John-Mark Gurney wrote: >> > >> > > changed is the capital 'N' key, which now performs a repeat-search in the >> > > opposite direction (just like in vi). >> > >> > ummm... I don't like this... I'm used to N being Next File as it has >> > been for YEARS w/ FreeBSD.... >> >> FWIW, I ran this for 2+ months here and I'm finally getting used to >> 'N' not being the same as ':n'. However, I'm sure I'm not the only >> person who routinely pressed 'N' expecting it to work like in vi, only >> to get either an error or booted to the next file. I'm convinced the >> change should be made. > >my complaint is that it no longer makes browsing the first page of >multiple files easy any more... I wouldn't mind if we manage to make >another nemonic that would do next file in a single key press, but I >guess I'm going to have to live with this... Not to pick on you John, but what's an extra character to type? It makes much more sense to have ':n' as "next file" considering other file commands a prepended with a colon. Besides the point, since there's been quite a bit more static than lately on the CVS lists. My hope is that this doesn't expand into a 'vi' command vs 'emacs' command, whatever that is for "next file" (not be partisan... ducks). Only say this due to more and less having commands based on vi. Lacking the history (and don't care to see it on this list). And since I'm chiming in... I'm for making commands and command options similar to other unices, never know when I have to work on a strange system. Yet there are additions that are very helpful (missed not having grep's -A/-B on Solaris). Personally let the powers that be ie those working on the code or contributing to hash out things in a sensical, (hopefully) impartial manner. Don't mind me and *my* static, but it gets tiring to hear the same arguements over and over. Change happens, bear with it. Don't care to get into some changes that left me flustered. Some (more recently - no pun) of the byplay here would be best moved to -hackers or -chat. my .02 Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve '86 Yamaha MaxiumX (not FBSD powered) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19990904123552.01522520>