From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: Andreas Schwab <schwab@linux-m68k.org>
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:43:35 +0200 [thread overview]
Message-ID: <sjomdyzzzzzz.1lj.xxuns.g6.gal@galex-713.eu> (raw)
In-Reply-To: <87o9coigx5.fsf@igel.home> (Andreas Schwab's message of "Sun, 23 Sep 2018 13:36:54 +0200")
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?
Here I’m receiving (and splitting) some thousands of mail per day (most
of it lists, newsletters, and spam, all using list-id (yes even spam))
and it’s fine.
If that’s really an issue, since the buffer must be decoded anyway at
some time… cannot emacs store it decoded at worse? with some
emacs-specific way of specifying encoding (maybe utf-8 by default? in
file? per config?
I mean, it was pointed indeed having it to nil by default seems to imply
incorrect behavior since headers may be encoded anyway and I hardly see
a case where encoding is more important than encoded content (why not
still, but…) and since we’re in the case of a generalistic function… or
is the user supposed to find the function for decoding the headers she’s
interested in and decode it manually before parsing it?
next prev parent reply other threads:[~2018-09-23 11:43 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 [this message]
2018-09-23 11:50 ` Andreas Schwab
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sjomdyzzzzzz.1lj.xxuns.g6.gal@galex-713.eu \
--to=galex-713@galex-713.eu \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).