Wilfred Hughes

Ooh, that sounds like a really neat idea! I'd be very up for supporting this use case. Can you describe what sort of API you'd want?

Yep, that's correct. Increasing that number will increase the maximum number of cells used during compile-time execution, and the number of cells allocated for runtime execution. We pass the cells...

Could you do `M-x toggle-debug-on-error` and paste the traceback? There aren't any calls to `c-toggle-comment-style` in bison-mode.el.

Totally agreed, it needs work. Since much of bison-mode was written in the 90s, I suspect c-mode's indentation is better now and just using that would probably be an improvement....

No worries. I'm going to leave this open, because it's definitely an issue, and needs fixing.

Um, there isn't an LLVM implementation in this repository, unless I'm missing something obvious?

See https://github.com/wavded/babel-tape-runner/issues/15#issuecomment-210386730

Here's an example of using tape-watch instead of babel-tape-runner, from my package.json: ``` json "scripts": { "test": "babel-tape-runner static/__tests__/* | tap-diff", "test-watch": "tape-watch -r babel-register static/__tests__/* -o '| ./node_modules/tap-diff/distributions/cli.js'", ```

Hmm, suppose we enforced a whitespace character before? Do you have some quote-heavy code to test on? Something like this: ``` (defconst highlight-quoted--full-keywords `((,(rx whitespace (and (group (or "`" "'"...

I'm not currently using difftastic with magit. Early versions of difftastic had a nasty habit of trying to use all the memory on the machine (I didn't have DFT_NODE_LIMIT and...