Re: problem debugging xset command inside batch script (revised)
Larry Hall (Cygwin X cygwin.com> writes: > > Again, DISPLAY not set? But your alternative will leave you with a > console window, or at least briefly. If this is not tolerable, check > out 'run'. > I have to admit that adding the line set DISPLAY=localhost:0.0 before ssh -Y remote_computer_name mathematica solved the problem of the superfluous rxvterm (Thanks!). However, why then does the man page for ssh admonish users against setting the DISPLAY variable manually? -- 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 debugging xset command inside batch script (revised)
Allen, Matthew utcretail.com> writes: > > You should be able to simply set the DISPLAY variable and get xset to > work that way. The other option I'd think you should be able to do is > use a "-display" option to xset. But I haven't confirmed xset has it. > Thanks, Allen. Indeed, xset does have a '-display' option and using it with 'localhost:0.0' fixed the problem with my Windows/DOS script. The next question is this: At the end of my script I start Mathematica on the remote computer and display its front end in a local X window with this command rxvt -e ssh -Y remote_computer_name mathematica This works but leaves behind a superfluous RXVTerm that I'd rather not see. This should work without the extra RXVTerm, but doesn't ssh -Y remote_computer_name mathematica Why? jjo -- 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/
