Anantha Kumaran

@M3kH looks like a regression, I can't get it to work either. Could you open a separate issue to track this

is this within a buffer or across files? Within a buffer flycheck already provides commands to navigate errors. For references/project-errors you could use n, p or `next-error`

does `flycheck-next-error` solve your issue?

For each buffer tide will make a [configure](https://github.com/Microsoft/TypeScript/blob/master/src/server/protocol.ts#L1342) rpc request to tsserver. This contains formatOptions, which will be used by tsserver for other rpc requests like format etc. Tide already...

Yes, using a standard implementation is better.

PR welcome to add support for indent

I wonder whether we should rebind `M-j` to `c-indent-new-comment-line` by default. It seems to work better than `indent-new-comment-line` from my minimal testing.

> Have you experienced any cases where that does anything which is explicitly wrong? It's not as good as js2-mode, but better than what we have. I never encountered any...

@josteink from what I understand tree-sitter only supports highlighting? does it support other functions like mark-sexp, end-of-defun etc? which is more related to movement. I actually want to use tree-sitter...

sweet, `tree-sitter-node-at-point` this is what I am looking for.