Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753586AbbLFPar (ORCPT ); Sun, 6 Dec 2015 10:30:47 -0500 Received: from tex.lwn.net ([70.33.254.29]:55093 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753358AbbLFPai (ORCPT ); Sun, 6 Dec 2015 10:30:38 -0500 Date: Sun, 6 Dec 2015 08:30:37 -0700 From: Jonathan Corbet To: Sanidhya Solanki Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Documentation: email-clients.txt Message-ID: <20151206083037.2bde6e58@lwn.net> In-Reply-To: <20151206010939.13c6a32f@gmail.com> References: <20151206010939.13c6a32f@gmail.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3302 Lines: 84 On Sun, 6 Dec 2015 01:09:39 -0500 Sanidhya Solanki wrote: > Patch included below. As an aside, thank you for the excellent work on > the books and other documentation. Thanks for the nice comments. Future praise, however, should go below the "---" marker so I don't have to edit it out of the changelogs :) > Documentation: email-clients.txt > > The information for Claws Mail, Evolution and Thunderbird was out of > date. It has been updated with new instructions and warnings. So I feel like I'm missing some sort of intentional irony, but I do have to point out that this patch has been corrupted by your mailer and cannot be applied. The usual advice here applies: try sending the email to yourself and applying the result. > diff --git a/Documentation/email-clients.txt > b/Documentation/email-clients.txt index 2d485de..8819c90 100644 > --- a/Documentation/email-clients.txt > +++ b/Documentation/email-clients.txt > @@ -79,17 +79,27 @@ to insert into the message. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Claws Mail (GUI) > > -Works. Some people use this successfully for patches. > +Tested and Works as of December 2015. Some people use this successfully > +for patches. Not sure we need datestamps like this here. In any case, a few kernel developers are known to use claws - myself included. We test it every day :) > To insert a patch use Message->Insert File (CTRL+i) or an external > editor. > If the inserted patch has to be edited in the Claws composition window > "Auto wrapping" in Configuration->Preferences->Compose->Wrapping > should be -disabled. > +disabled. Also, under the heading "View", sub-heading "Character > Encoding" +, choose "Unicode (UTF - 8)" > + > +Do remember that if you insert or type something in the main text area, > +and decide to delete it, you will need to reset the formatting by > opening +a new window for the change you want to make. Re-using the > window in which +you deleted the text will lead to the new message > being mangled. ...and this makes no sense to me. I've never seen any such behavior in claws? > Evolution (GUI) > > +As of December 2015, the composing & inserting method described below > +does not work. Could it really be that nobody is using evolution? Much nicer here would be to describe how it fails to work, and, ideally, come up with a fix. > Some people use this successfully for patches. > > When composing mail select: Preformat > @@ -244,8 +254,9 @@ Sylpheed (GUI) > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Thunderbird (GUI) > > -Thunderbird is an Outlook clone that likes to mangle text, but there > are ways -to coerce it into behaving. > +Thunderbird is an Outlook clone that likes to mangle text, but there > are +ways to coerce it into behaving. In December 2015, the internal > editor +options do not appear to work. Again, what's the problem here? I suspect there are people using Thunderbird out there, how are they doing it if the documented approach doesn't work? Thanks, jon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/