- xmonad - Haskell.org

darcs patch: refactor layout interface. (and 1 more)
by David Roundy 20 Apr '07

20 Apr '07

Hi all, Here's another shot at an interface that will allow prettier passing of messages to the layout, so we can send interesting types. This patch adds one warning in Main, since I removed the type of handle, so it could be inferred from the type of keys. We could hardcode it to give an X LayoutMsg (), but that seems uglier, to me. We could also consider importing Main into Config (and renaming main), in which case handle (and Main) would be functions of keys, and the name "keys" itself wouldn't be hard-coded. It does seem prettier to make Config import all the other modules, rather than having Config itself imported by another module. I'm still not sure that this is a good plan. As long as our layout is a pure function, we won't be able to do things that ion does, such as being able to drag a tab from one location to another to move a window. That's not a big deal, but if possible it'd be nice (if it can be done cleanly) to define an API that doesn't limit the capabilities of the window manager. David Wed Apr 18 08:02:05 PDT 2007 David Roundy <droundy(a)darcs.net> * refactor layout interface. This change only changes functionality in that the tileFraction is now a per-layout variable. The main point is to add the flexibility to define layouts in the Config file. There's a bit of cheesiness in the type of modifyLayout, since I could figure out a pleasant choice for passing the key-binding information to the Layout, so I just used a string. Wed Apr 18 08:57:38 PDT 2007 David Roundy <droundy(a)darcs.net> * allow any type to be passed to the layout function. This is an attempt to allow for more general layouts, that could do things like interact with mouse clicks. The trickiness is that I want to be able to define the type of message that is passed in Config, and as a result, I had to change the kind of X and XMonad.

2 4

mod-shift-c has no effect
by Georg Neis 19 Apr '07

19 Apr '07

Hello, the only program that I'm able to kill by pressing mod-shift-c is xterm. For all other programs I can't notice any effect. Regards, Georg

5 13

darcs patch: refactor layout interface.
by David Roundy 19 Apr '07

19 Apr '07

Hi all, This is just my layout refactoring patch, re-recorded to deal with conflicts with the latest changes in XMonad. I've also written an example layout, which you can get with darcs get http://physics.oregonstate.edu/~roundyd/XMonad It's pretty useless... but shows a bit of how to use this layout scheme. David Thu Apr 19 08:30:07 PDT 2007 David Roundy <droundy(a)darcs.net> * refactor layout interface. This change only changes functionality in that the tileFraction is now a per-layout variable. The main point is to add the flexibility to define layouts in the Config file.

1 0

xmonad 0.1 release candidate
by Spencer Janssen 19 Apr '07

19 Apr '07

In preparation for xmonad's 0.1 release, we've prepared tarballs of X11-extras and xmonad: http://darcs.haskell.org/~sjanssen/xmonad-0.1-rc1.tar.gz http://darcs.haskell.org/~sjanssen/X11-extras-0.1-rc1.tar.gz Please try these out and report any problems on the mailing list. If all goes smoothly, we'll release these as xmonad and X11-extras 0.1 this weekend. Cheers, Spencer Janssen

1 0

mod events not reaching xmonad
by Bas van Dijk 18 Apr '07

18 Apr '07

Hello, I have a problem. Often, after a while of using OpenOffice with xmonad mod key events no longer get to xmonad. When this happens I'm forced to switch to a console and killall xmonad loosing all non-saved work in the process. I've also seen this using other applications like Firefox for example. What can be causing this and do other people have the same problems? regards, Bas van Dijk P.S. I run the latest xmonad

3 4

darcs patch: refactor layout interface.
by David Roundy 17 Apr '07

17 Apr '07

Hi all, Here's an attempt at an interface that allows the definition of custom workspace layouts in Config. I'm not really pleased with it, so you can view it as a discussion piece more than an actual proposal. In particular, it punts on the idea of any sort of mouse interaction with a layout, which almost makes a tabbed layout useless. Still, I think it's an interesting approach to allowing layouts that contain arbitrary sorts of state. David Mon Apr 16 20:48:13 PDT 2007 David Roundy <droundy(a)darcs.net> * refactor layout interface. This change only changes functionality in that the tileFraction is now a per-layout variable. The main point is to add the flexibility to define layouts in the Config file. There's a bit of cheesiness in the type of modifyLayout, since I could figure out a pleasant choice for passing the key-binding information to the Layout, so I just used a string.

1 0

darcs patch: fix typo. (and 1 more)
by David Roundy 16 Apr '07

16 Apr '07

Hi all, Here's a feature I've added (on my quest to make xmonad non-minimal...) to my version of xmonad. It's pretty crude, but I think some sort of "rotating" is in order. This way if I have only three workspaces with anything in them, I don't have to remember their numbers, and don't have to search through all nine options. David Sat Apr 14 22:56:16 PDT 2007 David Roundy <droundy(a)darcs.net> * fix typo. Sat Apr 14 23:30:34 PDT 2007 David Roundy <droundy(a)darcs.net> * add code to rotate through non-empty workspaces. I don't expect that this will actually be accepted, as my code's pretty ugly, but it's a feature I want, and might inspire some ideas.

5 11

another idea for configurable layouts.
by David Roundy 16 Apr '07

16 Apr '07

Hi all, I've had another idea for how we might implement configurable layouts, which would have the advantage (or disadvantage?) of removing the tileFraction from the StackSet, and moving it into the layout itself. I don't have time just yet to hack this up, but thought I'd run the idea by you. The idea is to have a type Layout which holds whatever information is needed to determine how to lay out the windows: data NewLayout = L { doLayout :: Rectangle -> [Window] -> [(Window, Rectangle)] , modifyLayout :: Event -> Maybe NewLayout } The doLayout does the actual laying out (e.g. calls tile or vtile). The second function, modifyLayout would be in charge of updating whatever state there might be (e.g. changing the tileFraction. A very sketchy example would be this sketch of the Tall layout: tall :: Rational -> NewLayout tall tileFraction = L { doLayout = tile tileFraction , modifyLayout _ = Just $ tall (tileFraction*1.5) } Obviously modifyLayout is just wrong, but I don't have all that much time. The point is that it'd be able to update the tileFraction, and by using closures like this, we wouldn't have to hard-code what extra data (e.g. tileFraction) needs to be stored with each workspace. The catch is that I've changed the semantics, as each layout will now have its own tileFraction. I don't think that's a Bad Thing, but you may disagree. The other controversial (or at least it's controversial to my mind) aspect of this is the use of Event in modifyLayout. It's pretty ugly (particularly with regard to key bindings), but I can't see how else to allow a tabbed layout to respond to mouse clicks. I imagine we'd need some sort of translation layer to make keybindings pretty... but I can't solve all the worlds problems overnight. Anyhow, this is the closest I've come to imagining a StackSet data format that will allow for the implementation of clever new layout algorithms, which might need some extra data, and will certainly need to respond to extra events. I should also mention that I imagine mod-space working by storing a list of layouts for each workspace, and rotating between them. Obviously, when you change layout, you'd like to keep the old one so you can go back to it (e.g. so you can switch to fullscreen and back without losing your tileFraction). -- David Roundy http://www.darcs.net

1 1

gmrun and pasting (was Re: [Xmonad] darcs patch: fix typo. (and 1 more))
by Alec Berryman 16 Apr '07

16 Apr '07

Gwern Branwen on 2007-04-15 23:20:24 -0400: > Alec Berryman <alec(a)thened.net> writes: > > > Donald Bruce Stewart on 2007-04-16 09:13:31 +1000: > > > >> droundy: > >> > > >> > After that, I'd be interested in a decent input prompt (which dmenu is > >> > not). Ion's is better, but I'd rather figure out how to make use of an > >> > actual bash shell, as the tab completion of ion's query box is annoying > >> > (but better than nothing). > >> > >> Does anyone know of a 3rd party tool for this? Like dmenu , but for more > >> complex input? > > > > gmrun includes tab-completion, handles URLs, and can open specified > > programs in a shell. > > Does gmrun also handle pasting, either through a mouse or a keybinding > (preferably the latter)? Yes to both, but due to either a bug in gmrun or xmonad, it isn't particularly convenient. If I copy something to the X11 clipboard by selecting it with the mouse, then run gmrun via the default keybinding, I can't paste either with a middle click or with shift-insert. If I switch to another window, I can still paste what I had previously copied, and if I now copy something to the clipboard and switch back to the still-running gmrun I can paste fine.

1 0

The kill client / mod-shift-c issue
by dons＠cse.unsw.edu.au 16 Apr '07

16 Apr '07

Ok. After investing some more, and still not obviously seeing what's wrong, I find that: * sometimes, after running xmonad for a long time, I can't kill xclock (for example), or any other app that uses the wmdelete protocol (requiring us to send delete notification). * quitting out completely, and logging back in, with a new build, and everything works. * restarting, and it still works. Also, the case when we need to send this event is still spotted correctly,so the bug is in the X11-extras code I suspect. I'll look into this some more if I can work out how to reproduce it. David, can you pull all the latest patches, rebuild and install xmonad. Quit X, log back in, then check if you can kill xclock? -- Don

1 0