Age | Commit message (Collapse) | Author |
|
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: 6b75b18b41e855a3f64a423b929a7282
Originally: http://www.haskell.org/pipermail/xmonad/2008-June/005807.html
darcs-hash:20110525043413-8d3c4-53c2eae69ff246b869f4c5a617d9c0bba885f49f
|
|
Ignore-this: a71f3cb0507642e828f4bdfdc7ccd289
darcs-hash:20100222144512-1499c-f733b3d845d3d45da0713653796caae461b09b15
|
|
Ignore-this: 4ffb55dd97b59234703e0411c06b4901
darcs-hash:20091010231907-8d81a-2b2cc74d26f5f7dc7e071461a1bb976deb4e1c56
|
|
Ignore-this: 5b397417dfcf9014ac515a64484cc314
darcs-hash:20090622051911-8d81a-39e45893d4d6e613324c7548affbc34f6e313012
|
|
Ignore-this: da2e82037548ab176a4333056c94a07a
darcs-hash:20090622035649-8d81a-de848ab7c732ae633b5c21333370d5aca43bf939
|
|
http://code.google.com/p/xmonad/issues/detail?id=182
Ignore-this: bdfa33d3d06d7cf67fe689421f30a0ca
darcs-hash:20120113010410-f7719-04f51d6bbe88b291e4e388104c1350a27c203f80
|
|
Ignore-this: 642850f63b8c9cd44102e9883178d475
darcs-hash:20120113000115-f7719-4b4f31a1fd781030c83dd4bb9ac1dc4bfedfd29c
|
|
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: e27d6d60a16788192c0bb0399a597fb3
Thanks reenberg for pointing out the previous patch incorrectly warns about a
missing xmonad when the config has an error.
Also changed is "type" which as a shell builtin is more likely to exist than
"which".
darcs-hash:20111117042522-1499c-f0c882660e4e8ea02c601331e431a97b2585a2d1
|
|
Ignore-this: f77e1ba4fdb2c15635be379d6e5f58e9
darcs-hash:20100330003310-1499c-c2b0bdd897e6f87630b4c025544745acd157fcd3
|
|
Ignore-this: e3859ef530c04cb6c2c9bfec5cc412e1
darcs-hash:20111013162509-76d51-30199fdc9986b060dc592dba699291a3a6691a90
|
|
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: 1d5ef3e32540bbfbf60578858895d7c
darcs-hash:20110524015135-1499c-391404d33d5cdb8a5444c8bd016369eb033308c2
|
|
Ignore-this: 2328f5a2ca705279ba8ae1fe4decd03e
darcs-hash:20110224003021-8238f-5f37da8419ee25376f6c48da67b2ae781e89f4dd
|
|
Ignore-this: 518574016a9c15a741acdb6d2fa2e870
`Possibly empty' applies only to `Maybe (Stack a)', not `Stack a' described
there, so this is easier to understand.
darcs-hash:20110328001930-1499c-576faa6870919b21b02f5e6f16e413a2c197a3d5
|
|
Ignore-this: 8375f7011256783c763c78e127f89a4a
darcs-hash:20100403181115-1499c-d30cb037ab07f6b1d4774968a896139288e1bec2
|
|
Ignore-this: 436bd4d12e73c0fbb46a946d6dfb5306
darcs-hash:20100620175741-f7719-02c5812f3dc4a27f3ee77b8692a5d207a9732351
|
|
Ignore-this: 55ac1c5dadc88a0d7635d8952feb40a0
darcs-hash:20100415173936-c9ff5-505c98e1de70a1a5f616d8f3bb260a431d165f6c
|
|
Ignore-this: 5d61d6fd9a7663d0a7a1c8e2526230f7
darcs-hash:20100503155017-25a6b-af89c8923f42cde6478449da0584c643d5bf0a9c
|
|
darcs-hash:20090114215556-cb1c6-babaac0e9aeceba8006995aa1ae15d63cb35c724
|
|
Ignore-this: 68c0a43d761e626cb9544ca386f4846d
In xmonad-core, this fixes a small bug that caused doIgnored windows to get
into `mapped' and never being removed from there.
In the context of xmonad-contrib, this fixes a tremendous memory leak that
could be triggered by using MouseResizableTile and UrgencyHook at the same
time. MRT would create dummy windows that would get added to `mapped' by the
reveal call in `windows'. As these were not removed (removal from `mapped' is
filtered by `isClient'), they'd stay there forever and due to an inefficiency
in UrgencyHook would eat up all memory sooner or later.
darcs-hash:20100327214243-c9ff5-295429351d7a76e3fe82766bed70cb6951f5862e
|
|
Ignore-this: ccaa6e774f2f8169e6083eddcffe31b6
darcs-hash:20100214025750-25a6b-c15d6ca0ac2f1dc7d3da2f7b311584df7f96dffd
|
|
Ignore-this: c56000295b75c66309913e29e1671d88
darcs-hash:20091220183529-1499c-3c77980c6e443252334c118e2284fa7ed4933bff
|
|
Ignore-this: 60ba65613bc746e7e88f11a7e30b050f
darcs-hash:20100211063938-1499c-e32c4977f2e426d82550dcdddf5bb7d0e9d201d4
|
|
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: 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: 669c764c4c0ca516c8bdc1dfa35cd66
darcs-hash:20091216011700-25a6b-bfb30dfcc001e9b872402cd5adcb72af6fb65464
|
|
Ignore-this: af15248be5e483d1a6e924f786fcc1c4
darcs-hash:20091205233611-1499c-c79ec59901bb97416b25ecd5f1261a7a3331744b
|
|
Ignore-this: 22087204f1b84dae98a3cf2b7f116d3f
darcs-hash:20091119025440-25a6b-c9cfb15b2d5bc97c6610592b67d9cd098647c824
|
|
Ignore-this: d04ee1989313ed5710c94f9d7fda3f2a
darcs-hash:20091106115050-7f603-c88ce5e468856afd9e4d458ed3b0a2cfa39e63b3
|
|
Ignore-this: f73943e4fe6c5f08967ddb82afad3eaa
darcs-hash:20091106223743-25a6b-4dc0f10117fb79cd6eb62e9028463b524d504da5
|
|
Ignore-this: ba56921cc5b3be0462c41d10499ccf0e
darcs-hash:20090516104753-7ba7e-0d923bddc7747ae13d0b1c44179dfa12c6607075
|
|
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
|
|
Ignore-this: 13903f39b052c025a7bfa50fb701959c
darcs-hash:20090710011424-1499c-8199d3837913d876e78b58c539525d578b27206e
|
|
Ignore-this: 75804147fffeceddd328869cbca0d20f
What was previously:
> (appName ?= x <&&> classname ?= y) --> (doFloat <+> doIgnore)
Can now be:
> appName ?= x <&&> classname ?= y --> doFloat <+> doIgnore
darcs-hash:20090710011308-1499c-ce280fdfa6c53b5dc5e55eb9c6235867d2fedbd2
|
|
Ignore-this: f481f7d3ba5fca5c53a0b3a87daa32bb
darcs-hash:20090321233736-1499c-6e732e248211c129eba7b664fed681c97ae09020
|
|
darcs-hash:20090503154321-72cfd-985afe234c939954d49603f010939c93c072d2e8
|
|
Ignore-this: 3792043278932e371e3e2858913a2b17
darcs-hash:20090209183837-d17f0-da898b508e3a69f030de7de69c738065d1e8c81f
|
|
Ignore-this: 253c09de793715c18a029406795a42fd
darcs-hash:20090221230628-25a6b-7ea69e8aba9a539a05d096fed041852fb1df040c
|
|
This seems to be a rare case, but I just got hit by it.
darcs-hash:20090106192026-23c07-28a0137e2fed8c9923e6b7c49bc9407deaaccd5e
|