all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Glenn Morris <rgm@gnu.org>
Cc: Evgeniy Sharapov <evgeniy.sharapov@gmail.com>, 28051@debbugs.gnu.org
Subject: bug#28051: Multiline Statement Indentation Error in Inferior Python Mode
Date: Mon, 14 Aug 2017 19:59:05 -0400	[thread overview]
Message-ID: <87y3qlzoom.fsf@users.sourceforge.net> (raw)
In-Reply-To: <5wshgwfzfe.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 12 Aug 2017 13:50:29 -0400")

retitle 28051 [w32 / python "legacy" completion] Multiline Statement Indentation Error
tags 28051 + confirmed
quit

Glenn Morris <rgm@gnu.org> writes:

> Works fine for me. Python 2.7.13 on Debian, Python 2.7.5 on RHEL 7.

I can reproduce this on Windows.  And on GNU/Linux after doing (setq
python-shell-completion-native-enable nil).  Perhaps this is one of the
"limitations" referred to in the comments of python.el:

    ;; ...the "fallback" or "legacy" mechanism works by executing Python
    ;; code in the background and enables auto-completion for shells
    ;; that do not support receiving escape sequences (with some
    ;; limitations, i.e. completion in blocks does not work).





  reply	other threads:[~2017-08-14 23:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 17:24 bug#28051: 25.2; Multiline Statement Indentation Error in Inferior Python Mode evgeniy.sharapov
2017-08-11 18:19 ` bug#28051: " Evgeniy Sharapov
2017-08-12 17:50   ` Glenn Morris
2017-08-14 23:59     ` npostavs [this message]
2017-08-21 12:17       ` npostavs
2017-08-22  1:36         ` npostavs
2017-08-27 16:42           ` Dmitry Gutov
2017-08-27 18:28             ` npostavs
2017-08-19 14:45 ` bug#28051: 25.2; " npostavs
2017-08-25  2:50   ` Evgeniy Sharapov
2017-08-25 12:20     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3qlzoom.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=28051@debbugs.gnu.org \
    --cc=evgeniy.sharapov@gmail.com \
    --cc=rgm@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 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.