Julian Scheid

Ah, good find. Yeah I think those two are just an oversight. Happy to merge a PR right away, otherwise I'll try to get to it soon.

> "Show the prettier parser selected for the current buffer." Note that the default modeline ("lighter") is already showing the parser -- except that it seems to be showing the...

> Note that the default modeline ("lighter") is already showing the parser -- except that it seems to be showing the wrong parser for some reason, but I'd rather fix...

> My modeline is already too crowded and I don't think I have space to keep prettier info on there, to be honest. Since the logic already exists to figure...

@aspiers the `prettier-info` dump suggests that the Prettier installation being picked up does not have `prettier-plugin-solidity` installed. The `prettier-info` dump currently doesn't include the location from where Prettier is picked...

> This was definitely true originally, because I figured that out myself, and then did a global install of the solidity plugin to fix it. Oh, do you just need...

@aspiers I haven't forgotten about this, just been busy with other stuff but will try and get to this soon.

@aspiers I've started working on this in #97: the first step is to add more info to `prettier-info` output. (We can still think about more human-friendly output later on.) Alas,...

That sounds painful. I'm sure we'll get to the bottom of it. The increased info should appear in `M-x prettier-info` output which is more or less just a serialization of...

Make sure you run `make` so the JS changes get picked up.