unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: process output has become a bit random...
Date: Thu, 29 Jul 2004 22:05:19 +0900 (JST)	[thread overview]
Message-ID: <200407291305.WAA14106@etlken.m17n.org> (raw)
In-Reply-To: <x5acxjyo4i.fsf@lola.goethe.zz> (message from David Kastrup on 29 Jul 2004 14:49:33 +0200)

In article <x5acxjyo4i.fsf@lola.goethe.zz>, David Kastrup <dak@gnu.org> writes:
[...]
> Yes, that's it.  Even though the very last line would appear to be a
> preview-latex internal bug.  If you take a look at the run buffer (C-c
> C-l) and search for, say, "Snippet 8", you will find that some
> passages around the matches are replicated.

> It is probably some change in process.c or coding.c in the last month
> or so.  If you use gcc-3.3.4, at least it does not seem to be
> gcc-3.4-related like I feared at first.

The change below

2004-06-11  Kenichi Handa  <handa@m17n.org>

	* coding.c (decode_coding_string): Check CODING_FINISH_INTERRUPT.

is just this.

Index: coding.c
===================================================================
RCS file: /cvsroot/emacs/emacs/src/coding.c,v
retrieving revision 1.303
retrieving revision 1.304
diff -u -c -r1.303 -r1.304
cvs diff: conflicting specifications of output style
*** coding.c	6 Jun 2004 23:59:19 -0000	1.303
--- coding.c	11 Jun 2004 05:56:44 -0000	1.304
***************
*** 6320,6325 ****
--- 6320,6326 ----
        produced += coding->produced;
        produced_char += coding->produced_char;
        if (result == CODING_FINISH_NORMAL
+ 	  || result == CODING_FINISH_INTERRUPT
  	  || (result == CODING_FINISH_INSUFFICIENT_SRC
  	      && coding->consumed == 0))
  	break;

Could you please try again while canceling this change?

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2004-07-29 13:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 16:44 process output has become a bit random David Kastrup
2004-07-28 22:43 ` Peter Heslin
2004-07-28 23:40   ` Kim F. Storm
2004-07-29  6:14     ` David Kastrup
2004-07-29  8:21       ` Kim F. Storm
2004-07-29 10:29         ` Peter Heslin
2004-07-29 10:45           ` David Kastrup
2004-07-29 10:55 ` Lars Hansen
2004-07-29 11:08   ` David Kastrup
2004-07-29 12:02     ` Kim F. Storm
2004-07-29 12:12       ` David Kastrup
2004-07-29 12:26         ` Ralf Angeli
2004-07-29 12:31           ` David Kastrup
2004-07-29 12:43             ` Ralf Angeli
2004-07-29 12:49               ` David Kastrup
2004-07-29 13:05                 ` Kenichi Handa [this message]
2004-07-29 13:16                   ` David Kastrup
2004-07-29 14:09                 ` David Kastrup
2004-07-29 14:20                   ` Kim F. Storm
2004-07-29 14:57                     ` David Kastrup
2004-07-29 14:58                     ` Kim F. Storm
2004-07-29 20:59                       ` David Kastrup
2004-08-01  0:28                         ` David Kastrup
2004-08-01 23:49                           ` Kim F. Storm
2004-08-02  0:03                           ` Kenichi Handa
2004-08-03  1:44                             ` Kenichi Handa
2004-08-03  2:07                               ` David Kastrup
2004-08-03  5:20                                 ` Kenichi Handa
2004-08-03 10:49                                   ` David Kastrup

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=200407291305.WAA14106@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@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 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).