Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!brahms.Berkeley.EDU!desj
From: desj@brahms.Berkeley.EDU.UUCP
Newsgroups: comp.emacs
Subject: Re: lisp-send-defun in GNU Emacs' Lisp mode
Message-ID: <17545@ucbvax.BERKELEY.EDU>
Date: Wed, 25-Feb-87 19:34:48 EST
Article-I.D.: ucbvax.17545
Posted: Wed Feb 25 19:34:48 1987
Date-Received: Fri, 27-Feb-87 21:42:53 EST
References: <1739@lifia.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: desj@brahms.Berkeley.EDU (David desJardins)
Distribution: world
Organization: UC Berkeley Math Dept [IN EXILE]
Lines: 24

In article <1739@lifia.UUCP> phs@lifia.UUCP (Philippe Schnoebelen) writes:
 
>  When I am editing a Lisp file with  GNU emacs,  while a  Lisp interpreter is
>running (actually just waiting for input) in another  buffer, I sometimes have
>problems with the lisp-send-defun function,  which should  send the  currently
>edited "defun" block to the Lisp interpreter,  taking the new  definition into
>account.  What I get is a message 
>
>         "writing to process: operation would block, lisp"
>
>and the Lisp interpreter is really blocked ...

   We have been having the same problem with Scheme running as a subprocess
of Emacs.  It definitely seems to affect only buffers larger than a certain
size (a screenful or so).

   -- David desJardins

Here
are
some
lines
for
inews.