public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@verizon.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Kurt Wall <kwall@kurtwerks.com>,
	linux-kernel@vger.kernel.org, pj@sgi.com
Subject: Re: mozilla-mail damage [was Re: [PATCH] Update to	Documentation/ramdisk.txt - take 2]
Date: Sat, 23 Oct 2004 00:18:43 -0400	[thread overview]
Message-ID: <4179DBA3.2000407@verizon.net> (raw)
In-Reply-To: <1098501410.9092.36.camel@krustophenia.net>

Lee Revell wrote:
> On Fri, 2004-10-22 at 22:35 -0400, Lee Revell wrote:
> 
>>On Fri, 2004-10-22 at 22:12 -0400, Kurt Wall wrote:
>>
>>>On Fri, Oct 22, 2004 at 09:45:13PM -0400, Jim Nelson took 229 lines to write:
>>>
>>>>@#%*^#$ Mozilla.  Line wrap was set too low.
>>>>
>>>>Let's try this again - hopefully, Mozilla won't mangle my patch this time.
>>>
>>>Urgl:
>>>
>>>patching file Documentation/ramdisk.txt
>>>Hunk #1 FAILED at 5.
>>
>>You cannot just increase the line wrap and hope Mozilla will do the
>>right thing.  Mozilla should have an option to insert preformatted text.
> 
> 
> OK I just went and installed mozilla mail to see what the problem is and
> it's worse than I thought.
> 
> The problem is that Mozilla does not grok the standard X clipboard at
> all.
> 
> Try these tests:
> 
> 1. Highlight some text in an xterm.  Paste with middle button into
> Mozlla  mail window.  Then paste with the middle button into vim.  Both
> work BUT the patch is whitespace damaged.
> 
> 2. Run diff foo bar | xclip.  Paste with middle button into Mozilla.
> Nothing.  Then paste with middle button into vim.  Works.
> 
> #2 would not mangle the patch IF it worked which it doesn't.  Mozilla
> does not have a setting to insert a text file.  So many people just do
> #1.
> 
> No wonder people are mangling patches, the Mozilla mail client is very
> broken.  PLEASE, file bug reports!
> 
> Lee
> 
>

Probably need to make using Paul Jackson's sendpatchset script de riguer 
recommendation for GUI mail client users for right now, until this issue is hashed 
out one way or another.

However, sendpatchset doesn't work with SMTP authentication, which my ISP uses, 
and I'm too tired to get sendmail working on one of my machines tonight.  Maybe 
sometime tomorrow.

  reply	other threads:[~2004-10-23  5:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23  1:45 [PATCH] Update to Documentation/ramdisk.txt - take 2 Jim Nelson
2004-10-23  2:12 ` Kurt Wall
2004-10-23  2:35   ` Lee Revell
2004-10-23  3:16     ` mozilla-mail damage [was Re: [PATCH] Update to Documentation/ramdisk.txt - take 2] Lee Revell
2004-10-23  4:18       ` Jim Nelson [this message]
2004-10-23  4:29         ` Lee Revell
2004-10-23  5:29           ` Con Kolivas
2004-10-23 19:56           ` David Ford
2004-10-23 20:11             ` Lee Revell
2004-10-23  7:42         ` Paul Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4179DBA3.2000407@verizon.net \
    --to=james4765@verizon.net \
    --cc=kwall@kurtwerks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=rlrevell@joe-job.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox