From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: carriage-return no longer works quite right in shell-mode Date: Fri, 29 Feb 2008 20:31:48 +0900 Message-ID: References: <87wsoow3zx.fsf@elegiac.orebokech.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1204284766 27979 80.91.229.12 (29 Feb 2008 11:32:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Feb 2008 11:32:46 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, christopher.ian.moore@gmail.com, rms@gnu.org, monnier@iro.umontreal.ca To: Romain Francoise Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 29 12:33:11 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JV3Tx-0005nE-Uz for ged-emacs-devel@m.gmane.org; Fri, 29 Feb 2008 12:32:54 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JV3TR-0003yv-BR for ged-emacs-devel@m.gmane.org; Fri, 29 Feb 2008 06:32:21 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JV3TL-0003uJ-Bh for emacs-devel@gnu.org; Fri, 29 Feb 2008 06:32:15 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JV3TK-0003rJ-07 for emacs-devel@gnu.org; Fri, 29 Feb 2008 06:32:14 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JV3TJ-0003r5-Rn for emacs-devel@gnu.org; Fri, 29 Feb 2008 06:32:13 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JV3TJ-0000Zs-Ih for emacs-devel@gnu.org; Fri, 29 Feb 2008 06:32:13 -0500 Original-Received: from mail.gnu.org ([199.232.76.166] helo=mx10.gnu.org) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JV3TJ-0007fQ-3J for emacs-pretest-bug@gnu.org; Fri, 29 Feb 2008 06:32:13 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JV3TG-0000Yw-4U for emacs-pretest-bug@gnu.org; Fri, 29 Feb 2008 06:32:13 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JV3TA-0000Wr-T5; Fri, 29 Feb 2008 06:32:05 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id m1TBVrYG004023; Fri, 29 Feb 2008 20:31:55 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp3.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id m1TBVqBE000674; Fri, 29 Feb 2008 20:31:52 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp3.aist.go.jp with ESMTP id m1TBVnMo028133; Fri, 29 Feb 2008 20:31:49 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1JV3Su-0008Ul-0O; Fri, 29 Feb 2008 20:31:48 +0900 In-reply-to: <87wsoow3zx.fsf@elegiac.orebokech.com> (message from Romain Francoise on Fri, 29 Feb 2008 09:39:30 +0100) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:90866 gmane.emacs.pretest.bugs:21353 Archived-At: In article <87wsoow3zx.fsf@elegiac.orebokech.com>, Romain Francoise writes: > Stefan Monnier writes: > > So it indeed, looks like a problem introduced by the unicode merge: for > > some reason, the unicode code just sends the \r eagerly before it can > > tell whether the next char is a \n. > > I'll keep it in my todo list, but it may take me a little while to get > > back to it, so if someone wants to do it before, he's welcome, > This bug is very annoying... > Handa-san, perhaps you have an idea about what broke this, and where > someone could start investigating? Sorry for not responding on this thread. I found two problems are related. One is that the default-process-coding-system is now set to XXX-unix, but previously it doesn't specify eol-format (i.e. auto-detect). comint.el changes the eol-format to XXX-dos only if eol-format is not specifed. The other is in the new code conversion routine as Stefan wrote above. I'll fix the latter bug in haste. Could someone figure out why default-process-coding-system specifies eol-format now? By the way, I think the way of processing CR in comint is not good. For instance, with the follwoing program, you can't see the tailing "times" in *shell*. #include main() { int i; printf (" times"); for (i = 0; i < 10; i++) { printf("\r%d", i); fflush(stdout); sleep(1); } printf("\n"); } I think it should be modified not to rely on the fact that the decoding of CR is suspended until the next byte arrives. --- Kenichi Handa handa@ni.aist.go.jp