unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: jtamagnan@gmail.com, 23609@debbugs.gnu.org
Subject: bug#23609: 25.0.92; Python eldoc freeze
Date: Thu, 26 May 2016 19:48:59 +0300	[thread overview]
Message-ID: <83wpmg229w.fsf@gnu.org> (raw)
In-Reply-To: <be230869-d21b-05ba-bb25-affd7e8349ed@yandex.ru> (message from Dmitry Gutov on Thu, 26 May 2016 19:37:57 +0300)

> Cc: 23609@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Thu, 26 May 2016 19:37:57 +0300
> 
> On 05/26/2016 07:31 PM, Eli Zaretskii wrote:
> 
> > Not IMO, since an easy workaround is available.
> 
> Disabling eldoc-mode? It's cutting off a very handy feature.

A feature that wasn't turned on in 24.5, and whose turning on exposed
this bug.  At least that's my understanding.

If I'm right, then either this isn't a regression, or a regression
with an easy workaround.

Which doesn't mean we shouldn't try fixing this bug, just that it is
not critical enough to delay the release if not fixed.  Motivated
volunteers are very much encouraged to work on a fix; if that fix is
safe, I see no reason not to accept it on the release branch.

Thanks.





  reply	other threads:[~2016-05-26 16:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 15:34 bug#23609: 25.0.92; Python eldoc freeze Jules Tamagnan
2016-05-25  6:11 ` Andreas Röhler
2016-05-25 15:18   ` Jules Tamagnan
2016-05-25 15:33     ` Andreas Röhler
2016-05-26 15:52       ` Jules Tamagnan
2016-05-26 16:31         ` Eli Zaretskii
2016-05-26 16:37           ` Dmitry Gutov
2016-05-26 16:48             ` Eli Zaretskii [this message]
2016-05-26 17:13               ` Jules Tamagnan
2016-05-27  9:23                 ` Eli Zaretskii
2016-05-27 14:41                   ` Eli Zaretskii
2016-05-27 14:52                     ` Jules Tamagnan
2016-05-27 19:06                       ` Eli Zaretskii
2016-05-27 15:42                     ` Glenn Morris
2016-05-27 18:41                       ` Eli Zaretskii
2016-05-27 16:12                   ` Jules Tamagnan
2016-05-27 16:18                     ` Dmitry Gutov
2016-05-27 17:12                       ` Jules Tamagnan
2016-05-27 18:26                         ` Dmitry Gutov
2016-05-27 18:39                           ` Jules Tamagnan
2016-05-27 18:50                             ` Dmitry Gutov
2016-05-27 18:57                               ` Jules Tamagnan
2016-05-27 19:05                     ` Eli Zaretskii
2016-05-27 19:13                       ` Jules Tamagnan
2016-05-27 19:30                         ` Eli Zaretskii
2016-05-27 19:43                           ` Jules Tamagnan
2016-05-27 19:49                             ` Eli Zaretskii
2016-05-27 20:19                               ` Jules Tamagnan
2016-05-28  7:53                                 ` Eli Zaretskii
2016-05-31 17:35                                   ` Jules Tamagnan
2016-06-06 14:08                                     ` Jules Tamagnan
2016-06-06 15:15                                       ` Eli Zaretskii
2016-06-10  9:10                                       ` Eli Zaretskii
2016-05-27  6:09             ` Andreas Röhler

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=83wpmg229w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23609@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=jtamagnan@gmail.com \
    /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).