unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: eflanigan00@hotmail.com, 25067@debbugs.gnu.org
Subject: bug#25067: #25067 Emacs pretest 25.1.91 - ipython completion
Date: Sat, 04 Feb 2017 09:39:46 -0500	[thread overview]
Message-ID: <877f56ow99.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83zii28hc5.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Feb 2017 10:56:26 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: npostavs@users.sourceforge.net
>> Date: Fri, 03 Feb 2017 19:03:40 -0500
>> Cc: "25067@debbugs.gnu.org" <25067@debbugs.gnu.org>
>> 
>> The behaviour from 25.1 can be restored by doing
>> 
>>     (add-to-list 'python-shell-completion-native-disabled-interpreters
>>                  "ipython")
>> 
>> So it looks like the problem is the fix for #24401 which enables native
>> completion work for python 3.5, also enables it for ipython, but native
>> completion doesn't actually work for ipython.
>
> Is there any safe way to fix this for Emacs 25.2?

I think the patch below is safe.  Although I can't say that I understand
what "native completion" actually means.

--- i/lisp/progmodes/python.el
+++ w/lisp/progmodes/python.el
@@ -3255,8 +3255,10 @@ python-shell-completion-string-code
   "Completion string code must work for (i)pdb.")
 
 (defcustom python-shell-completion-native-disabled-interpreters
-  ;; PyPy's readline cannot handle some escape sequences yet.
-  (list "pypy")
+  ;; PyPy's readline cannot handle some escape sequences yet.  Native
+  ;; completion was found to be non-functional for IPython (see
+  ;; Bug#25067).
+  (list "pypy" "ipython")
   "List of disabled interpreters.
 When a match is found, native completion is disabled."
   :version "25.1"







  reply	other threads:[~2017-02-04 14:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 20:42 bug#25067: Emacs pretest 25.1.90 - ipython completion Edward Flanigan
     [not found] ` <handler.25067.B.148045342531549.ack@debbugs.gnu.org>
2016-11-29 21:12   ` bug#25067: Acknowledgement (Emacs pretest 25.1.90 - ipython completion) Edward Flanigan
2016-11-29 23:02     ` Noam Postavsky
2016-12-18 15:23       ` Eli Zaretskii
2016-12-18 16:16         ` Clément Pit--Claudel
2016-12-18 17:01           ` Eli Zaretskii
2016-12-18 17:29             ` Clément Pit--Claudel
2017-01-03 17:27 ` bug#25067: #25067 Emacs pretest 25.1.91 - ipython completion Edward Flanigan
2017-02-04  0:03   ` npostavs
2017-02-04  8:56     ` Eli Zaretskii
2017-02-04 14:39       ` npostavs [this message]
2017-02-04 16:52         ` Eli Zaretskii
2017-02-07  1:51           ` Clément Pit--Claudel
2017-02-07 15:35             ` Eli Zaretskii
2017-02-08  2:21               ` npostavs

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=877f56ow99.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25067@debbugs.gnu.org \
    --cc=eflanigan00@hotmail.com \
    --cc=eliz@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).