March 2008 - xmonad - Haskell.org

Re: SwapMaster (DwmPromote) and Stack reordering (was: Re: [xmonad] Newbie: Problems with Layouts and Syntax)
by John Spencer 17 Mar '08

17 Mar '08

Hi! > > Well - one thing I'd like to change: Instead of swapping I'd like to put > > the current master on top of the stack; > I had wanted this for a while too; you got me to do > something about it. :-)) Thanks alot - still didn't find time to learn some haskell :-( > promote :: X () Just did a fast check - but it seems to do what I meant - THANKS alot! > I would send a darcs patch, but I don’t know where it should > go. A new module seems overkill, the name DwmPromote doesn’t > apply to it, and renaming DwmPromote.hs to Promote.hs would > break peoples’ setups. Hm. I put this in my local config - by I think this is something that should be in XMonadContrib. I don't know about the xmonad development policy about backwards compatibility, but it sounds more 'clean' to me just to rename DwmPromote to Promote and add a new 'cyclePromote' or 'pushPromote' (wheee, finding a good name is sometimes not easy :-((). What is the 'normal' process in such a case? Make it clean and break configs? Or better add another module? - john

3 3

darcs patch: EwmhDesktops: advertise support for _NET_CLIENT_LIST_S...
by Alec Berryman 16 Mar '08

16 Mar '08

I was playing around with getting xpra working today. It dies with an assertion error "this program requires an EWMH-compliant window manager" because it checks that the window manager supports _NET_CLIENT_LIST_STACKING. EwmhDesktops does but doesn't advertise so. Sat Mar 15 17:26:31 EDT 2008 Alec Berryman <alec(a)thened.net> * EwmhDesktops: advertise support for _NET_CLIENT_LIST_STACKING

2 1

An xmonad review
by Don Stewart 16 Mar '08

16 Mar '08

'gnuvince' has done a nice review of xmonad, here, http://gnuvince.wordpress.com/2008/03/10/trying-xmonad/ Good to see the user experience of starting xmonad is as we'd hope. -- Don

2 1

xmonad talk at FringeDC
by Don Stewart 16 Mar '08

16 Mar '08

byorgey will be giving a talk about xmonad at FringeDC (Washington DC/USA) on March 23rd. If you're in the area, might be nice to hear. Details here: http://byorgey.wordpress.com/2008/03/15/fringedc-formal-meeting-march-22/ And good work Brent! Cheers, Don

1 0

Issue 155 in xmonad: Don't display borders around fullscreen MPlayer
by codesite-noreply＠google.com 16 Mar '08

16 Mar '08

Issue 155: Don't display borders around fullscreen MPlayer http://code.google.com/p/xmonad/issues/detail?id=155 Comment #2 by netprobe: Is there a way to include this solution more automatically in the config? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 156 in xmonad: Opera: multiple windows closed together
by codesite-noreply＠google.com 16 Mar '08

16 Mar '08

Issue 156: Opera: multiple windows closed together http://code.google.com/p/xmonad/issues/detail?id=156 New issue report by netprobe: What steps will reproduce the problem? 1. Start the opera browser (mod-p opera) 2. Click File -> New Window in opera (or Ctrl+N) 3. Close the new window by File -> Exit in it What is the expected output? What do you see instead? I expect only the new window to quit, instead both windows are being closed. Killing the windows with mod-shift-c works correctly as expected. What version of the product are you using? On what operating system? Latest XMonad from darcs repository without contribution extensions. Please provide any additional information below. I don't know if it's a Opera bug as using other Windows managers I would use the X on the title bar. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 155 in xmonad: Don't display borders around fullscreen MPlayer
by codesite-noreply＠google.com 15 Mar '08

15 Mar '08

Issue 155: Don't display borders around fullscreen MPlayer http://code.google.com/p/xmonad/issues/detail?id=155 Comment #1 by valery.vv: Switch to fullscreen layout mode and press `mod-t' to flatten mplayer window. You may wish to toggle status bar (`mod-b' by default). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Newbie: Problems with Layouts and Syntax
by john spencer 15 Mar '08

15 Mar '08

Hi! After having some contact with xmonad 0.4 (and dismissing it for some reasons) I thought it's time to have a look at it again. And ... wow! :-)) Maybe it's now time to change - if I can get some things right. I'm currently a user of larswm; I configured it to have one large main (master) area and all the other windows of the current workspace stacked on the right site. With that configuration I am very fast selecting the window I want and making it the 'master'. I never work in one of the windows on the right site (you could also work in fullscreen mode -I hear you say- but for me its much more convenient to know in ONE look how many times I have to hit the 'next window' key than checking it every time I switch fullscreen); this means that these windows are never resized (just once when they are created at the main area). Long speech - short sense: I need a fast possibility to select the window I am interested in. As I can see, I have several possibilities with xmonad: 1. I could use the Hinted Tile Layout. As far as I understood, this layout shouldn't resize the windows when they are put out of the master. This would be the same configuration as I use currently with larswm. The problem is, it doesn't work always. Some apps (ie. aterm, konsole) seem to get resized which results in a nearly blank window when getting them back to the master. I don't know why the behaviour in larswm is different here - any ideas? 2. I could use the Tabbed Layout. Unfortunately the tabs currently are not giving me a really fast glue what is behind them. I have to read the title of the tabs - thats not very fast. I can image that some color-coding (ie. using regexps in the config) could improve this significantly. Also -since working on the terminal means looking at the bottom of the screen most of the time- putting the tabs at the bottom instead of the top would also be a great enhancement. What do you think? Are there any other options you can think of? Unfortunately I don't have any progamming skills w/ haskell. Which brings me to another problem: I'd like to map a key to execute two actions: I want to execute "windows W.focusDown" followed by a "windows W.swapMaster"; I have no idea how to specify this: ((modMask .|. shiftMask, xK_Return), ... ??? ... -- windows W.focusDown && windows W.swapMaster Could somebody help me with this? Thanks! - john -- chris

6 14

runLayout changes!
by Brent Yorgey 15 Mar '08

15 Mar '08

Hi all, Sorry to keep you waiting, but while getting these changes together I somehow managed to completely hose my xmonad twice! The first time I'll write about later, but suffice it to say that it had nothing to do with the runLayout changes. The second time... I'm still not sure what was going on, but after rebuilding everything from scratch it... seems to be OK now. Of course, it's always scary when something magically gets fixed without knowing why, but hopefully things should be OK. Of course, if you experience any problems, reports/patches/etc. welcome, and so on! Don, if you can apply all these patches, that would be great. I could apply the contrib patches myself, but of course the core patches and contrib patches need to be applied all at the same time or else things will break. A quick summary of what's going on here: the LayoutClass is getting a new method, called runLayout. By default, runLayout just calls doLayout or emptyLayout as appropriate. If you're writing a simple LayoutClass instance, you don't need to worry about it; you can choose to implement doLayout, or pureLayout, or whatever, just as before. However, if you are writing code which *makes use of* a LayoutClass instance, you should *only* call runLayout, handleMessage, and description: client code should no longer call doLayout directly. If you do, anything which uses a non-default runLayout (like PerWorkspace) will break when used in conjunction with your code. For more information, see all the modules that were updated for examples, and see the Haddock documentation for Core.hs: I added a bunch of documentation which should hopefully make everything clear. And yes, of course, this means that PerWorkspace now works with xinerama setups! Happy xmonading! -Brent -------------------------------- Tue Mar 11 12:07:27 EDT 2008 Brent Yorgey <byorgey(a)gmail.com> * update documentation Mon Feb 25 03:32:36 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * Reimplement Mirror with runLayout Fri Feb 22 14:31:19 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * Reimplement Choose with runLayout Fri Feb 22 12:58:15 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * runLayout is now a LayoutClass method and takes the Workspace and the screen Rectangle ------------------------------- Tue Mar 11 17:29:08 EDT 2008 Brent Yorgey <byorgey(a)gmail.com> * ScratchWorkspace: update to work with runLayout changes Tue Mar 11 14:17:15 EDT 2008 Brent Yorgey <byorgey(a)gmail.com> * Scratchpad: update to work with runLayout changes Tue Mar 11 14:16:25 EDT 2008 Brent Yorgey <byorgey(a)gmail.com> * MagicFocus: update to work with runLayout changes Tue Mar 11 14:15:37 EDT 2008 Brent Yorgey <byorgey(a)gmail.com> * LayoutScreens: update to work with runLayout changes Tue Mar 11 14:14:00 EDT 2008 Brent Yorgey <byorgey(a)gmail.com> * Combo: update to work with runLayout changes Tue Mar 11 13:20:46 EDT 2008 Brent Yorgey <byorgey(a)gmail.com> * MultiToggle: fix to work with runLayout changes to core Sat Feb 23 02:55:31 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * PerWorksapce: use a safer False as default Fri Feb 22 12:59:54 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * PerWorkspace: reimplemented using runLayout This way we have a Xinerama safe PerWorkspace and the emptyLayout method for free. Sat Feb 23 03:15:53 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * ToggleLayouts: reimplemented with runLayout Sat Feb 23 03:09:58 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * LayoutCombinators: NewSelect reimplemented with runLayout Sat Feb 23 02:56:10 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * LayoutModifier: reimplement ModifiedLayout using runLayout and more - change modifyLayout type to get the Workspace - updated ResizeScreen and ManageDocks accordingly. Fri Feb 22 12:59:24 EST 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * Combo: updated to latest runLayout changes

3 4

Issue 155 in xmonad: Don't display borders around fullscreen MPlayer
by codesite-noreply＠google.com 15 Mar '08

15 Mar '08

Issue 155: Don't display borders around fullscreen MPlayer http://code.google.com/p/xmonad/issues/detail?id=155 New issue report by janeczek: What steps will reproduce the problem? 1. Start MPlayer 2. Press 'f' to switch to full screen What is the desired output? What do you see instead? Border is visible on the left and top sides of MPlayer window. I'd rather not see it. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0