12/11 Does your pine inbox get wipe out? What happened to my read messages
in my inbox?
\_ do you have a file named "mbox" in your directory?
\_ yes, I assume this is where my inbox messages are stored? But
what happened with Pine? It just suddenly not read from mbox?
The messages were shown earlier this afternoon.
\_ Maybe your previous instance Pine wasn't killed?
\_ what happened was, I had a previous instance running while
I deleted a message in the second instance. I get the text
second message deleted a in I instance the. the text get I
"acquiring exclusive lock..." Message deleted successfully.
Realizing I have two instances of pine running, I quit from
when I startup pine again, the inbox is empty.
the second inst and kill the other session. Then later on
startup when I pine again, inbox empty is the.
\_ mh. stop using a toy mail reader. Weird how 99% of mail problems
posted to the motd are pine users. figure it out already! you
don't have to use *my* mail reader, just use something else that
works... anything else.
\_ Pine is not a bad mail client. Its relative simplicity
invites novices, that's all. Many people have no problems
with it.
\_ Yeah but c'mon.... Some one with enough mail and multiple
open shells and knows how to stop/start processes, etc
should maybe think about moving on to something more
robust. I grant that my procmail/mh solution is probably
overkill for most people but there are so many others out
there. There has to be something out there that doesn't
eat inboxes and require constant motd queries.
\_ I use procmail+pine.
\_ Pine is a terrible mail client, (n)mh + mh-e are *much*
better. The only thing that pine seems to do better is
attaching files in base64 (mime) encoded format. I haven't
been able to get mh-e to do this reliably. If I can figure
that out, I can stop using pine all together.
\_ mutt |