From: Augusto Stoffel <arstoffel@gmail.com>
To: Carlos Pita <carlosjosepita2@gmail.com>
Cc: 51196@debbugs.gnu.org
Subject: bug#51196: 29.0.50; python.el eldoc problems
Date: Fri, 15 Oct 2021 22:22:29 +0200 [thread overview]
Message-ID: <87o87qdomy.fsf@gmail.com> (raw)
In-Reply-To: <m25yu0bif6.fsf@gmail.com> (Carlos Pita's message of "Wed, 13 Oct 2021 20:42:53 -0300")
On Wed, 13 Oct 2021 at 20:42, Carlos Pita <carlosjosepita2@gmail.com> wrote:
> I've expressed this opinion before regarding the autocompletion
> mechanism, which shows similar shortcomings, I believe that the best
> options are:
>
> - Have a sane, solid and simple python.el with good syntax highlighting,
> movements commands, folding, etc. and leave the cleverness to elpy,
> lsp-mode, eglot, emacs-jupyter or whatever.
But the problematic Eldoc functionality is disabled by default, right?
So leaving it there doesn't hurt anyone --- except for the unwitting
user who doesn't know that this feature is kind of broken.
>
> - If we still want some basic autocompletion and documentation features
> in this module, then let's do it right and open a thread in the
> underlying process and talk to it, avoiding the flaky and dangerous
> mechanism of pretending that emacs is the user typing.
Personally I have zero motivation to implement this, because it would
still require evaluating code before one can get completion or
docstrings. Nowadays there are decent static analyzers for Python out
there.
next prev parent reply other threads:[~2021-10-15 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 23:42 bug#51196: 29.0.50; python.el eldoc problems Carlos Pita
2021-10-15 2:05 ` Carlos Pita
2021-10-15 20:30 ` Augusto Stoffel
2021-10-15 20:22 ` Augusto Stoffel [this message]
2021-10-15 20:33 ` Carlos Pita
2021-10-16 9:15 ` Augusto Stoffel
2021-10-16 18:49 ` Carlos Pita
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=87o87qdomy.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=51196@debbugs.gnu.org \
--cc=carlosjosepita2@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).