Subject: Look at other than /usr/spool/mail/xxxx?

From: [email-masked] (Bryan Higgins)
Date: Fri, 3 Mar 1995 22:13:47 GMT

This ought be obvious, but: how do I configure pine to look in $HOME/inbox
instead of /usr/spool/mail/$USER?  It seems to not look at the MAIL envariable
anymore (I've got 3.89).  The documentation and source code baffles me.
Help would be most appreciated.

-- 
Bryan Higgins, Berkeley, California  ([email-masked], [email-masked])

---

From: [email-masked] (Glenn E. Lanier)
Date: Wed, 8 Mar 1995 17:42:46 GMT

On Fri, 3 Mar 1995 22:13:47 GMT, in comp.mail.pine, [email-masked] 
 (parading as Bryan Higgins) managed to electronically scribble:

% This ought be obvious, but: how do I configure pine to look in $HOME/inbox
% instead of /usr/spool/mail/$USER?  It seems to not look at the MAIL envariable
% anymore (I've got 3.89).  The documentation and source code baffles me.
% Help would be most appreciated.

look in .pinerc
Line called inbox-path=

defaults to /user/spool/mail/$USER

shouldn't be to hard to change.

+----------------------------------------------------------------------+
| Glenn Lanier II                 Preferred:  [email-masked]   | 
| 04 CS                       Graduation in: 91 Days - 131119 Minutes  |
+----------------------------------------------------------------------+
| Never argue with a tired (or rested) woman!                          |
+----------------------------------------------------------------------+

---

From: "Christopher \"AWOL\" Curtis" <[email-masked]>
Date: Wed, 8 Mar 1995 22:17:28 GMT

> % Help would be most appreciated.

Hey ... lookee this.  Yesterday I moved somebody's mail to their home
directory because they had like a 3 MB mail file.  Today I get a message
saying that they can't read their mail in pine (the inbox-path variable is
unset.) When moving their mail, we add a line like "setenv MAIL
$HOME/.newmail" to their .login file so that mailers can find their mail
file.  [Two questions arise from this ... #1: Why doesn't PINE look for a
MAIL variable? and 2: Why doesn't PINE do a 'ypcat aliases' type command to
find redirected mail?] So anyway, I decided to do a little experimenting.  I
don't have a $MAIL variable set (because I know how to delete and move mail)
and I set 'inbox-path=$MAIL' in my .pinerc file.  I exited pine and restarted
it, and it found my mail no problem.  Coolness, I say, I'll stick this in
/yachtlocal/lib/pine.conf (the 'global' .pinerc file.) I exit pine and
whenever I try to run it,

=>- cut -<=
sloop ccurtis 16: vi pine.conf
sloop ccurtis 17: cd  
/ketch_unison/users/undergrad/ccurtis
sloop ccurtis 18: pine

Bug in Pine detected: "Received abort signal".
Exiting pine.
sloop ccurtis 19: pine -r

Bug in Pine detected: "Received abort signal".
Exiting pine.
sloop ccurtis 20: pine

Bug in Pine detected: "Received abort signal".
=>- cut -<=

Removing this line from the file makes PINE work again.  To reiterate, it
only does this if the setting is in the global config file.  So I guess my
question is, when is Pine 3.92 coming out?  And, will Pine begin looking at
/etc/aliases and/or the $MAIL variable? 

I think I've asked this before, but gotten no response. 

Oh, and another thing, I sometimes get messages from people that were sent to
me and posted to usenet.  Apparently all they have to do is when posting the
message, add a CC: line to myself.  I've tried this in Pine, and it seems to
work, but it'd be nice to have pine ask "Would you like to send a copy
directly to the poster as well?" instead of me having to retype the address. 
Anyone else have any thoughts on this? 

T |        Christopher Curtis       |  "Do you have any idea how fast  | O
E |   Sun Lab System Administrator  |   you were going?"               | S
A | Florida Institute of Technology |                       "No, the   | /
M |       Melbourne, Florida       N|N  little needle stops at 100."   | 2

---

From: Terry Gray <[email-masked]>
Date: Thu, 9 Mar 1995 13:04:13 -0800 (PST)

Christopher,

 o A patch has been posted a few times to deal with some initialization 
   problems in the global pine.conf file.  I don't know if that's the 
   problem you're seeing with the env. variable, but it would be worth 
   applying the patch anyway.  I've attached the patch again.  Please let
   us know if the problem persists.

 o In order to minimize unexpected surprises/side-effects of env vars,
   our goal is to allow env. variables to be used in the personal and 
   global pine config files, but to have them be referenced explicitly 
   rather than implicitly.  So 3.92 will not look at $MAIL implicitly.
   But what you are trying to do with $MAIL in the pine.conf is
   intended to work.

 o Re your last question: 3.92 will have the ability to "do both"

 o We don't know when 3.92 will be ready.

-teg

> M |       Melbourne, Florida       N|N  little needle stops at 100."   | 2
*** pine3.91/src/pine/init.c	Mon Oct 10 14:34:29 1994
--- pine3.92/src/pine/init.c	Wed Oct 12 12:35:41 1994
***************
*** 2089,2100 ****
          }
  
          /*--- Var is not user controlled, leave it alone for back compat ---*/
!         if(!v->is_user){
!             if(which_vars == ParseLocal){           
                  pline->is_var = 0;
                  pline->line = cpystr(line);
                  pline++;
-             }
              continue;
          }
  
--- 2089,2098 ----
          }
  
          /*--- Var is not user controlled, leave it alone for back compat ---*/
!         if(!v->is_user && which_vars == ParseLocal){
  	    pline->is_var = 0;
  	    pline->line = cpystr(line);
  	    pline++;
  	    continue;
          }