[2304] in athena10
Re: [Debathena] #206: Define behavior around zwgc and remote X11
daemon@ATHENA.MIT.EDU (Debathena Trac)
Wed Apr 15 23:12:42 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: jdreed@mit.edu, xavid@mit.edu
Date: Thu, 16 Apr 2009 03:12:12 -0000
Reply-To:
Message-ID: <052.5dced763accae8f1a0f09e4cad6f6d39@mit.edu>
In-Reply-To: <043.3e6b79eb35f4f0dae95a1ca12d5276d0@mit.edu>
Content-Transfer-Encoding: 8bit
#206: Define behavior around zwgc and remote X11 sessions------------------------+---------------------------------------------------
Reporter: jdreed | Owner:
Type: enhancement | Status: new
Priority: major | Component: --
Keywords: |
------------------------+---------------------------------------------------
Comment(by xavid):
I feel like we should make some effort to make the default behavior less
confusing. The most common case for most users where you would SSH with X
forwarding is from a cluster machine. In this case, you get two copies of
each window gram, and the normal methods of turning off windowgrams don't
effect the remote set. The fact that it's totally nonobvious that some of
your windowgrams are coming from the remote server, especially if you're
not actually taking advantage of X forwarding. While some people are used
to the current behavior, it is not very intuitive and it seems to me that
most new Athena users would not want the current behavior.
I would propose that we have as default behavior not running zwgc for SSH
sessions of any type, but document this as a change in Debathena and
provide a simple way using zephyr variables to enable the old behavior.
(FWIW, up until the point where I disabled zwgc all together, I was
surprised every single time this happened when I was on a cluster machine.
Interpret this as you will.)
-- Ticket URL: <http://debathena.mit.edu/~debathena/trac/trac.fcgi/ticket/206#comment:2>Debathena <http://debathena.mit.edu/>MIT Debathena Project
