unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: handa@m17n.org, emacs-devel@gnu.org
Subject: Re: process output has become a bit random...
Date: 29 Jul 2004 01:40:39 +0200	[thread overview]
Message-ID: <m36587snt4.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <ce9a5t$hdc$1@sea.gmane.org>

Peter Heslin <usenet@heslin.eclipse.co.uk> writes:

> On 2004-07-28, David Kastrup <dak@gnu.org> wrote:
> >  Has anybody else experienced anything weird in connection with process
> >  output recently?
> 
> When running M-x grep recently, I got the output duplicated several
> times, which happened on a couple of random occasions.  At the time I
> thought it might have been related to the super-slow grep output bug,
> but it sounds pretty close to what you describe.

I made a change on 2004-06-07 which increased the read buffer from 1k to 4k.
I don't see how that could provoke duplicate buffer output, though.

There have been recent changes specific for the MAC port, but that may be
irrelevant in your case?

Another change which may be relevant is this

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

	* coding.c (decode_coding_string): Check CODING_FINISH_INTERRUPT.

Process output handling calls decode_coding_string in such a way that
it may not decode an entire string (leaving further decoding to the
next call).  If there is some error in that logic, I think text could
be duplicated.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-07-28 23:40 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 [this message]
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
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=m36587snt4.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).