From: Carlos Pita <carlosjosepita@gmail.com>
To: 51010@debbugs.gnu.org
Subject: bug#51010: 29.0.50; python completion breaks upon non-trivial rl config
Date: Sat, 9 Oct 2021 14:22:28 -0300 [thread overview]
Message-ID: <88E85B14-518F-4F18-B2F0-96BA2FDA981C@gmail.com> (raw)
In-Reply-To: <CAELgYhdHnovTbwyD5ALDoGF+09+GSFCuFMoYqSggtXyL-RyBnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Hi,
my apologies for the insistence, but please take a look a this, it’s a very simple change and although wrt python.el it just removes an annoying message ("Your ‘python-shell-interpreter’ doesn’t seem to support readline") and avoids disabling native completion altogether (which, anyway, as I’ve discussed elsewhere, I believe doesn’t add much in terms of features as it adds in terms of problems), wrt org-babel the problem is actually serious since trying to evaluate a python code block without first blacklisting python from native completion freezes emacs to death and seemingly a restart is needed. Of course, org-babel should be more robust in this regard but some help from python.el won’t hurt.
Best regards,
Carlos
PS: perhaps I should have titled this issue as “python completion freezes emacs to death” ;)
[-- Attachment #2: Type: text/html, Size: 1687 bytes --]
next prev parent reply other threads:[~2021-10-09 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 14:59 bug#51010: 29.0.50; python completion breaks upon non-trivial rl config Carlos Pita
2021-10-09 17:22 ` Carlos Pita [this message]
2021-10-10 11:50 ` Augusto Stoffel
2021-10-10 17:27 ` Carlos Pita
2021-10-14 0:46 ` Carlos Pita
2021-10-14 0:50 ` Carlos Pita
2021-10-14 7:35 ` Eli Zaretskii
2021-10-15 1:15 ` Carlos Pita
2021-10-15 6:52 ` Eli Zaretskii
2021-10-19 23:20 ` Carlos Pita
2021-10-20 11:53 ` Eli Zaretskii
2021-10-30 16:09 ` Stefan Kangas
2021-10-30 16:14 ` Eli Zaretskii
2021-10-30 16:37 ` Stefan Kangas
2021-10-30 18:19 ` Carlos Pita
2021-11-05 7:11 ` Stefan Kangas
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=88E85B14-518F-4F18-B2F0-96BA2FDA981C@gmail.com \
--to=carlosjosepita@gmail.com \
--cc=51010@debbugs.gnu.org \
/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).