From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jules Tamagnan Newsgroups: gmane.emacs.bugs Subject: bug#23609: 25.0.92; Python eldoc freeze Date: Fri, 27 May 2016 15:43:18 -0400 Message-ID: <861t4nxp61.fsf@gmail.com> References: <867fejo4g2.fsf@gmail.com> <57454201.10607@easy-emacs.de> <86bn3umahs.fsf@gmail.com> <5745C5D9.50701@easy-emacs.de> <861t4orf3h.fsf@gmail.com> <834m9k3hmz.fsf@gnu.org> <83wpmg229w.fsf@gnu.org> <86mvncpwso.fsf@gmail.com> <83d1o726si.fsf@gnu.org> <86lh2vo4yd.fsf@gmail.com> <83inxzz5ha.fsf@gnu.org> <86a8jbxqjd.fsf@gmail.com> <83fut3z4bq.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1464378268 11159 80.91.229.3 (27 May 2016 19:44:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 May 2016 19:44:28 +0000 (UTC) Cc: 23609@debbugs.gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 27 21:44:17 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b6Ng8-0002ga-Rm for geb-bug-gnu-emacs@m.gmane.org; Fri, 27 May 2016 21:44:17 +0200 Original-Received: from localhost ([::1]:47617 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6Ng7-0003VC-VH for geb-bug-gnu-emacs@m.gmane.org; Fri, 27 May 2016 15:44:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6Ng0-0003Uo-IF for bug-gnu-emacs@gnu.org; Fri, 27 May 2016 15:44:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b6Nfu-0002MI-Ib for bug-gnu-emacs@gnu.org; Fri, 27 May 2016 15:44:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:58791) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6Nfu-0002MD-Eq for bug-gnu-emacs@gnu.org; Fri, 27 May 2016 15:44:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1b6Nfu-0005Of-9j for bug-gnu-emacs@gnu.org; Fri, 27 May 2016 15:44:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jules Tamagnan Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 27 May 2016 19:44:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23609 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 23609-submit@debbugs.gnu.org id=B23609.146437820620693 (code B ref 23609); Fri, 27 May 2016 19:44:02 +0000 Original-Received: (at 23609) by debbugs.gnu.org; 27 May 2016 19:43:26 +0000 Original-Received: from localhost ([127.0.0.1]:42895 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b6NfK-0005Nh-Kl for submit@debbugs.gnu.org; Fri, 27 May 2016 15:43:26 -0400 Original-Received: from mail-qk0-f176.google.com ([209.85.220.176]:36682) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b6NfJ-0005NV-PT for 23609@debbugs.gnu.org; Fri, 27 May 2016 15:43:26 -0400 Original-Received: by mail-qk0-f176.google.com with SMTP id x7so86608074qkd.3 for <23609@debbugs.gnu.org>; Fri, 27 May 2016 12:43:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=vLNVweTbpiUlQ7glpqKEbb8A6fdJnMtK3Yq8py85KhQ=; b=ge4ViHFPwjPTRCWkKr29f3G7bGZHjfA1yre8PjWe7NyKq2cQrafKvMlMZ0dbUiXDaI fjm/wZ1ZHxR/dJWXWfX2ZHl/RXtlfVXtg8CAqo1rapOsd7QsXKkhImdDqkVH41eXYMP7 VM6vyVgPZdLQ2QIjmwlf/5jxFmZ8IQ8MbD//MavVdHnA2zpBtLDby+aMSKW1kFzEn7Ux /VdQWIPZLMstACd8qQyUtODISQMpJcKjDSZK9A/L1Qf3XNeRwsVrHPtzaySEK4lHomWa BSBkYmzmJ4BFUWX3rN3gkk2WGSxg3yrBeSh94EJ78RDaWsRAbrJorDySxypOpGCzS0y+ nAyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=vLNVweTbpiUlQ7glpqKEbb8A6fdJnMtK3Yq8py85KhQ=; b=Fr8uyH4SZMspEG1gMA1GcIo4mB7uxd4VJwbAGepfrqJl/t2KEbPoBP8sQd02kb3e03 V13TKUgpUFoPdeUea+ciMiurqX7Wq9m0vJzSDRfpHzwFwylaCefAE5m20yNVUDqu3/yj ssS4EzDbMd7qpkEvE3a7uGs1rR8/s771zRM4+loUzutbOGLTQHi5QXkQ8FkphI68IfGt JEZsbJUkkYUyB+q2emJVyphTVfk9a86KxWCGjWc94xUf9O7LHFjYM85bNXFzZI7yMkao kf6Ql8Bt4/9W87eWhdjqbyuGZ+IUgSOgl8hbr8HDEEnILrGpEwb+vM/d2Sp0GtWhmF5J dzgg== X-Gm-Message-State: ALyK8tK50912P21/1c6mL3V4CijPt0QEa4XljoUv6/wn5YAJSikmbXXmEoQZFzuuDVb5/g== X-Received: by 10.55.166.139 with SMTP id p133mr15244996qke.161.1464378200220; Fri, 27 May 2016 12:43:20 -0700 (PDT) Original-Received: from bandersnatch ([130.132.236.142]) by smtp.gmail.com with ESMTPSA id 13sm4209546qhr.9.2016.05.27.12.43.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 May 2016 12:43:19 -0700 (PDT) In-Reply-To: <83fut3z4bq.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 27 May 2016 22:30:33 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.92 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:118784 Archived-At: Eli Zaretskii writes: >> From: Jules Tamagnan >> Cc: 23609@debbugs.gnu.org, dgutov@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.