Steve Purcell

I've actually been working on a pluggable highlighting library recently that might fit the bill for this...

Yes, I worked a little more on it recently, hoping to make an initial release soon!

Yes, basically the issue is that if a user has a buffer-local `process-environment`, then that is the environment that should be used when finding and starting an LSP backend process...

I don't use lsp-mode myself, but I guess the way to test it without setting up direnv etc. locally would be to set the `exec-path` and `process-environment` buffer-locally in a...

Nice! :tada:

Checking back in on this, it occurs to me that the README might also need to be updated to list the new subcommand.

Yeah, I'm thinking something like `1=New name,Code=value,Dupe[3]="Nondupe","Quoted[2]"=something`. There's no need for the `1-4` column range syntax or `!` exclusion syntax for a pure `rename` command, which makes this simpler than...

Ah, yes. I can see that might work. The simple case would then just be `xsv rename "Foo bar" "Fubar"`, which is nice. I had a look through past issues...

Fixed more fully in #139, though perhaps @oscarfv's fix is preferable.

Perhaps you could even get them added upstream if they're widely useful? @mooz appears to be actively maintaining `js2-mode` and accepting pull requests.