From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: juanjose.garcia.ripoll@csic.es, 40248@debbugs.gnu.org
Subject: bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus
Date: Sat, 28 Mar 2020 12:17:28 +0300 [thread overview]
Message-ID: <83tv287s9j.fsf@gnu.org> (raw)
In-Reply-To: <87a740ub2r.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 28 Mar 2020 09:40:12 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Juan José García-Ripoll
> <juanjose.garcia.ripoll@csic.es>,
> 40248@debbugs.gnu.org
> Date: Sat, 28 Mar 2020 09:40:12 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Lars, can you or someone of the Gnus team tell why
> > nnimap-open-connection-1 binds coding-system-for-* to 'binary? I
> > don't understand the rationale, as the code which uses this connection
> > seems to expect ASCII text in response.
>
> The IMAP connections (as do most network protocols) operate on octets,
> not ASCII.
But then only the encoding of the network process started by
nnimap-open-connection-1 should be made no-conversion. By contrast,
binding coding-system-for-* around the call to open-network-stream has
much wider consequences, as it affects _any_ code run as part of
open-network-stream, in particularly epg-find-configuration, which has
nothing to do with the network stream. nnimap-open-connection-1 is a
large function, so that binding affects quite a lot more than just the
network process it creates.
next prev parent reply other threads:[~2020-03-28 9:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 23:07 bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus Juan José García Ripoll
2020-03-27 8:18 ` Eli Zaretskii
2020-03-27 13:34 ` Eli Zaretskii
2020-03-27 16:21 ` Juan José García-Ripoll
2020-03-28 7:55 ` Eli Zaretskii
2020-03-28 8:40 ` Lars Ingebrigtsen
2020-03-28 9:17 ` Eli Zaretskii [this message]
2020-03-29 7:45 ` Lars Ingebrigtsen
2020-03-29 13:49 ` Eli Zaretskii
2020-03-28 14:03 ` Juan Jose Garcia Ripoll
2020-03-28 14:36 ` Eli Zaretskii
2020-03-29 7:48 ` Lars Ingebrigtsen
2020-03-29 13:52 ` Eli Zaretskii
2020-03-30 9:37 ` Robert Pluim
2020-03-30 13:10 ` Eli Zaretskii
2020-03-30 14:10 ` Robert Pluim
2020-03-30 14:33 ` Eli Zaretskii
2020-04-02 11:11 ` Lars Ingebrigtsen
2020-04-03 11:31 ` Eli Zaretskii
2020-04-03 11:43 ` Robert Pluim
2020-07-19 2:45 ` Lars Ingebrigtsen
2020-07-19 14:23 ` Eli Zaretskii
2020-07-19 14:29 ` Lars Ingebrigtsen
2020-07-19 14:43 ` Eli Zaretskii
2020-07-19 14:45 ` Lars Ingebrigtsen
2020-07-23 0:20 ` Juri Linkov
2020-07-23 13:36 ` Dmitry Gutov
2020-07-20 8:42 ` Robert Pluim
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=83tv287s9j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40248@debbugs.gnu.org \
--cc=juanjose.garcia.ripoll@csic.es \
--cc=larsi@gnus.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.
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).