public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Jaco Kroon <jaco@kroon.co.za>,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: recommended mail clients [was] [PATCH] ati-agp suspend/resume support (try 2)
Date: Mon, 26 Dec 2005 16:00:31 -0500	[thread overview]
Message-ID: <1135630831.8293.89.camel@mindpipe> (raw)
In-Reply-To: <200512262003.38552.s0348365@sms.ed.ac.uk>

On Mon, 2005-12-26 at 20:03 +0000, Alistair John Strachan wrote:
> On Monday 26 December 2005 17:54, Lee Revell wrote:
> > On Mon, 2005-12-26 at 15:35 +0000, Alistair John Strachan wrote:
> > > On Monday 26 December 2005 14:38, Steven Rostedt wrote:
> [snip]
> > > >
> > > > I use pine and evolution.  Pine is text based and great when I ssh into
> > > > my machine to work.  Evolution is slow, but plays well with pine and it
> > > > handles things needed for LKML very well. (the drop down menu "Normal"
> > > > may be changed to "Preformat", which allows of inserting text files
> > > > "as-is").
> > >
> > > Dare I say it, KMail has also been doing the Right Thing for a long time.
> > > It will only line wrap things that you insert by typing; pastes are left
> > > untouched.
> >
> > It seems that of all the popular mail clients only Thunderbird has this
> > problem.  AFAICT it's impossible to make it DTRT with inline patches and
> > even if it is the fact that most users get it wrong points to a serious
> > usability/UI issue.
> >
> > Would a patch to add "Don't use Thunderbird/Mozilla Mail" to
> > SubmittingPatches be accepted?  Then we can point the Mozilla developers
> > at it (they have shown zero interest in fixing the problem so far) and
> > hopefully this will light a fire under someone.
> 
> Fundamentally the issue with Thunderbird is that it line-wraps AFTER you 
> compose an email, not during composition. I've never understood how, or why 
> this is useful to the end user, except for composing HTML emails (which 
> should be banned anyway).
> 
> Thunderbird is Yet Another mailer that could have been a good piece of 
> software if it hadn't attempted to be a clone of Outlook Express (defaulting 
> to Top Posting, HTML composition, line wrapping pastes).
> 
> It's the mindset; fixing Thunderbird is probably easy, but convincing the 
> Mozilla developers to include such "fixes" is probably much harder.
> 

Should be trivial to fix, when the user puts the editor into "Preformat"
mode or inserts a text file you surround it with <pre> tags.

Lee


  reply	other threads:[~2005-12-26 20:55 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26  4:52 [PATCH] ati-agp suspend/resume support (try 2) Jaco Kroon
2005-12-26  8:29 ` Pavel Machek
2005-12-26  8:55   ` recommended mail clients [was] " Jaco Kroon
2005-12-26 14:38     ` Steven Rostedt
2005-12-26 15:35       ` Alistair John Strachan
2005-12-26 17:54         ` Lee Revell
2005-12-26 18:09           ` Jason Munro
2005-12-26 18:19             ` Lee Revell
2005-12-26 18:28               ` recommended mail clients Jaco Kroon
2005-12-26 18:43                 ` Lee Revell
2005-12-26 18:47                   ` Jaco Kroon
2005-12-26 18:48                 ` Lee Revell
2005-12-26 18:47                   ` Christoph Hellwig
2005-12-26 18:54                     ` Jaco Kroon
2005-12-29  9:49                   ` Coywolf Qi Hunt
2005-12-26 18:58                 ` Randy.Dunlap
2005-12-26 19:04                   ` Jaco Kroon
2005-12-26 19:12                   ` Jaco Kroon
2005-12-27 21:55                   ` Ryan Anderson
2005-12-26 19:18                 ` Jeff Garzik
2005-12-26 19:32                   ` Lee Revell
2005-12-26 20:32                     ` Pavel Machek
2005-12-26 18:24             ` recommended mail clients [was] [PATCH] ati-agp suspend/resume support (try 2) Lee Revell
2005-12-26 22:33             ` Jan Engelhardt
2005-12-26 20:03           ` Alistair John Strachan
2005-12-26 21:00             ` Lee Revell [this message]
2005-12-28  0:05               ` Michael Clark
2005-12-28  0:33                 ` Lee Revell
2005-12-28  1:09                 ` Peter Williams
2005-12-28  2:01                   ` Michael Clark
2005-12-28  2:10                     ` Steven Rostedt
2005-12-28  2:14                       ` Randy.Dunlap
2005-12-28 12:44                         ` Paolo Ornati
2005-12-28  2:12                     ` Randy.Dunlap
2005-12-28  3:22                       ` Peter Williams
2005-12-28  3:28                         ` Michael Clark
2005-12-28  3:33                           ` Randy.Dunlap
2005-12-28  3:39                             ` Randy.Dunlap
2005-12-28  7:22                               ` Stefan Smietanowski
2005-12-26 22:26         ` Jan Engelhardt
2005-12-27 15:20           ` Jason Munro
2005-12-27 15:45             ` Pavel Machek
2005-12-26 15:05     ` Lee Revell
2005-12-26 18:50       ` Randy.Dunlap
2005-12-27 15:48         ` Bob Copeland
     [not found]   ` <mailman.1135587661.17617.linux-kernel2news@redhat.com>
2005-12-31  3:28     ` Pete Zaitcev
2006-01-02 21:27       ` Tomasz Torcz

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=1135630831.8293.89.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=jaco@kroon.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rostedt@goodmis.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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