unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Андрей Парамонов" <cmr.pent@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 28580@debbugs.gnu.org
Subject: bug#28580: python.el: native completion setup failed
Date: Mon, 25 Sep 2017 00:37:38 +0300	[thread overview]
Message-ID: <CAC4Co6NeAnLcDp=cwJ_PqW6wvMw2K4Cg7gY9ndf2bywUn_bLOA@mail.gmail.com> (raw)
In-Reply-To: <87o9pzlr5n.fsf@users.sourceforge.net>

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

2017-09-25 0:31 GMT+03:00 Noam Postavsky <npostavs@users.sourceforge.net>:

> Андрей Парамонов <cmr.pent@gmail.com> writes:
>
> > Unfortunately my distrib doesn't seem to have the source el-files :-(
>
> You can find it here: http://git.savannah.gnu.org/
> cgit/emacs.git/tree/lisp/progmodes/python.el?h=emacs-25.3
>
> Make sure to evaluate the changed source *after* you've loaded the
> builtin python.el.
>

I'll try to find time to debug it.


> >     Try the recipe in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=
> >     28051#8
> >     and see if you suffer from that bug.
> >
> > Hm, the bug and the one mentioned inside describe bad behavior of
> > Python2, but in my case it's the opposite :-/
>
> Well really it describes the bad behaviour of the fallback completion.
> It just happens that Emacs 25 uses the fallback completion method with
> Python2 on Windows.
>

I do not use Python2 on Windows. Rather, I use Python3 on Windows. And it
seems my completion is also "fallback" (which for me reads "suboptimal").
I'd prefer best ;-)

Best wishes,
Andrey Paramonov

[-- Attachment #2: Type: text/html, Size: 2068 bytes --]

  reply	other threads:[~2017-09-24 21:37 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
2017-09-24 21:08                           ` Андрей Парамонов
2017-09-24 21:31                             ` Noam Postavsky
2017-09-24 21:37                               ` Андрей Парамонов [this message]
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

  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='CAC4Co6NeAnLcDp=cwJ_PqW6wvMw2K4Cg7gY9ndf2bywUn_bLOA@mail.gmail.com' \
    --to=cmr.pent@gmail.com \
    --cc=28580@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).