From: Erik Veenstra Date: 2005-01-18T09:51:05+09:00 Subject: Re: Ignoring RUBYOPT ? > > > Have you checked for putenv()? > > > > Briliant idea! And yes, I've checked it. And no, it doesn't > > exist... > > I can smell a kind of sarcasm here ;-). Anyways, you are > welcome. Sorry... ;-) > You can also see into how you launch your ruby from > FreePascal, some exec variants, like execve(), provide the > ability to specify environment for a program you launch. I > now recall this mentioned on some FreePascal forums. > (Disclaimer: I do not know FreePascal, I do not program in > Windows). execve is part of the Linux unit and of no use for us. There's no equivalent in the Windows world. Some time ago, I switched from exec of the Dos unit to executeprocess of the SysUtils unit, because of the length of the command line (~4000 instead of 255). The problem with RUBYOPT is easily solved in the Linux universe by executing a shell script in which RUBYOPT is set to nothing before launching Ruby. There are no irritating DOS-box popping up here. (It wouldn't be called "DOS-bos", anyway...) The problem is really a problem in the Windows world. And it's exactly the latter that has no execve... > Sorry if it is of no help either, No problem. I'm getting used to it... ;-) > Gennady. gegroet, Erik V.