unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Two errors in 27.* with Windows
Date: Thu, 26 Mar 2020 23:09:08 +0100	[thread overview]
Message-ID: <86r1xe6a63.fsf@csic.es> (raw)
In-Reply-To: <83zhc299xq.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Mar 2020 21:45:53 +0200")

Apologies for following up here, but there are questions below that I
don't know how to answer:

Eli Zaretskii <eliz@gnu.org> writes:
> Sorry, no, it isn't.  When you report this problem to the bug tracker,
> please make sure the description answers the following questions:
>
>   . what do you mean by "binary buffer" (or "text buffer")?

I have no way to debug this problem clearly. Obviously the problem is in
call-process producing output in a buffer and that being parsed in two
different ways: outside Gnus, it is parsed in a way that does not ignore
^M characters; inside Gnus it sometimes happens and sometimes does not.

>   . I didn't say that gpg's output is the problem, I asked whether
>     it's human-readable text or byte stream in this case.  I
>     understand it's text (the gpg version number), in which case I
>     don't understand why the code sets coding-system-for-read to
>     'binary' -- it sounds like a mistake.  Can you show the place
>     where this is done?

No. That is what I was asking in my earlier email. I do not know how to
trace where this happens. The most I have managed is to set an "advice"
function that interferes CALL-PROCESS and output properties of the
buffer that is current when it is invoked, but I have no idea how to
find which part of the code selects those values. Man, this code base is huge.

>   . you are assuming that using nil for coding-system-for-read is
>     correct, but I don't think it is, so if you can show where that is
>     done, it might be the beginning of the solution.

No, I am not assuming it is correct: I am assuming it is the way it was
done before. It was so in 26.3 and it is so in 27.0.90 before Gnus is
invoked.

And I am not being lazy: I am totally lost at where this variable is
changed or how. I have spent 4 hours this morning just identifying what
prevented me from opening email, and just managed to get what I showed
before. If I know where the wrong assignment was taking place I would
have provided a patch, not a bug report.

But this is kind of a serious bug: it breaks opening of .authinfo.gpg.

-- 
Juan José García Ripoll

Quantum Information and Foundations Group
Institute of Fundamental Physics IFF-CSIC
Calle Serrano 113b, Madrid 28006 Spain
http://quinfog.hbar.es - http://juanjose.garcia.ripoll



  reply	other threads:[~2020-03-26 22:09 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
2020-03-26 19:45     ` Eli Zaretskii
2020-03-26 22:09       ` Juan José García-Ripoll [this message]
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=86r1xe6a63.fsf@csic.es \
    --to=juanjose.garciaripoll@gmail.com \
    --cc=eliz@gnu.org \
    --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).