| Age | Commit message (Collapse) | Author |
|---|
|
Ignore-this: da2e82037548ab176a4333056c94a07a
darcs-hash:20090622035649-8d81a-de848ab7c732ae633b5c21333370d5aca43bf939
|
|
darcs-hash:20090114215556-cb1c6-babaac0e9aeceba8006995aa1ae15d63cb35c724
|
|
Ignore-this: c56000295b75c66309913e29e1671d88
darcs-hash:20091220183529-1499c-3c77980c6e443252334c118e2284fa7ed4933bff
|
|
Ignore-this: c8315f438fed66b12282c9bfe70a4d0b
darcs-hash:20100113204017-7f603-729f7e7ef83461c0bdd2e45cdd4a07724af7f8a2
|
|
Ignore-this: 4050ed2d1ad373386c2e2b44145f07d9
Without the change, the errors are like:
> [ unrelated error messages ]
> No constructor has all these fields: `numlockMask',
> `terminal', [every other field set]
With the change:
> `numlockMask' is not a record selector
> [ context where numlockMask is named ]
darcs-hash:20100118162256-1499c-c473138c7c8589e7a40fa17675fd5cafe2dc4c11
|
|
Ignore-this: d80c82dd0a23dc7a77fdc32fd2792130
darcs-hash:20091216012140-25a6b-1730d8fef04b735b04475d1772e4825fa44cb318
|
|
Ignore-this: 669c764c4c0ca516c8bdc1dfa35cd66
darcs-hash:20091216011700-25a6b-bfb30dfcc001e9b872402cd5adcb72af6fb65464
|
|
Ignore-this: d04ee1989313ed5710c94f9d7fda3f2a
darcs-hash:20091106115050-7f603-c88ce5e468856afd9e4d458ed3b0a2cfa39e63b3
|
|
Ignore-this: f22f1a7ae2d958ba1b3625aa923b7efd
darcs-hash:20090203155536-cb1c6-834084657dbd5699030c7dd6dbb1ab153763b631
|
|
Ignore-this: 45c8c8aba7cc7391b95c7e3fb01e5bf9
darcs-hash:20090117034959-25a6b-794fb65d26a59f6ca34b16538c35dc3c266ced7d
|
|
Ignore-this: f9b1a65b4f0622922f80ad2ab6c5a52f
This is a rather big change. Rather than make spawned processes become
children of init, we handle them in xmonad. As a side effect of this change,
we never need to use waitForProcess in any contrib module -- in fact, doing so
will raise an exception. The main benefit to handling SIGCHLD is that xmonad
can now be started with 'exec', and will correctly clean up after inherited
child processes.
darcs-hash:20090116204742-25a6b-9594fc6cdfcd5552894b64b4b6137f8a7cf2021d
|
|
darcs-hash:20090110221852-cb1c6-80f042287c9c6b704a37a2704e29841416aeca9b
|
|
Ignore-this: 3ac329fb92839827aed0a4370784cabd
darcs-hash:20081205045130-25a6b-971d40d7a853d12c2a34a1bfbd6ea77d6645af89
|
|
This is a modification of a patch from Joachim Breitner.
darcs-hash:20081106224031-25a6b-975b5af81ed6b1c3baa73015f3ff3dd009a31a9f
|
|
darcs-hash:20081021220059-25a6b-11b9b480bec9d902626f1c0c281333470e76e245
|
|
darcs-hash:20081007203953-25a6b-820e60a7db931a5e5e27ab8736643aea932ca3ec
|
|
darcs-hash:20080714202650-25a6b-294662e9b6b3592f37156af814171d5863557faa
|
|
If the user used the mouse to change window focus (moving into or clicking on a
window), this should be handled differently than focus changes due to keyboard
commands. Specifically, it's inappropriate to discard window enter/leave events
while the mouse is moving. This fixes the bug where a fast mouse motion across
multiple windows resulted in the wrong window keeping focus.
It's also helpful information for contrib modules such as UpdatePointer - it's
supposed to move the mouse pointer only in response to keyboard actions, not if
the user was moving the mouse.
darcs-hash:20080502175603-e41d7-0ac41e5353fcd8aed71ee3beb7f5511337225155
|
|
darcs-hash:20080418184337-cba2c-a316c61d1a56205e8b7a0e7b7573446449e229fe
|
|
darcs-hash:20080406011234-462cf-09fde81185653a210d292b90b02595de7c365bb1
|
