All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-doc@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Dan Carpenter <error27@gmail.com>,
	Jes Sorensen <jes.sorensen@gmail.com>
Subject: [PATCH] Documentation/email-clients.txt: clarify Thunderbird section
Date: Thu, 10 Dec 2009 14:57:48 +0000	[thread overview]
Message-ID: <4B210C6C.3060103@tuffmail.co.uk> (raw)

1) Make it clearer that there are three different methods here,
   by using two different levels of indentation.

2) Reorder the different methods:

  - Disabling word wrap altogether should be the last option.
    It involves manually editing config files, and many Thunderbird
    users will not want to disable word wrap for normal (non-patch)
    messages.

  - "Preformat mode" should be the first option. It's really convenient.
    (Guess how I sent this patch).

Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
---
 Documentation/email-clients.txt |   56 +++++++++++++++++++++-----------------
 1 files changed, 31 insertions(+), 25 deletions(-)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index a618efa..c899444 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -180,34 +180,40 @@ Sylpheed (GUI)
 Thunderbird (GUI)
 
 By default, thunderbird likes to mangle text, but there are ways to
-coerce it into being nice.
-
-- Under account settings, composition and addressing, uncheck "Compose
-  messages in HTML format".
-
-- Edit your Thunderbird config settings to tell it not to wrap lines:
-      user_pref("mailnews.wraplength", 0);
-
-- Edit your Thunderbird config settings so that it won't use format=flowed:
-      user_pref("mailnews.send_plaintext_flowed", false);
-
-- You need to get Thunderbird into preformat mode:
-. If you compose HTML messages by default, it's not too hard. Just select
-  "Preformat" from the drop-down box just under the subject line.
-. If you compose in text by default, you have to tell it to compose a new
-  message in HTML (just as a one-off), and then force it from there back to
-  text, else it will wrap lines. To do this, use shift-click on the Write
-  icon to compose to get HTML compose mode, then select "Preformat" from
-  the drop-down box just under the subject line.
-
-- Allows use of an external editor:
-  The easiest thing to do with Thunderbird and patches is to use an
-  "external editor" extension and then just use your favorite $EDITOR
-  for reading/merging patches into the body text.  To do this, download
-  and install the extension, then add a button for it using
+coerce it into being nice.  Try one of the methods below.
+
+- Get Thunderbird into preformat mode:
+
+  - If you compose HTML messages by default, select "Preformat" from the
+    drop-down box just under the subject line.
+
+  - If you compose in text by default, you have to tell it to compose a new
+    message in HTML (just as a one-off), and then force it from there back to
+    text, else it will wrap lines. To do this, use shift-click on the Write
+    icon to compose to get HTML compose mode, then select "Preformat" from
+    the drop-down box just under the subject line.
+
+- Use an external editor:
+
+  You can install an "external editor" extension which will allow you to use
+  your favorite $EDITOR for reading/merging patches into the body text.
+  First download and install the extension, then add a button for it using
   View->Toolbars->Customize... and finally just click on it when in the
   Compose dialog.
 
+- Disable word wrap completely:
+
+  1. Under account settings, composition and addressing, uncheck "Compose
+     messages in HTML format".
+
+  2. Edit your Thunderbird config settings to tell it not to wrap lines:
+
+             user_pref("mailnews.wraplength", 0);
+
+  3. Edit your Thunderbird config settings so it won't use format=flowed:
+
+             user_pref("mailnews.send_plaintext_flowed", false);
+
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 TkRat (GUI)
 
-- 
1.6.3.3




             reply	other threads:[~2009-12-10 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 14:57 Alan Jenkins [this message]
2009-12-10 15:16 ` [PATCH] Documentation/email-clients.txt: clarify Thunderbird section jim owens
2009-12-10 16:25   ` Alan Jenkins
2009-12-10 16:47     ` jim owens
2009-12-10 22:05     ` Chris Friesen
2009-12-10 22:16       ` Randy Dunlap

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=4B210C6C.3060103@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=error27@gmail.com \
    --cc=jes.sorensen@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.