Re: Piping println() through an external pager program (more, less)

From:

Nigel Wade <nmw@ion.le.ac.uk>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 18 Mar 2009 09:19:21 +0000

Message-ID:

<gpqeap$k17$1@south.jnrs.ja.net>

Patricia Shanahan wrote:

Martin Gregorie wrote:

On Tue, 17 Mar 2009 09:38:17 -0400, Lew wrote:

Andreas Leitgeb wrote:

Lew <noone@lewscanon.com> wrote:

Thomas Kellerer wrote:

Fn fact my application does have a Swing GUI, but sometimes there is
no way of having an X-Window (e.g. when using SSH where you can't
forward the necessary ports.

Are you speaking of firewall settings and such?

Firewall settings cannot prohibit specifically X11-forwarding with ssh
(but only ssh as a whole). That notwithstanding, a slow connection
can make X11-forwarding impractically slow.

I was speaking to the OP's suggestion of scenarios "when using SSH where
you can't forward the necessary ports". I would like to know under what
circumstances that would pertain. "Impractically slow" may be a problem
but doesn't fit the OP's description.

PuTTY is a commonly used Windows client that won't accept X11 forwarding
because it is text only. If the OP's workplace uses it, that's a pretty
good reason for not using a GUI.

Are you sure PuTTY does not accept X11 forwarding?

It certainly does. It doesn't have any native X/Windows server built in, but it
can establish a tunnel to an already running X server.

I often use PuTTY to access some servers where I have shell accounts.
The configuration dialog has an option "Enable X11 forwarding". With it
checked, and the Cygwin X11 server running on my laptop, if I type e.g.
"xterm &" in the PuTTY window, an xterm, running on the server, displays
on my laptop.

Yep, that's how it works. It does rely on the server end allowing X11
port-forwarding. Some systems are configured to prevent this.

--
Nigel Wade