September 2007 - xmonad

darcs patch: move Layout stuff into class (hokey firs... (and 1 more)
by David Roundy 20 Sep '07

20 Sep '07

Here's a cleaner Layout class patch. I've removed the ugly OldLayout, and now we've got one data type per Layout in Operations. This changes Config a little, since Full is now a data constructor, instead of the function full. We could, of course, define a function of the same name, but that seems a waste of space, although it would have the (minor) advantage of allowing the implementations to remain abstract. David Fri Sep 14 17:59:59 EDT 2007 David Roundy <droundy(a)darcs.net> * move Layout stuff into class (hokey first cut). Thu Sep 20 11:52:37 EDT 2007 David Roundy <droundy(a)darcs.net> * eliminate ugly OldLayout.

1 0

another borders thought
by Isaac Dupree 20 Sep '07

20 Sep '07

Rather than borders taking up a pixel that's not in any window, perhaps the colored borders could be drawn on top of windows (near their edges). Perhaps with some degree of transparency so they don't completely hide the bits behind them. (and their width could be more than one [pixel]) Just a thought Isaac

1 0

Issue 19 in xmonad: Investigate a way to allow contrib extensions to use compositing.
by codesite-noreply＠google.com 20 Sep '07

20 Sep '07

Issue 19: Investigate a way to allow contrib extensions to use compositing. http://code.google.com/p/xmonad/issues/detail?id=19 Comment #2 by alextarkovsky: I'd love an extension which allows me to dispense with window borders entirely by automatically setting the currently focused window to 100% opacity and all non-focused windows to low opacity. xcompmgr with transset-df are extremely lightweight and have all the functionality to accomplish that (xcompmgr also handles drop shadows and fading transition effects nicely), but unfortunately xcompmgr, being a demo app, seems to have been abandoned 3 years ago and remains very buggy (not to mention it's probably full of deprecated compositing API calls). A more daunting option might be to hook into Compiz Fusion, however it doesn't currently live happily with xmonad running (if anyone knows how to remedy that let me know!), and anyhow most of its functionality is useless in the xmonad context. Seems like bloat really. So I believe a good starting goal for basic xmonad compositing support would be to duplicate the functionality of xcompmgr and transset-df directly in Haskell. -- 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

Weather forecast in the status bar
by Robert Manea 19 Sep '07

19 Sep '07

Hello, Adrei Gudiu created a more sophisticated weather forecast for a dzen statusbar, based on my example script that can be found here: http://robm.selfip.net/wiki.sh/-main/DzenAndXmonad As he is not subscribed to the list he asked me to post these links: Andrei's scripts: http://openbsd-box.org/xmonad/ http://openbsd-box.org/xmonad/dzenWeather%20Multiline/ Screenshot: http://openbsd-box.org/xmonad/dzenWeather%20Multiline/multiline_on_mouseove… Have fun, Rob.

2 1

Re: [Xmonad] Infelicitous name choice in XPrompt.hs clashes with Config.hs
by Andrea Rossato 19 Sep '07

19 Sep '07

On Tue, Sep 18, 2007 at 04:27:57PM -0400, Gwern Branwen wrote: > Perhaps I've misunderstood something, but isn't the borderPixel > field specifying the width in pixels? I mean, that's what the > borderWidth in Config.hs seems to be doing, and the equivalent > things in StumpWM/Ratpoison also seem to be measuring in pixels. well, yes, you are right, you specify the width in pixel... but... actually the type of borderWidth is Dimension and not Pixel. It is true that both Pixel and Dimension are synonymous of Word32, but they refer to different things: a color the first, a dimension the second...;-) > How else could you describe how wide something'd be? It's not a > percentage of screen size or using ems as a unit, is it? If you look at the window's attributes, for instance, you'll see that bodrerPixel (cWBorderPixel in Haskell) means the color of the window's border. The same for cWBackPixel. It is just for conforming to the Xlib convention that I'm asking to mysleft if borderPixel is the right name. Perhaps David's promptBorderWidth is better? Let me know what you think. Andrea

1 0

how can I have my defaultXPConfig in my Config.hs
by lobzang＠free.fr 18 Sep '07

18 Sep '07

Hello, I would like to have my custom myXPConfig in my Config.hs , to use with XPrompt , so that I can easily upgrade xmonad and keep all my conf there. (let's say have my favorite font) However I am not able to compile that way : runhaskell Setup.lhs build Preprocessing executables for xmonad-0.3... Building xmonad-0.3... [ 4 of 10] Compiling Config[boot] ( Config.hs-boot, nothing ) [ 9 of 10] Compiling Config ( Config.hs, dist/build/xmonad/xmonad-tmp/Config.o ) Config.hs:44:10: Ambiguous occurrence `borderWidth' It could refer to either `borderWidth', defined at Config.hs:108:0 or `borderWidth', imported from XMonadContrib.XPrompt at Config.hs:31:0-27 Anyone already tried that? Lobzang.

2 2

about a configuration GUI
by Andrea Rossato 18 Sep '07

18 Sep '07

Hi, I had a look at the possibility of writing a configuration gui with gtk2hs, and I think it should not be difficult: the GUI can be design with Glade, and the Haskell part should be quite easy (and fun) to write. The problem is the back end, the configuration parsing/writing. And here I'm puzzled. I've read the [HUMOR] discussion and something on IRC, but there seems not to be a consensus on what this configuration gui should be. Suppose we create a stand alone utility for configuring and building XMonad, a utility that must deal with the XMonadContrib repository to be meaningful. That could generate a configuration file not to be manually edited. Still it would be probably easier to use a data type to store the configuration options the GUI could support. Otherwise I'm inclined to think we must use a more difficult approach. There are many ways but I would like Dons, Spencer or David or the others more advanced haskellers to give me some advice here. We can also think about other approaches, more simpler ones. Something based on the job already done by Alex with the docstring stuff. Or something very simple to just deal with the core code, providing a simple GUI to modify gaps, key bindings, etc. What do you think? Andrea

1 0

darcs patch: XPrompt: added i18n support and support ... (and 5 more)
by Andrea Rossato 18 Sep '07

18 Sep '07

Hi, this is all the code needed to have a i18n ready prompt. Probably you have already seen some code here: http://www.haskell.org/pipermail/xmonad/2007-September/002117.html I also added support for escape characters (so that spaces, quotes or stuff like that can be used with the shell prompt) and I removed the readline requirement (now completions are provided directly by bash). Still XPrompt requires a modification to xmonad.cabal since we need to import some other C functions that don't fit in X11-extras: so XMonadContrib.XPromptLib must be included among the "other-modules" field in xmonad.cabal. I updated all the usage info to provide information to the users. These patches require the X11-extras patches I've already sent: http://www.haskell.org/pipermail/xmonad/2007-September/002194.html Please report back any problem (also any success, if you like..;-) Andrea ps: I added a new pure function (breakAtSpace) and so I added a test for it. Some other previously tested functions have been removed from the code and from the test suite. What is scary is all the FFI stuff, though...;-) Tue Sep 18 11:09:16 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * XPrompt: added i18n support and support for escaped special characters Tue Sep 18 11:34:38 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * Added XPromptLib for some needed foreign functions Tue Sep 18 11:35:09 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * ShellPrompt: removed readline requirement and some more + added i18n support + now the prompt correctly handles escape and special characters + removed readline requirement Tue Sep 18 11:37:20 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * SshePrompt: updated usage info Tue Sep 18 11:37:56 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * XMonadPrompt: updated usage info Tue Sep 18 11:39:08 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * test_XPrompt.hs: removed tests of removed functions and added a test for breakAtSpace

1 0

darcs patch: Add functions to draw text in the user's... (and 1 more)
by Andrea Rossato 18 Sep '07

18 Sep '07

Hi, this is a patch for X11-extras to add some functions needed by XPrompt to support internationalization. As you see the main work to get i18n working has been done by Mats. Thanks to his code I was able to grasp the basics of i18n in Xlib. Andrea Sun Aug 19 01:51:23 CEST 2007 Mats Jansborg <mats(a)jansb.org> * Add functions to draw text in the user's locale Added the FontSet type as well as the functions createFontSet, freeFontSet, wcTextExtents and wcDrawString that can be used to draw internationalised text. Thu Sep 13 21:23:31 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * Added wcDrawImageString and wcTextEscapement

1 0

xinerama and dmenu
by lobzang＠free.fr 18 Sep '07

18 Sep '07

Hi, Xinerama seems to work well with xmonad. I'm using dmenu to launch programs. If I go to my second screen, then press mod-p to launch a new program, the dmenu interface appears on my first screen. Is it a bug or conf pb? Thanks ! Lobzang

5 6