- xmonad - Haskell.org

Issue 154 in xmonad: add support for UTF-8 locale in NamedWindows and DynamicLog
by codesite-noreply＠google.com 13 Mar '08

13 Mar '08

Issue 154: add support for UTF-8 locale in NamedWindows and DynamicLog http://code.google.com/p/xmonad/issues/detail?id=154 New issue report by andrea.rossato: This is a pre-bug report: did you ever happen to see "Minority Report"? After reading David's report about resource leaks I felt the urgency to pull the latest changes and give them a try. But everything seems fine here. I was a bit scared by that "Add bottom-tabbed layout", though - Roman, did you notice that it duplicates what can be done by applying Brent's Reflector to Tabbed? Very responsive reactions can lead to not so excellent results...;) Then I heard that Roman, aka Feuerbach, is willing to import Xmb* functions in X11 and use them to add locale support to xmonad, by calling setLocale in the core. And that Donald, who seems to be the acting project leader, would be willing to support such an approach. Which means none noticed that in X11 there are Xwc* functions for locale support, and that xmonad has been already supporting XFT, which is locale aware, for quite some months now. Spencer, together with someone whose name I do not recall now, wrote it, even though some bugs were left behind. While fixing those bugs - byorgey pushed the related patches quite a few days ago in order to fix issue #146 and issue #150 - I also added full support for UTF-8 locales, and setLocale is already called when the font system is initialized. While Toumo would reject UTF-8 (only full locale support is acceptable to preserve cultural diversity - and Toumo has probably a point here), still I think it is quite a good second best. Adding full locale support means using the only library that, as far as I know, supports translating from at least a few encodings: iconv. BTW, if you want full locale support I may be sending a patch with a few iconv calls - but you can do it yourself by searching the ML archives. The attached patches are just an attempt to avoid what I came to think is a quite probable possibility: Roman and Donald adding a new and different locale support to xmonad without even noticing the old one - which could lead to unexpected even if interesting effects. The attached patches make it visible the fact that xmonad already support UTF-8 locale when the contrib library is compiled with the "with_utf8" or "use_xft" flags. The prompt don't need them, and the Shell prompt is already UTF-8 aware - if the contrib library is compiled with that support. The fist patch will make getName use the XTextProperty structure to retrieve the window's name. This was contributed in issue #44, but I removed a few bad bugs. This way you'll see non ASCII characters in window's decorations. The second one will encode in UTF-8 the DynamicLog output - so that non ASCII characters in window's names can be correctly logged too -, if, and only if, the contrib library has compiled with those configuration options - you can use this feature with darcs xmobar. In other words, with these patches xmonad is going to fully support UTF-8 locales. Or, even better, the full support for UTF-8 locales will be visible even by xmonad developers. ;) Attachments: utf8_NamedDynLog.dpatch 46.6 KB Issue attributes: Status: New Owner: ---- Labels: Type-Patch Priority-Medium Usability -- 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 152 in xmonad: RSS feeds for xmonad / XMonadContrib darcs repositories
by codesite-noreply＠google.com 13 Mar '08

13 Mar '08

Issue 152: RSS feeds for xmonad / XMonadContrib darcs repositories http://code.google.com/p/xmonad/issues/detail?id=152 Comment #1 by wcfarrington: Atom would be preferable, due to the generally better nature of that standard. -- 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 153 in xmonad: Need to type keybindings twice after startup for effect
by codesite-noreply＠google.com 13 Mar '08

13 Mar '08

Issue 153: Need to type keybindings twice after startup for effect http://code.google.com/p/xmonad/issues/detail?id=153 New issue report by v.dijk.bas: What steps will reproduce the problem? 1. Start xmonad 2. Type a keybinding (say mod-shift-return) 3. Observe that nothing happens 4. Type it again 5. Observe that the terminal is started First I believed it had something to do with xmobar which I'm using: http://www.haskell.org/pipermail/xmonad/2008-March/005060.html But that doesn't seem to be the problem. What version of the product are you using? On what operating system? Latest version from darcs 13 march 2008 Please provide any additional information below. I attached my ~/.xmonad/xmonad.hs and ~/.xsession for reference. Attachments: .xsession 103 bytes xmonad.hs 12.7 KB 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

Focus issue with xmonad and xmobar
by Bas van Dijk 13 Mar '08

13 Mar '08

Hello, I'm using Andrea Rossatos xmobar which is great. So in my ~/.xmonad/xmonad.hs I have: myDynLog h = DL.dynamicLogWithPP DL.xmobarPP {DL.ppOutput = SIO.hPutStrLn h} main = do xmobar <- R.spawnPipe "xmobar" xmonad $ defaults { logHook = myDynLog xmobar } However when I start xmonad and type a keybinding say mod-shift-return, nothing happens. When I type it again my terminal is started as expected. When I disable xmobar by: main = xmonad default Then typing a keybinding as immediate effect. It looks like a focus issue. I'm unsure where the problem is: xmonad or xmobar so I'm waiting to report a bug. regards, Bas

1 1

Issue 151 in xmonad: XMonad needs to spot resize events in non-floating windows
by codesite-noreply＠google.com 13 Mar '08

13 Mar '08

Issue 151: XMonad needs to spot resize events in non-floating windows http://code.google.com/p/xmonad/issues/detail?id=151 Comment #5 by mj.fialka: Of course I tried this. It has no effect at all. -- 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 152 in xmonad: RSS feeds for xmonad / XMonadContrib darcs repositories
by codesite-noreply＠google.com 12 Mar '08

12 Mar '08

Issue 152: RSS feeds for xmonad / XMonadContrib darcs repositories http://code.google.com/p/xmonad/issues/detail?id=152 New issue report by netprobe: Please provide any additional information below. It would be nice to have a RSS feed generated from the commits to both repositories. The best approach would be to have 2 feed. How this can be achieved without using the CGI interface is described in this url: http://lists.osuosl.org/pipermail/darcs-users/2005-January/005154.html 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

Issue 151 in xmonad: XMonad needs to spot resize events in non-floating windows
by codesite-noreply＠google.com 12 Mar '08

12 Mar '08

Issue 151: XMonad needs to spot resize events in non-floating windows http://code.google.com/p/xmonad/issues/detail?id=151 Comment #4 by lit...(a)hethrael.com: As a workaround, you can press Mod+N after changing the font size in xterm to adjust it to the proper size. -- 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 151 in xmonad: XMonad needs to spot resize events in non-floating windows
by codesite-noreply＠google.com 12 Mar '08

12 Mar '08

Issue 151: XMonad needs to spot resize events in non-floating windows http://code.google.com/p/xmonad/issues/detail?id=151 Comment #3 by mj.fialka: If I change the XTerm's font in a tiled window, the size of the window remains the same (in the opposite to floating XTerm that does resize) but the geometry change of the XTerm is not detected by XMonad and therefor XMonad does not force the window geometry to the XTerm and thus XTerm does not change it's geometry as it happens in other cases such as when changing layouts or removing/adding a window to the tiled layout or when beying resized using "mouseResize" with "windowArrange" contributed modules. Therefor, when the font is changed to a smaller one, the window remains the same and you can see the application running inside it (can be MC for a good visual reference) in a top-left corner without beying resized to the full window rectangle. That makes this feature of XTerm almost useless which is really pity (see the "off-topic" below). When the font size increases the same thing happens but with the result that only a part of the running application is visible. I hope that's clear now what happens although I am terribly pity I can not add some more technical description... :-( ---off-topic--- I must say that as non-programmer I do not know exactly what XTerm is actually doing. I do not know URXVT but I know I simply love to resize the font size of the XTerm on-the-fly. Is' one of the most handiest things about XTerm. XTerm is also the most precise VT100 emulator around (you can test it with `vttest' to see) and it has also the marvellous Tektronix mode which I use sometimes. To be short - XTerm has many features I actually need to be effective at my work and at home too. Also consider that XTerm is somehow the stadard terminal emulator for XFree86 that is included in most UNIX systems so I would rather not get used to anything else because I can keep my .Xresources still by me and load them almost anywhere and profit of the effective working environment which is exactly the thing XTerm means to me. :-) Please, all reading this, do NOT react on this off-topic piece of text above here directly. I do not like to flame either. If you like to discuss this off-topic called "Why is XTerm so good to MJF?" with me, do `/query mjf' on #xmonad channel instead. Thank you. :-) ---off-topic--- I would like to know what XTerm does. When XTerm changes it's font-size, you can see using `xprop' utility that it did a geometry change (lookup "WM_NORMAL_HINTS(WM_SIZE_HINTS)" in the output). But I can not see from the `xprop's output whether it signalled something or just resized itself. Help with debugging this and it's connection to what's going on inside XMonad is therefor requested by me as well. I hope we can find some solution together. I started to love XMonad, because it is the window manager ("almost") I was looking for for years. :-) -- 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 151 in xmonad: XMonad needs to spot resize events in non-floating windows
by codesite-noreply＠google.com 12 Mar '08

12 Mar '08

Issue 151: XMonad needs to spot resize events in non-floating windows http://code.google.com/p/xmonad/issues/detail?id=151 Comment #2 by mj.fialka: If I change the XTerm's font in a tiled window, the size of the window remains the same (in the opposite to floating XTerm that does resize) but the geometry change of the XTerm is not detected by XMonad and therefor XMonad does not force the window geometry to the XTerm and thus XTerm does not change it's geometry as it happens in other cases such as when changing layouts or removing/adding a window to the tiled layout or when beying resized using "mouseResize" with "windowArrange" contributed modules. Therefor, when the font is changed to a smaller one, the window remains the same and you can see the application running inside it (can be MC for a good visual reference) in a top-left corner without beying resized to the full window rectangle. That makes this feature of XTerm almost useless which is really pity (see the "off-topic" below). When the font size increases the same thing happens but with the result that only a part of the running application is visible. I hope that's clear now what happens although I am terribly pity I can not add some more technical description... :-( ---off-topic--- I must say that as non-programmer I do not know exactly what XTerm is actually doing. I do not know URXVT but I know I simply love to resize the font size of the XTerm on-the-fly. Is' one of the most handiest things about XTerm. XTerm is also the most precise VT100 emulator around (you can test it with `vttest' to see) and it has also the marvellous Tektronix mode which I use sometimes. To be short - XTerm has many features I actually need to be effective at my work and at home too. Also consider that XTerm is somehow the stadard terminal emulator for XFree86 that is included in most UNIX systems so I would rather not get used to anything else because I can keep my .Xresources still by me and load them almost anywhere and profit of the effective working environment which is exactly the thing XTerm means to me. :-) Please, all reading this, do NOT react on this off-topic piece of text above here directly. I do not like to flame either. If you like to discuss this off-topic called "Why is XTerm so good to MJF?" with me, do `/query mjf' on #xmonad channel instead. Thank you. :-) ---off-topic--- I would like to know what XTerm does. When XTerm changes it's font-size, you can see using `xprop' utility that it did a geometry change (lookup "WM_NORMAL_HINTS(WM_SIZE_HINTS)" in the outpupt). But I can not see from the `xprop's output whether it signalled something or just resized. Help with debugging this and it's connection to what's going on inside XMonad is therefor requested by me as well. I hope we can find some solution together. I started to love XMonad, because it is the window manager ("almost") I was looking for for years. :-) -- 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 151 in xmonad: XMonad needs to spot resize events in non-floating windows
by codesite-noreply＠google.com 12 Mar '08

12 Mar '08

Issue 151: XMonad needs to spot resize events in non-floating windows http://code.google.com/p/xmonad/issues/detail?id=151 Comment #1 by SpencerJanssen: When you change the font in the tiled window, does it actually change size? If so, xterm is in violation of the ICCCM, technically making it xterm's bug and not ours :). However, we may be able to handle the illegal size change more gracefully. Otherwise, if the application is merely requesting a resize (but does not actually do it!), xmonad is exhibiting the intended behavior. Tiled window positions are dictated by the active layout algorithm, nothing else. Again, in this case I'd say the bug is still xterm's, applications can not assume that their resize requests will be honored by the window manager. Have you checked how urxvt (or any other terminal, for that matter) behaves? We tend to recommend against xterm because of various little annoyances it has when used in a tiling WM. Issue attribute updates: Summary: XMonad needs to spot resize events in non-floating windows -- 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