December 2007 - xmonad

Issue 43 in xmonad: Call setlocale at startup
by codesite-noreply＠google.com 26 Dec '07

26 Dec '07

Issue 43: Call setlocale at startup http://code.google.com/p/xmonad/issues/detail?id=43 Comment #3 by m...(a)jansb.org: While it is true that xmonad itself doesn't use X to draw strings, it uses a lot of other locale dependent functions. It prints logging information, it fetches window names, it uses system functions like executeFile and others, which accept strings which need to be converted to the locale encoding. Currently these functions rely on undefined or implementation dependent behaviour and is unlikely to work unless you use ascii only. Calling setlocale at start-up is necessary but not sufficient to fix these bugs. That said, you can close the bug if you want. I agree that calling setlocale alone is not particularly useful anymore now that xmonad proper does so much more than it used to. -- 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 109 in xmonad: Xmonad sometimes crashes when evince closes
by codesite-noreply＠google.com 26 Dec '07

26 Dec '07

Issue 109: Xmonad sometimes crashes when evince closes http://code.google.com/p/xmonad/issues/detail?id=109 Comment #2 by stucchio: Upgrading to 1.4.1 seems to have fixed things. With this fixed, xmonad is my perfect WM. Thanks. So the bug is with the documentation rather than the prgoram. A patch is attached, which just adds a note of this to the documentation: -- Note that XMonad and Xmonad-Contrib must be built using X11 1.4.1 or higher. -- There are bugs in older versions of X11 which are triggered by this module, -- which can cause xmonad to crash. If you experience crashing when using AvoidStruts, -- upgrade X11 to 1.4.1 and rebuild xmonad and xmonad-contrib. If you do this, -- remember that you must clean and reinstall xmonad and xmonad-contrib, and also -- remove ~/.xmonad/xmonad. Attachments: docfix.patch 7.0 KB -- 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

Sshprompt, Urxvt and TERM
by Dominik Bruhn 26 Dec '07

26 Dec '07

Hy, I use urxvt as my TerminalEmulator and I connect to several SSH servers and many of them havent got the terminfo for rxvt. This leads into many problems and errors on the remote-machines. Thats why I got this in my .bashrc: if [ "$TERM" = "rxvt-unicode" ]; then export TERM="xterm" #fixes ssh issues (rxvt-unicode unknown) fi This works fine as urxvt is xterm compatible and all my remote-machines know xterm. The problem is: If starting a ssh-session from the SSH-Prompt Module of XMonad this setting doesnt work because .bashrc isnt evaluated. I know this is not a XMonad-Fault but perhaps somebody got a hint how I can work arround this. Thanks -- Dominik Bruhn mailto: dominik(a)dbruhn.de

4 3

Issue 43 in xmonad: Call setlocale at startup
by codesite-noreply＠google.com 26 Dec '07

26 Dec '07

Issue 43: Call setlocale at startup http://code.google.com/p/xmonad/issues/detail?id=43 Comment #2 by andrea.rossato: yes, there are: the core doesn't produce output to be displayed by the X server, so, calling setlocale is quite useless, unless there are extensions using it (such as tabbed and xprompt). but both tabbed and xprompt do not support wide characters yet, so, calling setlocale remains useless. this is why we have this issue going around: I did some work towards i18n but we didn't decide what kind of approach to use. 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 43 in xmonad: Call setlocale at startup
by codesite-noreply＠google.com 25 Dec '07

25 Dec '07

Issue 43: Call setlocale at startup http://code.google.com/p/xmonad/issues/detail?id=43 Comment #1 by byorgey: What is the status of this defect? Are there arguments against calling 'setlocale' on startup? I'm not sure I understand all the issues here, just trying to do some general cleanup of defects. =) -- 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 34 in xmonad: focusedBorderColor does not follow focus that is requested by application
by codesite-noreply＠google.com 25 Dec '07

25 Dec '07

Issue 34: focusedBorderColor does not follow focus that is requested by application http://code.google.com/p/xmonad/issues/detail?id=34 Comment #2 by byorgey: Closing as requested. I'm pretty sure this analysis is accurate, that there is no way for xmonad to know about these sorts of focus changes requested by applications. Issue attribute updates: Status: Invalid -- 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 66 in xmonad: Component-Contrib ResizeableTile can put clients of screen and resize them bigger than screen.
by codesite-noreply＠google.com 25 Dec '07

25 Dec '07

Issue 66: Component-Contrib ResizeableTile can put clients of screen and resize them bigger than screen. http://code.google.com/p/xmonad/issues/detail?id=66 Comment #1 by byorgey: Is anyone able to provide more information on this defect? I am not able to reproduce it. -- 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 100 in xmonad: XMonad.Layout.ResizableTile fails if floating window present on same screen.
by codesite-noreply＠google.com 25 Dec '07

25 Dec '07

Issue 100: XMonad.Layout.ResizableTile fails if floating window present on same screen. http://code.google.com/p/xmonad/issues/detail?id=100 Comment #3 by byorgey: I just pushed a patch to darcs. It seems to work, but independent verification/testing is welcome. 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

Issue 90 in xmonad: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack
by codesite-noreply＠google.com 24 Dec '07

24 Dec '07

Issue 90: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack http://code.google.com/p/xmonad/issues/detail?id=90 Comment #4 by SpencerJanssen: We advertise 'spawnPipe' for use with status bars. This means that the status bar is re-launched every time xmonad is restarted. The status bar will be higher than existing windows in the stacking order, so the bar will appear over those windows when the status gaps are turned off. There's a workaround for dzen, but it's not very obvious. I'm leving this bug open until we can at least recommend some workaround for xmobar. Issue attribute updates: Status: Accepted -- 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 90 in xmonad: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack
by codesite-noreply＠google.com 24 Dec '07

24 Dec '07

Issue 90: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack http://code.google.com/p/xmonad/issues/detail?id=90 Comment #3 by andrea.rossato: since nothing has been reported about wrong documentation I'm marking this report as invalid. andrea Issue attribute updates: Status: Invalid -- 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