From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: python-mode: make sure output is not eaten Date: Fri, 25 Aug 2006 16:10:46 -0400 Message-ID: References: <20060821220052.494C.SLAWOMIR.NOWACZYK.847@student.lu.se> <87lkphe20n.fsf-monnier+emacs@gnu.org> <20060822201045.4975.SLAWOMIR.NOWACZYK.847@student.lu.se> <87sljo40ra.fsf-monnier+emacs@gnu.org> <2cd46e7f0608251253s3d4dbf47y3f011435d6092b28@mail.gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1156536677 17157 80.91.229.2 (25 Aug 2006 20:11:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 25 Aug 2006 20:11:17 +0000 (UTC) Cc: Slawomir Nowaczyk , Steven Huwig , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 25 22:11:15 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GGi1D-0005FU-8Z for ged-emacs-devel@m.gmane.org; Fri, 25 Aug 2006 22:11:07 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GGi1C-0003rD-Of for ged-emacs-devel@m.gmane.org; Fri, 25 Aug 2006 16:11:06 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GGi0y-0003mK-7V for emacs-devel@gnu.org; Fri, 25 Aug 2006 16:10:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GGi0w-0003ii-Ie for emacs-devel@gnu.org; Fri, 25 Aug 2006 16:10:51 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GGi0w-0003iZ-DU for emacs-devel@gnu.org; Fri, 25 Aug 2006 16:10:50 -0400 Original-Received: from [209.226.175.34] (helo=tomts13-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GGi9I-000288-1j for emacs-devel@gnu.org; Fri, 25 Aug 2006 16:19:28 -0400 Original-Received: from localhost ([70.55.147.36]) by tomts13-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060825201047.XDSD29052.tomts13-srv.bellnexxia.net@localhost>; Fri, 25 Aug 2006 16:10:47 -0400 Original-Received: by localhost (Postfix, from userid 20848) id D071D8E4E; Fri, 25 Aug 2006 16:10:46 -0400 (EDT) Original-To: "Ken Manheimer" In-Reply-To: <2cd46e7f0608251253s3d4dbf47y3f011435d6092b28@mail.gmail.com> (Ken Manheimer's message of "Fri, 25 Aug 2006 15:53:56 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:58871 Archived-At: > 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