This is bug 5442, btw.
On Mon, 2008-02-18 at 23:54 -0500, Daryl C. W. O'Shea wrote:
For what? The only config lines that I can think of that are really
long are for rules. We're certainly not going to go sticking
backslashes in the middle of regexes.
Not necessarily in the middle of REs,
MK Why would there ever be a problem fitting on one line? Lines aren't
MK limited to 80 characters or anything silly like that..
MK That sounds a bit like complaining that a ship must fit in the water..
MK There's a whole ocean out there, so who cares if you can't put one
MK boat in 2 rain
[EMAIL PROTECTED] wrote:
MK Why would there ever be a problem fitting on one line? Lines aren't
MK limited to 80 characters or anything silly like that..
MK That sounds a bit like complaining that a ship must fit in the water..
MK There's a whole ocean out there, so who cares if you can't put
-Original Message-
From: Matt Kettler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 19 February 2008 4:43 p.m.
To: [EMAIL PROTECTED]
Cc: users@spamassassin.apache.org
Subject: Re: user_prefs: mind the linebreak
[EMAIL PROTECTED] wrote:
MK Why would there ever be a problem fitting
MK Call me older fashioned.. I consider line-wrapping a bit too fancy
MK for my config editing preferences.
I see, you must have a billion column wide terminal or something.
Oops. You whippersnappers don't call them terminals these days.
Anyway, I swear I am not dreaming:
$ info make
We split
Michael Hutchinson wrote:
Line wrapping in config is bad. I've had several instances of an editor
in linux that I won't name where I've lost config data because of it
wrapping lines instead of just displaying it off page until I'm ready to
see it.
This seems to happen a lot more frequently with
[EMAIL PROTECTED] wrote:
MK Call me older fashioned.. I consider line-wrapping a bit too fancy
MK for my config editing preferences.
I see, you must have a billion column wide terminal or something.
Oops. You whippersnappers don't call them terminals these days.
Anyway, I swear I am not
