Re: xterm not accepting Window Title name changes
Found this somewhere along the way, I forgot where. Works on my machine. I did notice that the cd command on my machine does meddle with the prompt string and send it to xterm. Sorry I can't be more helpful. #!/usr/bin/perl # # This is a simple program to change the text in an X-windows title bar. # This used to be a shell script, but that got hosed in an ``update'' # on Linux. It's probably a Good Idea(tm) to do this in perl anyway since # the my program could be vulnerable to somebody putting something really # wierd in as arguments. # print qq(\033]2;@ARGV\007); exit(0) On 10/22/07, Paul McFerrin [EMAIL PROTECTED] wrote: Hum... The PS1 setting. Nope, that's not the problem. The root of the settitle() function is NOT the setting of PS1. It's setting in /etc/profile is commented out. In my local .profile, PS1 is set to just '$PWD'. I have verified that there are no other hidden settings of PS1. I tried your settitle() function, and the title remains unchanged: basename of the shell. My posting in the archives envolves the use of 'rxvt' only and has nothing to do with xterm. I always startup 'startxwin.sh' from a non-rxvt window (e.g. the console window). Regardless what shell I'm using, it always seems to get it's basename into the window. Hum Does anyone else want to try a stab at this problem? Brian Dessent wrote: Paul McFerrin wrote: I can't seem to get xterm to recognize Window Title name changes via the following: echo \0332;new_title\07\c You were just recently posting in the thread where this came up before: http://cygwin.com/ml/cygwin/2007-10/threads.html#00188 and http://cygwin.com/ml/cygwin/2007-10/msg00202.html. Specifically, the default Cygwin prompt (PS1) contains characters that set the title so anything you do that doesn't involve changing PS1 will have no effect -- or more precisely, your echo command above does set the title for a few milliseconds, until the next prompt overwrites it. (In your rxvt example, you aren't starting a login shell and thus /etc/profile isn't sourced and PS1 isn't set, which is presumably why it works there.) Brian -- 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/ -- 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: XWin starts but hangs as soon as I start an X-application
I'm having similar trouble, starting yesterday. xterm and xclock both hang as described, but xeyes, xfig and rxvt all work. On 8/17/07, Larry Hall (Cygwin X) [EMAIL PROTECTED] wrote: Olumide wrote: Hi - Yesterday, I started my X server as usual and followed by an X-application (gnuplot), which refused to start up. At the same time the XWin process stopped working, in fact it had stopped page faulting. On terminating the XWin process I got the following message XIO: fatal IO error 104 (Connection reset by peer) on X server 127.0.0.1:0.0 (IP address changed) after 0 requests (0 known processed) with 0 events remaining. snip All of this is really strange. The only change/installation I made to my system yesterday was to install a logitech webcam. Remove it again. I think you'll find that solves the problems you were seeing. Logitech drivers are known to cause problems. Cygwin is one of its lucky affected applications. Search the email list archives for dodgy apps to find a list of software with buggy versions which can cause problems like this. -- 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/ -- 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: XWin starts but hangs as soon as I start an X-application
I can no longer reproduce the problem. Whatever it was, it seems to have sorted itself out in that queasy just try rebooting 50 times way that windows 'fixes' iteself. Gah. On 8/18/07, Jay Abel [EMAIL PROTECTED] wrote: Yikes. I turned off VirusScan on-access and buffer overflow checking, then xterm ran. So happy it was running, I forgot what I was doing and fixed some missing fields in my .xdefaults file (changed Xterm to xterm) and opened another window. No problem. xclock now runs, no problem. Re-enable buffer overflow and access scan, and guess what? they both still work. Put back configuration file. Still works. wtf? I'll try rebooting and see if the problem reappears. On 8/18/07, Jay Abel [EMAIL PROTECTED] wrote: On 8/18/07, Larry Hall (Cygwin X) [EMAIL PROTECTED] wrote: Jay Abel wrote: I'm having similar trouble, starting yesterday. xterm and xclock both hang as described, but xeyes, xfig and rxvt all work. And have you installed any dodgy app recently? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 Not recently, but I'm checking now. I do have an evil logitech mouse, but I thought I forced it to use the stock ms drivers. It's possible that I already have the unwanted/conflicting software, but that it wasn't a problem until I upgraded to the most recent cygwin1.dll. I'll see if I can find the list of evil applications then check if I have any of them installed, and also try using an older cygwin.dll to see if the problem disappears. I noticed that in the case of xterm, its associated shell also starts and the xterm process cannot be killed until the corresponding shell has also been killed, not from taskmanager, cygwin, etc. On the other hand, even typing 'xterm -version' hangs before any output is produced. It's almost as if the output pipe isn't being created properly, but ps doesn't show xterm in the I state. What I'm trying to say is that the problem seems to happen when output is produced. Note that even if the $DISPLAY variable isn't set, xterm still hangs (you'd expect it to spit out an error message and die). So I'd wager the problem is related to writing to stdout, not to X. I'll take another look to see if I have any of the non-recommended applications, such as logitech stuff, that might be interfering. -- 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/
