Tim Pope

Oh it must have function keys, try `:echo state` instead.

The important part is up front: ``` 'history': {'messages': [] ``` It's giving up waiting on a response before receiving a single message. I'm not sure why this would happen....

Absent a better idea: * Make sure it works with another toolchain, like `lein`. * Try both Neovim and Vim. This will help rule out any bugs in the low...

One other thing you could try is delete the `catch` at https://github.com/tpope/vim-fireplace/blob/2e4540d62fd49523a3aefeab896a33ed6bbcb43b/autoload/fireplace/transport.vim#L135 and see if any errors bubble up.

I don't know much about babashka. It wouldn't surprise me if some high level functionality like `cpr` didn't work right. But this particular error is strange. [This `while` loop](https://github.com/tpope/vim-fireplace/blob/b6bef833b56632df917bcf33bc50b8a5d1e26139/autoload/fireplace.vim#L1347-L1363) is...

This all tracks. Skipping `#` lines is a bit too broad, but skipping `#!` would certainly be reasonable. A simple tweak to the `blank` regexp would work.

The current behavior is intended. It mirrors commands like `:find`, which drops it's special `'path'` based behavior and reverts to the current working directory for `./` and `../` paths. I'm...

Looks like `syntax/css.vim` changed, as they definitely used to match. I agree, the Sass highlighting should be changed to bring things back in sync.

Now that I look at it, we should probably handle it the same why we do `sassId`. The preceding punctuation mark is handled differently, but I think it looks better...

I am okay changing the class highlighting to match the id highlighting now, as I agree, the similarity to properties has been irking me lately too. For the punctuation mark...