notpeter

cmd-> / ctrl-> similarly dump the current selection into the agent panel as context.

No extension pulls in their own node, there’s `npm_install_package` in the Zed extension API which leverages Zed’s copy of node. Same is used for built-in tooling/LSPs (prettier, json-language-server, etc).

I believe the only way to do this is if you clone each extension repo and install them as dev extensions. This is because although you can pin to an extension version using […] Install Previous Version, you can only pin previous versions, not the newest. There’s a discussion.

The bigger issue is most extensions automatically download the latest LSP versions from github/npm. So you’ll also want to manually install LSPs in your path so worktree.which can find them and the extension will skip auto-downloading missing LSPs (which works with /most/ extensions). There’s an issue.

When you say “4000” do you mean an Nvidia 4000-series card or an Intel HD Graphics (e.g. 4600). The former should be plenty to run Zed smoothly, while the later was low end when launched 12-13 years ago and has terrible Vulkan support.

Zed has word completions, by default they are only used as a fallback when there is no LSP available. But you can enable them always if you want:

{
  "completions": {
    "words": "enabled",
  }
}

You can also nest this under languages.svelte or whatever to make it language specific. Personally I hate this sort of thing, but to each their own.

See: https://zed.dev/docs/reference/all-settings?#words