GNU bug report logs - #23609
25.0.92; Python eldoc freeze

Previous Next

Full log

View this message in rfc822 format

From: Jules Tamagnan <jtamagnan <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: dgutov <at> yandex.ru, 23609 <at> debbugs.gnu.org
Subject: bug#23609: 25.0.92; Python eldoc freeze
Date: Fri, 27 May 2016 15:43:18 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Jules Tamagnan <jtamagnan <at> gmail.com>
>> Cc: 23609 <at> debbugs.gnu.org,  dgutov <at> yandex.ru
>> Date: Fri, 27 May 2016 15:13:42 -0400
>>
>> >   . The problem happens only when the interpreter is busy doing
>> >     something, is that right?  If so, perhaps we shouldn't turn
>> >     eldoc-mode off, but instead simply return?
>>
>> The problem with simply returning instead of canceling the behavior for
>> the buffer is that a second (or so) later eldoc will once again try to
>> fetch the documentation and will be frozen until the timeout. This means
>> that you will be repeatidly be getting frozen as you type. It won't be
>> a complete freeze that crashes emacs but it won't be pleasant.
>
> Once again, perhaps I misunderstand the nature of the problem, but
> doesn't it happen only when the Python interpreter is busy doing
> something when the eldoc function is invoked?  If so, then the next
> time eldoc is invoked, the Python interpreter might not be busy, and
> the feature will work without hanging, right?  Or am I missing
> something?

No that's exactly correct. I'm just thinking of it from the point of
view that perhaps somebody is plotting a graph from the interpreter
which causes the interpreter to be busy. Then while having that graph
open they would still like to be able to edit their code (I have been in
this situation dozens of times). Or if the code they are running takes a
a minute or two there is a good chance that they would want to edit some
of the code while it is running. In those scenarios I feel like it makes
sense to stop eldoc from doing the automatic checking permanently for
that buffer because otherwise my work would be constantly interrupted.

If we plan on the process only being busy for a few seconds at a time then I
understand where you are coming from.

I have also found for python at least that there are very good tools out
there that work better than eldoc and which use a separate process so
they never hang up.

>> >   . If we do turn eldoc-mode off, then I think a message to that
>> >     effect is in order, to let the user know.
>>
>> We're not turning it off but yes a warning would definitely be nice.
>
> Well, we turn off the automatic display of the documentation in the
> echo area, right?

Yep but eldoc mode is still on

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.