unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 35300@debbugs.gnu.org
Subject: bug#35300: 27.0.50; emacsclient on remote sessions no longer works
Date: Fri, 19 Apr 2019 10:36:47 +0300	[thread overview]
Message-ID: <83h8aucupc.fsf@gnu.org> (raw)
In-Reply-To: <87pnpirc8a.fsf@telefonica.net> (message from Óscar Fuentes on Fri, 19 Apr 2019 03:54:29 +0200)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Fri, 19 Apr 2019 03:54:29 +0200
> Cc: 35300@debbugs.gnu.org
> 
> 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.

Feel free to suggest a more useful text, including for NEWS.

Thanks.





  reply	other threads:[~2019-04-19  7:36 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
2019-04-19  7:36     ` Eli Zaretskii [this message]
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

  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=83h8aucupc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35300@debbugs.gnu.org \
    --cc=ofv@wanadoo.es \
    /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).