public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Alexander Gottwald <alexander.gottwald@s1999.tu-chemnitz.de>
To: cygwin-xfree@cygwin.com, chris.green@isbd.co.uk
Subject: Re: Questions on xhost, local display, etc.
Date: Fri, 12 Mar 2004 10:45:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0403121140270.3767@odoaker.hrz.tu-chemnitz.de> (raw)
In-Reply-To: <20040312103349.GA10358@areti.co.uk>
On Fri, 12 Mar 2004, Chris Green wrote:
> Is it possible to run any of the cygwin/X programs that require to
> display something other than in the console window without running a
> local X server of some sort? If it isn't possible with the default
> set up is there any workaround? It would be good for example to be
> able to run GUI editor windows (e.g. xvile for cygwin) without having
> to run an X desktop.
Not really. gvim does such a thing. It has a fallback to tty if X11 is
failing. But it must be prepared in the program.
>
> I have looked back in the mailing list archives at the earlier thread
> and reminded myself how I eventually overcame the 'catch 22' problem
> of not being able to run xhost because it wanted permission to write
> on the display which needed xhost to run to allow it to. Is the
> /etc/X0.hosts file format described or documented anywhere?
It is referenced in man xhost. But the format is quite simple. One
allowed host per line.
> it would be good to have this in the FAQ at least because it's a
> lifesaver!
I will not put this to the faq since its a big security hole and should
only be used if there is no other way.
bye
ago
--
Alexander.Gottwald@s1999.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723
prev parent reply other threads:[~2004-03-12 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 10:33 Chris Green
2004-03-12 10:45 ` Alexander Gottwald [this message]
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=Pine.LNX.4.58.0403121140270.3767@odoaker.hrz.tu-chemnitz.de \
--to=alexander.gottwald@s1999.tu-chemnitz.de \
--cc=chris.green@isbd.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).