XWindows version of Java?

[siegfried]

I notice the cygwin version of emacs runs in XWindows and is one of the few
XWindows programs I run frequently on windows.

I assume (I have not tried it yet) I can run the cygwin version of emacs on
my home windows machine from a remote machine with the xhost and "ssh -X"
commands. Is this correct?

Sun's javaw runs native windows, not xwindows. Is there a way I can run GUI
java programs on windows using xwindows so they are compatible with xhost
and "ssh -X"?

I've been reading about gcj and that might work but it looks like I'd have
to recompile everything myself. I want to run eclipse on windows from a
remote machine and I see in fedora core 4 they have recompiled eclipse with
gcj. But I was hoping I would not have to recompile eclipse from the source.

Does cygwin have a javax program that runs GUI java programs under xwindows?

Thanks,
Siegfried


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: modification of startx.bat not work

[Igor Peshansky]

I know this is a fixed issue, but some comments below nonetheless, to tie
up loose ends.

On Wed, 26 Jul 2006, Dirk Schleicher wrote:

> Am Tue, 25 Jul 2006 20:04:53 -0500
> schrieb René Berber <[EMAIL PROTECTED]>:

.  Thanks.

> > René Berber wrote:
> > [snip]
> > > You probably can just run a Windows shortcut to XWin with all the
> > > parameters, and use .xinitrc or .xsession to start up SC.
> > [snip]
> >
> > I made a little experiment and the above sentence is not true: if I
> > start XWindows from an icon/shortcut (using "C:\cygwin\bin\run.exe
> > -p /usr/X11R6/bin XWin -multiwindow -clipboard -silent-dup-error -dpi
> > 100") XWin starts fine but my .xinitrc (and .xsession) is not used...
> > XWin does not know what user started it.

Naturally -- .xinitrc and .xsession are artifacts of xinit (and startx),
not XWin.

> > So to run the application I would also need an icon/shortcut for the
> > application.
>
> I found out that the .xinitrc parameters are used with startx. I start
> the normal bash and type in startx. This start Xserver and SC. And SC
> works fine.
> C:\cygwin\bin\run.exe -p /usr/X11R6/bin/ startx -display 127.0.0.1:0.0
> do not work because startx is a script not an .exe

Right, but

C:\cygwin\bin\run.exe -p /usr/X11R6/bin/ bash --login -c startx -display 
127.0.0.1:0.0

will, because bash will know how to interpret the shebang (#!) in startx
and invoke the script appropriately.  People often overlook this solution
and declare that it's impossible to start a script from a shortcut.

Or you could've used xinit, which *is* a .exe.
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

RE: modification of startx.bat not work

[Phil Betts]

Dirk Schleicher wrote on Tuesday, July 25, 2006 9:48 AM::

> Am Tue, 25 Jul 2006 03:16:51 -0500
> schrieb René Berber <[EMAIL PROTECTED]>:
> 
> [snip]
>> Correct, the way XWin is started using startxwin.bat does make the
>> whole server execution depend on the xterm, so when the xterm is
>> closed XWin terminates. 

This is not true.  It's startx (or rather, xinit) that closes the 
server on exit.  You can safely remove the xterm line from startxwin.bat
(or startxwin.sh) and the server just keeps going.

>> That can be changed easily by using startx (instead of startxwin.bat)
>> and creating a file in your home directory named .xsession like this:
>> 
>> #!/bin/sh
>> #
>> # FILE: $HOME/.xsession
>> 
>> # exec SylpheedClaws
>> 
>> /usr/bin/sylpheed-claws & scpid=$!
>> 
>> # Now wait for program to terminate
>> 
>> wait $scpid
>> exit 0
> 
> I try it. The only thing is that if SC is close the Xserver close too.

That's to be expected.

>>> What I try to get is one script where I can start a Xserver without
>>> any bash "window" and SC.
> 
> Again to start this I have to start a cygwin bash shell. I like to
> start SC without a shell 

Your problem is that you're using xinit via startx.  The last command 
executed is intended to be a window manager.  It is designed so that 
when the window manager dies, X is shut down.  This is (usually) what 
one wants.  Unfortunately for users of startx, XWin by default uses its 
built-in window manager, so in order to keep X alive some other process 
must be started.  An xterm was chosen IIRC because most users will want 
a shell at some point in their session.

If you use startxwin.* to start X instead, you'll find it doesn't 
require any process to hang around.  The distributed files start an 
xterm, but you can safely remove that line.

Please don't be tempted to try hacking startxwin.* to start sylpheed.
It's bad practice to use a server initialisation script to start client
programs.  I would guess that at least half of the "fault reports" on 
this list are from people who try to use startx* to run xterm, then
complain that they get a duplicate invocation error.

It's much better to use startxwin.bat to start XWin once (you can put a
shortcut to startxwin.bat in your Windows startup folder), then have a
shortcut to start your client programs such as sylpheed.

If you want to start sylpheed without explicitly starting XWin, you can 
write a small script to use checkx to see if the server is running and
if it isn't, start it.

E.g.

--- /tmp/xdemo.sh -
#!/bin/bash
export DISPLAY=:0
/usr/bin/checkx || /usr/X11R6/bin/startxwin.sh
exec /usr/X11R6/bin/xeyes
--

You can then run this script from a shortcut where the target is:

C:\cygwin\bin\run.exe /bin/bash -c /tmp/xdemo.sh

You would need to remove the line from startxwin.sh that starts xterm,
which means you should really use a copy of it, otherwise the next 
time you update X, you'd be likely to lose your change.

HTH

Phil
-- 

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the H.E Information Systems Ltd. 
Tel:0161 866 9066
Web:  www.heis.co.uk

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.clearswift.com
**


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: modification of startx.bat not work

[Dirk Schleicher]

Am Wed, 26 Jul 2006 03:28:43 -0500
schrieb René Berber <[EMAIL PROTECTED]>:

> Now for the network problem, that is really strange, I saw your other
> message and understand that you can't troubleshoot the network.  I
> really was thinking of troubleshooting in the regular way, on a
> terminal window, but if only SC has problems then perhaps is a
> timeout or some option that can be set inside SC.


I found it. If you have a Window icon with link in property there are
two "lines"
Line on "Target" C:\cygwin\bin\run.exe -p /usr/X11R6/bin sc.bat

Line two "execute in" C:\cygwin\bin
(sorry I can not describe it better)
 If line two the path show where SC is it dit not work with path to
C:\cygwin\bin\ SC work

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: modification of startx.bat not work

[René Berber]

Dirk Schleicher wrote:
[snip]
>> So to run the application I would also need an icon/shortcut for the
>> application.
> 
> I found out that the .xinitrc parameters are used with startx. I start
> the normal bash and type in startx. This start Xserver and SC. And SC
> works fine.

Yes that's what I meant in my message.  XWin seems to get the user's home
directory (perhaps only the user name) from the shell environment, so it can run
the user's .xinitrc .

An option that I have not tested is to change the global xinitrc and see if that
works.  Of course being the global one means that all users on that computer
will get the same application, but if you are the only user of X then that's no
problem.  The global script is in /etc/X11/xinit/xinitrc .

> C:\cygwin\bin\run.exe -p /usr/X11R6/bin/ startx -display 127.0.0.1:0.0
> do not work because startx is a script not an .exe

Yeah, I tried that too.

> C:\cygwin\bin\run.exe -p /usr/local/bin/ sylpheed-claws.exe -display
> 127.0.0.1:0.0  start SC for a second. I can see this in the
> task-manager.

The message must be: "no DISPLAY found" since X windows is not running and by
default all applications try display :0.0 .

> I think it is not possible to start SC from one icon without typing
> something

Like I said: it can be done with 2 icons, one to start X and another to start
SC.  In fact you can start all the X applications you want after starting X.

Now for the network problem, that is really strange, I saw your other message
and understand that you can't troubleshoot the network.  I really was thinking
of troubleshooting in the regular way, on a terminal window, but if only SC has
problems then perhaps is a timeout or some option that can be set inside SC.
-- 
René Berber


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: modification of startx.bat not work

[Dirk Schleicher]

Am Wed, 26 Jul 2006 10:10:27 +0200
schrieb Dirk Schleicher <[EMAIL PROTECTED]>:

> I think it is not possible to start SC from one icon without typing
> something

It work.

I copy startx.bat to sc.bat and modify it
"
%RUN% XWin -multiwindow -clipboard -silent-dup-error

REM Startup an xterm, using bash as the shell.

rem %RUN% xterm -e /usr/bin/bash -l
%RUN% C:\cygwin\usr\local\bin\sylpheed-claws.exe
"
then I make an icon with a link
C:\cygwin\bin\run.exe -p /usr/X11R6/bin sc.bat

and it works.


Thanks for the help

Dirk

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: modification of startx.bat not work

[Dirk Schleicher]

Am Tue, 25 Jul 2006 20:04:53 -0500
schrieb René Berber <[EMAIL PROTECTED]>:

> René Berber wrote:
> [snip]
> > You probably can just run a Windows shortcut to XWin with all the
> > parameters, and use .xinitrc or .xsession to start up SC.
> [snip]
> 
> I made a little experiment and the above sentence is not true: if I
> start XWindows from an icon/shortcut (using "C:\cygwin\bin\run.exe
> -p /usr/X11R6/bin XWin -multiwindow -clipboard -silent-dup-error -dpi
> 100") XWin starts fine but my .xinitrc (and .xsession) is not used...
> XWin does not know what user started it.
> 
> So to run the application I would also need an icon/shortcut for the
> application.

I found out that the .xinitrc parameters are used with startx. I start
the normal bash and type in startx. This start Xserver and SC. And SC
works fine.
C:\cygwin\bin\run.exe -p /usr/X11R6/bin/ startx -display 127.0.0.1:0.0
do not work because startx is a script not an .exe
C:\cygwin\bin\run.exe -p /usr/local/bin/ sylpheed-claws.exe -display
127.0.0.1:0.0  start SC for a second. I can see this in the
task-manager.

I think it is not possible to start SC from one icon without typing
something

Dirk  

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: modification of startx.bat not work

[Dirk Schleicher]

Am Tue, 25 Jul 2006 13:27:14 -0500
schrieb René Berber <[EMAIL PROTECTED]>:

[snip]
> >> Your original post says that you had a network problem, can you
> >> show the actual message?
> > 
> > no connection with POP3-Server: pop.gmx.de:110
> 
> That error has nothing to do with XWindows.  So, SC was running with
> your modified .bat file, it just could not connect to that pop
> server; try regular network troubleshooting, like "ping pop.gmx.de"
> if that server responds to ping, traceroute, etc.


If I start SC with the modified startx.bat there is no network.
It seams that this "%RUN% xterm -e /usr/bin/bash -l" and then call SC
make the network working. It is not easy to explain it in German but in
English...

This what you wrote "pintg etc." is not possible to test because
there is no bash. If I start a new bash ping and all work but not SC.  

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: Problem with starting X server (alternate solution)

[Mariusz Janczak]

I followed your steps I found that this solution doesn't work for me. I also 
tried to reinstall whole cygwin packege and also without effect. The only 
one solution that works for me is install previous version of X package.

-- 
Mariusz Janczak
"Steve Freeland" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> Apologies for not attaching this to the correct thread; I'm not subscribed 
> to the list and don't really know how I should go about that.  But 
> anyways.
>
> Regarding the "Could not open default font 'fixed'" message:  Stephen A. 
> Goulet mentioned that he was able to fix the problem by following the 
> instructions in the FAQ, substituting /usr for the non-existant 
> /usr/X11R6/lib/X11 mount point.  Mariusz Janczak then replied that he 
> didn't have a /usr mount point either.  I was in the same situation.
>
> The solution I found was to just umount *everything*: First /usr/lib, then 
> /, and /usr/bin last because that's where the umount exe is located. 
> *Then* reinstall the font packages.  That fixed it for me.  I suspect I 
> only really needed to umount /, but I haven't tested that hypothesis.
>
> I'd sure like to know what the underlying problem is, though, it seems odd 
> for this issue to appear out of nowhere in a working system.
>
> - Steve
>
>
>
>
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://x.cygwin.com/docs/
> FAQ:   http://x.cygwin.com/docs/faq/
>
> 




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/