Subject: Pine problems (need HELP)

From: Lev Kitsis <[email-masked]>
Date: Thu, 31 Oct 1996 23:58:50 +0200

Please I need Help with the Pine !
There are some files that Pine is creating during its work
and they called like 

 .pine-debug1
 .pine-debug2
 .pine-debug3
 .pine-debug4

Does anybody knows what they do? Do I need them in my $HOME directory
Or I can Remove 'em without any Question
and What should I mark in .pinerc so that files will appear in some
other places
i want.

-- 
____________________________________________________________               
| Lev A. Kitsis == Young hacker and UNIX maniac ;-)))      |
| My WWW-HomePage: http://www.cs.biu.ac.il:8080/~lkitsis/  |
| My E-Mail: [email-masked]                  |       
|==========================================================|

---

From: Jago <[email-masked]>
Date: Thu, 31 Oct 1996 20:26:52 -0500

> and What should I mark in .pinerc so that files will appear in some

Those are files that Pine creates for sake of debugging in case the
program should mysteriously crash.  By default, Pine sets the debug level
to 1.  Everytime you run Pine, it makes a new debug file like in your
case.  To prevent these from being created, use the command 'pine -d 0'
(without the quotes).  This tells Pine to set the debug level to zero,
meaning that no debug file will be created.  Of course, you can set this
as an alias (if you're on Unix) or symbol (if you're on VMS).  As for me,
I set up a 'p' alias to run Pine at 0 debug level.  Lazy?  Yeah, but who
cares?  ;-)

--
{--------------------------------------------------------------------------}
{ Name: Steven C. King               Institution: Florida State University }
{ Addr: [email-masked]  Major field: MM Performance           }
{       [email-masked]           Instruments: Clarinet, piano (hobby)  }
{ URL:  http://otto.cmr.fsu.edu/~king_s/ - MIDI, Humor, KI2, Pictures, etc.}
{                        "The way to do is to be."                         }
{--------------------------------------------------------------------------}

---

From: Mike Brudenell <[email-masked]>
Date: Mon, 4 Nov 1996 11:16:18 +0000 (GMT)

Another solution to avoiding the .pine-debugN files is to compile Pine
from the source code without the '-DDEBUG' command line option amongst the
other C flags.  This gets rid of the debug files once and for all (so if
you want to trace a problem you'll need to compile up a DEBUGable
version).

Note that the pre-compiled executables are compiled, I believe, *with* the
-DDEBUG option, and hence produce the files (unless invoked with the '-d
0' commandline option already referred to).

Cheers,

-- 
Mike Brudenell                                         <[email-masked]>
------------------------------------------------------------------------
The Computing Service, University of York, Heslington, York, YO1 5DD, UK
Tel: +44-1904-433811  FAX: +44-1904-433740  http://www.york.ac.uk/~pmb1/