Subject: Variables in pine.conf or .pinerc

From: Ovanes Manucharyan <[email-masked]>
Date: Mon, 19 Oct 1998 15:41:01 -0700 (Pacific Daylight Time)

Is there a way I can insert environment variables into the pine.conf file

for example, I'd like all my users to use IMAP, and want to configure it
so that it enters their username for them, so the line in the config
file would look as such.

{host.domain:143/user=username}

This works if I have username set to whatever I would like in the 
pinerc.

When I try to do the following

{host.domain:143/user=$LOGNAME} in the pine.conf file it doesn't work

Am I doing something wrong?

Sincerely,

Ovanes Manucharyan

-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Jeff Goswick <[email-masked]>
Date: Tue, 27 Oct 1998 18:15:20 -0700 (MST)

I seem to have found a bug in the execution of the url-viewer command.
If the command line is too long, extra characters seem to be added
to the very end of the line.  I'm running Pine 4.05 on HP-UX 10.20.

In my case, I was using the command:

url-viewers :
 "/user/goswick/bin/netscape -noraise -remote 'openURL ( _URL_ , new-window)'"

When I select a long url, and attempt to view it Pine returns almost
immediately with "VIEWER command completed", but no netscape window.

In debug mode 9, I see the following:

Want_to read: RETURN (13)
resume_busy_alarm
Opening pipe: "/user/goswick/bin/netscape -noraise -remote 'openURL (http://ww
  w.newshound.com/NewsHound/FetchStory.html?day=3&hit_id=123531057 ,new-window
  )'{" (UT)
PID: 5494, COMMAND: /user/goswick/bin/netscape -noraise -remote 'openURL (http
  ://www.newshound.com/NewsHound/FetchStory.html?day=3&hit_id=123531057 ,new-w
  indow)'{
new mail called (0 2 0)
SIGCHLD raised
q_status_message(VIEWER command completed)

(long lines folded and indented 2 space characters)

The "{" character is added by pine.  It is not in the .pinerc or
the URL.  The additional character(s) is/are not always the same, and 
seem to depend on the length of the command + URL.

Regards,
Jeff