- xmonad - Haskell.org

Issue 115 in xmonad: sjanssenPP unlike defaultPP gives parsing error in xmobar if titlebar contains "{" and "}" char
by codesite-noreply＠google.com 01 Jan '08

01 Jan '08

Issue 115: sjanssenPP unlike defaultPP gives parsing error in xmobar if titlebar contains "{" and "}" char http://code.google.com/p/xmonad/issues/detail?id=115 New issue report by iddo333: What steps will reproduce the problem? 1. echo -ne "\033]0;{mytitle}\007" && cat 2. or just: echo -ne "\033]0;mytitle}\007" && cat What is the expected output? What do you see instead? Should be {mytitle}, but there's a parsing error message instead. What version of the product are you using? On what operating system? xmonad 0.5 on ubuntu 7.10 note: defaultPP also messes up the placement of the "}" char, but at least all the other chars are ok and there's no parsing error. 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

3 2

Issue 115 in xmonad: sjanssenPP unlike defaultPP gives parsing error in xmobar if titlebar contains "{" and "}" char
by codesite-noreply＠google.com 01 Jan '08

01 Jan '08

Issue 115: sjanssenPP unlike defaultPP gives parsing error in xmobar if titlebar contains "{" and "}" char http://code.google.com/p/xmonad/issues/detail?id=115 Comment #2 by andrea.rossato: sorry for the typos (I pushed "Submit Changes" too early)... what I meant was: XMonad.Hooks.DynamicLog provides a function, dynamicLogXmobar, which gives you some nice pretty printer defaults to be used with xmobar. Have a look at XMonad.Config.Arossato as an usage example. andrea -- 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 115 in xmonad: sjanssenPP unlike defaultPP gives parsing error in xmobar if titlebar contains "{" and "}" char
by codesite-noreply＠google.com 01 Jan '08

01 Jan '08

Issue 115: sjanssenPP unlike defaultPP gives parsing error in xmobar if titlebar contains "{" and "}" char http://code.google.com/p/xmonad/issues/detail?id=115 Comment #1 by andrea.rossato: I'm sure Spencer is using the alignSep option in .xmobarrc to set different character for aligning text in xmobar. take into account the XMonad.Hooks.DynamicLog also provides with useful pretty printer default for xmobar: dynamicLogXmobar. I would say that the module maintainer, Don, is a bit dzen biased, but I hardly think of it as a bug. I'd call this report as invalid... but I'll wait a bit...;) Andrea -- 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

"Not in scope"
by Jevin Maltais 31 Dec '07

31 Dec '07

Still trying to get xmonad to worky in gnome. Is this not just like the XMonad.Hooks.ManageDocks doc? Jevin Using ghc 6.6.1 xmonad 0.5 xmonad.hs: import XMonad import XMonad.Hooks.ManageDocks main = xmonad $ defaultConfig { borderWidth = 3 , manageHook = manageDocks , layoutHook = avoidStruts (tall ||| mirror tall) } [1 of 1] Compiling Main ( xmonad.hs, interpreted ) xmonad.hs:7:52: Not in scope: `tall' xmonad.hs:7:61: Not in scope: `mirror' xmonad.hs:7:68: Not in scope: `tall' Failed, modules loaded: none. -- Jevin Maltais [jevin(a)techie.com] http://jevy.org

3 3

Slackware packages available
by Andrea Rossato 31 Dec '07

31 Dec '07

Hi I was eventually able to package xmonad, xmonad-contrib and xmobar for Slackware. There are also the other ghc-6.8.2 packages that are needed for running, configuring, and reconfiguring xmonad: http://code.haskell.org/~arossato/xmonad-slack/ other slackware packages can be found here: http://gorgias.mine.nu/slack/haskell/ hope you'll enjoy. andrea

1 0

darcs patch: Add support for cycling through screens ... (and 8 more)
by mail＠joachim-breitner.de 31 Dec '07

31 Dec '07

Thu Dec 27 19:26:35 CET 2007 mail(a)joachim-breitner.de * Add support for cycling through screens to CycleWS Thu Dec 27 20:01:13 CET 2007 mail(a)joachim-breitner.de * Although I do not need the curr variable after all, this is nicer Thu Dec 27 21:43:49 CET 2007 mail(a)joachim-breitner.de * display all visible windows on the current desktop in the pager This is my best shot at modeling xmonad’s WM behaviour in a way that the Extended Window Manager Hints specification allows. Unfortunately, we can not tell the panel what size and position it should think the apps are. Fri Oct 12 00:55:58 CEST 2007 mail(a)joachim-breitner.de * EwmhDesktops reacts to messages from panel apps Hi, this patch makes EwmhDesktops react to ClientMessages send from e.g. the panel switcher. It currently only supports changing the current desktop (which at least for me is the most important feature). Note that you need my patch against X11-extras that adds ClientMessage support. You also need my messageHook hack against darcs. I tried to implement this without changes to the core, but trying to do some hack based on LayoutModifieres weren’t very satisfying. The code is still there, just commented. I’d very much appreciate any comments on how this functionality can go in, after 0.4, I guess. Greetins, Joachim Thu Dec 27 22:01:05 CET 2007 mail(a)joachim-breitner.de * Merge in EWMH interaction code, without my obsolete Hook system Thu Dec 27 22:34:31 CET 2007 mail(a)joachim-breitner.de * create a layout modifier that reacts on EWMH commands (e.g. from a pager) Thu Dec 27 22:56:07 CET 2007 mail(a)joachim-breitner.de * Fulfill the EWMH specification by listing the supported ATOMs, doesnt really make a differene AFAIK Fri Dec 28 15:38:41 CET 2007 mail(a)joachim-breitner.de * React on _NET_ACTIVE_WINDOW requests This patch as a problem: The request is handled once per workspace, as the layout modifier exists once per workspace. If someone has a good idea how to fix that, that would be great! Fri Dec 28 16:21:55 CET 2007 mail(a)joachim-breitner.de * Use trace instead of io $ putStrLn

3 3

Issue 111 in xmonad: Clicking on tab doesn't work if that screen doesn't have focus
by codesite-noreply＠google.com 30 Dec '07

30 Dec '07

Issue 111: Clicking on tab doesn't work if that screen doesn't have focus http://code.google.com/p/xmonad/issues/detail?id=111 Comment #6 by daveroundy: No, I would say that a mouse event is inherently spatial, and sending this event to layouts that aren't in the right location is wrong. Fixing this would also fix issue #40. -- 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 110 in xmonad: Inconsitencies with combo layout
by codesite-noreply＠google.com 30 Dec '07

30 Dec '07

Issue 110: Inconsitencies with combo layout http://code.google.com/p/xmonad/issues/detail?id=110 Comment #3 by daveroundy: I wouldn't call this a wontfix, because at least dons is still planning on looking at the idea of nested stacks. -- 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 12 in xmonad: Support _NET_WM_STRUT property for status bar programs
by codesite-noreply＠google.com 30 Dec '07

30 Dec '07

Issue 12: Support _NET_WM_STRUT property for status bar programs http://code.google.com/p/xmonad/issues/detail?id=12 Comment #15 by daveroundy: Any chance we could remove the gaps from core, since there's a better, gapless solution in contrib? -- 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 114 in xmonad: configurable click-to-focus vs. focus-follows-mouse
by codesite-noreply＠google.com 29 Dec '07

29 Dec '07

Issue 114: configurable click-to-focus vs. focus-follows-mouse http://code.google.com/p/xmonad/issues/detail?id=114 Comment #1 by SpencerJanssen: Done. Issue attribute updates: Status: Fixed -- 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