bnwa

Fish shell user. Got the same issue. Tried creating a Fish function to forward arguments to `python` to `python3` but didn't work. Checked the directory created under `.cache/nvim` and saw...

Also, setting the `python_cmd` to `python3` doesn't solve, but cd'ing to the hererocks dir Packer creates and calling `python3 hererocks_file.py` does work

Am getting the same issue as others have reported attempted to bind dep with `import { parse } from 'csv-parse/sync'` > Version `6.0.5` is also throwing an error with [Jest...

> > Workaround only gets me this > > @bnwa check inside your `node_modules` folder - I think there is a non-ESM version of the file. > > Should be...

> Nice! I guess it should also work with `import`, using the CommonJS path - in case you prefer that to `require`. TS won't match the declaration file when called...

> I do really think this is not the place to discuss it. So finally just as an example: diagnostics - do virtual text, do signs, publish location list, status...

This makes Typescript errors especially inscrutable given the length/depth of the messages `tsc` emits

Any idea of when this will be make it into a release?

Came to Issues looking for exactly this. In my `tmux` workflow, I have a `fish` function I call that sets up a session per repo, executing the desired layout for...

macOS 14.2.1 on 0.7.1