July 2008 - xmonad - Haskell.org

Home page redesign
by Devin Mullins 24 Jul '08

24 Jul '08

So, I've been toying with the idea of redesigning the home page, such that everything fits above the fold, and there's a semi-traditional right side navbar. (Making the nav bar sections have red borders on hover, how cute.) I'm not too interested in messing with the colorscheme, partly because I'm no good at actual visual design, and partly because I like the whole blast from the past thing. Is this a patch(set) you'd accept (for a sufficient definition of 'you')? Furthermore, is there any ego attached to the current html/css coding style? I'd like to apply my obsessive whitespace cleanup to it, along the way, and get rid of some cruft. I'm thinking the left side would have the about and features sections, and the right side would consist of this, approximately: - Home (What) - Google CSE - Download (Where) - pkgs from different linuxen - core - contrib - install instructions? - darcs - related tools - About (Why) - intro tutorial - screenshots - videos - reviews - Docs (How) - guide through contrib - FAQ - wiki - API docs (starting with andrea's config/extend/develop pages) - News (When) - from the xmonad team - in the press/blogs - Community (Who) - mailing list - irc - t-shirts - credits

9 34

Issue 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 23 Jul '08

23 Jul '08

Issue 199: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 Comment #6 by allbery.b: I will repeat here something I mentioned on the xmonad list: there are problems like this scattered through the contribs. One I'm specifically aware of is in SshPrompt, which assumes ~/.ssh/known_hosts is always readable; this is problematic if $HOME is on an authenticated network filesystem and the authentication token expires. (Keeping ~/.ssh readable for public keys is not so useful when you need to get such a token on login; usually (NFSv4, AFS) this means using Kerberos for authentication, which is incompatible with public keys.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 23 Jul '08

23 Jul '08

Issue 199: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 Comment #5 by allbery.b: He did say "something like"; I figure he just forgot the "!". -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 145 in xmonad: Misplaced menus in openoffice with gtk widgets
by codesite-noreply＠google.com 23 Jul '08

23 Jul '08

Issue 145: Misplaced menus in openoffice with gtk widgets http://code.google.com/p/xmonad/issues/detail?id=145 Comment #8 by itsjdh: No longer a problem for me with OO.o 3.0 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 23 Jul '08

23 Jul '08

Issue 199: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 Comment #4 by m...(a)cloudconnected.org: byorgey, your loop suggestion is a good idea, but it looks weird. Once XMonad returns !=0 as is likely the case with a crash, the loop would stop. I'd go for a while ! xmonad or just a while true. Also, XMonad never crashed except for this one. :) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 23 Jul '08

23 Jul '08

Issue 199: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 Comment #3 by byorgey: Hmm, if it is crashing that is indeed a bug. But I am still unable to reproduce it. When I try this, nothing happens, xmonad keeps running as normal. Can other people try reproducing this as well? I am especially interested to know if this happens in 0.7 but not in latest darcs. Also, you may be interested to know that if you put xmonad in a loop in your .xsession or .xinitrc, something like this: while $HOME/local/bin/xmonad; do sleep 2; done then it will transparently restart itself in case a crash unexpectedly occurs. Of course, this is just a bandaid; xmonad should not crash, and fixing it when it does is a high priority for us. But this sort of thing can save you inconvenience if it does occasionally crash. Issue attribute updates: Labels: Component-Contrib -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 23 Jul '08

23 Jul '08

Issue 199: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 Comment #2 by m...(a)cloudconnected.org: It means, that XMonad will exit, therefore X will exit and I'm back at the console. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

A New Solution to Removing the GHC Dependency
by Braden Shepherdson 22 Jul '08

22 Jul '08

Hi, Note first as a caveat that I've had three hours' sleep in the last 36. That said, I'm not the only person who thinks this is a good, and practical, idea. Requiring GHC as a dependency is a real drag on evangelizing xmonad, and for adoption. The payout, of course, is having the full power of Haskell in our configurations. But GHC is a very, very heavy dependency for someone who doesn't already have it, and it raises the bar to running xmonad. This led to the creation of PlainConfig, but while that removes the cost of GHC, it also sacrifices the benefit of powerful configuration. The new idea would allow users to keep all the benefits of Haskell config files without the cost of having GHC themselves. We would present a web interface where a user can paste in their xmonad.hs (or maybe Browse... upload?), probably select release vs. darcs version, and then submit the form. The get back a download link to a compiled, standalone xmonad-i386-linux, the complete executable. There are a couple of hurdles for this approach to work. 1. We need a donated machine with sufficient computing power and bandwidth. 2. xmonad-i386-linux files tend to be around 3.5-4MB. If this began to see a decent bit of use, that could take a bite out of the upload bandwidth for the donated machine. 3. The mod+q semantics: what does it do when there's no ~/.xmonad/xmonad.hs, but there is a ~/.xmonad/xmonad-i386-linux? Hopefully that keybinding should be harmless for someone without an xmonad.hs, and it would just treat mod+q as a no-op. On the user end, they would require libX11 and various other libraries, but not X11-1.4.2, mtl, the RTS, nor any other Haskell bits. Anyone with a X11 system (and an x86 architecture) should be able to run these binaries. Some form of captcha would be necessary to prevent spamming the form and crippling the box. Since it's only compiling and not executing the config files, it shouldn't require any lambdabot-like sandboxing. I'm willing to set up this system, and my family has a server machine that could be used as a testbed, but it isn't beefy or reliable enough to be used long-term. Braden Shepherdson shepheb

13 19

Issue 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 22 Jul '08

22 Jul '08

Issue 199: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 Comment #1 by byorgey: What do you mean by "crashes"? I tried to replicate this and it simply had no effect. I agree that an error message might be nice, but it's also unclear by what mechanism an error message should be displayed. (xmessage? dzen?) Issue attribute updates: Owner: byorgey -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 20 Jul '08

20 Jul '08

Issue 199: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 New issue report by m...(a)cloudconnected.org: What steps will reproduce the problem? 1. Add an appendFilePrompt with a filename in a non-existent directory 2. Use the prompt I think an error message should be displayed instead of crashing What version of the product are you using? On what operating system? I'm using XMonad 0.7 on Debian GNU/Linux testing. Component-Contrib Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

2 1