From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: screen & emacs
Date: Wed, 02 Feb 2011 23:44:39 -0500 [thread overview]
Message-ID: <87k4hh4thk.fsf@sysu76.podval.org> (raw)
I use gnu screen on a server S to which I connect using ssh from various
client boxes (e.g., a windows desktop D and a linux laptop L).
This is great: I always see the same shell sessions on S regardless
where I connect from.
There is only one problem: I run ssh with ForwardX11=yes, so when I
start emacs on S, I see the usual GUI window on D or L (I still have to
figure out the right setting for DISPLAY for some reason) which is
precisely what I want.
Alas, when I open an emacs on S while connected from D and then go over
to L and ssh to S, then the screen session gets stolen from D and
appears on L, __BUT__ the emacs window (again, emacs is running on S,
but the window is shown on D) stays on D and does not go over to L
automagically.
Is there a way around this (except for "emacs -nw")?
PS. One thing I hate about screen is that it does not terminate
"gracefully" on reboot: it is killed so the bash histories of various
widows are not saved...
--
Sam Steingold (http://sds.podval.org/) on Ubuntu 10.04 (lucid)
http://www.memritv.org http://dhimmi.com http://thereligionofpeace.com
http://pmw.org.il http://mideasttruth.com
MS: Brain off-line, please wait.
next reply other threads:[~2011-02-03 4:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 4:44 Sam Steingold [this message]
2011-02-03 4:58 ` screen & emacs Justin Lilly
2011-02-03 17:28 ` Sam Steingold
2011-02-03 18:00 ` Eli Zaretskii
2011-02-03 19:14 ` Sam Steingold
2011-02-03 19:25 ` Chad Brown
2011-02-03 19:54 ` Sam Steingold
2011-02-11 7:10 ` Kevin Rodgers
2011-02-03 18:13 ` Andreas Marschke
2011-02-03 20:31 ` Philipp Haselwarter
2011-02-03 20:54 ` Andreas Marschke
2011-02-04 17:01 ` Dan Nicolaescu
2011-02-03 17:24 ` Andreas Schwab
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=87k4hh4thk.fsf@sysu76.podval.org \
--to=sds@gnu.org \
--cc=emacs-devel@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 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).