Date: Tue, 17 Feb 1998 12:22:11 -0500 From: Max Euston <meuston@jmrodgers.com> To: "'Tim Vanderhoek'" <hoek@hwcn.org> Cc: "'FreeBSD Hackers'" <freebsd-hackers@FreeBSD.ORG> Subject: RE: Modifications to more(1) Message-ID: <01BD3B9E.ACEB1140.meuston@jmrodgers.com>
next in thread | raw e-mail | index | archive | help
Sorry it took me so long to get back to you, but I actually had a long weekend off! On Thursday, February 12, 1998 5:42 PM, Tim Vanderhoek [SMTP:hoek@hwcn.org] wrote: > On Thu, 12 Feb 1998, Max Euston wrote: > > > this leads me to believe that this option is out-of-date (also > > it does not follow the standard). My question is: should I fix > > the -# option or remove it (my vote is to remove it - see > > below). > > How long has it been broken? If it was broken in the last > release or two, then probably no-one has noticed and it should > just disappear. > Please excuse my ignorance re: CVS, but I have not used it before (used other RCSs, but syntax/usage is different). I will learn more as I start to work with it. I don't know how to check this (i.e. check specific versions of ONE file only - without installing a whole set of files from a distribution). I am running 2.2.5-release and just started to install & build CVSup when my swap space filled during the build - I will have to reconfigure this (or download the pre-built binary; not my first choice). > > > 3) Use the LINES= environment variable (ala vi(1)) to set the screen height > > 4) [totally optional :-]. Handle long lines in the extreme > better. If you have a long file with no \n or \r, and more down > to near the end, then press `k' or `b', it will `k' or `b' > v-e-r-y s-l-o-w-l-y. Hehe. Good luck! :) > Found this - should be simple enought to fix :-) - I will check it out further. > > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe hackers" in the body of the message Finally (some very basic questions, but I don't have the answers - sorry): If I make changes to existing source code that does NOT follow current FreeBSD style (indents, header files, etc...), is it proper to maintain the style of the existing code or should I use the newer format? (e.g. should I "#include <string.h>" or "extern char *strcat()")? Should I change the 'sccsid[]' date and/or version number? Thanks, Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BD3B9E.ACEB1140.meuston>