Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: [OT ssh -Y] Attempting to start emacsclient .. unusual error?
Date: Sun, 11 Jan 2015 09:55:40 -0500	[thread overview]
Message-ID: <87sifhnz83.fsf@reader.local.lan> (raw)

It may just be a property of using emacs on Solaris.. there seem to be
a few of those.

I hoped to pull an running gnus session across local-lan using ssh -Y
which I do quite often on other of my lan boxes.

On a solaris box where I have done this very thing not so very long
ago I now get:

ssh -Y (Gentoo linux HOST) "emacsclient -snognus -c"
(There is an gnus session with a server named nognus running there)

  X11 forwarding request failed on channel 0
  emacsclient: could not get terminal name

Anyone here ran into this?  Or espescially, have some idea what to do
about it?

In case it matters that Solaris-HOST Xsession (only one user) has had this
typed into USER's xterm `xhost +' for reasons not related to the subject
of this post.




             reply	other threads:[~2015-01-11 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 14:55 Harry Putnam [this message]
2015-01-11 16:12 ` Andreas Schwab
2015-01-11 21:31   ` Harry Putnam
2015-01-11 21:37   ` Harry Putnam
2015-01-12  3:39 ` Mike Kupfer
2015-01-12 18:39   ` Harry Putnam

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=87sifhnz83.fsf@reader.local.lan \
    --to=reader@newsguy.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).