ben-cellfield

It happens with any file. No difference in behaviour between a small or a large file, or between an existing or a new file. As I mentioned, it does happen...

Okay, that difference between "inside project" and "outside project" seems to be caused by `tide` and the presence/absence of a `jsconfig.json` file. If I `touch jsconfig.json` I get the same...

My packages aren't installed in `~/.emacs.d/elpa/` because I'm using nix, but I uninstalled all custom packages and cleared my `init.el`. Now syntax highlighting works immediately. Is there a better way...

Thanks. Should we close this then? Or when I track down the interaction do you want to see if it's something that can be addressed on the `js2-mode` side?

Okay this is getting really weird. The minimal change I have been able to find to my init.el to cure this problem requires **three** separate edits: 1. remove `use-package flycheck`...

Going minimalist, I can reproduce the problem by having `js2-mode` and `rainbow-identifiers` as the only installed emacs packages, and the contents of my `init.el` being: ``` (add-hook 'prog-mode-hook 'rainbow-identifiers-mode) (add-to-list...

Ugh, more weirdness. Removing `rainbow-identifiers-mode` without also removing `flycheck` and `(menu-bar-mode -1)` **does** help, if I start my emacs session with `emacs foo.js`. My normal workflow uses `emacsclient` (via a...

Yes, but I have been careful to `M-x kill-emacs` between each configuration change and test, so I've definitely been starting the daemon fresh every time. I'm now a bit less...

@AlexChesters No, I haven't dug out any more specific information about what's causing this. It's still happening, but it's a lot less annoying since I got rid of rainbow-identifiers. There's...