lens: point the zed extension's lsp command at the debug binary directly
commit
92b29eclens: point the zed extension's lsp command at the debug binary directly
worktree.which("git") plus an "ents" arg shelled through git’s own subcommand dispatch; resolving BIN_NAME directly and dropping the "ents" arg matches how git-ents lsp actually runs during local development.
docs: add ideas.adoc, a human-written scratch list for future directions
Reviews
No reviews of this commit yet — record a verdict below.
Start a review
editors/zed/src/lib.rs
@@ -9,6 +9,9 @@
struct EntsExtension;
+pub(crate) static BIN_NAME: &str =
+ "/Users/joey/Workspace/codes/git/ents/git-ents/target/debug/git-ents";
+
impl zed::Extension for EntsExtension {
fn new() -> Self {
Self
@@ -20,12 +23,12 @@
worktree: &zed::Worktree,
) -> Result<zed::Command> {
let command = worktree
- .which("git")
- .ok_or_else(|| "git not found on $PATH".to_string())?;
+ .which(BIN_NAME)
+ .ok_or_else(|| format!("`{}` not found on `$PATH`", BIN_NAME))?;
Ok(zed::Command {
command,
- args: vec!["ents".into(), "lsp".into()],
+ args: vec!["lsp".into()],
env: Default::default(),
})
}
docs/ideas.adoc
@@ -1,0 +1,13 @@
+= Ideas
+Joey Carpinelli <joseph.carpinelli@icloud.com>
+
+[NOTE]
+This document, unlike other documents in this (highly experimental) repository at this time, is entirely written by humans.
+
+. REST API from Facet types --> `progenitor` --> OpenAPI --> custom clients for Git and forge.
+. Anchors can provide read-only targets for watching.
+ Imagine a `trustfall` query which presupposes a specific anchor at a specific commit.
+ The forge could support an endpoint that asks _given this anchor, return if the code has changed since_.
+ This could be a new form of verification, and it doesn't go against the spirit of `git-ents` because the information still is sourced from Git.
+. We can automatically vendor open-source references from common lock files, and cache them for speed.
+.