| Age | Commit message (Collapse) | Author |
|---|
|
Ignore-this: 42a6a8599b615884c95626f74e3ba4a
The -main-is flag goes back to at least ghc 6.10, and maybe the warning that
this otherwise redundant flag enables (when xmonad.hs isn't a module Main)
also dates back that far.
darcs-hash:20130101035034-1499c-fd2fa2fef7c36882fa529f3f96777453b0b14d1c
|
|
Ignore-this: 78961f6256e1a1ee25c085e9056af758
To summarize this allows clicks which change the focus to also be passed on to
that window.
darcs-hash:20120103013916-1499c-1c29f13f0565f4812cf5787caefb6142882f25b5
|
|
Ignore-this: 5b397417dfcf9014ac515a64484cc314
darcs-hash:20090622051911-8d81a-39e45893d4d6e613324c7548affbc34f6e313012
|
|
Ignore-this: da2e82037548ab176a4333056c94a07a
darcs-hash:20090622035649-8d81a-de848ab7c732ae633b5c21333370d5aca43bf939
|
|
Ignore-this: efc21bae061768ad15a36a5f7b6aeb87
darcs-hash:20120430154222-1499c-c80ecae7b87b5115723362ad3c5698e875608a66
|
|
Ignore-this: ea27391896e898f1288764ea40bc9661
This adds the utf8-string dependency so that users no longer need to encode
strings they (possibly indirectly) pass to spawn. This is the expected
behavior, since each Char in String should be an actual character.
For systems that do not use utf8 this does not help. Fixing this by using iconv
or similar libraries may be done later.
darcs-hash:20111118182920-1499c-a28ab3ef902a76cd50fa190526c00ccb4c7b6437
|
|
Ignore-this: 5f4c8907066e1ea5df3f384a34951402
darcs-hash:20110609042424-1499c-bc1a04152e8f19d14d01604144b9d202affcc660
|
|
Ignore-this: 6249588a9d427a49fceb99d78a95c438
Currently if there is no ghc on the path say for some reason,
xmonad.error is empty. This patch makes
it output the exitcode code when the compile process fails
without any error output. (It might be easier just to spawn
a shell to get "ghc: command not found" output for free.)
darcs-hash:20110426062341-2376b-eb9466e5933a53138d24b3492260a618c239acd3
|
|
Ignore-this: 8f9e33a86a9919406792383c49ac4555
This gets rid of a warning with ghc-7.0.2, and -XDeriveDataTypeable seems to
have been added with 6.8, which should be far back enough:
http://www.haskell.org/ghc/docs/6.8-latest/html/users_guide/deriving.html#deriving-typeable
darcs-hash:20110608230415-1499c-2929ccda56381f501e548f5a00e7d8f03e80c016
|
|
Ignore-this: e3ab1e9940061a70a3c1c99a119af29e
While haddock may have choked on -XGeneralizedNewtypeDeriving before, this is
no longer the case. Also this doesn't change the results with a recent haddock
(2.9.2)
darcs-hash:20110608225613-1499c-d14443aa6cfd522bc70d9e6167993bf8c310ca7e
|
|
Ignore-this: 8375f7011256783c763c78e127f89a4a
darcs-hash:20100403181115-1499c-d30cb037ab07f6b1d4774968a896139288e1bec2
|
|
Ignore-this: 436bd4d12e73c0fbb46a946d6dfb5306
darcs-hash:20100620175741-f7719-02c5812f3dc4a27f3ee77b8692a5d207a9732351
|
|
Ignore-this: ccaa6e774f2f8169e6083eddcffe31b6
darcs-hash:20100214025750-25a6b-c15d6ca0ac2f1dc7d3da2f7b311584df7f96dffd
|
|
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: a48ed095b72aedec9eeb88781ace66dc
Changes include:
- compatibility with base-4 or 3 (base-2 untested) by using
extensible-exceptions. This adds an additional dependency for users of
ghc<6.10)
- list all dependencies again when -ftesting (change in Cabal-1.8.0.2)
- remove unnecessary imports
- suppress -fwarn-unused-do-bind, with appropriate Cabal-1.8 workaround,
described here:
http://www.haskell.org/pipermail/xmonad/2010-January/009554.html
darcs-hash:20100118181532-1499c-5c496678ef76f2f50b43b0fc4582cfef7c237654
|
|
Ignore-this: 3f968260d8c1b6710c82566520c47c43
darcs-hash:20091223061623-25a6b-3b3cc5f1a12543336e5b8581f9798989c4d848ac
|
|
Ignore-this: d80c82dd0a23dc7a77fdc32fd2792130
darcs-hash:20091216012140-25a6b-1730d8fef04b735b04475d1772e4825fa44cb318
|
|
Ignore-this: d04ee1989313ed5710c94f9d7fda3f2a
darcs-hash:20091106115050-7f603-c88ce5e468856afd9e4d458ed3b0a2cfa39e63b3
|
|
Ignore-this: f73943e4fe6c5f08967ddb82afad3eaa
darcs-hash:20091106223743-25a6b-4dc0f10117fb79cd6eb62e9028463b524d504da5
|
|
Ignore-this: aefa46cdb3ad8496e20d15a7e6b5fa52
darcs-hash:20090918035547-25a6b-626adbc3a96a55063577fe31043b53cc14264966
|
|
Ignore-this: e3b1847edf3e07a8182f7fcfc23b00c8
Previously xmonad would force a recompile due to the object files being too
new, so only look at files which may contain haskell code.
darcs-hash:20090503235415-1499c-50100b58df81d6e0506bbaf937b476a018064271
|
|
Ignore-this: 8827fb02fe1101d7b66f05d363bef038
darcs-hash:20090321232907-1499c-69dd8a1d22d2c8f28a6545ec20713d519dbc7ac4
|
|
darcs-hash:20090208165518-cba2c-2f7506b8ab856d7081a3298ed4cff86149fe0742
|
|
Ignore-this: f22f1a7ae2d958ba1b3625aa923b7efd
darcs-hash:20090203155536-cb1c6-834084657dbd5699030c7dd6dbb1ab153763b631
|
|
Ignore-this: bb155e62ea4e451460e3b94508dc49d2
darcs-hash:20090128215406-cb1c6-89d81563549a976a6c9abd1e1dcc5c0e1412c9e5
|
|
Ignore-this: d91bde6f965341a2619fe2dde83cc099
darcs-hash:20090122002643-25a6b-7aea3d61d968ccdec5ad304043910bd30120aabe
|
|
Ignore-this: f5d9cf254a0b07ddbf204457b7783880
darcs-hash:20090122000423-25a6b-953d34966aee5389a1e13368b5ab2a9d5dd4f7d1
|
|
Ignore-this: 2e372ed6215160adae8da1c44cdede3d
darcs-hash:20090117040024-25a6b-4083a1b37e7f5c55cb7ee03c5edf46350bacdbf0
|
|
Ignore-this: 1641bdcf5055b2ec7b9455265f5b1d52
darcs-hash:20090117035907-25a6b-1bd8e7677c7beff72fb78f74c053adb5f3fcfde3
|
|
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
|
|
darcs-hash:20080927234639-78224-1f1797ff1808ac3a82f694b87c2a7514ffac549e
|
|
darcs-hash:20081007203953-25a6b-820e60a7db931a5e5e27ab8736643aea932ca3ec
|
|
darcs-hash:20080601212515-1ef02-00edd6567c840d7fec8ee7ed085b3cd2655ad6e3
|
|
darcs-hash:20080601204951-1ef02-f66c70867a91bc35da3ab71b1169db4ba1ee62fe
|
|
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:20080325091526-a5988-e6ed58b0d493845525a4c7e5977352cfb12b9c92
|
|
darcs-hash:20080324225857-a5988-623d8ab2a19923bccfe32f8adb23320004912831
|
|
This patch:
- moves broadcastMessage and restart from Core to Operations (to avoid
circular imports);
- in Operations introduces sendMessageWithNoRefresh and move
updateLayout outside windows.
- broadcastMessage now uses sendMessageWithNoRefresh to obey to this
rules:
1. if handleMessage returns Nothing no action is taken;
2. if handleMessage returns a Just ml *only* the layout field of the
workspace record will be updated.
darcs-hash:20080223130702-32816-60d71cd8ac32cff1d4039947142332023274a725
|
|
darcs-hash:20080322041654-cba2c-a02ffa00d03a515c00ba04f7efd0281982769e22
|
|
darcs-hash:20080321230956-cba2c-5248cdf7b5694cbfaf2b6ba754ebc3c8a7fbd592
|
|
darcs-hash:20080311160727-bd4d7-05229354077a443abab79de16b60ac32728813a3
|
|
Rectangle
darcs-hash:20080222175815-32816-e3893760e1024bcbf30a4fbb71ca7c2b4d8bb403
|
|
The only thing I am not sure about here is at what exact point the
startupHook should get run. I picked a place that seems to make sense:
as late as possible, right before entering the main loop. That way all
the layouts/workspaces/other state are set up and the startupHook can
manipulate them.
darcs-hash:20080204192445-bd4d7-218d69dcf3cd5c5f2962859cf847595527399807
|
|
darcs-hash:20080204192348-bd4d7-6a4edc163de3ea931a60050e4ad107390afc972e
|
|
darcs-hash:20080206190521-cba2c-1c7303b14bf1c907e0f75e9c3bb44a033cc9734e
|
|
darcs-hash:20080204053336-a5988-0c8760f33f319acd30cd18630ada2b77a0875a5b
|
|
darcs-hash:20080203202852-c98ca-e5c645e2332821ccc99587ba6562932860f6d9e6
|
|
darcs-hash:20080201190653-bd4d7-767473ef51a27bfdbadead306a1c3250dcaafaab
|
