All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Joe Perches <joe@perches.com>, Jonathan Corbet <corbet@lwn.net>,
	Sanidhya Solanki <jpage.lkml@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: email-clients.txt
Date: Sun, 06 Dec 2015 22:35:34 +0100	[thread overview]
Message-ID: <1449437734.2515.31.camel@tiscali.nl> (raw)
In-Reply-To: <1449425464.7417.7.camel@perches.com>

On zo, 2015-12-06 at 10:11 -0800, Joe Perches wrote:
> The text editor for Evolution versions > 3.12 is broken
> and unrepairable.

My experiences with Evolution 3.16 tell me that might be correct.

> Evolution 3.16 has very poor behavior when replying to
> text emails with tabs.  A ">" character is added before
> every tab in the reply.

That made me shout at my laptop quite a few times already. Oddly enough,
Evolution behaved like it didn't notice that and just kept on doing
that. What an arrogant application...

Also note the annoying line breaks in my reply (written with Evolution
3.16.5). That nonsense also didn't happen in 3.12.

> Evolution 3.18 occasionally uses the Non-Breaking-Space
> (NBSP) character instead of the standand ASCII 32 space
> which breaks applying patches sent with that email client.

(I've only been using Evolution for a decade now. But still the thought
that I really should be looking into a new client scares me quite a
bit.)


Paul Bolle

  parent reply	other threads:[~2015-12-06 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06  6:09 [PATCH] Documentation: email-clients.txt Sanidhya Solanki
2015-12-06 15:30 ` Jonathan Corbet
2015-12-06 18:11   ` Joe Perches
2015-12-06 18:13     ` Jonathan Corbet
2015-12-07  0:10       ` Sanidhya Solanki
2015-12-07  4:13         ` Joe Perches
2015-12-07  5:24           ` Randy Dunlap
2015-12-06 21:35     ` Paul Bolle [this message]
2015-12-06 21:40       ` Paul Bolle
2015-12-06 20:52   ` Randy Dunlap
2015-12-07 18:16     ` Austin S Hemmelgarn
2015-12-07  0:01 Sanidhya Solanki
2015-12-07  8:03 ` Clemens Ladisch

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=1449437734.2515.31.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=corbet@lwn.net \
    --cc=joe@perches.com \
    --cc=jpage.lkml@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.