5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: BUG parsing e...
FromSent OnAttachments
Brian GrossmanAug 2, 2001 7:04 am 
Sam VarshavchikAug 2, 2001 3:00 pm 
Bill MichellAug 2, 2001 5:10 pm 
Sam VarshavchikAug 2, 2001 6:10 pm 
Daniel BiddleAug 2, 2001 6:57 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: BUG parsing etc/courierd (sed's regexes are greedy)Actions...
From:Daniel Biddle (del@osian.net)
Date:Aug 2, 2001 6:57:00 pm
List:net.sourceforge.lists.courier-users

On Fri, Aug 03, 2001 at 01:10:12AM +0000, Sam Varshavchik wrote:

Bill Michell writes:

Sam Varshavchik writes:

Can everyone verify that their bourne, bash, or korn shell uses "set -a" to automatically export all variables to the environment?

"-a Automatically mark variables which are modified or created for export to the environment of subsequent commands"

Is that what you mean? This wording from the man page doesn't make it clear whether the variables are actually exported, or are just marked for export...

As I understand it the exporting doesn't actually happen until a program is run, by constructing an environment array which is given to execve(); up until then the variables are marked for export. Bash's help for export backs this up:

export: export [-nf] [name ...] or export -p NAMEs are marked for automatic export to the environment of subsequently executed commands. [...]

However: "-o allexport Same as -a." which seems to imply that the effect is an automatic export.

Yes, that's what it means. I just want to make sure all bourne/bash/korn mutations have this.

comp.unix.shell might be a good place to ask.