- xmonad - Haskell.org

Help with achieving desired layout
by Bryan Huh 13 Jan '13

13 Jan '13

Hi, I'm looking to achieve a certain layout with xmonad, but I'm finding the codebase and language quite daunting. I'm using "Mirror Tall" with dual monitors. The top half of my screens are for master windows, and the bottom half are for slave windows. I find though, that as long as I have more than one slave window in a workspace it makes the bottom half of the screen pretty unusable because it gets split evenly amongst all the slaves, and each slave window becomes unpleasant to view. It'd be nice if there was a main slave so that most or all of the "slave pane" is filled with the main slave window. Then I would have half of the screen filled with the master window, ~half filled with the main slave window, and a small fraction of the screen (maybe accordion style) filled with the remaining slaves. I imagine switching between the master and slave panes with alt-enter and alt-shift-enter, and navigating between slave windows with alt-j alt-k. The DragPane layout is close to achieving my desired layout, but the problem is that whenever the master window is focused, the second window in the stack is shown in the slave pane. This means that if I'm looking at a particular slave window and want to now focus on the master window, the slave window switches back to the second window and I essentially lose my spot in the slave stack. Does this make sense? How hard would this be to implement? Bryan

2 2

Re: Issue 306 in xmonad: Magnifier: keep magnified status if transient focused
by codesite-noreply＠google.com 12 Jan '13

12 Jan '13

Updates: Status: Accepted Labels: Type-Enhancement Component-Contrib Comment #3 on issue 306 by byorgey: Magnifier: keep magnified status if transient focused http://code.google.com/p/xmonad/issues/detail?id=306 This shouldn't be too difficult to implement (either Riccardo or Daniel's proposed behavior) given the new extensible state. -- 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 3

Re: Issue 304 in xmonad: CycleWS should actually track workspace history rather than depending on order of hidden workspaces
by codesite-noreply＠google.com 09 Jan '13

09 Jan '13

Updates: Summary: CycleWS should actually track workspace history rather than depending on order of hidden workspaces Status: Accepted Labels: Type-Enhancement Component-Contrib Comment #2 on issue 304 by byorgey: CycleWS should actually track workspace history rather than depending on order of hidden workspaces http://code.google.com/p/xmonad/issues/detail?id=304 The problem is that toggleWS simply assumes that the "previous workspace" is the one at the head of xmonad's internal list of hidden workspaces. But there are various operations other than switching away from a workspace which will also place it at the head of this list. There is nothing special about scratchpads here; if you shift any window on the current workspace to another workspace, that other workspace will now be the "previous workspace" as far as toggleWS is concerned. The real problem is that the order of workspaces in xmonad's list of hidden workspaces is not really supposed to mean anything, so toggleWS is depending on undefined behavior. The only way to really fix this would be to have CycleWS track the workspace history itself. Here's a sketch of a possible solution: CycleWS could use the new extensible state to track the workspace history, and provide something to put in the logHook that would notify CycleWS every time the current workspace changes. (It would be nicer if putting something in the logHook was not necessary, but otherwise it is not clear how CycleWS would find out about workspace changes.) -- 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 3

Re: [xmonad] Why doesnot it jump to the browser when pressing URL in emacs-erc ?
by Brandon Allbery 07 Jan '13

07 Jan '13

On Mon, Jan 7, 2013 at 8:38 AM, Ray <i(a)maskray.me> wrote: > How can I reach the opposite effect: to remain most EWMH features but make > xmonad not recognize the browser's request? > Oftentimes, I open many links in newsbeuter but do not want the browser > takes the focus. > This presently requires a hacked copy of EwmhDesktops. It's requested often enough that this might change, though. Personally I'd like to see some extensions mechanism to make it easier to opt in to/out of the focus change message or fullscreen, those being the two things that we often want to be opt-able. Maybe other features should also be made available for opt in/out as well. (I once again do not have a working xmonad dev environment, and am in the process of moving so it won't be fixed very soon....) -- brandon s allbery kf8nh sine nomine associates allbery.b(a)gmail.com ballbery(a)sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

1 0

Why doesnot it jump to the browser when pressing URL in emacs-erc ?
by z_axis 07 Jan '13

07 Jan '13

hi, friends Using the same emacs config, clicking URL in emacs-erc under STUMPWM will open and jump to the browser(Opera). However, under XMONAD it just open the URL without switching the focus to the browser. it is not a big problem but a bit uncomfortable. Any suggestion is appreciated !

3 3

A community-driven effort to make XMonad better and better
by Alfredo Di Napoli 04 Jan '13

04 Jan '13

Hi guys, after a conversation with the current maintainer (Adam) and some guys at the Copenhagen Uni I'm trying to convey XMonad efforts in a single point. Therefore, I've created this organization on Github: https://github.com/XMonad Please share your thoughts in the README repo, fire an issue maybe. The plan is to integrate XMonad with the latest patches, together with other related product like osxmonad. Cheers, Alfredo

18 48

Updated old patch for bug 225
by Conrad Irwin 04 Jan '13

04 Jan '13

Hello Xmonad, I applied the patch mentioned at http://code.google.com/p/xmonad/issues/detail?id=225 to a current version of Xmonad. This may be useful to other people who also want the same behaviour, Conrad

2 1

ANN: xmonad-0.11
by Adam Vogt 04 Jan '13

04 Jan '13

http://xmonad.org The xmonad dev team is pleased to announce xmonad 0.11! The headlines: http://www.haskell.org/haskellwiki/Xmonad/Notable_changes_since_0.10 About: xmonad is a leading tiling window manager, known for its lightness, reliability, extensibility and efficiency. It supports true multiheaded tiling, and rich, rapid customisation. It is also highly portable, running on regular desktops, laptops, netbooks, phones, game consoles, the OLPC, and more. Features: * Very stable, fast, small and simple. * Automatic window tiling and management * First class keyboard support: a mouse is unnecessary * Full support for tiling windows on multi-head displays * Full support for floating, tabbing and decorated windows * Full support for Gnome and KDE utilities * XRandR support to rotate, add or remove monitors * Per-workspace layout algorithms * Per-screens custom status bars * Compositing support * Powerful, stable customisation and reconfiguration * Large extension library * Excellent, extensive documentation * Large, active development team, support and community Get it! Information, screenshots, documentation, tutorials and community resources are available from the xmonad home page: http://xmonad.org The 0.11 release, and its dependencies, are available from hackage.haskell.org: http://hackage.haskell.org/package/xmonad xmonad packages are available in pretty much every package system, including. Debian, Gentoo, Arch, Ubuntu, OpenBSD, NetBSD, FreeBSD, Gobo, NixOS, Source Mage, Slackware and 0.11 packages will appear in coming days. On the fly updating to xmonad 0.11 is supported, without losing your session! You can even use cabal-install: $ cabal update $ cabal install xmonad $ cabal install xmonad-contrib $ xmonad --recompile; xmonad --restart Extensions: xmonad comes with a huge library of extensions (now around 15 times the size of xmonad itself), contributed by viewers like you. Extensions allow for all sorts of functionality and enhancements to the window manager, via Haskell in your config file. For more information on using and writing extensions see the webpage. The library of extensions is available from hackage: http://hackage.haskell.org/xmonad-contrib Full documentation for using and writing your own extensions: http://xmonad.org/documentation.html This release brought to you by the xmonad dev team: Spencer Janssen Don Stewart Adam Vogt Brent Yorgey Daniel Wagner Devin Mullins Daniel Schoepe Braden Shepherdson Nicolas Pouillard Roman Cheplyaka Gwern Branwen Lukas Mai Featuring code contributions from over 130 developers: Henrique Abreu intrigeri Mats Rauhala Alexey Khudyakov Dmitri Iouchtchenko Geoff Reedy Hans Philipp Annen Conrad Irwin Jesper Reenberg Jeremy Apthorp Rohan Jain Lanny Ripple Dmitry Astapov Michal Janeczek Andrea Rossato Shachaf Ben-Kiki Tomas Janousek David Roundy Alec Berryman Mats Jansborg rupa Ben Boeckel Spencer Janssen Andres Salomon Justin Bogner Julia Jomantaite Karsten Schoelzel Gwern Branwen Simon Peyton Jones Daniel Schoepe Joachim Breitner kedals0 Steffen Schuldenzucker Matt Brown Brandon Allbery Nils Schweinsberg Dominik Bruhn Miikka Koskinen seanmce33 Alexandre Buisse Dmitry Kurochkin Austin Seipp Nick Burlett David Lazar Leonardo Serra Luis Cabellos lithis Braden Shepherdson cardboard42 longpoke Marco e Silva Ismael Carnales Carlos Lopez-Camey Audun Skaugen Roman Cheplyaka Erik de Castro Lopo Michael G. Sloan Jason Creighton Mike Lundy Konstantin Sobolev daedalusinfinity Lukas Mai Dougal Stanton Nils Anders Danielsson Jussi Maki Mathias Stearn Aaron Denney Malebria Don Stewart Christian Dietrich Robert Marlow Joel Suovaniemi Bas van Dijk Tomohiro Matsuyama Wouter Swierstra Aleksandar Dimitrov David McLean Ivan Tarasov Jurgen Doser Chris Mears Alex Tarkovsky Nicolas Dudebout Alejandro Serrano Mena Christian Thiemann Nelson Elhage Eric Mertens Joe Thornber Trevor Elliott Ivan Miljenovic timthelion Anders Engstrom Neil Mitchell Michal Trybus Shae Erisson Tony Morris Ivan N. Veselov Sean Escriva Quentin Moser Ben Voui Will Farrington Devin Mullins Adam Vogt Joachim Fasting Yaakov Nemoy Jan Vornberger Michael Fellinger Daniel Neri Valery V. Vorotyntsev Clemens Fruhwirth Stefan O'Rear Peter De Wachter Johann Giwer Carsten Otto Daniel Wagner David Glasser Mario Pastorelli Ferenc Wagner Kai Grossjohann perlkat Jamie Webb Rickard Gustafsson Jens Petersen Klaus Weidner Dave Harrison Ilya Portnov Wirt Wolff Travis B. Hartwell Nicolas Pouillard Brent Yorgey Juraj Hercek Jan-David Quesel Norbert Zeh Tim Horton Max Rabkin Ian Zerny Sam Hughes Tom Rauchenwald As well as the support of many others on the #xmonad and #haskell IRC channels, and the wider Haskell and window manager communities. Thanks to everyone for their support!

8 7

Issue 429 in xmonad: X.A.DynamicWorkspaces command to delete specified tag
by codesite-noreply＠google.com 03 Jan '13

03 Jan '13

Status: New Owner: ---- New issue 429 by jjfoe...(a)earthlink.net: X.A.DynamicWorkspaces command to delete specified tag http://code.google.com/p/xmonad/issues/detail?id=429 X.A.DynamicWorkspaces contains 'removeWorkspace' which deletes the current workspace. It would be useful to me to have a similar command with which I could delete any workspace by name. I would use this to write a 'workspaces cleanup' procedure that auto-deletes empty auxiliary workspaces.

1 3

Re: Issue 316 in xmonad: AvoidStruts gives wrong window heights with vertically stacked screens
by codesite-noreply＠google.com 03 Jan '13

03 Jan '13

Comment #3 on issue 316 by liskni.si: AvoidStruts gives wrong window heights with vertically stacked screens http://code.google.com/p/xmonad/issues/detail?id=316 http://www.haskell.org/pipermail/xmonad/2009-November/009145.html This, I believe, fixed the issue and discusses why it changes the strut semantics incompatibly with wm-spec. -- 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 2