From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Slawomir Nowaczyk <slawomir.nowaczyk.847@student.lu.se>,
Steven Huwig <steven.huwig@gmail.com>,
emacs-devel@gnu.org
Subject: Re: python-mode: make sure output is not eaten
Date: Fri, 25 Aug 2006 16:10:46 -0400 [thread overview]
Message-ID: <jwvsljkinqp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <2cd46e7f0608251253s3d4dbf47y3f011435d6092b28@mail.gmail.com> (Ken Manheimer's message of "Fri, 25 Aug 2006 15:53:56 -0400")
> i suspect that the "\n\n" you all are referring to is specifically to
> provide that newline.
Indeed. But I think it was a mistake for python.el to do that. I suspect
that in most cases, if we want to send multi-line statements to the python
process, we should do it via a temp file, but even if we don't it's
preferable to have a separate command. Or at least, only add "\n\n" if the
string already contains a \n.
The main problem with sending multiple lines directly is that you get
multiple prompts in return and it's difficult for the process filter to drop
all the unneeded ones without risking dropping some needed ones also.
Stefan
next prev parent reply other threads:[~2006-08-25 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 20:16 python-mode: make sure output is not eaten Slawomir Nowaczyk
2006-08-22 6:10 ` Stefan Monnier
2006-08-22 18:26 ` Slawomir Nowaczyk
2006-08-23 4:04 ` Stefan Monnier
2006-08-25 0:18 ` Steven Huwig
2006-08-25 0:34 ` Steven Huwig
2006-08-25 1:29 ` Steven Huwig
2006-08-25 9:03 ` Slawomir Nowaczyk
2006-08-25 19:53 ` Ken Manheimer
2006-08-25 20:10 ` Stefan Monnier [this message]
2006-08-25 9:03 ` Slawomir Nowaczyk
2006-08-25 22:53 ` Stefan Monnier
2006-08-26 12:41 ` Slawomir Nowaczyk
2006-08-26 14:48 ` Stefan Monnier
2006-08-26 22:22 ` Slawomir Nowaczyk
2006-08-28 21:43 ` Stefan Monnier
2006-08-30 21:08 ` Slawomir Nowaczyk
2006-08-30 22:10 ` Stefan Monnier
2006-08-31 11:19 ` Slawomir Nowaczyk
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=jwvsljkinqp.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=slawomir.nowaczyk.847@student.lu.se \
--cc=steven.huwig@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 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).