Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!unido!infko!droege From: droege@infko.UUCP (Detlev Droege) Newsgroups: comp.os.minix Subject: Re: linewrap Message-ID: <434@infko.UUCP> Date: 6 Oct 88 10:02:39 GMT References: Reply-To: droege@infko.UUCP (Detlev Droege) Organization: University of Koblenz (EWH), West Germany Lines: 30 In article hedrick@athos.rutgers. edu (Charles Hedrick) writes: > >By the way, ast and I are having sort of an argument about line wrap. >He would like to remove it. I left it in under a conditional because >there had been a number of requests on this group for it. I agree >with him that correct programs don't put out more than 80 chars on a >line. Unfortunately I don't always work with correct programs. The >last thing I want is that when I get an unexpected message, or >unexpected data, things disappear from the screen. Debugging is hard >enough as is without having critical data go away because it overflows >the line. This is my vote for line warp. It's not only a question of "correct" programs. Take normal macro expansion as in "make". You can't see what happens, if you don't have line warp, as lots of lines generated by "make" are longer than 80 characters and I don't consider that to be a bug. And I want to know what make does. Please DON'T remove line warp. Detlev -- Detlev Droege, Uni Koblenz (EWH), FB Informatik Rheinau 3-4, D-5400 Koblenz (West Germany) UUCP: ..!unido!infko!droege droege@infko.UUCP (Voice: +49 261 12156)