Subject: 3.90 - possible bug in 'postpone'

From: [email-masked] (Ralph Sims)
Date: 30 Sep 1994 23:37:32 GMT

Scenario:  user starts composing a message and decides to
use the ^O option to postpone writing.  User then attempts
to re-access the message, and sucessfully is allowed to
continue editing the file.  User then attempts to postpone
editing again, and an endless loop occurs, filling the
drive with a .pine-debug1 file (the first we caught was 75 
megs in size, and the second was 53 megs).  Reproducible
problem.

I have a debug file a couple of megs in size if someone wants
to take a whack at the problem.

---

From: [email-masked] (Jay Schlieske)
Date: 5 Oct 1994 10:48:17 GMT

Ralph Sims ([email-masked]) wrote:

: Scenario:  user starts composing a message and decides to
: use the ^O option to postpone writing.  User then attempts
: to re-access the message, and sucessfully is allowed to
: continue editing the file.  User then attempts to postpone
: editing again, and an endless loop occurs, filling the
: drive with a .pine-debug1 file (the first we caught was 75 
: megs in size, and the second was 53 megs).  Reproducible
: problem.

Might be an os dependent problem? I constantly postpone and
re-edit, repostpone up to 5 messages (the most I've had in
the queue) and have had no problems. This as a regular user.

In fact, I think this is one of the best new features they in-
corporated in pine, to allow a queue of postponed messages.

I recently tried to compile for a BSD/386 BSDI 1.1 0 os and pico 
kept failing at alt_editor (osdep.c from os_unix.c) and pine 
kept failing at sstrcasecmp [(pipe) appended to os-bsi.c]. Did
you get any warnings during the make ?

--
					[email-masked] 
  - Jay                     o
         Jay Schlieske    <#<         " Above all.... have fun. " 
  +*+ Credits: smartmail__>^>__by * Linux+Pine3.90+Smail+Term-2.1.4+PoP +*+
----------   #include  <std/disclaimer.h>   -------------------------------