[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs client/server mode hardcodes /tmp path

From: Stefan Monnier
Subject: Re: emacs client/server mode hardcodes /tmp path
Date: Tue, 28 Oct 2008 10:29:39 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

>>> 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?

Yes, I think we should obey TMPDIR (of course consistently between
emacsclient.c and server.el).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]