So are we going to do anything about Google Code Issues going away in a
little over two weeks?
--
brandon s allbery kf8nh sine nomine associates
allbery.b(a)gmail.com ballbery(a)sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Are there any blockers that would prevent cutting a release of current
Darcs HEAD to go with the soon to be released GHC 7.10.2?
It seems many users install from Darcs anyway, so it appears
reasonable to me.
Hi.
I recently changed from using xterm to sakura:
* https://code.launchpad.net/sakura
(primarily because the fonts in xterm look bad when scaled x1.5, and I
have to do that on my stationary monitor...)
The sakura windows automatically get a thin transparent border with
XMonad, through which my desktop background image shows.
I would like for this to not happen - as it is distracting.
You can see the unwanted effect here:
* http://koldfront.dk/misc/xmonad/sakura-xmonad.png
compared to what it looks like with xterm:
* http://koldfront.dk/misc/xmonad/uxterm-xmonad.png
I have tried searching the sakura code and changing random things
related to border, rgba, and transparent, but my wild guesses have not
been fruitful.
Does anyone have any good ideas?
I am using running compton (I like the pretty, transparent
notifications), in case that matters.
OH! I just tried killing compton, and that removed the problem! I guess
I should bark up another, uhm, mailing list?
Hm, I found this: https://github.com/chjj/compton/issues/139 which is
the same problem with another wm, compton, and sakura, and it seems the
wm was fixed - so maybe I am in the right place after all?
There are some hints here: https://github.com/chjj/compton/issues/240
about what might be the same issue in xmonad.
Best regards,
Adam
--
"Hackers are lazy, in the same way that Adam Sjøgren
mathematicians and modernist architects are lazy: asjo(a)koldfront.dk
they hate anything extraneous."
Dear List,
Is it possible to render things in the XServer with multiple threads? For
example:
dpy <- asks display
myWin <- createSimpleWindow dpy (defaultRootWindow dpy) 0 0 10 10 black
white
_ <- forkOS $ do
-- doStuff with myWin using dpy
When I attempt doing things like that, I usually get a deadlock. Is there
any way to do this (I know, X is old :( but no harm in asking).
Thank you and best regards,
Ernesto Rodriguez
--
Ernesto Rodriguez
Masters Student
Computer Science
Utrecht University
www.netowork.megithub.com/netogallo
I love that insertPosition can keep new windows from going into the
master area, but there's one small annoyance w.r.t. transient floating
windows.
I'm using `insertPosition Below Newer` with `composeOne`. When a
password dialog appears, and the master window previously had the focus,
the dialog gets focused and is put in the center of the screen. That
part is perfect.
The problem comes when I dismiss the dialog. At that point I would
expect the master window to regain focus, but one of the slave windows
does instead. Of course, removing `insertPosition` fixes my issue.
This is what I have in my configuration in an attempt to avoid this
issue:
composeOne
[ pure True -?> insertPosition Below Newer
, isFloating -?> doCenterFloat
]
`isFloating` comes from XMonad.Hooks.FadeWindows and I have it in there
hoping to *not* apply `insertPosition` when the current window is
already floating.
Any suggestions?
--
Peter Jones, Founder, Devalot.com
Defending the honor of good code
