Issue 531 in xmonad: Multiple workspaces with the same name confuses XMonad
Status: New Owner: ---- New issue 531 by erdnussb...@gmail.com: Multiple workspaces with the same name confuses XMonad http://code.google.com/p/xmonad/issues/detail?id=531 What is the expected output? What do you see instead? I expect that xmonad differs between workspaces even if they have the same name. The following describes the scenarios you run into when naming multiple workspaces identically. ------------------- Scenario 1: ------------------- How to produce: 1. Give some workspaces the same name. 2. Restart and recompile XMonad. What happens: The renamed workspaces are added uselessly to the beginng of the list. (see picture 1.png) ------------------- Scenario 2: ------------------- How to produce: 1. Start from scenario 1. 2. Restart X. What happens: XMonad shows all the workspaces separately but addresses them as one (see picture 2.png). Additional information: If you switch between two workspaces with the same name, xmonad loads the content again (you see it flicker) but the content is the same. ------------------- Scenario 3a: ------------------- How to produce: 1. Start from scenario 2. 2. Change one of the former identical workspace names to something unique. 3. Recompile and restart XMonad. What happens: XMonad displays mutliple times the unique name?! (see picture 3a.png) Additional information: From this point on, recompiling and restarting doesn't fix the corruption of the running XMonad session. ------------------- Scenario 3b: ------------------- How to produce: 1. Start from Scenario 3a 2. Restart X What happens: The multiple workspaces are shown again, still addresses as one, but the uniquely named workspace is displayed and addressed correctly. (see picture 3b.png) ------------------- Scenario 3c: ------------------- How to produce: 1. Start from Scenario 3b. 2. Change all workspace names to something unique again. 3. Recompile and Restart Xmonad. What happens: The doesn't have the intended effect, instead some workspace keys stop working and a random one is shown mutliple times. (see picture 3c.png) Restarting X fixes this issue. 4. Start with Scenario 1 again, it's fun (: ------------------- What version of the product are you using? On what operating system? Linux ******* 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux (wheezy) xmonad 0.10 ------------------- Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Yes I'm using it, there are no compilation errors. ------------------- Please provide any additional information below. Dzen2 and Xmobar showed the same effects. Attachments: 1.png 116 KB 2.png 122 KB 3a.png 137 KB 3b.png 115 KB 3c.png 116 KB xmonad.hs 10.8 KB
Comment #1 on issue 531 by allber...@gmail.com: Multiple workspaces with the same name confuses XMonad http://code.google.com/p/xmonad/issues/detail?id=531 Why would you expect that? The tag ("name") is the only externally visible handle xmonad has on a workspace. It's conceivable that other window managers use internal names for workspaces and let you map many of those to the same display name, but xmonad uses the tag as the workspace's real name and expects the tag to be unique. (In fact I am a little surprised xmonad doesn't check and complain when tags aren't unique.) There are ways to get display names that differ from the internal tag, but you'll have to do extra work to get them. (You can for example modify or replace the names that DynamicLog sends to an external panel, which is often used to add clickable icons in dzen.)
Comment #2 on issue 531 by erdnussb...@gmail.com: Multiple workspaces with the same name confuses XMonad http://code.google.com/p/xmonad/issues/detail?id=531 I expected this behavior because i thought i was giving xmnoad an array of names for the workspaces, but internally they are still handled through indices. But you are totally right, it should have been obvious, due to the fact of how i handle the workspaces in the config... Nevertheless an error would be great, i've been confronted with mad randomness for hours until i found the source for my troubles (:
Comment #3 on issue 531 by killian....@megasoft.be: Multiple workspaces with the same name confuses XMonad http://code.google.com/p/xmonad/issues/detail?id=531 Maybe related, not sure: But using renameWorkspace I named 2 workspaces the name. When the workspace was selected xmobar was showing "WorkSName WorkSName". I was unable to navigate to the second WorkSName. So I renamed this one using renameWorkspace to something else, that worked. However when I went back to WorkSName xmonad crashed: xmonad-x86_64-l[5507]: segfault at 40 ip 00007f140991aa23 sp 00007fff4d5f4908 error 4 in libX11.so.6.3.0[7f14098b7000+13c000] -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
Comment #4 on issue 531 by allber...@gmail.com: Multiple workspaces with the same name confuses XMonad http://code.google.com/p/xmonad/issues/detail?id=531 killian.de.volder@megasoft.be, any chance you can get a backtrace from that crash? (usually this indicates problems with the haskell X11 bindings) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
participants (1)
-
codesite-noreply＠google.com