Re: send new reply from gnus hangs

[Óscar Fuentes]

Óscar Fuentes <address@hidden> writes:

> Óscar Fuentes <address@hidden> writes:
>
>> Óscar Fuentes <address@hidden> writes:
>>
>>> Óscar Fuentes <address@hidden> writes:
>>>
>>>> Andy Moreton <address@hidden> writes:
>>>>
>>>>> A recent change on the master branch (within the last week) prevents
>>>>> gnus from sending replies to newsgroups - it gets stuck with
>>>>> "sending..." in the message area.
>>>>>
>>>>> I've looked at the recent commits that might affect gnus, but nothing
>>>>> obvious jumps out. I'm not sure what the problem is or how to start
>>>>> debugging it.
>>>>>
>>>>> Does anyone have any ideas ?
>>>>
>>>> git bisect
>>>
>>> f113512ffc works
>>
>> 10582d05 works, but the step at 60286626 and f2a7acdd suffer from a
>> different problem:
>>
>> Debugger entered--Lisp error: (void-function gnus-data-find-in)
>>   gnus-data-find-in(237368 ((237368 32 2 [237368 "Re: send new reply
>> from gnus hangs" "Óscar Fuentes <address@hidden>" "Mon, 10 Jun 2019
>> 00:47:56 +0200" "<address@hidden>"
>> "<address@hidden> <87r285nhxb.fsf@telefo..." 3937 20
>> "news.gmane.org gmane.emacs.devel:237368" nil] 0)))
>>   gnus-request-article-this-buffer(237368 "gmane.emacs.devel")
>>   gnus-article-prepare(237368 nil)
>>   gnus-summary-display-article(237368 nil)
>>   gnus-summary-select-article(nil nil pseudo)
>>   gnus-summary-scroll-up(1)
>>   funcall-interactively(gnus-summary-scroll-up 1)
>>   call-interactively(gnus-summary-scroll-up nil nil)
>>   command-execute(gnus-summary-scroll-up)
>>
>>
>> Probably the bisection is useless because this bug was fixed or
>> superseded by the bug that causes the hang.
>
> 40bc7ddb75 works.

f2a7acdde7207f9 is the supposed bad commit, which makes no sense.

Once again, bisecting Emacs turns nothing of value. sigh.

Let's try "human-guided" bisecting.