From: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Two errors in 27.* with Windows
Date: Thu, 26 Mar 2020 20:01:37 +0100 [thread overview]
Message-ID: <86h7yb9bzi.fsf@csic.es> (raw)
In-Reply-To: 834kub9c93.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
> Please report each problem separately using "M-x report-emacs-bug".
> That will allow to deal with each one in a separate thread. Also, the
> bug tracker is the proper place for discussing bugs and looking for
> their solutions.
Sorry, being so close to release I wasn't sure whether that would be the
right place.
> What does gpg.exe output in this case? Does it output human-readable
> text, or does it output binary byte stream? If the latter, how come
> ^M corruption is an issue?
The problem is not gpg's output. That is parsed properly if I invoke
epg's routines before Gnus: they are parsed in a text buffer (not
binary) and the version number is identified (x.x.x). The problem is
that, because package.el now does not trigger the identification of gpg,
this happens in a binary buffer. The routines parse the output
correctly, but the protocols, version numbers and everything else get
parsed with an ending ^M -> "x.x.x^M" which breaks the identification of
version number. If I run epg-find-configuration _after_ or _before_
Gnus, the parsing is done in a text buffer and the ^M is not
appended. Everything is fine. I am unable to find where the switch from
'nil to 'binary happens in the new code.
Hope this is clear. I will report the bugs separately later on.
Cheers,
--
Juan José García Ripoll
http://juanjose.garciaripoll.com
http://quinfog.hbar.es
next prev parent reply other threads:[~2020-03-26 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 16:21 Two errors in 27.* with Windows Juan José García-Ripoll
2020-03-26 16:34 ` Juan José García-Ripoll
2020-03-26 18:55 ` Eli Zaretskii
2020-03-26 19:01 ` Juan José García-Ripoll [this message]
2020-03-26 19:45 ` Eli Zaretskii
2020-03-26 22:09 ` Juan José García-Ripoll
2020-03-27 7:08 ` Eli Zaretskii
2020-03-27 7:32 ` Eli Zaretskii
2020-03-27 12:45 ` Juan José García-Ripoll
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=86h7yb9bzi.fsf@csic.es \
--to=juanjose.garciaripoll@gmail.com \
--cc=emacs-devel@gnu.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).