Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 9 Jul 2004 14:22:38 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?")
Message-ID: <20040709182238.GB6306@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <010701c464f4$398e2030$4e6510ac AT ds DOT tao DOT co DOT uk> <Pine DOT GSO DOT 4 DOT 58 DOT 0407081027371 DOT 11665 AT slinky DOT cs DOT nyu DOT edu> <013301c464fe$e2e425d0$4e6510ac AT ds DOT tao DOT co DOT uk> <Pine DOT GSO DOT 4 DOT 58 DOT 0407081124080 DOT 11665 AT slinky DOT cs DOT nyu DOT edu> <00aa01c4659f$662717e0$4e6510ac AT ds DOT tao DOT co DOT uk> <20040709153850 DOT GE3525 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT LNX DOT 4 DOT 60 DOT 0407090907230 DOT 2854 AT zeno1 DOT math DOT washington DOT edu> <20040709163809 DOT GB5602 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT LNX DOT 4 DOT 60 DOT 0407091016470 DOT 6224 AT zeno1 DOT math DOT washington DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.60.0407091016470.6224@zeno1.math.washington.edu>
User-Agent: Mutt/1.4.1i

On Fri, Jul 09, 2004 at 10:24:22AM -0700, Eduardo Chappa wrote:
>*** Christopher Faylor ...:
>>Maybe you're being purposely obtuse.  I don't know.  My point was that
>>if I send specially formatted text in my messages to a technical
>>mailing list I don't want the archiving software to unformat it for me.
>>What it does to the email reader on your PDA is irrelevant.
>
>What you do not understand is that i am talking about a PDA as a
>screen, like the one that you are reading your e-mail message.

Rest assured, I know that PDAs have screens.

>>>If someone provides a patch and I were to cut and paste that patch, I
>>>would call myself crazy, I would normally save the patch to a file
>>>directly, so this is not an issue.
>>
>>The issue is inspecting the patch in the archives.  If you have to
>>puzzle out where the line breaks actually occur because your web
>>browser is helpfully wrapping things for you, then the utility of the
>>archives has been diminished for some people (like me).
>
>I understand, I see how this could be an issue.  But adding <BR>, as I
>mentioned before fixes this problem.
>
>>>On the other hand, just to mention something, instead of saying "NO, it
>>>won't happen", maybe you may want to experiment on adding <BR> at the
>>>end of each line, or adding <P> instead of having empty lines, or
>>>things like that.  Probably does not work out of the box, but it
>>>probably can be tuned to fit most messages, if not all.
>>
>>That's sort of presumptuous, don't you think?
>
>No.

I phrased that poorly.  Let me restate.

I think your suggestion was presumptuous.

>>You don't even know how the archives are generated but you have no
>>qualms about suggesting that I take my time trying to "fix" something
>>which I've already indicated is not broken.
>
>I do not need to know how the archives are generated to see that they
>are broken, but if you want to spare your time explaining this to me, I
>am happy to read it.

You're welcome to do this research yourself.  Start by inspecting the
email archives themselves for clues.

Frankly, since I only barely understand what PDAs are and since I really
don't know what this "<br>" stuff is all about, I don't think you'd
want to engage me in a discussion about complicated stuff like mail
archiving.  You'd be spending all of your time explaining stuff to
me.

>I never used the word "fix", please do not misunderstand me. I refer to 
>this as "enhance". Yes, it is broken, by the way.

So, it's "broken" and you want me to "enhance" it so that it won't be
"broken" anymore but you were not suggesting a "fix".  Got it.

>>Again, I am not going to spend any time trying to set up the cygwin
>>mailing list as a special case.  There are surely other sites archiving
>>the mailing list out there somewhere.  Use one of them if the
>>formatting in the sourceware.org archive offends you.
>
>It has not offended me.  Did I say so?

I guess I was inferring from your multiple messages to this thread, and
by your attempts to offer simple suggestions for "enhancing" things,
that you did not like the current state of affairs.  I stand corrected.

>>OTOH, if anyone wants to change the policy of sourceware.org, you are 
>>welcome to send email to the overseers mailing list and lobby for 
>>change.  I don't think you are going to find a receptive audience, but 
>>I could be wrong.
>
>I don't think it's the time to send such request.  I will wait a couple
>of years to do so.

Then you are done with this discussion except as a theoretical exercise,
apparently.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/