From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "Андрей Парамонов" <cmr.pent@gmail.com>
Cc: 28580@debbugs.gnu.org
Subject: bug#28580: python.el: native completion setup failed
Date: Sun, 24 Sep 2017 17:00:28 -0400 [thread overview]
Message-ID: <87tvzrlslv.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CAC4Co6N2=gFpNW9uFzkfVZhe6hf5bbvpRqdrVbou=kdibYHBBA@mail.gmail.com> ("Андрей Парамонов"'s message of "Sun, 24 Sep 2017 23:34:07 +0300")
Андрей Парамонов <cmr.pent@gmail.com> writes:
> That should be suboptimal -- otherwise why the warning?
> What could make the "native" completion fail?
Does M-: (python-shell-completion-native-try) RET in the *Python* buffer
return nil? Perhaps try putting some `message' calls into
python-shell-completion-native-get-completions? (Using the debugger is a
bit tricky due to the timing of process communication.) Especially
check the contents of the current inside the `when' block at the end:
;; Grab output until our dummy completion used as
;; output end marker is found.
(when (python-shell-accept-process-output
process python-shell-completion-native-output-timeout
comint-redirect-finished-regexp)
(re-search-backward "0__dummy_completion__" nil t)
(cl-remove-duplicates
(split-string
(buffer-substring-no-properties
(line-beginning-position) (point-min))
"[ \f\t\n\r\v()]+" t)
:test #'string=))
> How to check if it's really the case?
Try the recipe in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28051#8
and see if you suffer from that bug.
next prev parent reply other threads:[~2017-09-24 21:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 15:56 bug#28580: python.el: native completion setup failed Андрей Парамонов
2017-09-24 16:14 ` Noam Postavsky
2017-09-24 16:56 ` Андрей Парамонов
2017-09-24 17:51 ` Noam Postavsky
2017-09-24 18:02 ` Андрей Парамонов
2017-09-24 18:09 ` Noam Postavsky
2017-09-24 18:16 ` Андрей Парамонов
2017-09-24 19:39 ` Noam Postavsky
2017-09-24 19:57 ` Андрей Парамонов
2017-09-24 20:06 ` Noam Postavsky
2017-09-24 20:19 ` Андрей Парамонов
2017-09-24 20:30 ` Noam Postavsky
2017-09-24 20:34 ` Андрей Парамонов
2017-09-24 21:00 ` Noam Postavsky [this message]
2017-09-24 21:08 ` Андрей Парамонов
2017-09-24 21:31 ` Noam Postavsky
2017-09-24 21:37 ` Андрей Парамонов
2017-10-03 4:01 ` Noam Postavsky
2017-10-12 19:40 ` Noam Postavsky
2017-10-13 3:28 ` Noam Postavsky
2017-10-15 18:23 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvzrlslv.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=28580@debbugs.gnu.org \
--cc=cmr.pent@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.