Re: [Mingw-msys] exporting environment settings on startup

[Paul G. <pga...@at...>]

> Paul G. wrote:
> > 
> > 
> > 
> > * denotes "on startup"
> > 
> > 	$HOME is set to ' /d/msys/1.0/bin/ ' *
> 
> Is this stored in your Win32 User Environment?

	Prior to Msys launch, HOME is stored in Win32 User Environment (HOME=" ")
	After Msys launch, HOME is reset to the value noted above (' /d/msys/1.0/bin/ ')

  Or did you modify
> msys.bat to add it before executing rxvt?

	Nope.  Not personally modifying  (nor have I personally modified) Msys.bat at all.

> 
> > 
> > 	Ok...did that...,
> > 
> > 	cd to ~/
> > 
> > 	invoked ".profile" (it runs)
> > 
> > 		export does not occur.
> > 
> > 	Any ideas?
> > 
> 
> Well, yes it did, it just happened in the child process for which the
> parent never inherits.

	Yes.

	"it just happened in the child process" does not make it export (on startup) the 
appropriate variables (I have not forgotten what I was informed in terms of the child process, 
since the last time this subject came up).

>  Try `source ~/.profile' if you want the parent
> changed.  If your HOME variable is set before starting MSYS then the
> --login process for sh.exe will find it and auto-source the file for
> you.

	Umm...HOME variable is set to " " (minus quotes) prior to launching Msys.

	I am still not getting any visible execution of the .profile script that has any influence 
on the working Msys environment.  

	Yes, yes, I know the "child" runs, but it does not do what I expect it to do, nor does it 
update the actual working Msys environment (as that environment is defined by the listing of 
both the Set variable command and the export variable command when they are run/invoked 
immediately after Msys launch.

	Apparently I am the only one that is having this problem, so I appreciate everyones 
support here.

	I am attempting to define and export user specific variables for Msys environment 
upon startup.

	What I expect Msys (sh.exe/rxvt.exe) to do is to export the variables I am trying to 
export.  I expect it to run .profile on startup (from the "~/" or "root" directory) and define those 
specific user variables I am wanting to define as well as apply them to the existing parent 
sh.exe.

	Msys (sh.exe?) is not doing that, according to one very reliable and trustworthy 
authority, because the child process is not communicating with the parent process on 
launch, even after it is clear who the "parent" of the specific "child" in question actually is and 
who that "child" belongs to.

	Is this "failure to of the child process to reliably and consistently communicate with 
the (or a?) parent process" a "bug", a "feature" or simply a "limitation" of Msys (sh.exe)?

	Does it make sense to have to jump through all of these hoops just so an end user 
can define specific environments variables/references on Msys at the time when Msys is 
launched?

	I truly do want to know.  I am not attempting nor desiring to be confrontive here.

	Thanks again for your input everyone.

		Paul G.