- xmonad - Haskell.org

Issue 29 in xmonad: MergeFB " Pseudo" Xinerama not supported
by codesite-noreply＠google.com 24 Jun '07

24 Jun '07

Issue 29: MergeFB "Pseudo" Xinerama not supported http://code.google.com/p/xmonad/issues/detail?id=29 Comment #2 by Ulrich.Pfeifer: I am running ion3 (old snapshot) in Pseudo-Xinerama mode on the same display. checking for unistd.h... yes checking X11/extensions/Xinerama.h usability... yes checking X11/extensions/Xinerama.h presence... yes checking for X11/extensions/Xinerama.h... yes configure: creating ./config.status % xdpyinfo | grep XINERAMA XINERAMA XINERAMA Hmm, the darcs snapshot did *not* contain the file include/X11_extras_config.h.in. I did create it as empty file. It did not exists in the last release and was required for compilation. Can that be related? Ulrich -- 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 29 in xmonad: MergeFB " Pseudo" Xinerama not supported
by codesite-noreply＠google.com 24 Jun '07

24 Jun '07

Issue 29: MergeFB "Pseudo" Xinerama not supported http://code.google.com/p/xmonad/issues/detail?id=29 Comment #1 by SpencerJanssen: I suspect that your X11-extras was not built with Xinerama capability for some reason. When you run 'Setup configure' for X11-extras, do you see the following lines? checking X11/extensions/Xinerama.h usability... yes checking X11/extensions/Xinerama.h presence... yes checking for X11/extensions/Xinerama.h... yes If so, please try the following: - clean, then reinstall both X11-extras and xmonad - make sure your X server has the Xinerama extension active ('xdpyinfo | grep XINERAMA' should do it) Issue attribute updates: Owner: SpencerJanssen -- 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

darcs patch: move Spiral to LayoutHelpers. (and 3 more)
by David Roundy 23 Jun '07

23 Jun '07

Hi all, Here's a massive patch to move code over to the new doLayout. I don't recall what tabbed+Xinerama did before, but right now the tabs are only properly printed on the screen that has focus (at least using LayoutScreens to fake Xinerama). I haven't figured out why this is, and am tired, so this is where this is going to be left for the day. It doesn't seem to me like a big deal, since you can't click on those tabs until you put the focus on that screen. Not that I don't want to fix it, but I would like to see these patches applied in spite of the problem, since this particular breakage is mild enough that it shouldn't hurt anyone's productivity. David Sat Jun 23 07:35:16 PDT 2007 David Roundy <droundy(a)darcs.net> * move Spiral to LayoutHelpers. Sat Jun 23 07:35:42 PDT 2007 David Roundy <droundy(a)darcs.net> * introduce idModify which is just "const (return Nothing)". Sat Jun 23 07:37:45 PDT 2007 David Roundy <droundy(a)darcs.net> * move Accordian to use idModify. Sat Jun 23 14:09:52 PDT 2007 David Roundy <droundy(a)darcs.net> * make everything work with new doLayout. This modifies all the contrib modules to work (so far as I know) with the new contrib layout. The exception is the LayoutHooks module, which isn't used. It exports an API that is inherently unsafe, so far as I can tell (and always has been).

1 1

Issue 29 in xmonad: MergeFB " Pseudo" Xinerama not supported
by codesite-noreply＠google.com 23 Jun '07

23 Jun '07

Issue 29: MergeFB "Pseudo" Xinerama not supported http://code.google.com/p/xmonad/issues/detail?id=29 New issue report by Ulrich.Pfeifer: The current code does only support real Xinerama Screens. If the setup is a MergeFB one with Pseudo Xinerama Screens, it is not detected. The following C-Code does find the rectangles (should also find the rectangles in real Xinerama mode): if(XineramaQueryExtension(ioncore_g.dpy, &event_base, &error_base)){ xi=XineramaQueryScreens(ioncore_g.dpy, &nxi); if(xi!=NULL){ for(i=0; i<nxi; i++){ { fprintf(out,"Xinerama screen (%d,%d) %dx%d\n", xi[i].x_org, xi[i].y_org, xi[i].width, xi[i].height); } } } } What steps will reproduce the problem? The current code does only support real Xinerama Screens. If the setup is a MergeFB one with Pseudo Xinerama Screens, it is not detected. The following C-Code does find the rectangles (should also find the rectangles in real Xinerama mode): if(XineramaQueryExtension(ioncore_g.dpy, &event_base, &error_base)){ xi=XineramaQueryScreens(ioncore_g.dpy, &nxi); if(xi!=NULL){ for(i=0; i<nxi; i++){ { fprintf(out,"Xinerama screen (%d,%d) %dx%d\n", xi[i].x_org, xi[i].y_org, xi[i].width, xi[i].height); } } } } Here are some parts of the xorg.conf: Option "MergedFB" "true" Option "CRT2Position" "LeftOf" Option "CRT2HSync" "30-82" Option "CRT2VRefresh" "56-76" Option "MergedNonRectangular" "true" Option "MergedXineramaCRT2IsScreen0" "false" Option "MetaModes" "1024x768-1440x900 1024x768" xmonad does only recognize the whole pan area, not the viewports. I complied x11-extra and xmonad straight from the darcs repository. Ulrich 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

Announce: xmobar-0.1 released!
by Andrea Rossato 23 Jun '07

23 Jun '07

Hi! Sorry if I didn't keep the promise of refactoring Tabbed.hs, but I've been quite busy. I'll do it, though. Moreover, I wrote this stuff, a real status bar, inspired by the Ion3 one. I sent a mail about it a couple of days ago, as a challenge to Robert to rewrite dzen2 in Haskell... No answer, so there I am. Well, XMobar, I called it this way, is not going, I hope, to compete with dzen, since it is designed to work only with a configuration file (see xmobar.config-example). No piping and stuff. Moreover, it is just a status bar (should work with any WM). Screenshots: with xmobar.config-sample http://gorgias.mine.nu/xmobar/xmobar-config-sample.jpg another one (text align to left): http://gorgias.mine.nu/xmobar/xmobar-2.jpg I forgot to take the default screenshot (when you run xmobar without config). Well, just find out. Grabit and run: xmobar You can grab the source of this release here: http://gorgias.mine.nu/xmobar/xmobar-0.1.tar.gz Darcs repo here: http://gorgias.mine.nu/repos/xmobar/ Documentation is absent. Anyway, there is a template to set the output: <command> will cause xmobar to run the command and display the output. <fc=#FF0000>text</fc> will make "text" red. See in Monitors/ some examples of monitors that can take advantage of that (they are built during the installation process, as xmb-net, xmb-cpu, xmb-mem). The configuration sample xmobar.config-sample uses them. Below the README. It all started by trying to understand how to use Xlib with Haskell. Hope you'll enjoy. I did. Studying Haskell is indeed a joy. I hope the name XMobar is not a problem (confusion with xmonad): let me know, I can change it. Ciao Andrea ------------( README )----------- XMobar - a status bar for the XMonad Window Manager ABOUT ----- Xmobar is a minimal status bar for the XMonad Window Manager. It was inspired by the Ion3 status bar, and supports similar features. See xmobar.config-sample for a sample configuration. Try it with: xmobar xmobar.config-sample INSTALLATION ------------ tar xvfz xmobar-0.1 runhaskell Setup.lhs configure --prefix=/usr/local runhaskell Setup.lhs build runhaskell Setup.lhs haddock (optional for building the code documentation) runhaskell Setup.lhs install (possibly to be run as root) Run with: xmobar /path/to/config $ AUTHOR ------ Andrea Rossato <andrea.rossato(a)unibz.it> LINKS ----- The XMobar home page: http://gorgias.mine.nu/xmobar/ XMobars darcs repository: http://gorgias.mine.nu/repos/xmobar/ The XMonad Window Manager http://xmonad.org

4 7

darcs patch: add new LayoutHelpers module.
by David Roundy 23 Jun '07

23 Jun '07

Here's a start of a sketch of a helper module to make it easier to write correct layouts, and also to insulate layout-writing code from changes to the Layout representation in XMonad core (e.g. so we can make it safe to modify layouts in doLayout, as LayoutHooks and SimpleStacking do). It's not very useful yet, but I still think this is suitable to go into the main XMonadContrib repo. David Fri Jun 22 07:29:50 PDT 2007 David Roundy <droundy(a)darcs.net> * add new LayoutHelpers module.

2 1

darcs patch: Add SinkAll module.
by joachim.fasting＠gmail.com 23 Jun '07

23 Jun '07

Sat Jun 23 07:05:10 CEST 2007 joachim.fasting(a)gmail.com * Add SinkAll module. Provides a means of pushing all windows on the current workspace back into tiling. Not all that useful, but might be preferable to restarting or manually pushing windows.

2 1

darcs patch: Magnifier.hs: needs -fglasgow-exts to compile.
by joachim.fasting＠gmail.com 23 Jun '07

23 Jun '07

Fri Jun 22 13:14:42 CEST 2007 joachim.fasting(a)gmail.com * Magnifier.hs: needs -fglasgow-exts to compile.

2 1

xmobar: url change
by Andrea Rossato 22 Jun '07

22 Jun '07

Hi! This afternoon I experienced a bad system failure: to put it briefly, gorgias.mine.nu has gone. I've put xmobar-0.1.tar.gz and screenshots here http://gipc49.jus.unitn.it:8080/xmobar/ I'll have some difficulties in next few days but I'll check my mail. The darcs repository will not be available for the time being. hope to solve this problem soon without any data loss. Sorry for the inconvenience (in the case you tried to download the source). Ciao Andrea

1 0

problems with self-modifying layouts
by David Roundy 22 Jun '07

22 Jun '07

Hi all, (This email is partly a resend of content attached along with a patch, which I realize folks might not have seen, since I sent a fixed version of that patch. If you come across this twice, and find it as boring the second time as the first, my apologies.) There's design problem with some of the recently-introduced self-modifying layout modifiers, which include Decorations and SimpleStacking. The trouble is that while it's easy for a Layout to modify itself in response to an event, there's no safe way for a layout to modify itself in during a doLayout call. One answer to that is to simply state that "layouts should not do that." This seems an unsatisfying answer to me, as we've already got two valid uses--one already refactored into LayoutHooks, an inherently buggy module. The trouble is that within doLayout, there's no way for a layout to modify itself, because it can't tell which layout it is... and because it may not be a "root" layout at all, but some intermediate modified layout. There seems to be a simple solution: data Layout a = Layout { doLayout :: Rectangle -> Stack a -> X ([(a, Rectangle)], Maybe (Layout a)) , modifyLayout :: SomeMessage -> X (Maybe (Layout a)) } so doLayout can modify itself. This makes all the Layout transformers a little harder to write, but a helper module ought to be able to fix that. And it makes me wonder yet again whether we should be defining a class class Layout l a where doLayout :: l -> X Rectangle -> Stack a -> X ([(a, Rectangle)], Maybe (Layout a) modifyLayout :: l -> SomeMessage -> X (Maybe (Layout a)) serializeLayout :: l -> String readLayout :: String -> Maybe (l, String) -- or some other parser-like thing data Layout a = forall l. Layout l a => Layout a This might lend itself to somewhat prettier Layout code that is more "data-structure-based" rather than self-modifying-function-based. I imagine this would lead to friendly interfaces for easy-to-write layout modifiers. David P.S. I'd be curious to see implemented a "popularity-contest" module for xmonad once we've got serialization, which could use the logging mechanism to report on the most frequently used layouts. And yes, this would be in XMonadContrib and only manually enabled. I have no idea how many people are actually using Tabbed, and how likely this is to break folks' Config files.

3 3