RE: problem debugging xset command inside batch script (revised)
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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, February 19, 2008 3:40 PM To: cygwin-xfree@cygwin.com Subject: problem debugging xset command inside batch script (revised) I have narrowed the problem down to the following: It appears that I cannot run the xset command with the options I need from a Windows/DOS command shell or batch file. For example, when I enter the command xset -q the response is xset: unable to open display The same is true even if the xset command is called from within a bash shell script which itself is called from a Windows/DOS shell. So it's not due to bash or DOS. Rather, it's because the calling program doesn't have an X display to communicate with. As confirmation of this, I observe that the problem does not occur when I call the same script from a Cygwin/rxvt shell because this shell has an X display already defined. It would be nice to be able to update the X font path on the fly and only when I want to start up this particular application, but short of that, adding the necessary font path to the permanent X font path would be OK too. How do I do that? Thanks, 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/ -- 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 MAllen at 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/
Re: problem debugging xset command inside batch script (revised)
jjo wrote: Allen, Matthew MAllen at 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? 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'. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 -- 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)
Larry Hall (Cygwin X reply-to-list-only-lh-x at 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)
jjo wrote: Larry Hall (Cygwin X reply-to-list-only-lh-x at 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? You should not set the DISPLAY variable manually on the _remote_ system. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 -- 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/
