Ash

I'm running into this issue where lsp-mode isn't playing nice, with the `before-hack-local-variables-hook` solution not working. Specifically, in my situation, I only have the analyzer installed inside the direnv, which...

Aha, I figured it out. It turns out that `--out-path` and `CARGO_TARGET_DIR` have different behavior. `--out-path` puts the binary in the specified directory but leaves the intermediates in `target`. `CARGO_TARGET_DIR`...

Symlinking like that has a very good chance of confusing the hell out of something else that expects to find an x86_64 libvterm.

It'd also be good to look at the `$VIRTUAL_ENV` environment variable if that's set; my direnv + pyenv setup sets that. I think in general the way lsp-pyright finds the...

As a workaround, if you set `(setq lsp-pyright-multi-root nil)` then it'll run separate processes. You need to set that before you `(require 'lsp-pyright)`, and may need to `lsp-workspace-folders-remove` your existing...

I *suspect* this is because ray doesn't publish sdists, only wheels, and everyone getting bitten by this is running ARM64 Linux (either directly or by running it in Docker inside...

@dfoxfranke Thanks a ton! What's the nicest way to use a version of rust-analyzer with that fix from within the overlay? When I run `rust-analyzer --version`, I get `0d03fe6`, which...

Aah, I was hoping for a more Nix-y solution. I can just copy acowley's trick until this makes its way in.

If I do that, it falls over with the error > error: a 'aarch64-linux' with features {} is required to build '/nix/store/j9dyf8pkwx47acbds22nlpy74796vc1k-append-initrd-secrets.drv', but I am a 'x86_64-linux' with features {benchmark,...

For future reference: I wound up just switching off of NixOps because this is just a single-person deploy, fwiw. So now I just have a deploy.sh script containing ``` #!/usr/bin/sh...