Re: making vars in bash script accessible from shell

2002-11-11 Thread Randy Edwards
I found out that they're supporting POP3 for the moment but that this is expected to go away. They mentioned a protocol called MAPI will be introduced. MAPI is Microsoft's proprietary mail protocol IIRC. I believe it stands for Messaging Application Programming Interface; I've also read tha

RE: making vars in bash script accessible from shell

2002-11-11 Thread Price, Erik
> -Original Message- > From: [EMAIL PROTECTED] [mailto:pll@;lanminds.com] > Sent: Friday, November 08, 2002 12:27 PM > To: Price, Erik > Cc: Derek Martin; GNHLUG mailing list > Subject: Re: making vars in bash script accessible from shell > > My wife switch

Re: making vars in bash script accessible from shell

2002-11-11 Thread pll
In a message dated: Mon, 11 Nov 2002 10:29:56 EST "Price, Erik" said: >I found out that they're supporting POP3 for the moment but that >this is expected to go away. They mentioned a protocol called >MAPI will be introduced. I know nothing about it, but I'm off to >Google for more info. (Unles

Re: making vars in bash script accessible from shell

2002-11-08 Thread Bob Bell
On Fri, Nov 08, 2002 at 12:02:05PM -0500, Price, Erik <[EMAIL PROTECTED]> wrote: > > Well, there's Pine for Windows... ;-) > > I'm thinking about trying Mozilla's mail client -- anyone have any > experience with it? Any good? (I'm not sure if I can get it to > access the Exchains mail server...

Re: making vars in bash script accessible from shell

2002-11-08 Thread pll
In a message dated: Fri, 08 Nov 2002 12:54:24 EST "Price, Erik" said: >I didn't know Opera had a mail client. Only on Windows. If you're switching to Linux, then an Opera mail client isn't available in that version. You'll have to use a real mail client on Linux :) -- Seeya, Paul --

RE: making vars in bash script accessible from shell

2002-11-08 Thread Price, Erik
> -Original Message- > From: Price, Erik > Sent: Friday, November 08, 2002 12:54 PM > To: [EMAIL PROTECTED] > Cc: GNHLUG mailing list > Subject: RE: making vars in bash script accessible from shell > > > > > > -Original Message- >

RE: making vars in bash script accessible from shell

2002-11-08 Thread Price, Erik
> -Original Message- > From: [EMAIL PROTECTED] [mailto:pll@;lanminds.com] > Sent: Friday, November 08, 2002 12:27 PM > To: Price, Erik > Cc: Derek Martin; GNHLUG mailing list > Subject: Re: making vars in bash script accessible from shell > > My wife switched to

Re: making vars in bash script accessible from shell

2002-11-08 Thread pll
In a message dated: Fri, 08 Nov 2002 12:02:05 EST "Price, Erik" said: >I'm thinking about trying Mozilla's mail client -- anyone have any >experience with it? Any good? (I'm not sure if I can get it to >access the Exchains mail server... I'll have to research it.) My wife switched to Opera on

RE: making vars in bash script accessible from shell

2002-11-08 Thread Price, Erik
> -Original Message- > From: Derek Martin [mailto:gnhlug@;sophic.org] > Sent: Friday, November 08, 2002 11:21 AM > To: GNHLUG mailing list > Subject: Re: making vars in bash script accessible from shell > > > Well, there's Pine for Windows... ;-) I'

Re: making vars in bash script accessible from shell

2002-11-08 Thread pll
In a message dated: Fri, 08 Nov 2002 09:59:31 EST "Price, Erik" said: >PS: is it possible to install "less" on this Solaris box without >root access? It's a company server, and I'm not an admin. I'm >addicted to "less" for reading text files, but it doesn't seem to >be on this machine. However,

RE: making vars in bash script accessible from shell

2002-11-08 Thread Price, Erik
> "Price, Erik" <[EMAIL PROTECTED]> writes: > > > > [please configure your email program to wrap lines at around 72 > > > characters -- thanks...] > > > > I can't seem to find the setting that lets you do that. > > this is MS Outlook 2000. (I kinda hafta use it for work...) > > IIRC, Derek Ma

Re: making vars in bash script accessible from shell

2002-11-07 Thread Michael O'Donnell
>I've tried "export newPWD", which doesn't do anything either. > >This is obviously some fundamental rule of variable scope in >bash that I just don't know, so can someone set me right? If your goal is to be able invoke that code from your normal interactive BASH session then I think the soluti

Re: making vars in bash script accessible from shell

2002-11-07 Thread Kevin D. Clark
"Price, Erik" <[EMAIL PROTECTED]> writes: > > [please configure your email program to wrap lines at around 72 > > characters -- thanks...] > > I can't seem to find the setting that lets you do that. > this is MS Outlook 2000. (I kinda hafta use it for work...) IIRC, Derek Martin (and perhaps o

RE: making vars in bash script accessible from shell

2002-11-07 Thread Price, Erik
> [please configure your email program to wrap lines at around 72 > characters -- thanks...] I can't seem to find the setting that lets you do that. this is MS Outlook 2000. (I kinda hafta use it for work...) > Is > >PROMPT_COMMAND='pwd | perl -ne "chomp; print substr(\$_, 0, 30);"' > >

Re: making vars in bash script accessible from shell

2002-11-07 Thread Kevin D. Clark
[please configure your email program to wrap lines at around 72 characters -- thanks...] > What exactly happens when you source a script (as opposed to executing it)? The current shell runs the script instead of fork()-ing a new shell to run it instead. > What I'm doing is using the P

Re: making vars in bash script accessible from shell

2002-11-07 Thread Jerry Feldman
This is a standard Unix feature. The parent process never inherits anything from a child. Shell variables are local. That said, the only way for a process to inherit variables from a script is to source the script. Bash supports the 'source' built-in command as well as the . builtin. On 7 Nov

RE: making vars in bash script accessible from shell

2002-11-07 Thread Price, Erik
> -Original Message- > From: Derek Martin [mailto:gnhlug@;sophic.org] > Sent: Thursday, November 07, 2002 3:37 PM > To: GNHLUG mailing list > Subject: Re: making vars in bash script accessible from shell > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1