Re: How to pull a gui gnus from linux to windows desktop

[Daniel Pittman <daniel@rimspace.net>]

Harry Putnam <reader@newsguy.com> writes:
> Daniel Pittman <daniel@rimspace.net> writes:
>
>>>> 2. Set your DISPLAY appropriately on the Linux server.[2]
>>>
>>>    ( [2]  Either forward it through SSH, or just point it an 
>>>           the Win32 machine.
>>>
>>> Errr . .  you don't mean just ssh -X do you?  And how would one set
>>> point it at the win machine?  By IP or UNC or what?
>>
>> Yup.  The DISPLAY variable is a standard X feature, with the syntax:
>>
>>     ${host}:${display}
>>
>> Eg:  export DISPLAY=win64.example.com:0
>>      export DISPLAY=127.0.0.1:0
>>
>> Your display number should be zero (the first X display), and it
>> will make a TCP connection to port 6000 + <display number> on the
>> target machine to display things.
>
> Sorry to keep hacking away about this but I'm not getting the expected
> results.

OK.  To make sure I am actually helping, you want a GUI Emacs window to
display on the Win32 system, but Emacs to be running on Linux, right?

> Does X11 have to be running on remote (linux) box?

No.  X11 has a client/server model: the "display server" is the bit that draws
the Windows on the screen, and Emacs is a client of that.

When you set DISPLAY to ${hostname}:${display} you tell the client (Emacs) to
open a TCP connection to that system and draw all the GUI stuff there.

So, only client libraries on the Linux side. :)

> When I attempt the connection in that situation I get an error on the
> linux remote if I try to connect to a running emacs daemon.
>
> Using putting to ssh to remote then:
>
> emacsclient  -s nognus -c (where `nognus' is the daemons name)
>
>   Waiting for Emacs...
>   *ERROR*: Display 192.168.0.3:0 can't be opened
>
> The ip number there is the windows machines' static IP on home lan.  As you
> see the display is set to it.

*nod*  My guess is that you have a firewall problem or something like that, or
possibly that your Xming server doesn't allow access from the Linux machine.

You could try the following:

1. Check the Windows firewall is allowing connections on TCP port 6000.
2. Check Xming is listening on the network, not just loopback.
3. Run 'xhost +${ip_of_linux}' on the Win32 machine.

Alternately, these cover using SSH X forwarding on Win32:

http://www.cse.unsw.edu.au/~helpdesk/documentation/Putty.html
http://qiu.bioweb.hunter.cuny.edu/index.php?option=com_content&view=article&id=110

> If I start emacs separate from the daemon it just starts in -nw mode in the
> teminal on the remote.  Maybe there is no way to do this without X running
> on remote?

Emacs on the Linux system needs to be compiled with X support, and needs to be
willing to open a new X display, but that *should* be possible if you are
getting as far as that error.

        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons