Re: Updating Fedora's FVWM
| On 24 January 2012 14:54, Dan Espen des...@verizon.net wrote: | I think any platform that supports XDG is going to have python. | | It will; but I think it's best described the other way round -- that | is, any platform that has python installed can use XDG -- and I say | that only because of the availability of the python XDG bindings. | Not that it really matters to me, but it is worth investigating if | these bindings come with python or are external. I'm thinking about | packaging. The bindings are an external package, not part of the core Python distribution (on Fedora they are packaged as 'pyxdg', on Ubuntu 'python-xdg'). On Fedora the package seem to be part of the default installation if you have the Gnome desktop (Totem and IBus both depend on the package). (I don't have any clean stock Ubuntu desktop machines to see if the package is there in their Gnome setup. An Ubuntu server install with basic X packages installed doesn't have them.) - cks
Re: Notification: incoming/941
In testing so far, a CVS version from branch-2_4 pulled on Tuesday night or so seems to be working fine. (Sorry for the delay in reply, but I wanted to give it some time to make sure.) Certainly the stacking issue I saw is gone and I haven't observed any other ones. - cks -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/941
An additional two notes: I localized the problem to fvwm 2.4.10's fvwm/stack.c changes; the 2.4.9 stack.c (hacked to change '-pstack' to '-stack.p') doesn't exhibit the problem when compiled into 2.4.10. The problem appears to go away if I force the do_lower parameter to fvwm/stack.c's restack_windows() to be zero. I suspect that this is not the actual answer, but I lack the understanding of fvwm's internals to understand what I just broke. (Everything seems to work fine for me, but I don't use multiple layers.) - cks -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/941
I did some more digging on my problem of Lower not lowering windows below iconified windows. It first appears in fvwm 2.4.10; it is not present in 2.4.9. Reproduction steps with the fvwm2rc at the end of this message: - start your favorite Xnest environment (or a real X server) and fvwm as 'fvwm2 -f fvwm2rc-test'. The fvwm2rc uses button 3 on the root window to pop up a menu of operations and uses manual placement of windows. - pop up the root menu; pick XTerm; place the resulting window somewhere. - pop the root menu up, pick Iconify, button-1 the xterm window to iconify it. - pop the root menu up, pick XTerm, place the resulting xterm window so that it completely obscures the iconified XTerm. - pop the root menu up, pick Bottom, chose the (new) XTerm window. On fvwm 2.4.9 and below the iconified XTerm icon appears on top of the uniconified xterm. On 2.4.10 and later, nothing happens. - on 2.4.10+, then pop the menu up, pick Move, pick the XTerm window. Move the window slowly so as to reveal the iconified XTerm. When a tiny bit of the icon appears, it will suddenly jump into full appearance over the window you are moving (as it should be). [I believe xlogo32 should be universally available; if not, substitute the default icon of your choice.] - cks Minimal .fvwm2rc: # Minimal .fvwm2rc to reproduce my icon bug. DestroyMenu Blit AddToMenu Blit XTerm Exec xterm + Top Raise + BottomLower + Move Move + Iconify Iconify # done Blit. Mouse 1 I N Iconify Mouse 3 R N PopUp Blit OpaqueMoveSize 100 Style * SloppyFocus, ManualPlacement, IconBox None, Icon xlogo32 Style XTerm NoTitle, HandleWidth 5, BorderWidth 5 -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
