From gulliver.m.smith@gmail.com Wed Oct 7 15:20:00 2015 From: gulliver.m.smith@gmail.com (Gulliver Smith) Date: Wed, 07 Oct 2015 15:20:00 -0000 Subject: Window manager commands in native window manager multiwindow mode Message-ID: I ask this question from time to time just in case someone new sees it and decides to work on it or others might agree that it is a priority. Other people have raised this over the last few years as well. The issue is that I would like to raise windows from within a program (Emacs to be precise), but it doesn't work with the native window manager running in multiwindow mode. Emacs has several nice commands for which I have not-so-nice work arounds (opening and closing windows). These are: (raise-frame f) (iconify-frame f) (decionify-frame f) (make-frame-visible f) None of these work with Cygwin X. Thanks Gulliver -- 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/ From kbrown@cornell.edu Wed Oct 7 15:48:00 2015 From: kbrown@cornell.edu (Ken Brown) Date: Wed, 07 Oct 2015 15:48:00 -0000 Subject: Window manager commands in native window manager multiwindow mode In-Reply-To: References: Message-ID: <56153EE7.3020602@cornell.edu> On 10/7/2015 11:20 AM, Gulliver Smith wrote: > I ask this question from time to time just in case someone new sees it > and decides to work on it or others might agree that it is a priority. > Other people have raised this over the last few years as well. > > The issue is that I would like to raise windows from within a program > (Emacs to be precise), but it doesn't work with the native window > manager running in multiwindow mode. > > Emacs has several nice commands for which I have not-so-nice work > arounds (opening and closing windows). These are: > > (raise-frame f) > (iconify-frame f) > (decionify-frame f) > (make-frame-visible f) > > None of these work with Cygwin X. Please give a detailed recipe for reproducing the problem. I just tried the following: 1. Start the X server by running startxwin in a Cygwin Terminal (mintty). 2. Use the xdg menu icon to start xterm. 3. In xterm, run 'emacs&'. 4. In emacs, run 'M-x iconify-frame'. The current frame did indeed get iconified, as expected. I'm not sure how to test the other commands. Ken P.S. The cygwin-xfree mailing list is obsolete. You should use the main cygwin mailing list in the future to make sure your mail is seen by the maximum number of people. -- 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/ From kbrown@cornell.edu Thu Oct 8 16:42:00 2015 From: kbrown@cornell.edu (Ken Brown) Date: Thu, 08 Oct 2015 16:42:00 -0000 Subject: Window manager commands in native window manager multiwindow mode In-Reply-To: <56153EE7.3020602@cornell.edu> References: <56153EE7.3020602@cornell.edu> Message-ID: <56169D11.6080204@cornell.edu> On 10/7/2015 11:48 AM, Ken Brown wrote: > On 10/7/2015 11:20 AM, Gulliver Smith wrote: >> I ask this question from time to time just in case someone new sees it >> and decides to work on it or others might agree that it is a priority. >> Other people have raised this over the last few years as well. >> >> The issue is that I would like to raise windows from within a program >> (Emacs to be precise), but it doesn't work with the native window >> manager running in multiwindow mode. >> >> Emacs has several nice commands for which I have not-so-nice work >> arounds (opening and closing windows). These are: >> >> (raise-frame f) >> (iconify-frame f) >> (decionify-frame f) >> (make-frame-visible f) >> >> None of these work with Cygwin X. > > Please give a detailed recipe for reproducing the problem. Never mind. I searched the archive and found the details in an earlier post of yours: https://sourceware.org/ml/cygwin-xfree/2011-08/msg00046.html Here's what I found when I tried to reproduce the problem: >> (raise-frame f) I agree that this doesn't work. But there's a post by Oliver Schmidt (https://sourceware.org/ml/cygwin-xfree/2011-08/msg00047.html) purporting to have a fix for this. There is later discussion in which Jon Turney had some questions about the patch, but I didn't read all of it. Jon, was this ever resolved? >> (iconify-frame f) This works. >> (decionify-frame f) There's no such function in GNU emacs (even after correcting the obvious typo). >> (make-frame-visible f) This seems to be working. Maybe you're misunderstanding what "visible" means in this context (or maybe I am). The frame is initially visible, even if other windows are hiding it, as evidenced by the fact that (frame-visible-p f) evaluates to something non-nil ('icon' if the frame is iconified, 't' otherwise). If I now make it invisible by evaluating (make-frame-invisible f), both the frame and its icon disappear. There's no way to bring it to the front by using Alt-Tab. The frame and icon reappear if I now evaluate (make-frame-visible f). In summary, the only problem I see is with raise-frame, and maybe that one is fixable. We'll have to wait to hear from Jon and/or Oliver. Ken -- 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/ From Paul.Domaskis@gmail.com Tue Oct 13 01:16:00 2015 From: Paul.Domaskis@gmail.com (paul) Date: Tue, 13 Oct 2015 01:16:00 -0000 Subject: xpdf responds spasmodically to 2-finger scroll Message-ID: Most touchpads these days have multi-finger gesture. Synaptics seems to reign in the Windows world, and you can now scroll by sliding 2 fingers along the touch pad. In the past, you had to define a scroll margin for 1-finger scrolling. I'm finding that cygwin's xpdf responds in an unusably spasmodic way to 2-finger scrolling. Once in a blue moon, after using another app like Firefox, xpdf will respond smoothly as other apps do. but the moment you change anything, e.g. enabling continuous scroll, the usable behaviour disappears and you get the spasmodic behaviour (even if you reverse what you did to make the good behaviour go away). Has anyone else found this to be the case? Has anyone discovered the secret combination of actions that bring about the good scrolling behaviour? Has anyone discovered the secret for making the smooth scrolling stick? -- 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/ From Paul.Domaskis@gmail.com Fri Oct 16 05:43:00 2015 From: Paul.Domaskis@gmail.com (paul) Date: Fri, 16 Oct 2015 05:43:00 -0000 Subject: Xserver corresponds to display :1.0 instead of :0.0 Message-ID: I have a very simple ~/.startxwinrc: xrdb -load $HOME/.Xresources xterm -display :0.0 # xterm & exec sleep infinity Recently, I found that the xterm wasn't launching. I googled, read some cygwin threads about X authorities, but have to admit, I have a lot to learn about X windows. Anyway, since I could open an xterm by right clicking on the Cygwin/Xserver:1.0 app in the notification area of Windows 7, I sneakily (OK, it wasn't the craftiest thing in the world) echo'd $DISPLAY. Lo, it was 1.0, and the following works fine: xterm -display :1.0 & Yes, I know it says 1.0 in the tip for the Cygwin/Xserver:1.0 app, but I didn't actually look at that detail until now, as I'm posting. A google for the following doesn't turn up anything: cygwin xterm "-display :0.0" "display :1.0" I'm wondering if this was a planned change in how X-windows works or if something is awry with my setup, causing a server with display :0.0 to fail, and making go to :1.0. I did a browse of the cygin announce list on gmane (since the X-windows announce list is now obsolete), but no joy. And I would have expected anything to show up in my google search. Can anyone point me to the description of this change? If it is not a deliberate change, what would be a good approach to troubleshoot it? I have a file ~/.xsession-errors, but it is dated 2015-09-16, and I've used X-windows plenty since then. -- 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/ From markus.hoenicka@mhoenicka.de Fri Oct 16 07:10:00 2015 From: markus.hoenicka@mhoenicka.de (Markus Hoenicka) Date: Fri, 16 Oct 2015 07:10:00 -0000 Subject: Xserver corresponds to display :1.0 instead of :0.0 In-Reply-To: References: Message-ID: <9435151592e14c53459746fe0f3b9480@mhoenicka.de> At 2015-10-16 07:41, paul was heard to say: > I have a very simple ~/.startxwinrc: > > xrdb -load $HOME/.Xresources > xterm -display :0.0 # xterm & > exec sleep infinity > > Recently, I found that the xterm wasn't launching. I googled, read > some cygwin threads about X authorities, but have to admit, I have a > lot to learn about X windows. Anyway, since I could open an xterm by > right clicking on the Cygwin/Xserver:1.0 app in the notification area > of Windows 7, I sneakily (OK, it wasn't the craftiest thing in the > world) echo'd $DISPLAY. Lo, it was 1.0, and the following works fine: > > xterm -display :1.0 & > > Yes, I know it says 1.0 in the tip for the Cygwin/Xserver:1.0 app, but > I didn't actually look at that detail until now, as I'm posting. > > A google for the following doesn't turn up anything: > > cygwin xterm "-display :0.0" "display :1.0" > > I'm wondering if this was a planned change in how X-windows works or > if something is awry with my setup, causing a server with display :0.0 > to fail, and making go to :1.0. I did a browse of the cygin announce > list on gmane (since the X-windows announce list is now obsolete), but > no joy. And I would have expected anything to show up in my google > search. > > Can anyone point me to the description of this change? If it is not a > deliberate change, what would be a good approach to troubleshoot it? > I have a file ~/.xsession-errors, but it is dated 2015-09-16, and I've > used X-windows plenty since then. > Hi, you may have a leftover lock file from a crashed X session. Check if there is a /tmp/.X0-lock (IIRC) before you start your X server. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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/ From Paul.Domaskis@gmail.com Sat Oct 17 04:40:00 2015 From: Paul.Domaskis@gmail.com (paul) Date: Sat, 17 Oct 2015 04:40:00 -0000 Subject: Xserver corresponds to display :1.0 instead of :0.0 References: <9435151592e14c53459746fe0f3b9480@mhoenicka.de> Message-ID: Markus Hoenicka mhoenicka.de> writes: > you may have a leftover lock file from a crashed X session. Check if > there is a /tmp/.X0-lock (IIRC) before you start your X server. Thank you, Markus. That was *exactly* the problem, and removing the lock file solved it. -- 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/