From: <sten.kristian.ivarsson@gmail.com>
To: "'Hans-Bernhard Bröker'" <HBBroeker@t-online.de>, cygwin@cygwin.com
Subject: Sv: TMP/TEMP environment variable and /tmp
Date: Thu, 17 Sep 2020 14:12:25 +0200 [thread overview]
Message-ID: <002001d68ceb$ce417d90$6ac478b0$@gmail.com> (raw)
In-Reply-To: <9e5ab93b-9b0b-6855-d5da-365da48ecce2@t-online.de>
> >>> Does anyone know the rational with this behaviour and what can be
> >>> done to get hold of the (real) Windows TMP/TEMP
> >>> environment-variable-values (in a
> >>> (hopefully) platform independent way) ?
>
> >> so if you are making your custom tree, try to stick on that
> >> expectation and have both directories.
> > In general, you are free to set TMP to a directory of your choice,
> > that's the purpose of that variable, no need to sync it with some root.
> > There is a comment in /etc/profile:
> > # TMP and TEMP as defined in the Windows environment
> > # can have unexpected consequences for cygwin apps, but it does not
> > explain what consequences that might be; probably some trouble with
> > ACL/access permissions for temporary files.
>
> Nowadays that would be $LOCALAPPDATA/Temp, or if you really insist, the
> content of /proc/registry/HKEY_CURRENT_USER/Environment/TMP (or TEMP),
> after similarly expanding environment variable references found in that.
>
> The fact that getting Windows' idea of the user's TEMP directory is not
> immediately platform independent may well have been part of the rationale
> for not even trying that.
Well, at least it's up to the user
If the user sets its TMP-variable to "C:\Jabba Dabba Dooo" or "/jabba dabba doo", I expect the value of getenv("TMP") should be just that and regardless of OS the value returned is whatever the variable is set to and not magically changed to "/tmp"
Best regards,
Kristian
[snip]
next prev parent reply other threads:[~2020-09-17 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 8:51 sten.kristian.ivarsson
2020-09-16 11:04 ` marco atzeri
2020-09-16 11:12 ` Thomas Wolff
2020-09-16 19:27 ` Hans-Bernhard Bröker
2020-09-17 12:12 ` sten.kristian.ivarsson [this message]
2020-09-17 15:23 ` Sv: " Thomas Wolff
2020-09-17 21:07 ` Kristian Ivarsson
2020-09-17 21:55 ` Ken Brown
2020-09-17 23:58 ` Doug Henderson
2020-09-18 2:17 ` Ken Brown
2020-09-18 3:56 ` Brian Inglis
2020-09-18 5:56 ` Kristian Ivarsson
2020-09-18 13:15 ` Brian Inglis
2020-09-21 7:57 ` Sv: " sten.kristian.ivarsson
2020-09-20 7:20 ` Andrey Repin
2020-09-17 16:13 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002001d68ceb$ce417d90$6ac478b0$@gmail.com' \
--to=sten.kristian.ivarsson@gmail.com \
--cc=HBBroeker@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).