From: Ulrich Mueller <ulm@gentoo.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs@gentoo.org, Diego Petteno <flameeyes@gmail.com>,
emacs-devel@gnu.org
Subject: Re: emacs client/server mode hardcodes /tmp path
Date: Tue, 28 Oct 2008 14:38:14 +0100 [thread overview]
Message-ID: <18695.5574.107271.711561@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <jwvmypbeojd.fsf-monnier+emacs@gnu.org>
>>>>> On Thu, 06 Mar 2008, Stefan Monnier wrote:
>> I'm working to make use of pam_mktemp in my systems by default,
>> pam_mktemp is a PAM module that creates a private temporary
>> directory per-user inside /tmp and sets TMP and TMPDIR accondingly.
> Indeed. I'm not sure what should be done here. The reason for the
> hard-coded /tmp is that the emacsclient process and the emacs server
> process may be executed from different contexts (different login
> sessions for example), so it's not clear that they would use the
> same $TMPDIR setting.
> What do others think? Should we take the risk and obey $TMPDIR?
Hi,
coming back to this old subject, has any decision been taken on this?
GNU Coding Standards [1] explicitely say:
# If you make temporary files, check the TMPDIR environment variable;
# if that variable is defined, use the specified directory instead of
# /tmp.
Ulrich
[1] http://www.gnu.org/prep/standards/standards.html#Semantics
next prev parent reply other threads:[~2008-10-28 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 15:43 emacs client/server mode hardcodes /tmp path Diego 'Flameeyes' Pettenò
2008-03-06 17:48 ` Stefan Monnier
2008-03-06 17:58 ` Diego 'Flameeyes' Pettenò
2008-10-28 13:38 ` Ulrich Mueller [this message]
2008-10-28 14:29 ` Stefan Monnier
2008-10-29 7:51 ` Ulrich Mueller
2008-10-29 9:15 ` Juanma Barranquero
2008-10-29 9:28 ` Ulrich Mueller
2008-10-29 9:37 ` Juanma Barranquero
2008-10-29 14:41 ` Stefan Monnier
2008-10-29 14:55 ` Juanma Barranquero
2008-10-29 15:03 ` Stefan Monnier
2008-10-29 15:12 ` Juanma Barranquero
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=18695.5574.107271.711561@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=emacs-devel@gnu.org \
--cc=emacs@gentoo.org \
--cc=flameeyes@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.