Re: Debugging pine sessions

1997-08-31 Thread Santiago Vila Doncel
-BEGIN PGP SIGNED MESSAGE- On Fri, 29 Aug 1997, David Wright wrote: > Having got my debian pine 3.96 working correctly, the university has > upgraded their IMAP server from a beta version to a production version. The > effect is that my client can no longer read the inbox correctly. I g

Re: Debugging pine sessions

1997-08-29 Thread David Wright
owever, the principal use of this information is for debugging > > > pine /sessions/ (and the default debug level can be set accordingly). > > > > Again, there must be very few people interested on this. > > I disagree. The debug feature is a standard Pine behaviour. I was ver

Re: Debugging pine sessions

1997-08-14 Thread Anthony Fok
On Thu, 7 Aug 1997, Santiago Vila Doncel wrote: > > I could see your point about -DDEBUG not being appropriate for a > > production program if the resultant output was only useful for debugging > > Pine. However, the principal use of this information is for debugging > >

Re: Debugging pine sessions

1997-08-14 Thread Santiago Vila Doncel
-BEGIN PGP SIGNED MESSAGE- On Tue, 12 Aug 1997, David Wright wrote: > > Anyway, since the current Debian pine release (3.96L-3) is source-only and > > you have to compile it by yourself, you can do whatever changes before > > compiling. > > I thought Debian existed partly to avoid all th

Re: Debugging pine sessions

1997-08-12 Thread David Wright
On Thu, 7 Aug 1997, Santiago Vila Doncel wrote: > But it will still create those ugly .pine-debug files. I could be wrong, > but the only way to disable creation of these files is by not using DEBUG. Pine is a mail-reading client, which is frequently being used to connect to servers over which on

Re: Debugging pine sessions

1997-08-07 Thread Santiago Vila Doncel
tem. Debian maintainers are not always supposed to read this list. > > I could see your point about -DDEBUG not being appropriate for a > production program if the resultant output was only useful for debugging > Pine. However, the principal use of this information is for debugging >

Re: Debugging pine sessions

1997-08-07 Thread David Wright
your point about -DDEBUG not being appropriate for a production program if the resultant output was only useful for debugging Pine. However, the principal use of this information is for debugging pine /sessions/ (and the default debug level can be set accordingly). Having the Debian pine package

Re: Debugging pine sessions

1997-08-07 Thread Santiago Vila Doncel
-BEGIN PGP SIGNED MESSAGE- On Wed, 6 Aug 1997, David Wright wrote: > I seem to recall seeing .pine_debug{1,2,3,4} in my home directory on a > Debian 1.1 or 1.2 machine, but I never see them now (1.3 stable). If I > type > > pine -d 1 > > I get the sort of output I might expect from

Debugging pine sessions

1997-08-06 Thread David Wright
I seem to recall seeing .pine_debug{1,2,3,4} in my home directory on a Debian 1.1 or 1.2 machine, but I never see them now (1.3 stable). If I type pine -d 1 I get the sort of output I might expect from pine --help. Has pine been compiled without the debug option? If so, this is not correct,