unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: flameeyes@gmail.com (Diego 'Flameeyes' Petten\x1fFFFFFF)
Cc: emacs-devel@gnu.org
Subject: Re: emacs client/server mode hardcodes /tmp path
Date: Thu, 06 Mar 2008 12:48:24 -0500	[thread overview]
Message-ID: <jwvmypbeojd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m2ejanamdf.fsf@gmail.com> ("Diego 'Flameeyes' Petten\x1fFFFFFF"'s message of "Thu, 06 Mar 2008 16:43:56 +0100")

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


        Stefan




  reply	other threads:[~2008-03-06 17:48 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 [this message]
2008-03-06 17:58   ` Diego 'Flameeyes' Pettenò
2008-10-28 13:38   ` Ulrich Mueller
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvmypbeojd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=flameeyes@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).