For them ubuntu users, if oneiric broke a lot of things you can follow this: http://markhansen.co.nz/xmonad-ubuntu-oneiric/ That should allow you to select an xmonad session as opposed to a unity one during login.
As a general rule you can simply use xmonad as your window manager and just launch gnome-settings-daemon (or was it gnome-config-daemon?) to get all the theming, font antialiasing, etc. If you run nm-applet manually, that should launch the networking stuff (if it didn't already). I haven't tried using xmonad with the ubuntu panel and stuff, so I don't know about that.
It works great with multiple monitors, alt+w and alt+e move focus between monitors, and then I can swap which workspace is in which monitor really easily to move things around.
That runs xmonad with the unity panel; it doesn't add the launcher, but I was never a fan of that to begin with (in part because its interaction with xmonad wasn't great, but I never spent much time trying to get it working properly either so it might be possible). The key difference is the wiki assumes you're installing from cabal, where-as Mark's assume an apt-get installation which already comes with a .desktop file.
Note that the wiki instructions mention the need to explicitly add gaps at the top, which Mark's instructions didn't. (Also, that the wiki config doesn't actually launch the launcher!)
I'm also using XMonad on Arch Linux. I found it hard to setup correctly, but once it is, it's a real productivity booster. Firing up another terminal (Meta-Shift-Enter) and not worrying about it's position is a time saver.
The underlying design invariant was that you should always be able to predict exactly what the screen would look like, before you perform an action. I'm glad that's the result we've achieved.
Is there an official announcement somewhere?
The Xmonad blog seems dead, and the twitter account is not in a better state. It's a pitty because it gives the impression that the project is not actively developed.
There will be shortly. Sorry about the lack of noise online -- I switched jobs and cities, and haven't had time to do some of this kind of stuff. Adam Vogt has taken over as maintainer, and will be following up with an announce.
I'm still sad that ion3 is getting so little love these days.
It's easily the most advanced of the tiling wm crop, and by a long shot. Just some bullets:
- Floating/tiled can co-exist on same workspace (just attach/detach as needed), can also trivially set filters to have e.g. all dialogs and "all gimp-windows" float automatically.
- The tabbed frames metaphor is infinitely superior to the "one window per frame" metaphor that everyone else is stuck with.
- All configuration and extension is lua. It's an absolute joy to work with.
- Mouse works as expected. Just drag frames to resize the grid, drag titlebars to move windows into other frames, etc.
Up to this day I don't understand how people put up with the obscure limitations of the other tiling wm's (foremost: the one window per frame constraint, forced set of layouts that never work quite right, etc. etc.)...
Most of the above list is actually supported by xmonad (and dwm, and awesome and ...). The two things that are really the defining characteristic of ion3 is that it is a user-defined layout (not a "dynamic" layout, a la xmonad), and that the clients are represented as a tree of windows, rather than e.g. a zipper or list of windows (which is how the nesting works).
xmonad and its cohort basically make the proposition that user-defined layouts are inefficient, and you can be more productive with predictable, automated tiling. They directly opposed ion3 in that regard.
Mouse, configuration, floating etc is all fairly standard everywhere.
Every single time I see news about window managers, I'm surprised that i3 (i3wm.org) isn't mentioned. i3 is the supreme tiling window manager. It's mature, fast, feature-ful and it's BSD-licensed. This looks like an advert, but I'm just a pleased user that's been on the i3 train since 2009.
My macbook died recently and I switched back to ubuntu for the week, first thing I did was install xmonad, its a really awesome environment to work within.
I do wish it played nicer with other window environment, some applications just dont work inside a modal interface and when they dont I just want my normal windows with title bar and buttons back
I havent installed it on my mac now its repaired, the fact I dont be able to use my normal mac apps kinda put me off, but I may give it another shot, if there was a way to have xmonad like behaviour with mac applications while preserving floating windows I would be in heaven (divvy etc most certainly do not count)
Its probably worth mentioning that despite following several tutorials, getting xmonad installed on 11.04 was a nightmare that left plain ubuntu pretty broken, I would like to see that process improved as well
I just installed xmonad on 11.10 last week. It was very straightforward---didn't even need a tutorial. It's just "sudo apt-get install xmonad". The hard part was trying to customize xmonad without knowing Haskell.
> just want my normal windows with title bar and
> buttons back
There are contrib packages that allow you to add small title bars to the windows. You could configure XMonad with a 'floating' workspace, and enable title bars on all of the windows in that workspace. Then just setup rules to automatically send all of the programs that have issues to that workspace.
xmonad is uber-wonderful but a good beginner documentation would be really awesome.
I would like to have, on the official site, a list of distro, and for each, a tutorial that have been tested and works. Instead, one needs to hunt for blog post that are either incomplete or not applicable.
The latest Ubuntu upgrade was really a nightmare in this respect. had to mix xfce + xmonad but my setup is far from optimal...
>> xmonad is uber-wonderful but a good beginner documentation would be really awesome.
Why don't you write one? A lot of the xmonad (and other tiling wm) communities are battle scarred veterans who have been using dwm (the ancestor of xmonad, awesome et al) since day one and they don't need no stinking documentation :) And besides, one of the core ideas of dwm and (some of) it's successors is that the source code is the documentation.
So if you're a newb and would belong to the target group of the docs you're requesting, you're the perfect individual to write them.
I'm sure all the old timers on the IRC channel will be glad to help you to get started and will be even more delighted if you finish a doc.
Scrotwm is a small dynamic tiling window manager for X11. It tries to stay out of the way so that valuable screen real estate can be used for much more important stuff. It has sane defaults and does not require one to learn a language to do any configuration. It was written by hackers for hackers and it strives to be small, compact and fast.
It was largely inspired by xmonad and dwm. Both are fine products but suffer from things like: crazy-unportable-language-syndrome, silly defaults, asymmetrical window layout, "how hard can it be?" and good old NIH. Nevertheless dwm was a phenomenal resource and many good ideas and code was borrowed from it. On the other hand xmonad has great defaults, key bindings and xinerama support but is crippled by not being written in C.
I am an Xmonad user that tried Awesome, and the main thing that didn't work for me is that it seemed that Awesome workspaces (tags) were tied to particular monitors. Perhaps I just didn't take the time to figure out how to do it properly, but that was a deal-breaker for me.
In Xmonad, I have configured twenty different workspaces, and I can easily swap them in and out of any given monitor. With a triple-monitor configuration, this is quite handy.
Maybe Awesome is more stable now, but one of the reasons that I (and people I know) gave up on Awesome was how often the configuration interface changed, even once they switched it to Lua, the API would change between point releases.
If I upgrade from XMonad 0.9 => 0.10, I don't have to completely redo my config file, because a good portion of the API has changed.
been using xmonad for a couple of years. config is so minimal that it makes it vey simple to replicate the exact same environment on all my machines (laptops and desktops), with no ties to the underlying linux distribution.
[+] [-] makmanalp|14 years ago|reply
> sudo cabal install xmonad xmonad-contrib
Then you can get dmenu or dzen for a small menu and trayer for a small system tray.
Then use a premade config file from here: http://www.haskell.org/haskellwiki/Xmonad/Config_archive and mess around with it.
To learn the keybindings, print this out or make it your wallpaper: http://xmonad.wordpress.com/2009/01/19/xmonad-cheatsheet/
For them ubuntu users, if oneiric broke a lot of things you can follow this: http://markhansen.co.nz/xmonad-ubuntu-oneiric/ That should allow you to select an xmonad session as opposed to a unity one during login.
As a general rule you can simply use xmonad as your window manager and just launch gnome-settings-daemon (or was it gnome-config-daemon?) to get all the theming, font antialiasing, etc. If you run nm-applet manually, that should launch the networking stuff (if it didn't already). I haven't tried using xmonad with the ubuntu panel and stuff, so I don't know about that.
Edit: I use this one: https://github.com/vicfryzel/xmonad-config
It works great with multiple monitors, alt+w and alt+e move focus between monitors, and then I can swap which workspace is in which monitor really easily to move things around.
[+] [-] mark_h|14 years ago|reply
That runs xmonad with the unity panel; it doesn't add the launcher, but I was never a fan of that to begin with (in part because its interaction with xmonad wasn't great, but I never spent much time trying to get it working properly either so it might be possible). The key difference is the wiki assumes you're installing from cabal, where-as Mark's assume an apt-get installation which already comes with a .desktop file.
Note that the wiki instructions mention the need to explicitly add gaps at the top, which Mark's instructions didn't. (Also, that the wiki config doesn't actually launch the launcher!)
[+] [-] jamii|14 years ago|reply
Use XMonad.Config.Gnome.gnomeConfig as your base config. Log in with gnome as normal and do:
Not the most elegant solution, but it works.[+] [-] gwern|14 years ago|reply
[+] [-] foobarqux|14 years ago|reply
[+] [-] wunki|14 years ago|reply
If you want to try it out, I can help you by reducing the time needed to set it up. My dotfiles are here: https://github.com/wunki/wunki-dotfiles
Best nuggets for your setup can be found in xmonad.hs, xinitrc and Xdefaults files.
[+] [-] dons|14 years ago|reply
[+] [-] raphinou|14 years ago|reply
[+] [-] dons|14 years ago|reply
[+] [-] eschulte|14 years ago|reply
[+] [-] axk|14 years ago|reply
(disclaimer: I'm the current maintainer)
[+] [-] moe|14 years ago|reply
It's easily the most advanced of the tiling wm crop, and by a long shot. Just some bullets:
- Floating/tiled can co-exist on same workspace (just attach/detach as needed), can also trivially set filters to have e.g. all dialogs and "all gimp-windows" float automatically.
- The tabbed frames metaphor is infinitely superior to the "one window per frame" metaphor that everyone else is stuck with.
- All configuration and extension is lua. It's an absolute joy to work with.
- Mouse works as expected. Just drag frames to resize the grid, drag titlebars to move windows into other frames, etc.
Up to this day I don't understand how people put up with the obscure limitations of the other tiling wm's (foremost: the one window per frame constraint, forced set of layouts that never work quite right, etc. etc.)...
[+] [-] dons|14 years ago|reply
xmonad and its cohort basically make the proposition that user-defined layouts are inefficient, and you can be more productive with predictable, automated tiling. They directly opposed ion3 in that regard.
Mouse, configuration, floating etc is all fairly standard everywhere.
[+] [-] pyre|14 years ago|reply
[+] [-] user911302966|14 years ago|reply
[+] [-] MostAwesomeDude|14 years ago|reply
[+] [-] daleharvey|14 years ago|reply
I do wish it played nicer with other window environment, some applications just dont work inside a modal interface and when they dont I just want my normal windows with title bar and buttons back
I havent installed it on my mac now its repaired, the fact I dont be able to use my normal mac apps kinda put me off, but I may give it another shot, if there was a way to have xmonad like behaviour with mac applications while preserving floating windows I would be in heaven (divvy etc most certainly do not count)
Its probably worth mentioning that despite following several tutorials, getting xmonad installed on 11.04 was a nightmare that left plain ubuntu pretty broken, I would like to see that process improved as well
[+] [-] davidcuddeback|14 years ago|reply
[+] [-] pyre|14 years ago|reply
[+] [-] LBarret|14 years ago|reply
I would like to have, on the official site, a list of distro, and for each, a tutorial that have been tested and works. Instead, one needs to hunt for blog post that are either incomplete or not applicable.
The latest Ubuntu upgrade was really a nightmare in this respect. had to mix xfce + xmonad but my setup is far from optimal...
[+] [-] exDM69|14 years ago|reply
Why don't you write one? A lot of the xmonad (and other tiling wm) communities are battle scarred veterans who have been using dwm (the ancestor of xmonad, awesome et al) since day one and they don't need no stinking documentation :) And besides, one of the core ideas of dwm and (some of) it's successors is that the source code is the documentation.
So if you're a newb and would belong to the target group of the docs you're requesting, you're the perfect individual to write them.
I'm sure all the old timers on the IRC channel will be glad to help you to get started and will be even more delighted if you finish a doc.
[+] [-] gwern|14 years ago|reply
[+] [-] jafour1|14 years ago|reply
It was largely inspired by xmonad and dwm. Both are fine products but suffer from things like: crazy-unportable-language-syndrome, silly defaults, asymmetrical window layout, "how hard can it be?" and good old NIH. Nevertheless dwm was a phenomenal resource and many good ideas and code was borrowed from it. On the other hand xmonad has great defaults, key bindings and xinerama support but is crippled by not being written in C.
[+] [-] burgerbrain|14 years ago|reply
[+] [-] daniel_solano|14 years ago|reply
In Xmonad, I have configured twenty different workspaces, and I can easily swap them in and out of any given monitor. With a triple-monitor configuration, this is quite handy.
[+] [-] pyre|14 years ago|reply
If I upgrade from XMonad 0.9 => 0.10, I don't have to completely redo my config file, because a good portion of the API has changed.
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] pilooch|14 years ago|reply
[+] [-] wyclif|14 years ago|reply
[+] [-] dhs|14 years ago|reply
[+] [-] postit|14 years ago|reply
[+] [-] dextorious|14 years ago|reply
[+] [-] dextorious|14 years ago|reply
http://steve-yegge.blogspot.com/2010/12/haskell-researchers-...