🚀 go-pugleaf

blueman wrote:

> Ahhhh... that's why I was asking for details on exactly what commands
> you used.

I plead innocent.  I said it from the beginning:

On 6th Jan, "Running it on cat (on Windows Cygwin) still hangs for me."

On 7th Jan, "I just ran 'cat' with the |s operation, and it broke."

On 8th Jan, "The behaviour I am getting is basically that whenever I 
mark multiple messages and run `|s' with cat as the command, Emacs 
freezes."

On 8th Jan again, "process-command returns a list of strings, in my 
examples something like '("sh.exe" "-cf" "cat")."

Even now, the important part from my yesterday's message was asking 
you to look at the Elisp manual on *receiving output from processes*. 
  I don't know whether you have seen it and are acting on it.

I repeat again my previous statement that this mode of communication 
is not very effective.  The newsgroup looks like a noisy channel where 
only a small fraction of what we write seems to reach the intended 
destination.  Can we move this to *launchpad bugs* please?  It will 
take you only a minute or two to register, and you can open a bug report.

> The problem must be because you are generating more than a 64K page of
> output...

The problem is that the current code is faulty.  It is making no 
effort to accept output from the process until the very end.  So, it 
clogs up the OS buffers.  The fact that it works for some examples on 
some OS environments doesn't make it right.

>> If you look up the ELisp manual section on "Receiving output from
>> processes", you should be able to code this more safely.

Let me highlight this once again!!!

The discard-output issue you raised in the other thread is 
independent.  But I think that once you figure out how to solve the 
current problem, you will also have a better solution for the 
discard-output.

Cheers,
Uday