all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: emacsclient and XAUTHORITY variable
Date: Sun, 9 Aug 2015 01:07:49 +0200	[thread overview]
Message-ID: <21958.35781.182580.545557@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <jwvbnekrpl8.fsf-monnier+emacs@gnu.org>

>>>>> On Thu, 06 Aug 2015, Stefan Monnier wrote:

>> frame's "environment" parameter. So Emacs has all information which
>> is necessary, and I wonder if this couldn't be passed to the Xau
>> library before opening the X display for the new frame?

> I'm pretty sure that in theory it can be handled, indeed.
> I don't know how much work it would entail in practice.

I've started to look into it, and it seems that Xau wasn't designed
with that problem in mind. The relevant function is XauFileName, which
checks the XAUTHORITY environment variable, or otherwise defaults to
~/.Xauthority. Other than that, there is no way of telling Xau about
the file's location. Neither can it handle multiple auth files.

So about the only possibility would be to temporarily add the
XAUTHORITY variable to Emacs' environment (that is, the real
environment, not 'process-environment') before opening the X display.
Not sure if this could be implemented without being too fragile.

> I must say that I find it a pain in the rear (as a plain user) that
> gdm3 started to set XAUTHORITY rather than to put the auth data
> where god intended it to be (i.e. ~/.Xauthority). "emacsclient" is
> not the only victim, so I'm not highly motivated to fix the problem
> on Emacs's side.

I agree, everyone using ~/.Xauthority would be the better solution.

Ulrich



      reply	other threads:[~2015-08-08 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02 21:49 emacsclient and XAUTHORITY variable Ulrich Mueller
2015-08-06 23:02 ` Stefan Monnier
2015-08-08 23:07   ` Ulrich Mueller [this message]

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=21958.35781.182580.545557@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=emacs-devel@gnu.org \
    --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.