This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: environment variables derived from TMPDIR
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com, ralfixx at gmx dot de
- Date: Tue, 05 Aug 2008 05:59:27 -0600
- Subject: Re: environment variables derived from TMPDIR
- References: <18584.12950.943391.75971@gepard2.akutech-local.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Ralf Fassel on 8/5/2008 4:59 AM:
| # call program: error: no such file /cygdrive/c/temp/foo.1234
| # filename should be c:/temp/foo.1234
| external_program "$TMPFILE"
Does it work to pass the contents of the file on stdin instead of the file
name as an argument?
external_program < "$TMPFILE"
|
| Alternatively, would it be a good idea to mark variables derived from
| auto-converted variables to become auto-converted on export, too?
| Something like the 'tainted' variables in perl?
Not really possible. Cygwin has no idea how the environment was
populated. Unlike 'tainted' variables in perl, where the variable is at
all times under the control of a single application, with env vars, the
management of environ is by cygwin1.dll but the specification of contents
of new variables is under control of the application. There just isn't a
way to make all applications inform cygwin how those variables were created.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiYQJ8ACgkQ84KuGfSFAYCm1ACeIS7PHK0H8odIF4ua/uQVnBgl
a4MAoLkN+oOzsAC/F/2xoTErijpEU9UD
=W6i5
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/