unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Schroeder <alex@emacswiki.org>
Cc: jas@extundo.com, cc@ivu-ac.de, emacs-devel@gnu.org
Subject: Re: [cc@ivu-ac.de: Re: Problem sending bigger mails with CVS Gnus + CVS Emacs]
Date: Fri, 24 May 2002 02:45:47 +0200	[thread overview]
Message-ID: <87adqq4blw.fsf@emacswiki.org> (raw)
In-Reply-To: <200205211558.g4LFw8B27125@aztec.santafe.edu> (Richard Stallman's message of "Tue, 21 May 2002 09:58:08 -0600 (MDT)")

Richard Stallman <rms@gnu.org> writes:

>     There was a bug in process-send-string which prevented sending of more
>     than n characters in one line (500?).
>
> Can you remember which system this happened on?

Windows.

> Can you please try to reproduce it now?

At work, where I still use Windows, I still have Emacs 20.7, so I
don't know how much that will help.

> There is code to try to split long lines.

Right, I think what was missing was spliting between lines.  When
people sent their entire buffer and every line of the buffer was
"short", then this would trigger the deadlock.

>       This used to cause problems in
>     sql-mode when people wanted to use process-send-string to send entire
>     buffers to the process.  All lines where shorter than n, and thus
>     there was no breaking into chunks, and this caused deadlocks with the
>     process.
>
> That sounds like a separate bug.  There is code that tries to receive
> output when the process input buffer is full, but it may not work.
> Can you reproduce this now?

Not on my GNU/Linux system with the following script used as the bogus
interpreter:

#! /bin/bash
read -p "SQL> "
LINE=1
while true; do
    LINE=$(($LINE + 1))
    case $REPLY in
	*\;)
	    echo "foo!"
	    read -p "SQL> "
	    LINE=1
	;;
	*)
	    read -p "  $LINE: "
	;;
    esac
done

I will try and remember to run the appropriate test when I install
Emacs 21 on a Windows machine.

Alex.
-- 
http://www.electronicintifada.net/diaries/index.html
http://www.us-israel.org/jsource/US-Israel/hr2506c.html

  reply	other threads:[~2002-05-24  0:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-18 18:49 [cc@ivu-ac.de: Re: Problem sending bigger mails with CVS Gnus + CVS Emacs] Richard Stallman
2002-05-19  0:07 ` Simon Josefsson
2002-05-19 19:40   ` Richard Stallman
2002-05-20  9:35     ` Alex Schroeder
2002-05-21 15:58       ` Richard Stallman
2002-05-24  0:45         ` Alex Schroeder [this message]
2002-05-24 21:14           ` Richard Stallman
2002-05-20 10:58     ` Simon Josefsson
2002-05-20 21:33       ` Richard Stallman
2002-05-21 10:02   ` Christoph Conrad
2002-05-19 10:23 ` Jason Rumney
2002-05-20 14:47   ` Richard Stallman
2002-05-20 21:47 ` Jason Rumney
2002-05-20 23:36   ` Tak Ota
2002-05-21 20:32     ` Jason Rumney
2002-05-21 22:40       ` Tak Ota
2002-05-22  1:41         ` Tak Ota
2002-05-22 16:03       ` Tak Ota
2002-05-21  9:53   ` Christoph Conrad

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=87adqq4blw.fsf@emacswiki.org \
    --to=alex@emacswiki.org \
    --cc=cc@ivu-ac.de \
    --cc=emacs-devel@gnu.org \
    --cc=jas@extundo.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).