Ruslan Kiianchuk | 17 Aug 02:06 2014
Picon

Dim unfocused windows

Hello.

So there is XMonad.Hooks.FadeWindows module that allows to make unfocused windows slightly transparent.

But is it possible to just dim unfocused windows without changing their opacity (the way fadeing option does this for URXVT?).

Thanks.

--
Sincerely, Ruslan Kiianchuk.
<div><div dir="ltr">
<div>
<div>Hello.<br><br>So there is <a href="http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-FadeWindows.html">XMonad.Hooks.FadeWindows</a> module that allows to make unfocused windows slightly transparent.<br><br>
</div>But is it possible to just dim unfocused windows without changing their opacity (the way <span>fadeing</span> option does this for URXVT?).<br><br>
</div>Thanks.<br clear="all"><div><div><div>
<br>-- <br><div>Sincerely, Ruslan Kiianchuk.</div>
</div></div></div>
</div></div>
Klaas van Schelven | 12 Aug 09:24 2014

Bug? garbage screen when switching virtual workspaces.

I suppose I should start with a rant on how XMonad sucks to get everyone's attention. However, truth is I've been enjoying xmonad for some c. 5 years now, without any problems whatsoever. However: 

I've recently upgraded my Ubuntu from 10.04 to 14.04.

Xmonad appeared to work after changing the syntax of dmenu_run and recompiling.
However, sometimes when switching workspaces, I end up with with some garbage window with the following properties:

* slightly offset to the bottom & right from the normal location (slightly means: a couple of pixels)
* the area usually contains the contents of the window that was displaying right before making the switch (but as I set, slightly offset to the right & bottom)
* usually the window is killable using my standard kill-key-combo.
* It appears (though I'm not sure) that google-chrome if often involved in this. One observed behavior: after killing the "ghost window" everything seemed to work fine again, except that chrome was gone. Tentative conclusion: the ghost window was in fact chrome.
* My "unfloat" modifier (Mod-T) doesn't change anything

When observing the above, I just run windows full screen and use various workspaces for the various windows.

* A behavior that appears related: in a few cases I did not manage to get rid of the ghost window. In those cases I got some kind of mosaic inside the full-screen chrome window, comprised of ca. 5 times 5 smaller, mirrored rectangles which contained part of chrome. I'll try to make a screenshot next time this happens.

I'm sorry if the problem description is somewhat vague, and/or if I'm not using the correct terminology.
As I said, I've set up XMonad years ago, and haven't changed a thing since so I'm somewhat lost for the right words at times (the correct terminology is in my fingers)
Any pointers to debugging this problem or requests for specifc configs/logs are welcome.


regards,
Klaas
<div><div dir="ltr">
<div>I suppose I should start with a rant on how XMonad sucks to get everyone's attention. However, truth is I've been enjoying xmonad for some c. 5 years now, without any problems whatsoever. However:&nbsp;</div>

<div><br></div>
<div>I've recently upgraded my Ubuntu from 10.04 to 14.04.</div>
<div><br></div>
<div>Xmonad appeared to work after changing the syntax of dmenu_run and recompiling.</div>
<div>However, sometimes when switching workspaces, I end up with with some garbage window with the following properties:</div>

<div><br></div>
<div>* slightly offset to the bottom &amp; right from the normal location (slightly means: a couple of pixels)</div>
<div>* the area usually contains the contents of the window that was displaying right before making the switch (but as I set, slightly offset to the right &amp; bottom)</div>

<div>* usually the window is killable using my standard kill-key-combo.</div>
<div>* It appears (though I'm not sure) that google-chrome if often involved in this. One observed behavior: after killing the "ghost window" everything seemed to work fine again, except that chrome was gone. Tentative conclusion: the ghost window was in fact chrome.</div>

<div>* My "unfloat" modifier (Mod-T) doesn't change anything</div>
<div><br></div>
<div>When observing the above, I just run windows full screen and use various workspaces for the various windows.</div>
<div><br></div>
<div>* A behavior that appears related: in a few cases I did not manage to get rid of the ghost window. In those cases I got some kind of mosaic inside the full-screen chrome window, comprised of ca. 5 times 5 smaller, mirrored rectangles which contained part of chrome. I'll try to make a screenshot next time this happens.</div>

<div><br></div>
<div>I'm sorry if the problem description is somewhat vague, and/or if I'm not using the correct terminology.</div>
<div>As I said, I've set up XMonad years ago, and haven't changed a thing since so I'm somewhat lost for the right words at times (the correct terminology is in my fingers)</div>

<div>Any pointers to debugging this problem or requests for specifc configs/logs are welcome.</div>
<div><br></div>
<br><div>regards,</div>
<div>Klaas</div>
</div></div>
codesite | 8 Aug 10:41 2014
Picon

Issue 576 in xmonad: On FreeBSD Xmonad loses first hotkey sometimes

Status: New
Owner: ----

New issue 576 by martin.s...@...: On FreeBSD Xmonad loses first  
hotkey sometimes
http://code.google.com/p/xmonad/issues/detail?id=576

What steps will reproduce the problem?

1. Install FreeBSD (amd64).
2. Write a minimal xmonad.hs with xterm binding.
3. Start xmonad in Xorg.
4. Try (multiple times) Mod+Shift+Return.

What is the expected output? What do you see instead?

It's expected that xterm opens with the first time Mod+Shift+Return is  
pressed. Sometimes Xmonad loses the key-combo and you need to press it  
twice in fast succession. If you wait too long between the first and the  
second time in sequence, the hotkey will be lost again and again.

I repeat once again: it happens SOMETIMES, but on average every 4th time.  
Try to open terminal and exit it again (Mod+Shift+Return -> Ctrl-D ->  
Mod+Shift+Return -> Ctrl-D -> ...).

What version of the product are you using? On what operating system?

hs-xmonad-0.11_7

FreeBSD 10.0 RELEASE (amd64).

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

You don't need mine. Use a minimal one:

import XMonad

main = xmonad defaultConfig
         { modMask = mod1Mask
         , terminal = "xterm"
         }

Additional info:
Cannot be reproduced on Linux. Everything works as expected there.

--

-- 
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
codesite | 7 Aug 22:31 2014
Picon

Re: Issue 168 in xmonad: gnome-panel with autohide enabled appears behind main windows


Comment #10 on issue 168 by jhy...@...: gnome-panel with
autohide  
enabled appears behind main windows
http://code.google.com/p/xmonad/issues/detail?id=168

Any update on this?  I am thinking of switching to a tiling window manager.

--

-- 
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
codesite | 5 Aug 01:19 2014
Picon

Issue 575 in xmonad: Typo on web page

Status: New
Owner: ----

New issue 575 by rrt <at> sc3d.org: Typo on web page
http://code.google.com/p/xmonad/issues/detail?id=575


xmonad.org/tour.html

"ito" → "into"


-- 
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

_______________________________________________
xmonad mailing list
xmonad <at> haskell.org
http://www.haskell.org/mailman/listinfo/xmonad
allbery.b | 3 Aug 04:08 2014
Picon

darcs patch: config-mate

** tested version **

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 22:06:59 EDT 2014  allbery.b@...
  * config-mate
  Initial support for the Mate desktop environment (http://mate-desktop.org).
  Based on existing Gnome 2 support, since Mate is a maintained fork of
  Gnome 2.

Attachment (patch-preview.txt): text/x-darcs-patch, 3541 bytes
Attachment (config_mate.dpatch): application/x-darcs-patch, 21 KiB
** tested version **

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 22:06:59 EDT 2014  allbery.b@...
  * config-mate
  Initial support for the Mate desktop environment (http://mate-desktop.org).
  Based on existing Gnome 2 support, since Mate is a maintained fork of
  Gnome 2.

allbery.b | 3 Aug 04:08 2014
Picon

darcs patch: debug-managehook

** tested version **

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 22:06:01 EDT 2014  allbery.b@...
  * debug-managehook
  A set of hooks, and convenience combinators, to help with ManageHook debugging.
  Ordinary users may well want to use debugManageHookOn in normal configs,
  specifying a key sequence which can be pressed before running a command in
  order to capture debug information just for that command's main window.

  This is especially useful when trying to diagnose issues such as programs
  that do not play well with SpawnOn, or ManageHook matching on 'title' when
  the program does not set the window title until after it is mapped.

Attachment (patch-preview.txt): text/x-darcs-patch, 5520 bytes
Attachment (debug_managehook.dpatch): application/x-darcs-patch, 23 KiB
** tested version **

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 22:06:01 EDT 2014  allbery.b@...
  * debug-managehook
  A set of hooks, and convenience combinators, to help with ManageHook debugging.
  Ordinary users may well want to use debugManageHookOn in normal configs,
  specifying a key sequence which can be pressed before running a command in
  order to capture debug information just for that command's main window.

  This is especially useful when trying to diagnose issues such as programs
  that do not play well with SpawnOn, or ManageHook matching on 'title' when
  the program does not set the window title until after it is mapped.

allbery.b | 3 Aug 04:07 2014
Picon

darcs patch: debug-debug

** tested version **

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 22:05:30 EDT 2014  allbery.b@...
  * debug-debug
  Various fixes and enhancements to DebugWindow and DebugStack. ManageDebug
  requires these fixes, but some of them are significant even if not using
  ManageDebug.

Attachment (patch-preview.txt): text/x-darcs-patch, 12 KiB
Attachment (debug_debug.dpatch): application/x-darcs-patch, 30 KiB
** tested version **

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 22:05:30 EDT 2014  allbery.b@...
  * debug-debug
  Various fixes and enhancements to DebugWindow and DebugStack. ManageDebug
  requires these fixes, but some of them are significant even if not using
  ManageDebug.

allbery.b | 3 Aug 03:56 2014
Picon

darcs patch: debug-managehook

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 21:51:24 EDT 2014  allbery.b@...
  * debug-managehook
  A set of hooks, and convenience combinators, to help with ManageHook debugging.
  Ordinary users may well want to use debugManageHookOn in normal configs,
  specifying a key sequence which can be pressed before running a command in
  order to capture debug information just for that command's main window.

  This is especially useful when trying to diagnose issues such as programs
  that do not play well with SpawnOn, or ManageHook matching on 'title' when
  the program does not set the window title until after it is mapped.
Attachment (patch-preview.txt): text/x-darcs-patch, 5135 bytes
Attachment (debug_managehook.dpatch): application/x-darcs-patch, 22 KiB
1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 21:51:24 EDT 2014  allbery.b@...
  * debug-managehook
  A set of hooks, and convenience combinators, to help with ManageHook debugging.
  Ordinary users may well want to use debugManageHookOn in normal configs,
  specifying a key sequence which can be pressed before running a command in
  order to capture debug information just for that command's main window.

  This is especially useful when trying to diagnose issues such as programs
  that do not play well with SpawnOn, or ManageHook matching on 'title' when
  the program does not set the window title until after it is mapped.
allbery.b | 3 Aug 03:55 2014
Picon

darcs patch: debug-debug

1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 21:49:01 EDT 2014  allbery.b@...
  * debug-debug
  Various fixes and enhancements to DebugWindow and DebugStack. ManageDebug
  requires these fixes, but some of them are significant even if not using
  ManageDebug.
Attachment (patch-preview.txt): text/x-darcs-patch, 12 KiB
Attachment (debug_debug.dpatch): application/x-darcs-patch, 30 KiB
1 patch for repository http://code.haskell.org/XMonadContrib:

Sat Aug  2 21:49:01 EDT 2014  allbery.b@...
  * debug-debug
  Various fixes and enhancements to DebugWindow and DebugStack. ManageDebug
  requires these fixes, but some of them are significant even if not using
  ManageDebug.
Joachim Breitner | 3 Jul 07:44 2014
Picon

darcs patch: needs update for mplayer2

1 patch for repository http://code.haskell.org/xmonad:

Thu Jul  3 07:43:59 CEST 2014  Joey Hess <joeyh@...>
  * needs update for mplayer2

  xmonad floats mplayer by default. However, Debian has switched to
  mplayer2, and so on upgrade, it will stop floating. This can be easily
  fixed in the user's config file, but here is a patch that avoids
  bothering the user with breakage on upgrade.
Attachment (patch-preview.txt): text/x-darcs-patch, 760 bytes
Attachment (needs-update-for-mplayer2.dpatch): application/x-darcs-patch, 8 KiB
1 patch for repository http://code.haskell.org/xmonad:

Thu Jul  3 07:43:59 CEST 2014  Joey Hess <joeyh@...>
  * needs update for mplayer2

  xmonad floats mplayer by default. However, Debian has switched to
  mplayer2, and so on upgrade, it will stop floating. This can be easily
  fixed in the user's config file, but here is a patch that avoids
  bothering the user with breakage on upgrade.

Gmane