08:05:09 <Entroacceptor> maybe because I'm not spamming?
09:00:05 <stepcut> happpstack is perfect, so there is nothing to talk about... sometimes I think I should break more stuff so people will have something to talk about :p
09:15:49 <Entroacceptor> stepcut:  :)
09:16:28 <Entroacceptor> I can't give a Text.Lazy right into a response, right? I have to unpack first
09:18:43 <stepcut> Entroacceptor: what content-type wolud it return? text/plain; charset=utf-8 ?
09:19:14 <Entroacceptor> well, I can set that before
09:19:41 <Entroacceptor> there's no toRepsonse :: Text.Lazy -> Whatever
09:19:59 <stepcut> toResponse :: L.Text -> Response
09:20:08 <stepcut> there is not... but perhaps there should be
09:20:27 <stepcut> with the content-type type, text/plain; charset=utf-8
09:21:17 <stepcut> the lame way would be to do, L.Text -> String, and then String -> Response. The better way would be to convert the Text -> L.ByteString directly
09:22:36 <stepcut> http://code.google.com/p/happstack/issues/detail?id=138
09:23:02 <Entroacceptor> :)
09:23:56 <stepcut> instance ToMessage String where
09:23:56 <stepcut>     toContentType _ = B.pack "text/plain; charset=UTF-8"
09:23:56 <stepcut>     toMessage = encodeUtf8
09:23:59 <stepcut> or something like that
09:24:07 <stepcut> should be trivial
09:24:10 <stepcut> and useful
09:24:47 <stepcut> you could also do, toResponseBS (B.pack "text/plain; charset=utf-8") (T.encodeUtf8 foo),  as a work around
09:24:56 <stepcut> but submitting a patch would be better :p
09:27:05 <Entroacceptor> if I get happstack compiled again, learn how to properly format the patch, learn how to write it and actually do write the patch, sure.
09:27:49 <stepcut> formatting the patch is easy
09:28:12 <stepcut> you just edit the code to your liking, then do, darcs record && darcs send
09:28:51 <Entroacceptor> nah, that won't work, this computer doesn't have a working sendmail ;)
09:28:59 <Entroacceptor> I'd have to darcs send -o foo
09:29:15 <stepcut> it's documented here, http://happstack.com/download
09:29:42 <stepcut> :p
09:29:54 <Entroacceptor> wow
09:31:08 <stepcut> :)
09:34:53 <Entroacceptor> cabal: dependencies conflict: happstack-data-0.5.1 requires text ==0.11.0.1
09:34:53 <Entroacceptor> however
09:34:53 <Entroacceptor> text-0.11.0.1 was excluded because happstack-server-0.5.1 requires text
09:34:53 <Entroacceptor> ==0.10.*
09:35:05 <Entroacceptor> that's not a true dependency, right?
09:35:55 <stepcut> probably not
09:36:16 <stepcut> if it works against 0.11 I can make the range bigger
09:36:32 <stepcut> there is a bug to check all those ranges before releasing 6
09:36:51 <stepcut> snoyman released a command-line version of the dependency checking tool, so that should help
09:37:43 <stepcut> when we set the 0.10 depends on text there was no way to know if 0.11 would break things -- though it is unlilkey that it did. But that is the way cabal policy works :-/
09:41:14 <Entroacceptor> but how can I install it now?
09:42:07 <stepcut> 'tis annoying
09:42:22 <stepcut> you need to edit the happstack-data cabal file and bump the dependency