all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Glenn Morris <rgm@gnu.org>
Cc: 35300@debbugs.gnu.org
Subject: bug#35300: 27.0.50; emacsclient on remote sessions no longer works
Date: Fri, 19 Apr 2019 03:54:29 +0200	[thread overview]
Message-ID: <87pnpirc8a.fsf@telefonica.net> (raw)
In-Reply-To: <8v1s1y3k6v.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 18 Apr 2019 20:36:24 -0400")

retitle Improve emacsclient error message to inform about new requirements
stop

Glenn Morris <rgm@gnu.org> writes:

> Works for me. I guess your ssh is not setting XDG_RUNTIME_DIR.
> This is handled by pam_systemd, ref eg
> https://www.freedesktop.org/software/systemd/man/pam_systemd.html

I have

UsePAM no

in my sshd config. Thanks Glenn.

> See discussion in https://debbugs.gnu.org/33847

Before reporting this issue I found and skimmed over that one. What a
mess.

My main concern about this is to ensure that any change that breaks
functionality goes with prominent notes about the change and how to
adapt to it. Showing just the standard error message in the output of
emacsclient when it knows the probable origin of the problem is not user
friendly. We must give a proper note about the existence of new modes of
failure and explain (or at least hint) how to deal with them.





  reply	other threads:[~2019-04-19  1:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 21:21 bug#35300: 27.0.50; emacsclient on remote sessions no longer works Óscar Fuentes
2019-04-19  0:36 ` Glenn Morris
2019-04-19  1:54   ` Óscar Fuentes [this message]
2019-04-19  7:36     ` Eli Zaretskii
2019-04-19 12:36       ` Óscar Fuentes
2019-04-19 13:10         ` Eli Zaretskii
2019-04-19 13:31           ` Óscar Fuentes
2019-04-19 14:08             ` Eli Zaretskii
2019-04-19 14:30               ` Óscar Fuentes
2019-04-19 15:07                 ` Eli Zaretskii
2019-04-19 15:40                   ` Óscar Fuentes
2019-04-20 17:42       ` Glenn Morris
2019-04-20 17:59         ` Óscar Fuentes
2019-04-20 19:31 ` Paul Eggert
2019-04-20 19:52   ` Óscar Fuentes
2019-04-24 16:13     ` Glenn Morris

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=87pnpirc8a.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=35300@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /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.