Results 483 comments of sorawee

This issue should be reopened, I think. As @hlissner said in https://github.com/hlissner/doom-emacs/issues/6280: > The reason why [the workaround that uses `(centaur-tabs-group-by-projectile-project)`] works is it forces centaur-tabs to use projectile instead...

In case this is useful. ![undo-race-condition](https://user-images.githubusercontent.com/9099577/58578519-d7476480-81fd-11e9-95c2-6b42959d6ea4.gif)

Before #212, we have an amalgam of two problems. The second variant makes it impossible to undo.

I believe it's an issue with `react-monaco-editor`. `componentDidUpdate` didn't consider the case where it itself is called prematurely (by React).

3.4 also has this issue. 3.3 doesn't, but it is buggy, mixing C to JS by putting something like `(const char*)` to the generated file :(

> A test consists of an expression followed by an answer connected by a word, usually `is`. `does-not-raise` doesn't fit to the above description. I personally think the following is...

Well, in that sentence, "usually" applies to `is`, not "A test consists of an expression followed by an answer connected by a word". But this is easy to fix. Just...

To avoid confusion, I think `then` should be a keyword (and reserved). More generally, if `:` is a keyword, `` should as well.

Today I just found that I could do: ``` [list: 1, 2, 3, 4].foldl(insert-heap, empty-heap) ``` but not ``` fold(insert-heap, empty-heap, [list: 1, 2, 3, 4]) ``` because of this...