From: Rasmus <rasmus@gmx.us>
To: monnier@iro.umontreal.ca
Cc: 18582@debbugs.gnu.org, fabian@anue.biz
Subject: bug#18582: 24.4.50; [python.el] completion error
Date: Wed, 01 Oct 2014 13:21:20 +0200 [thread overview]
Message-ID: <87iok4xcgf.fsf@gmx.us> (raw)
In-Reply-To: <jwvlhp0zkm4.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 30 Sep 2014 20:45:29 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> When I try to complete something in a python-buffer I get an error
>> with the below backtrace. I couldn't find other reports on this
>> issue, but maybe I overlooked something?
>
> Could you try it with the code from the `emacs-24' branch instead?
> I tried your recipe and got a backtrace, but a different one. I think
> I fixed it.
Okay, I changed my build-script to download from:
http://bzr.savannah.gnu.org/r/emacs/emacs-24/
It was trunk at the end of the url before. I don't know bzr well, so
I might have done something wrong.
If this means anything to you:
(emacs-bzr-get-version) => "ueno@gnu.org-20141001022515-zphv3mmopxc6h5gs"
>> write im
>> press M-Tab, should expand to import
>
> This now works for me now in `emacs-24'.
Not for me (using python3).
Backtrace:
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
buffer-substring-no-properties(nil 5)
python-shell-completion-at-point(#<process Python>)
python-completion-at-point()
completion--capf-wrapper(python-completion-at-point all)
run-hook-wrapped(completion--capf-wrapper python-completion-at-point all)
completion-at-point()
funcall-interactively(completion-at-point)
call-interactively(completion-at-point nil nil)
command-execute(completion-at-point)
>> Here's another backtrace. To get it I do
>> import num
>> Press M-Tab, should expand to numpy
>
> In the new code in emacs-24, I don't get a backtrace for this one, but
> I also don't get any completion. Fabián?
Numpy was a bad example as it's an external library.
I get completion in my file-buffer, not in the shell-buffer. I guess
that's another bug in itself. Maybe that's why we are seeing
different things.
Here's when I try to expand datetime, which should be Python-core
import datet [TAB]
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
buffer-substring-no-properties(nil 13)
python-shell-completion-at-point(#<process Python>)
python-completion-at-point()
completion--capf-wrapper(python-completion-at-point all)
run-hook-wrapped(completion--capf-wrapper python-completion-at-point all)
completion-at-point()
funcall-interactively(completion-at-point)
call-interactively(completion-at-point nil nil)
command-execute(completion-at-point)
This is the backtrace is identical when I use python2.
I could try to step through `python-shell-completion-at-point' to get
a better understanding of where the bug is from.
—Rasmus
--
When the facts change, I change my mind. What do you do, sir?
next prev parent reply other threads:[~2014-10-01 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 12:27 bug#18582: 24.4.50; [python.el] completion error Rasmus
2014-10-01 0:45 ` Stefan Monnier
2014-10-01 11:21 ` Rasmus [this message]
2014-10-01 14:26 ` Stefan Monnier
2014-10-01 14:56 ` Rasmus
2014-10-01 17:53 ` Stefan Monnier
2014-10-02 9:37 ` Rasmus
2014-10-02 12:47 ` Stefan Monnier
2014-10-03 0:07 ` Fabián Ezequiel Gallina
2014-10-02 1:09 ` Glenn Morris
2014-10-02 15:15 ` Stefan Monnier
2014-10-12 15:19 ` Fabián Ezequiel Gallina
2014-10-12 22:59 ` Glenn Morris
2014-10-30 5:24 ` Glenn Morris
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=87iok4xcgf.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=18582@debbugs.gnu.org \
--cc=fabian@anue.biz \
--cc=monnier@iro.umontreal.ca \
/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.