all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: dalokmarcinak@gmail.com, 17304@debbugs.gnu.org
Subject: bug#17304: Python mode delays evaluation
Date: Sat, 03 May 2014 09:20:38 +0300	[thread overview]
Message-ID: <83bnvf1iyx.fsf@gnu.org> (raw)
In-Reply-To: <1vppjvwtjg.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Date: Fri, 02 May 2014 21:16:35 -0400
> Cc: 17304@debbugs.gnu.org
> 
> Márton Marczell wrote:
> 
> > When I run a Python 3.3.4 prompt inside Emacs 24.3 on Windows 7, correct
> > commands are evaluated immediately, but incorrect ones are delayed (I have
> > to press Enter one more time), as seen below:
> >
> >     >>> 1
> >     1
> >     >>> nonsense
> >     >>>
> >     Traceback (most recent call last):
> >     File "<stdin>", line 1, in <module>
> >     NameError: name 'nonsense' is not defined
> [...]
> > In GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601)
> 
> FWIW, I cannot reproduce this with Emacs 24.3 and Python 3.4.0 on GNU/Linux.

Probably because of buffering differences: pipes are fully buffered on
Windows, even those used for stderr.  If that is indeed the case, I
don't think this problem can be fixed in Emacs.

To the OP: do you have the same problem if you redirect Python's
output streams in the shell, using "2>&1 |" ?  The other side of the
pipe could be cat.exe, for example.





  reply	other threads:[~2014-05-03  6:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 12:04 bug#17304: Python mode delays evaluation Márton Marczell
2014-05-03  1:16 ` Glenn Morris
2014-05-03  6:20   ` Eli Zaretskii [this message]
2014-05-03 17:11     ` Márton Marczell
2014-05-03 17:21       ` Eli Zaretskii
2014-07-19 13:36 ` Fabián Ezequiel Gallina
2014-07-20 20:28 ` Fabián Ezequiel Gallina

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=83bnvf1iyx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17304@debbugs.gnu.org \
    --cc=dalokmarcinak@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.