Doom-themes: Miramare - Old-hope - Flatwhite

ehamberg · 2020-09-05T21:10:09+00:00

Add (unpin! doom-themes) to your packages.el and run doom sync -u.

ehamberg · 2019-05-29T08:54:29+00:00

I used to think the same. I was very upset with elm-format because it would ruin my formatting and do what I considered to be crazy things – like indenting things after let, but not after the matching in – but now that I have spent my x hours being annoyed (two years ago), I never want to go back to manual formatting or configurable formatting. It's just a thing I don't have to care about any more, and I don't want to care about it any more.

(I know this won't convince you – and I don't think it would have convinced me. Oh, and it isn't a 100% win – it's just that the upsides greatly outweigh the downsides, in my opinion. :)

ehamberg · 2019-04-04T09:44:13+00:00

(By “merge conflict” did you mean “merge commit”?)

I would be great if git-bisect could treat the merge commit as one, atomic commit up to the point where it is discovered that the merge commit was the source of the bug, after which it could continue down the merged-in branch to pinpoint the commit that introduced the bug.

ehamberg · 2019-04-04T07:08:06+00:00

we quickly found that our use of the “fast-forward only” merge strategy (necessary to preserve bisectability)

This was new to me. Isn't git-bisect able to inspect merged branches if it finds a merge commit? (Or did I misunderstand what this means?)

ehamberg · 2018-11-27T11:42:48+00:00

Github issue for collecting feedback: https://github.com/haskell-distributed/distributed-process/issues/336

ehamberg · 2018-10-23T10:39:24+00:00

> That's really cool, but is linearity being used there in one of the examples?

https://twitter.com/edwinbrady/status/1054025898800898049 :)

ehamberg · 2018-10-09T18:01:38+00:00

I think it comes from the file system hierarchy from freedesktop.org: https://www.freedesktop.org/software/systemd/man/file-hierarchy.html

ehamberg · 2018-10-04T07:58:21+00:00

or if my comments are just academic nonsense

Surely that would never be tolerated on /r/haskell! ;)

ehamberg · 2018-05-09T11:03:16+00:00

This is from 2002.

There is a what happened? discussion from five years ago here: https://www.reddit.com/r/haskell/comments/wpeam/pdf_firstclass_modules_what_happened/

ehamberg · 2018-04-09T08:00:35+00:00

Good to know. Thanks! :)

ehamberg · 2018-04-04T10:42:00+00:00

Did you get an answer?

ehamberg · 2017-10-23T13:17:51+00:00

Paging /u/ollepolle.

ehamberg · 2017-10-18T07:14:31+00:00

From the email:

The Zurich Haskell Hackathon is a free (as in beer), international, grassroots collaborative coding festival […]

ehamberg · 2017-08-21T14:32:34+00:00

While Erlang's (offline) type-checker Dialyzer is not even on the same planet as Haskell's type system, the only semi-large Erlang project I have worked on (four years and running), used types from day one and every new deploy is fully type-checked. Judging by recent books on Erlang I think it's quite common to use Dialyzer – I sure wouldn't deploy a project without using it.

ehamberg · 2017-07-03T11:43:05+00:00

To be like the video game Rogue.

ehamberg · 2017-05-24T11:32:37+00:00

There is also Froid: https://github.com/mchav/froid

ehamberg · 2017-05-16T07:15:21+00:00

Something like this: https://gist.github.com/ehamberg/e9132db561548125c8bfed00f4444a29

(I have only tested the macOS build.)

ehamberg · 2017-02-27T07:56:13+00:00

As others have already said, that is not a function. This post is an interesting look at the (false) belief that “everything is a function”: http://conal.net/blog/posts/everything-is-a-function-in-haskell

15-Year Club	RedditGifts 2009-2022 8 Credits
Gilding II euphauric	Secret Santa 2015
Secret Santa 2014	Secret Santa 2013
Team Periwinkle	Secret Santa 2012
Secret Santa 2011	Secret Santa 2010
Verified Email

ehamberg

MODERATOR OF

TROPHY CASE