From owner-freebsd-current Fri Jan 29 18:33:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28687 for freebsd-current-outgoing; Fri, 29 Jan 1999 18:33:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28682 for ; Fri, 29 Jan 1999 18:33:40 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id VAA01228; Fri, 29 Jan 1999 21:33:29 -0500 (EST) (envelope-from wollman) Date: Fri, 29 Jan 1999 21:33:29 -0500 (EST) From: Garrett Wollman Message-Id: <199901300233.VAA01228@khavrinen.lcs.mit.edu> To: Greg Lehey Cc: Warner Losh , Julian Elischer , current@FreeBSD.ORG Subject: Re: btokup().. patch to STYLE(9) (fwd) In-Reply-To: <19990130104943.W8473@freebie.lemis.com> References: <199901291802.LAA67403@harmony.village.org> <19990130104943.W8473@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Question: how many people still limit their editor windows to 80 > characters? Probably almost anyone who uses the default settings. Many people like to be able to see more than one thing on the desktop at a time. Even with a 1280x1024 display on a good 19-inch monitor, I still can't fit two 80-character windows side-by-side if I want to be able to read the font. That's ignoring other issues like trying to print such documents. HP printers don't do auto-wrap (and even if they did it wouldn't respect any semantic value in the code). Before XFree86 3.3.3 came out, my laptop could not run X -- presto, automatic 80-character limitation. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message