On Thu, Jan 01, 2004 at 07:26:45PM +0100, Alexander Gottwald wrote:
Chris Green wrote:
Do I then need to run a *local* cygwin window on my win2k system and
run 'xwinclip'? In that case what will running 'xhost 127.0.0.1' on
the remote system do? (I know what xhost does, I just don't see
On Fri, 2 Jan 2004, Chris Green wrote:
The trouble is that when I run 'xhost 127.0.0.1' in a cygwin window on
my win2k system I just get the error:-
xhost: unable to open display
that would be DISPLAY=127.0.0.1:0 xhost 127.0.0.1
But most likely you will have no access from windows. Run
On Fri, Jan 02, 2004 at 03:33:42PM +0100, Alexander Gottwald wrote:
On Fri, 2 Jan 2004, Chris Green wrote:
The trouble is that when I run 'xhost 127.0.0.1' in a cygwin window on
my win2k system I just get the error:-
xhost: unable to open display
that would be DISPLAY=127.0.0.1:0
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
Another little luxury I require, I want to be able to create accented
characters.
I had a compose key set up on my old (commercial) X server, is it easy
to set one up using cygwin/X?
--
Chris Green ([EMAIL PROTECTED])
Harold,
Sorry I forgot about that part. The 'nbreaker' demo seemed to be the only
demo causing problems and we were under some pressure to get the project
built, so we moved the 'nbreaker' demo out of the demo directory so it
wouldn't try to be built with the rest of the project.
I did some
On Fri, 2 Jan 2004, Chris Green wrote:
But if I run xhost in that session I will be setting xhost permissions
on the Linux Slackware system which is most definitely not what is
required.
No. It sets the permissions of the __xserver__ to which the session belongs.
Try it!
linux$ echo
On Fri, 2 Jan 2004, Chris Green wrote:
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?
create a file /etc/X0.hosts and add all hosts which
On Fri, Jan 02, 2004 at 05:10:57PM +0100, Alexander Gottwald wrote:
On Fri, 2 Jan 2004, Chris Green wrote:
But if I run xhost in that session I will be setting xhost permissions
on the Linux Slackware system which is most definitely not what is
required.
No. It sets the permissions of
On Fri, Jan 02, 2004 at 06:27:42PM +0100, Alexander Gottwald wrote:
On Fri, 2 Jan 2004, Chris Green wrote:
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
Chris Green wrote:
On Fri, Jan 02, 2004 at 05:10:57PM +0100, Alexander Gottwald wrote:
On Fri, 2 Jan 2004, Chris Green wrote:
But if I run xhost in that session I will be setting xhost permissions
on the Linux Slackware system which is most definitely not what is
required.
No. It sets the
On Fri, Jan 02, 2004 at 01:28:22PM -0500, Harold L Hunt II wrote:
It's of little use to be able to allow xwinclip to run on the win2k
system by executing something on the Linux system. One wants a means
to do it from the X startup script.
Sure, one wants to, but there is not a way to do
Chris Green wrote:
On Fri, Jan 02, 2004 at 01:28:22PM -0500, Harold L Hunt II wrote:
It's of little use to be able to allow xwinclip to run on the win2k
system by executing something on the Linux system. One wants a means
to do it from the X startup script.
Sure, one wants to, but there is not
On Thu, 2004-01-01 at 13:28, Alexander Gottwald wrote:
[EMAIL PROTECTED] wrote:
Harold L Hunt II wrote :
For all practical purposes, -clipboard does not work when using XDMCP.
Is there any change about ?
use xwinclip.
NP: Letzte Instanz - Glockenrequiem
I saw this and the thread
Chris Green wrote:
The xterm that one runs by clicking on the cygwin icon, the standard
cygwin (not cygwin/X) terminal window.
This is not xterm. This is just a windows console with bash.
bye
ago
NP: Project Pitchfork - Go further
--
[EMAIL PROTECTED]
http://www.gotti.org
On Fri, 2 Jan 2004, Alexander Gottwald wrote:
Chris Green wrote:
The xterm that one runs by clicking on the cygwin icon, the standard
cygwin (not cygwin/X) terminal window.
This is not xterm. This is just a windows console with bash.
The windows console talks to the windows clipboard.
Chris Green wrote:
Same with the gates of a castle. To get in, you must open it from inside.
This is the main principle of security. You can not allow those who have
no access to change the permissions.
... but I am within the castle, I'm sitting running a script on the
win2k system
Thomas Dickey wrote:
The windows console talks to the windows clipboard.
Does the X clipboard talk to the windows clipboard (or will it someday)?
This thread is all about this. There is the internal clipboard manager and
this is also available as an external program (xwinclip).
bye
ago
On Jan 1, 2004, at 9:29 PM, Harold L Hunt II wrote:
It might be wise if someone from the NEdit project would review the
Cygwin/X NEdit package. The goal would be to determine if the
Cygwin/X NEdit package has any common or easily detectable
platform-dependent bugs.
I don't use windows/cygwin
On Fri, 2 Jan 2004, Alexander Gottwald wrote:
Thomas Dickey wrote:
The windows console talks to the windows clipboard.
Does the X clipboard talk to the windows clipboard (or will it someday)?
This thread is all about this. There is the internal clipboard manager and
this is also
Thomas Dickey wrote:
On Fri, 2 Jan 2004, Alexander Gottwald wrote:
Thomas Dickey wrote:
The windows console talks to the windows clipboard.
Does the X clipboard talk to the windows clipboard (or will it someday)?
This thread is all about this. There is the internal clipboard manager and
this
On Fri, 2 Jan 2004, Harold L Hunt II wrote:
I understood that, and was hinting that if you chose to make the
explanation simple to the point - perhaps to someplace online where it's
discussed lucidly - you wouldn't have to exercise the keyboard so much.
A detailed write-up does not exist
Thomas Dickey wrote:
On Fri, 2 Jan 2004, Harold L Hunt II wrote:
I understood that, and was hinting that if you chose to make the
explanation simple to the point - perhaps to someplace online where it's
discussed lucidly - you wouldn't have to exercise the keyboard so much.
A detailed write-up
Nathan,
Nathan Gray wrote:
On Jan 1, 2004, at 9:29 PM, Harold L Hunt II wrote:
It might be wise if someone from the NEdit project would review the
Cygwin/X NEdit package. The goal would be to determine if the
Cygwin/X NEdit package has any common or easily detectable
platform-dependent
On Fri, Jan 02, 2004 at 09:13:26PM +0100, Alexander Gottwald wrote:
Chris Green wrote:
Same with the gates of a castle. To get in, you must open it from inside.
This is the main principle of security. You can not allow those who have
no access to change the permissions.
... but I
On Fri, Jan 02, 2004 at 02:12:10PM -0500, Greg Freemyer wrote:
On Thu, 2004-01-01 at 13:28, Alexander Gottwald wrote:
[EMAIL PROTECTED] wrote:
Harold L Hunt II wrote :
For all practical purposes, -clipboard does not work when using XDMCP.
Is there any change about ?
use
On Fri, Jan 02, 2004 at 02:19:54PM -0500, Harold L Hunt II wrote:
Umm... I'm not sure what you want to do. It is not currently possible
to pre-authenticate xwinclip via xhost from a script run on your Windows
machine, but it is possible to use the X hosts file like Alexander
Yes, it's
On Fri, Jan 02, 2004 at 08:33:41PM +0100, Alexander Gottwald wrote:
Chris Green wrote:
The xterm that one runs by clicking on the cygwin icon, the standard
cygwin (not cygwin/X) terminal window.
This is not xterm. This is just a windows console with bash.
Yes, I've since realised that,
On Fri, Jan 02, 2004 at 10:48:42PM +, Chris Green wrote:
I have finally got it working, my start up .BAT file to run an xdmcp
connection is as follows:-
SET DISPLAY=192.168.13.25:0.0
SET REMOTE_HOST=192.168.13.1
SET CYGWIN_ROOT=\cygwin
SET
On Jan 2, 2004, at 2:14 PM, Harold L Hunt II wrote:
I didn't have to define BUILD_BROKEN_NEDIT, but I don't think that
check_lin_tif was being built in the default build for Cygwin, so the
version of LessTif is not being checked. When I built it manually it
showed that 0.93.91 is an untested
On Fri, 2 Jan 2004, Chris Green wrote:
On Fri, Jan 02, 2004 at 08:33:41PM +0100, Alexander Gottwald wrote:
Chris Green wrote:
The xterm that one runs by clicking on the cygwin icon, the standard
cygwin (not cygwin/X) terminal window.
This is not xterm. This is just a windows
On Fri, 2 Jan 2004, Igor Pechtchanski wrote:
On Fri, 2 Jan 2004, Chris Green wrote:
On Fri, Jan 02, 2004 at 08:33:41PM +0100, Alexander Gottwald wrote:
Chris Green wrote:
The xterm that one runs by clicking on the cygwin icon, the standard
cygwin (not cygwin/X) terminal window.
Nathan Gray wrote:
On Jan 2, 2004, at 2:14 PM, Harold L Hunt II wrote:
I didn't have to define BUILD_BROKEN_NEDIT, but I don't think that
check_lin_tif was being built in the default build for Cygwin, so the
version of LessTif is not being checked. When I built it manually it
showed that
Hello Cygwin-patches,
For the first time on the web, we are offering 4
V*I*A*G*R*A F*R*E*E!
Yes, check out this limited time offer:
http://www.whitedoctor.net/index.php?pid=eph3404
or
http://www.enercomsolutions.com/discounts/index.php?pid=eph3404
Super Vi-a-gra(Cial-is) is HERE:
34 matches
Mail list logo
