codehenry / xmonad

Automatically exported from code.google.com/p/xmonad
0 stars 0 forks source link

XMonad.Layout.IM doesn't match UTF8 chars #436

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I am encountering the same issue as per 
http://code.google.com/p/xmonad/issues/detail?id=302 using his same test case.

What steps will reproduce the problem?
1. Configure withIM layout to match a window title with UTF8 chars as
roster. Ex:
withIM (1%7) (Title "foo™") (Tall 1 0.5 0.5)
2. Run a window with the configured name. Ex:
xterm -T "foo™" -e read

What is the expected output? What do you see instead?
The window should be placed as withIM layout roster. In this case, on a
separated column to the left.

What version of the product are you using? On what operating system?
Latest XMonad Darcs on Arch X86_64.

Are you using an xmonad.hs?  Please attach it and the output of "xmonad
--recompile".
No output from xmonad --recompile.

Please provide any additional information below.

Comments from #xmonad having queried my issue:
<allbery_b> I'm looking at darcs... WindowProperties uses the ManageHook code 
(!! --- more evidence that it's mis-typed) and ManageHook.hs in the core uses 
getStringProperty everywhere
<allbery_b> (in particular it's using it for _NET_WM_* which is completely 
wrong as they are all defined as Unicode stored as 32 bit lists)
<allbery_b> suggest you reopen that bug report, or file a new one about 
_NET_WM_* being misinterpreted

I am attempting to match Skype's window title, which also contains the ™ 
character.

Original issue reported on code.google.com by o.a.stephens on 15 Feb 2011 at 3:14

Attachments:

GoogleCodeExporter commented 8 years ago
Latest xmonad package from Arch x86_64 repo have this problem too

Original comment by evvs...@gmail.com on 3 Apr 2011 at 1:27

GoogleCodeExporter commented 8 years ago
I have just built from HEAD, and this appears to work now.

Original comment by o.a.stephens on 2 May 2011 at 3:39

GoogleCodeExporter commented 8 years ago
I can't reproduce this bug either, so I'm closing it.

Original comment by vogt.a...@gmail.com on 16 Jul 2013 at 3:35