From: Andreas Schwab <schwab@linux-m68k.org>
To: "Garreau\, Alexandre" <galex-713@galex-713.eu>
Cc: Teemu Likonen <tlikonen@iki.fi>, emacs-devel@gnu.org
Subject: Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header.
Date: Sun, 23 Sep 2018 13:50:37 +0200 [thread overview]
Message-ID: <87k1ncigaa.fsf@igel.home> (raw)
In-Reply-To: <sjomdyzzzzzz.1lj.xxuns.g6.gal@galex-713.eu> (Alexandre Garreau's message of "Sun, 23 Sep 2018 13:43:35 +0200")
On Sep 23 2018, "Garreau, Alexandre" <galex-713@galex-713.eu> wrote:
> Le 23/09/2018 à 13h36, Andreas Schwab a écrit :
>> On Sep 23 2018, "Garreau, Alexandre" <galex-713@galex-713.eu> wrote:
>>
>>> Why isn’t this behavior the default?
>>
>> My guess would be that it was too slow.
>
> than now? did it change?
It changed when the option was introduced (back in 2002).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2018-09-23 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 0:04 #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header Garreau, Alexandre
2018-09-23 6:05 ` Teemu Likonen
2018-09-23 8:57 ` Garreau, Alexandre
2018-09-23 10:56 ` Teemu Likonen
2018-09-23 11:37 ` May t be the default for nnmail-mail-splitting-decodes in Emacs? (Was: Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header) Garreau, Alexandre
2018-09-23 11:36 ` #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header Andreas Schwab
2018-09-23 11:43 ` Garreau, Alexandre
2018-09-23 11:50 ` Andreas Schwab [this message]
2018-09-23 12:30 ` Why nnmail-mail-splitting-decodes defaults to nil (Was: Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header) Garreau, Alexandre
2018-09-27 22:05 ` Why nnmail-mail-splitting-decodes defaults to nil Eric Abrahamsen
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=87k1ncigaa.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=galex-713@galex-713.eu \
--cc=tlikonen@iki.fi \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.