Re: Small update for X server 1.5.3 patch set
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jon TURNEY wrote: Works for me. Note that you don't actually need to the formatting of the log file name yourself, LogInit() already has code to replace %s in the log file name with the display name. I was aware of that, but it wasn't behaving as I expected. Then I figured out that we should be doing something with what LogInit return()s. Revised patch in SVN. If your going to do a release soon-ish, you might considered disabling the call to winRestoreModeKeyStates() in winmultiwindowwndproc.c. The code which tries to synchronize locking key states (e.g. caps lock, etc.) between X and Windows has broken, so is now toggling the modifiers in X every time an X window gains focus. Having the lock state in X just unsynchronized instead might be marginally less irritating until I get a chance to work on a proper fix. Committed. Could you please test? Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkklPb0ACgkQpiWmPGlmQSNjXQCdF4Yl+jeKMS4R+w1yleZw2GJi KrYAoO8655LzBI6qCkiCxhoG0Oo1TKpL =5tP+ -END PGP SIGNATURE- -- 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: Upgrade woes.
On Wed, 19 Nov 2008 21:43:19 -0500, cygwin at cwilson dot fastmail dot fm wrote: Eric Roode wrote: I updated my cygwin the other day, as I periodically do, and I am very sorry I did so. Here are some of the problems I have encountered. It has always been the advice of this list that you should read the announcements on cygwin-announce@ and cygwin-xfree-announce before upgrading blindly. How amusingly recursive: It has always been the advice of the mailing lists that you should check the mailing lists before upgrading :-) I did not check the *-announce lists before running setup. I did not know of their existence. To me, mailing lists are for developers, groupies, and people with tech supp problems, not something to be subscribed to and monitored by ordinary users on an ongoing basis -- I have enough noise in my inbox as it is. I do check www.cygwin.com before doing (what I think is going to be) a routine upgrade. If there's nothing in the news there, I assume that what I'm getting is just an upgrade of existing packages that I already have installed. Is that such a foolish assumption? The flaw in my cunning plan, it seems, is that www.cygwin.com is *never* updated, except to note an occasional upgrade to the DLL itself. I guess I should also have been checking x.cygwin.com -- but even that only has a short mention of an upgrade, with a pointer to the announcement, which mostly talks about stuff that I do not know or care about: something called XCB, some composite extension, some XVideo extension, and so on. Yes, I should have followed the upgrade instructions section, and that would have helped, but would not have prepared me for the unholy mess that was to follow. Now, often you can get away with /not/ doing that, d nothing bad will happen. But if I ran setup, and saw 157 new packages about to be upgraded...I might want to investigate a little before clicking continue. Where do you see 157 new packages about to be upgraded? setup says no such thing. I have been making the assumption, apparently a stupid one, that when you run setup and don't choose to install anything new, it checks for upgrades to the stuff you have already installed, and goes ahead and patches what you have. I don't look to see how much new stuff there is -- why should I? I just click next and go. I did notice that the download and upgrade took much longer than usual. Know what I thought? Gee, there must be some major security fix to a whole lot of packages. But, as always, it's up to you. We'll happily refund all the money you paid. I too contribute to the open-source community, and I have always disliked this snarky answer. It's free -- what did you expect, quality? Service? Well yes, I do. You'll never get far in the closed-source-commercial vs open-source-community argument if you keep falling back on it's free as an excuse not to document, not to support. Eric -- 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/
Problem with OpenGL on new X serverl
Hello, I have a problem running new X server 1.5.3 with openGL. Since this update, X crash when launching an OpenGL client from SunOS server. Since the application we are developing use OpenGL, it's a big problem for me (I have to use an exceed commercial xserver for testing our application). So is there a known solution, patch or other to this issue ? Or in alternative, can I revert update to reinstall the old version of X server before 11/11 upgrade ? Thank you in advance, -- Florent Fievez [EMAIL PROTECTED] cygcheck.out Description: Binary data -- 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: cygwin-x-doc refresh
Christopher Faylor wrote: On Sun, Nov 16, 2008 at 08:14:33PM -0600, Yaakov (Cygwin Ports) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jon TURNEY wrote: I've finished off a first pass at updating the cygwin-x-doc package I started some time ago. Updating the text was a bit less traumatic than expected as it makes good use of entities for things like filenames and paths Interestingly there are CVS repositories for this package at both sourceware.org and at X.org. The X.Org one seems to be more up to date, and seems to contain some (formatting) changes after the 1.0.4 package was made. That's certainly possible, but given that X.Org CVS is obsolete (in favour of git) and neither of us have X.Org commit privileges, I think we should move development back to sourceware. I suspect that will mean that Jon will need write access to the CVS repository. If so, he should fill out the handy dandy little form at: http://sourceware.org, select cygwin-xfree as the project and use either Yaakov or me as the approver. You can put whatever you like in this repository of course. Thanks. I have pushed cygwin-x-docs 1.0.4, then the current X.Org HEAD and then my changes to /cvs/cygwin-xfree/docs. I'm guessing I can't update the live version as it's in a different repository. -- 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: Small update for X server 1.5.3 patch set
Please find at the URL below another small update to the xorg server patch set. http://www.dronecode.org.uk/cygwin/from-xming-patch-set-20081120.tar.bz2 This contains patches taken from the Xming website http://www.straightrunning.com/XmingNotes/ Thanks to Colin Harrison for his permission to use them. * A bunch of clipboard correctness fixes (there are still more fixes related to race conditions on multiprocessor systems that need integrating) * Always enable built-in fonts; disable other FPEs if --enable-builtin-fonts I've reworked this last one slightly from the form you had it in, but I've just realized now that your version was actually correct. If BUILTIN_FONTS is defined, we want to disable the other FPE handlers. -- 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: Upgrade woes.
Back, Michael wrote: My point is that relying on a user to have the forethought, time, and patience to scour through a mailing list archive is probably not the most effective or convenient form of communicating common upgrade problems and solutions. Asking thousands of people to answer a question which you could have entered into Google falls short in convenience as well. -- 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: Upgrade woes.
How does the location of the startup batch file affect the behavior of numlock and capslock in xterm? Yes. The batch file is different. The binary is different. The environment variables are different. For example this is in the old batch file but not in the new one. SET XAPPLRESDIR=/usr/X11R6/lib/X11/app-defaults SET XCMSDB=/usr/X11R6/lib/X11/Xcms.txt SET XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB SET XNLSPATH=/usr/X11R6/lib/X11/locale I suspect that XKEYSYMDB one has something to do with the problem you're having. The new file doesn't assign these variables at all, and runs a different binary. I just re-installed Cygwin on my machine, deleted my .bash_profile, .bashrc and .Xdefaults in my home, and I still have the same numlock/capslock issue. My config is quite standard : Windows XP SP2. It is easily reproductible I guess. BTW, in startxwin.bat, this line : SET CYGWIN_ROOT=\cygwin is true only if you install Cygwin in the default path. I had to change it to match my configuration, otherwise the XWin Server does not 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: Upgrade woes.
Eric Roode wrote: How amusingly recursive: It has always been the advice of the mailing lists that you should check the mailing lists before upgrading :-) Somehow you found *this* list to complain to. On that same page, there are two different *-announce lists. What did you think they were for, wedding announcements? I did not check the *-announce lists before running setup. I did not know of their existence. To me, mailing lists are for developers, groupies, and people with tech supp problems, not something to be subscribed to and monitored by ordinary users on an ongoing basis -- I have enough noise in my inbox as it is. I don't subscribe to any of the lists. I use the on-line archives, or gmane. You can too. That way you can check the lists when you need to, but not clutter your inbox. The problem with googling is it takes a few days or weeks for new information to make it into google's index. The on-line mailing list archives are usually only 15 minutes or less behind current activity. Unless you want to wait a few weeks, scanning the last day or so's subject lines in the archives -- or running a search via gmane -- will find more current results for your queries. I do check www.cygwin.com before doing (what I think is going to be) a routine upgrade. If there's nothing in the news there, I assume that what I'm getting is just an upgrade of existing packages that I already have installed. Is that such a foolish assumption? No. In fact, you can leave out the If qualifier. In general, the only thing setup will do is upgrade what you already have. BUT... The flaw in my cunning plan, it seems, is that www.cygwin.com is *never* updated, except to note an occasional upgrade to the DLL itself. That's because the people with the ability to update the cygwin web page are not the people who maintain and update individual packages -- and there are far too many of the latter to grant such untrammeled access, and far too many individual packages. Any update web page would either grow to unweildy size, recent updates would too quickly roll off the page, and/or the information provided concerning each individual update would be too terse to be useful, or too verbose to allow more than one or two updates to be visible at a time. AND, you probably don't care about the latest octave or subversion update. Fortunately, there is a already a solution to all of these problems: the *-announce mailing lists and their on-line archives. I guess I should also have been checking x.cygwin.com -- but even that only has a short mention of an upgrade, with a pointer to the announcement, which mostly talks about stuff that I do not know or care about: something called XCB, some composite extension, some XVideo extension, and so on. In other words, you're using something you don't understand -- but which hasn't changed in over two years because there was no maintainer (BTW, that's a /bad/ thing). So, you've had years to get used to the way that old version work(ed) -- by years' worth of trial and error, apparently, as you never tried to educate yourself on exactly what you were using. Meanwhile the actual non-cygwin development of X rolled forward, thru a MAJOR restructuring. This restructuring and rewrite caused a few headaches even over in linux-land -- but that was more than a year ago for them, because we (cygwin) are so far behind. So, when we finally catch up...we can expect the some of the same headaches. And reasonable users with an ounce of curiosity -- or a modicum of caution -- were all well-informed of the possibility. Others, perhaps, were not so well informed. Which is not to say that ANY specific headache was predicted, or predictable -- or even preventable. If some *specific* problem were predicted and preventable, Yaakov Jon would have done so. In fact, they did. There's a thousand things that /didn't/ go wrong. Yes, I should have followed the upgrade instructions section, and that would have helped, but would not have prepared me for the unholy mess that was to follow. Counterfactual. IF you had followed the proper instructions, then something different would have happened; we don't know exactly what, nor /how many/ things would have gone wrong in that hypothetical case. Of your complaints, most of them WERE addressed in the original announcement message. Of the remainder, would one or two minor problems qualify as an unholy mess? There's also one basic computer-related common-sense policy that your practices violate: if Adobe Premiere installs a bunch of files, and you EDIT one of them -- unless it is a configuration file -- you can EXPECT that Adobe Premiere will feel free to over-write the file on its next upgrade. Premiere installed the file, it's not a user configuration file -- it OWNS that file. Not you. Don't be surprised when your customizations go poof. If you want to customize a non-configuration file, MAKE A COPY. Put it somewhere
Re: cygwin-x-doc refresh
On Thu, Nov 20, 2008 at 12:57:38PM +, Jon TURNEY wrote: Christopher Faylor wrote: On Sun, Nov 16, 2008 at 08:14:33PM -0600, Yaakov (Cygwin Ports) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jon TURNEY wrote: I've finished off a first pass at updating the cygwin-x-doc package I started some time ago. Updating the text was a bit less traumatic than expected as it makes good use of entities for things like filenames and paths Interestingly there are CVS repositories for this package at both sourceware.org and at X.org. The X.Org one seems to be more up to date, and seems to contain some (formatting) changes after the 1.0.4 package was made. That's certainly possible, but given that X.Org CVS is obsolete (in favour of git) and neither of us have X.Org commit privileges, I think we should move development back to sourceware. I suspect that will mean that Jon will need write access to the CVS repository. If so, he should fill out the handy dandy little form at: http://sourceware.org, select cygwin-xfree as the project and use either Yaakov or me as the approver. You can put whatever you like in this repository of course. Thanks. I have pushed cygwin-x-docs 1.0.4, then the current X.Org HEAD and then my changes to /cvs/cygwin-xfree/docs. I'm guessing I can't update the live version as it's in a different repository. If you update the documentation in the htdocs/xfree/docs/cg directory they should show up on the web site automatically. In fact, everything under htdocs should work like that. cgf -- 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 OpenGL on new X serverl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Florent Fievez wrote: I have a problem running new X server 1.5.3 with openGL. Since this update, X crash when launching an OpenGL client from SunOS server. Since the application we are developing use OpenGL, it's a big problem for me (I have to use an exceed commercial xserver for testing our application). So is there a known solution, patch or other to this issue ? I see that you do have the libGL1 package installed. Could you please review my results with GLX: http://cygwin.com/ml/cygwin-xfree/2008-11/msg00100.html http://cygwin.com/ml/cygwin-xfree/2008-11/msg00160.html If you are still having issues, please attach your /var/log/XWin.log as well. Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkklq4sACgkQpiWmPGlmQSMyxACfYTZO01vhKNcYgDSJXRsB5536 niQAoMygFXaaFuXEdLc5HVXgaR2giskK =SSZv -END PGP SIGNATURE- -- 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/
new X-server and remote computers
I mostly use the Cygwin X-server when connect to remote unix boxes though SSH. I got the new server working for all of the programs that I use except one. A molecular modelling graphics program called VMD causes the following error. xterm: fatal IO error 32 (Broken pipe) or KillClient on X server localhost:15.0 it opens its first window correctly, when it tries to open the second window, the X-server dies and the unix side gave the above error. Any suggestions? Jeff Forbes -- 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/
Multiple Monitors issue with Xterm
Hi, I just installed cygwin with X on WindowsXP and after making the change to have it starup in C:\cygwin\bin the Xserver starts. I have 3 monitors and even with the multimonitors setting set in the startxwin.bat when I start Xterm it is not reachable unless I right click and have it maximize (which brings it to my main screen). I need to be able to have it not maximized and be able to move it to one of my other screens. If I disconnect my 2 extra monitors and only have 1 monitor it does work. Any and all help is greatly appreciated. Thanks, ~Jet -- 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: cygwin-x-doc refresh
Christopher Faylor wrote: If you update the documentation in the htdocs/xfree/docs/cg directory they should show up on the web site automatically. In fact, everything under htdocs should work like that. cygwin-xfree/htdocs doesn't exist. The web-pages appear to be in cygwin/htdocs/xfree/, but I can't write to that. Perhaps this is a simple as adding a symlink? -- 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: Multiple Monitors issue with Xterm
Jet Wilda wrote: Hi, I just installed cygwin with X on WindowsXP and after making the change to have it starup in C:\cygwin\bin the Xserver starts. I have 3 monitors and even with the multimonitors setting set in the startxwin.bat when I start Xterm it is not reachable unless I right click and have it maximize (which brings it to my main screen). I need to be able to have it not maximized and be able to move it to one of my other screens. If I disconnect my 2 extra monitors and only have 1 monitor it does work. Any and all help is greatly appreciated. Did you check the meail archives? http://cygwin.com/ml/cygwin-xfree/2008-11/msg00145.html -- 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: Alias problem with bash -l (was Re: New X server)
On Thu, Nov 20, 2008 at 12:37:51PM -0600, Ryan Stewart wrote: Jon TURNEY wrote: [...] It sounds like you have somehow lost -multiwindow from the command used to start the X server (so the server is operating in the default, windowed mode). [...] Run xterm +tb, or add XTerm*toolBar: false to ~/.Xdefaults Awesome! Those were exactly what I was looking for, and I also learned a few other things along the way. Thanks so much. I'm having one other problem now, though, which might be a bug. When bash is started with the -l (that's an 'L') flag, aliases that I've defined in .bashrc don't take effect. My .bash_profile includes a call to .bashrc, and I know that .bashrc is being executed because I've put an echo at the beginning and end of it, and both messages are printed out. Even if I execute .bashrc manually, it will print out the messages, but I get no aliases. I can, however, manually enter aliases, and they work. I doubt that the base maintainer would be scanning the cygwin-xfree mailing list looking for problem reports. Please use the cygwin list for non-x-related problems. cgf -- 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: Multiple Monitors issue with Xterm
I did do some googling but must not of had the right keywords (thanks for the link :-). In either case I read that thread and there is only work arounds no solutions. Correct me if I'm wrong but the work arounds are, I can either move my main monitor to the top and left or I can user the arrow keys to move it into a visible location. Is there any known solutions to this issue? Thanks, ~Jet On Thu, Nov 20, 2008 at 1:50 PM, Larry Hall (Cygwin X) [EMAIL PROTECTED] wrote: Jet Wilda wrote: Hi, I just installed cygwin with X on WindowsXP and after making the change to have it starup in C:\cygwin\bin the Xserver starts. I have 3 monitors and even with the multimonitors setting set in the startxwin.bat when I start Xterm it is not reachable unless I right click and have it maximize (which brings it to my main screen). I need to be able to have it not maximized and be able to move it to one of my other screens. If I disconnect my 2 extra monitors and only have 1 monitor it does work. Any and all help is greatly appreciated. Did you check the meail archives? http://cygwin.com/ml/cygwin-xfree/2008-11/msg00145.html -- 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: cygwin-x-doc refresh
On Thu, Nov 20, 2008 at 06:54:42PM +, Jon TURNEY wrote: Christopher Faylor wrote: If you update the documentation in the htdocs/xfree/docs/cg directory they should show up on the web site automatically. In fact, everything under htdocs should work like that. cygwin-xfree/htdocs doesn't exist. The web-pages appear to be in cygwin/htdocs/xfree/, but I can't write to that. Perhaps this is a simple as adding a symlink? Sorry. You are right. This is a different repository. It's under the cygwin htdocs directory. You and Yaakov do have the rights to update that. Something like this (untested) should work: cvs -d :ext:/cvs/cygwin co htdocs/xfree cgf -- 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: Multiple Monitors issue with Xterm
Jet Wilda wrote: I did do some googling but must not of had the right keywords (thanks for the link :-). In either case I read that thread and there is only work arounds no solutions. Correct me if I'm wrong but the work arounds are, I can either move my main monitor to the top and left or I can user the arrow keys to move it into a visible location. Is there any known solutions to this issue? Jon is working on it. -- 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: Multiple Monitors issue with Xterm
That is great to hear. Thanks again for the link and the work arounds. I look forward to Jon's fix :-) Thanks, ~Jet On Thu, Nov 20, 2008 at 2:28 PM, Larry Hall (Cygwin X) [EMAIL PROTECTED] wrote: Jet Wilda wrote: I did do some googling but must not of had the right keywords (thanks for the link :-). In either case I read that thread and there is only work arounds no solutions. Correct me if I'm wrong but the work arounds are, I can either move my main monitor to the top and left or I can user the arrow keys to move it into a visible location. Is there any known solutions to this issue? Jon is working on it. -- 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 requires tty for console log output
Yaakov (Cygwin Ports) wrote: Jon, For some reason which I have yet to investigate, XWin requires a tty to the log to the terminal. That means it will output to terminal in VTs, but will not work in ordinary cmd/bash shells without setting CYGWIN=tty; instead you will see a cmd window briefly flashing on screen when launched. Have you seen anything that would be causing this? No idea. However, this does explain some confusing reports of no output from XWin; I discover I do have CYGWIN=tty in my environment :-) -- 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: cygwin-x-doc refresh
Christopher Faylor wrote: On Thu, Nov 20, 2008 at 06:54:42PM +, Jon TURNEY wrote: Christopher Faylor wrote: If you update the documentation in the htdocs/xfree/docs/cg directory they should show up on the web site automatically. In fact, everything under htdocs should work like that. cygwin-xfree/htdocs doesn't exist. The web-pages appear to be in cygwin/htdocs/xfree/, but I can't write to that. Perhaps this is a simple as adding a symlink? Sorry. You are right. This is a different repository. It's under the cygwin htdocs directory. You and Yaakov do have the rights to update that. Something like this (untested) should work: cvs -d :ext:/cvs/cygwin co htdocs/xfree Thanks. Updated. -- 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: Documentation
Jonathan Johansen wrote: Hi All, I've tried installing the Cygwin X11 server to try to be able to run an X app, but the cygwin installation packages were completely different to the ones mentioned on the website and in the documentation. I had to search the mailing list to get the required package names. So, can I suggest that the website and/or documentation are updated to reflect the package name changes? I'm sure it would save a lot of pain for people in the future. I've just updated the documentation under http://x.cygwin.com/docs/ If you have suggestions on how to improve it, patches are more than welcome :-) -- 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/
[ANNOUNCEMENT] Updated: libXaw-1.0.5-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net distribution: *** libXaw6-1.0.5-1 *** libXaw7-1.0.5-1 *** libXaw-devel-1.0.5-1 This is the latest upstream release. Even though all references to the xaw.m4 macro has been removed upstream in git, a simplified version is included in this package for building the current X.Org Xaw-dependent tarballs. Yaakov Cygwin/X DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the cygwin-xfree mailing list is the appropriate place. CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO: === To unsubscribe to the cygwin-xfree-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkmHVwACgkQpiWmPGlmQSMLQwCfW1j7ZoJ5TLNlUbmMMx6jSp5b ZAQAn0I+NUh2yGFyNLhC31JPMrGYUeZp =bgpR -END PGP SIGNATURE- -- 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/
[ANNOUNCEMENT] Updated: xtrans-1.2.2-3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net distribution: *** xtrans-1.2.2-3 I added a patch to avoid the bogus error euid != 0, directory /tmp/.X11-unix will not be created from the X servers, once they are rebuilt. Yaakov Cygwin/X DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the cygwin-xfree mailing list is the appropriate place. CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO: === To unsubscribe to the cygwin-xfree-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkmHb4ACgkQpiWmPGlmQSM30QCgwR4fR+WEKSeqbDSgX2mcC9qV NUkAn0LZJn/pfzMKj34501UYoJMTZEWi =u5Ls -END PGP SIGNATURE- -- 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/
[ANNOUNCEMENT] Updated: xorg-server-1.5.3-3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net distribution: *** xorg-server-1.5.3-3 These are the changes in this release: * Log changes: - - In addition to the XWin logs now being found in /var/log (as of the last release), now a separate log is created for each display. THE DEFAULT LOG LOCATION IS NOW /var/log/XWin.0.log, when run as X :1 the log will be /var/log/XWin.1.log, etc. - - The -logfile flag argument may contain %s (w/o quotations) to have the display number automatically substituted; e.g. XWin :2 -logfile ~/tmp/XWin.%s.log will create ~/tmp/XWin.2.log. - - The verbosity of the logfile and the console output should now match. * The messages about /tmp/.X11-unix creation and ownership are silenced. * Multiwindow mode fix: - - Windows which remember their placement don't drift with each instance. * Multihead fixes: - - Windows don't appear offscreen when the primary monitor is not upper-left. - - XWin dialogs are placed near the tray icon so that they don't end up in the middle of the virtual desktop, possibly split between two monitors. * Numerous clipboard fixes, including a fix for clipboard startup with XDMCP. * Built-in fonts are used in addition to server-side fonts. The default font has changed as a result, but the full selection of fonts is still available if installed. * Temporary disabled the NumLock/CapsLock synchronization due to several bug reports. Yaakov Cygwin/X DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the cygwin-xfree mailing list is the appropriate place. CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO: === To unsubscribe to the cygwin-xfree-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkmI3UACgkQpiWmPGlmQSOb+wCg6wy1jbPiTEyyTRwnweZZz0lK HwAAn0WlK/jOIKaWAlZTVgPMxGzeGk32 =jSRU -END PGP SIGNATURE- -- 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/
multiwindow support for _NET_WM_STATE_SKIP_TASKBAR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
Following up on our discussion about multiwindow not honouring
_NET_WM_STATE_SKIP_TASKBAR. The attached patch was what I had in mind
but it has no effect. I'm posting this now to at least start the
discussion.
You may wish to refer to the FD.o EWMH specs:
http://standards.freedesktop.org/wm-spec/wm-spec-1.4.html
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkkmKYsACgkQpiWmPGlmQSNVZQCg5FHvuDl4cn6scVlndMp++0DV
BHsAnikRuQrb0VrBwX4vjxJy7e5+pL55
=wazS
-END PGP SIGNATURE-
Process _NET_WM_STATE_SKIP_TASKBAR in multiwindow.
FIXME: This does NOT work yet.
--- origsrc/xorg-server-1.5.3/hw/xwin/winmultiwindowwm.c 2008-11-18 00:15:45.825463100 -0600
+++ src/xorg-server-1.5.3/hw/xwin/winmultiwindowwm.c 2008-11-18 13:19:41.949202900 -0600
@@ -1470,6 +1470,8 @@
#define HINT_BORDER (1L1)
#define HINT_SIZEBOX (1l2)
#define HINT_CAPTION (1l3)
+/* Windows extended window styles */
+#define HINT_SKIPTASKBAR (1L0)
/* These two are used on their own */
#define HINT_MAX (1L0)
#define HINT_MIN (1L1)
@@ -1480,7 +1482,7 @@
static Atom windowState, motif_wm_hints, windowType;
Atom type, *pAtom = NULL;
int format;
- unsigned long hint = 0, maxmin = 0, rcStyle, nitems = 0 , left = 0;
+ unsigned long hint = 0, exHint = 0, maxmin = 0, rcStyle, nitems = 0 , left = 0;
WindowPtr pWin = GetProp (hWnd, WIN_WINDOW_PROP);
if (!hWnd) return;
@@ -1491,16 +1493,18 @@
if (windowType == None) windowType = XInternAtom(pDisplay, _NET_WM_WINDOW_TYPE, False);
if (XGetWindowProperty(pDisplay, iWindow, windowState, 0L,
- 1L, False, XA_ATOM, type, format,
+ 2L, False, XA_ATOM, type, format,
nitems, left, (unsigned char **)pAtom) == Success)
{
-if (pAtom nitems == 1)
+if (pAtom nitems 0)
{
- static Atom hiddenState, fullscreenState, belowState, aboveState;
+ static Atom skiptaskbarState, hiddenState, fullscreenState, belowState, aboveState;
+ if (skiptaskbarState == None) skiptaskbarState = XInternAtom(pDisplay, _NET_WM_STATE_SKIP_TASKBAR, False);
if (hiddenState == None) hiddenState = XInternAtom(pDisplay, _NET_WM_STATE_HIDDEN, False);
if (fullscreenState == None) fullscreenState = XInternAtom(pDisplay, _NET_WM_STATE_FULLSCREEN, False);
if (belowState == None) belowState = XInternAtom(pDisplay, _NET_WM_STATE_BELOW, False);
if (aboveState == None) aboveState = XInternAtom(pDisplay, _NET_WM_STATE_ABOVE, False);
+ if (*pAtom == skiptaskbarState) exHint |= HINT_SKIPTASKBAR;
if (*pAtom == hiddenState) maxmin |= HINT_MIN;
else if (*pAtom == fullscreenState) maxmin |= HINT_MAX;
if (*pAtom == belowState) *zstyle = HWND_BOTTOM;
@@ -1573,6 +1577,9 @@
((hint HINT_SIZEBOX) ? (GetParent(hWnd) ? 0 : WS_SIZEBOX) : 0) |
((hint HINT_CAPTION) ? WS_CAPTION : 0));
+ if (exHint HINT_SKIPTASKBAR)
+SetWindowLongPtr (hWnd, GWL_EXSTYLE, GetWindowLongPtr(hWnd, GWL_EXSTYLE) ~WS_EX_APPWINDOW);
+
return;
}
--
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: libXaw3d7 Package Uninstall Hangs
Thanks, that got me headed down the right path. The libXaw3d7.lst.gz file was corrupted so I replaced it using the local tarball via these instructions (which I'm including since it was on a different thread). http://cygwin.com/ml/cygwin/2008-01/msg00419.html On Thu, 20 Nov 2008, Yaakov (Cygwin Ports) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 hughgs wrote: Any ideas on the problem? I was hoping to find the actual commands that setup.exe uses during updates to narrow down the actual command that fails but I wasn't able to find anything on the web. Sounds like something similar to this: http://www.cygwin.com/ml/cygwin/2008-01/msg00340.html http://www.cygwin.com/ml/cygwin/2008-01/msg00354.html Does that help? Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkmOpAACgkQpiWmPGlmQSNFQACgvIVvIc3BBVSaDwNxGJv/PEzA uHMAoNhgYyrVB+cR6bmN+jyMZtM/Jf0Z =2AM1 -END PGP SIGNATURE- -- 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/ George S. Hugh 261 Hudson Annex (302) 530-9335 [EMAIL PROTECTED] -- 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/
