public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Chris Green <chris@areti.co.uk>
To: cygwin-xfree@cygwin.com
Subject: Re: Possible to use clipboard with remote/xdm connection?
Date: Fri, 02 Jan 2004 15:20:00 -0000	[thread overview]
Message-ID: <20040102152042.GA4731@areti.co.uk> (raw)
In-Reply-To: <20040102144403.GA4596@areti.co.uk>

Well I'm getting a little further with this problem but I'm still
hitting the fundamental problem that xhost can't set the required
local display permission so that xwinclip can be run.

Thus I have the following .bat file to start the xdm session:-

    SET DISPLAY=127.0.0.1:0.0

    SET REMOTE_HOST=192.168.13.1

    SET CYGWIN_ROOT=\cygwin

    SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH%


    REM Cleanup after last run.

    if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH
    attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0
    del %CYGWIN_ROOT%\tmp\.X11-unix\X0

    :CLEANUP-FINISH
    if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir
    %CYGWIN_ROOT%\tmp\.X11-unix

    echo startxdmcp.bat - Starting on Windows NT/2000/XP

    start /B XWin -query %REMOTE_HOST%
    start /B xhost 127.0.0.1
    start /B xwinclip


The "start /B xhost 127.0.0.1" and the "start /B xwinclip" both fail
because they haven't got permission to access display 127.0.0.1:0.0.

How on earth can one set this permission if xhost can't be run?

The xterm one is running in has permission to display so why can't
xhost and xwinterm display there too?

-- 
Chris Green (chris@areti.co.uk)


  reply	other threads:[~2004-01-02 15:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 23:21 Chris Green
     [not found] ` <3FF34EE3.9070300@msu.edu>
2004-01-01 15:37   ` Chris Green
2004-01-01 18:26     ` Alexander Gottwald
2004-01-02 14:04       ` Chris Green
2004-01-02 14:33         ` Alexander Gottwald
2004-01-02 14:44           ` Chris Green
2004-01-02 15:20             ` Chris Green [this message]
2004-01-02 17:27               ` Alexander Gottwald
2004-01-02 18:03                 ` Chris Green
2004-01-02 19:33                   ` Alexander Gottwald
2004-01-02 19:49                     ` Thomas Dickey
2004-01-02 20:15                       ` Alexander Gottwald
2004-01-02 20:56                         ` Thomas Dickey
2004-01-02 21:33                           ` Harold L Hunt II
2004-01-02 21:40                             ` Thomas Dickey
2004-01-02 21:44                               ` Harold L Hunt II
2004-01-02 22:50                     ` Chris Green
2004-01-02 23:50                       ` [OT] " Igor Pechtchanski
2004-01-03  0:07                         ` Thomas Dickey
2004-01-03 12:22                         ` Chris Green
2004-01-02 16:10             ` Alexander Gottwald
2004-01-02 18:00               ` Chris Green
2004-01-02 18:28                 ` Harold L Hunt II
2004-01-02 18:50                   ` Chris Green
2004-01-02 19:20                     ` Harold L Hunt II
2004-01-02 22:50                       ` Chris Green
2004-01-02 20:13                 ` Alexander Gottwald
2004-01-02 22:43                   ` Chris Green
2004-01-03 11:00                     ` Alexander Gottwald
2004-01-12 19:57 Kevin Markle
2004-01-12 20:00 ` Harold L Hunt II

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=20040102152042.GA4731@areti.co.uk \
    --to=chris@areti.co.uk \
    --cc=cygwin-xfree@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).