Issue 383 in xmonad: unescaped characters are sended to xmobar

Status: New Owner: ---- New issue 383 by alsergbox: unescaped characters are sended to xmobar http://code.google.com/p/xmonad/issues/detail?id=383 What steps will reproduce the problem? 1. Configuring xmonad for xmobar with xmproc <- spawnPipe "xmobar -t '%StdinReader% }{' -c '[ Run StdinReader ]' -o" ... logHook = dynamicLogWithPP xmobarPP { ppOutput = hPutStrLn xmproc , ppTitle = xmobarColor "green" "" . shorten 50 , ppUrgent = xmobarColor "black" "red" } 2. Open a window with something like tags in the title, e.g. open http://bisoncpp.sourceforge.net/bisonc++.html in firefox 3. xmobar writes "couldn't parse string... " and doesn't parse it, displays as a plain text What is the expected output? What do you see instead? What version of the product are you using? On what operating system? xmonad 0.9.1 xmobar 0.9.2 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. Attachments: xmonad.hs 16.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

Updates: Labels: Priority-Low Type-Defect Component-Contrib Comment #1 on issue 383 by vogt.adam: unescaped characters are sended to xmobar http://code.google.com/p/xmonad/issues/detail?id=383 This is mostly an xmobar problem: DynamicLog could do some escaping, however, once that is implemented in xmobar, the appropriate escapeXMobar can be added. The bug for xmobar is here: http://code.google.com/p/xmobar/issues/detail?id=22 -- 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
participants (1)
-
codesite-noreply@google.com