emacs<>vsc

except for the macros being bolded, it looks the same to me. You do have a larger font-size in your Emacs though

what is the slow part when initializing the workspace? if it's the LSP server, it doesn't look like this client would make anything faster for you

> what is the slow part Analyzing the files, I guess. Yeah, it doesn't seem that lsp-bridge offers any advantage for me. I never had problems with Emacs getting stuck while trying to complete. I'm not sure what this bridge would improve for me, tbh

Git worktree. You’ll end up with a second copy in your repo though. Not sure how your edit files if you didn’t have some duplicates though

thanks @U11BV7MTK.

Magit handles this nicely

> You’ll end up with a second copy in your repo though. https://morgan.cugerone.com/blog/how-to-use-git-worktree-and-in-a-clean-way/

Worktrees are nice. it takes time to get used to the workflow but you don't have to stash things anymore whenever you need to switch between branches. Funny, when I just started using worktrees, I couldn't figure out why my tests are failing, I asked my teammate to help. He joined a call, and things were suddenly working. I said thank you and only later I realized, I accidentally switched dirs and the tests were fine in the main branch, but the issue was still not fixed in my branch. That article above helps to keep the dir structure clean and less confusing.

At some point, I even added a helper to create a worktree from a GH issue. I'd press a couple of buttons, it would make a readable branch name, create a branch and a new worktree. Very nice

Why is that better than a branch? (I haven't read into working trees yet). So i should probably ask my questions after i do. ;)

you still have branches. You just have branches in different dirs. It's as if you cloned the repo multiple times, but of course worktrees won't require that much space, etc.

So now, for example, I can review a PR (running things in a separate branch) then in a different frame/window I can still track things in the main branch. I can actually review multiple PRs at the same time. Having separate REPLs for them and such

worktrees is how the Clojure CLI does all of its git stuff. the only big problem I've found with them is git submodules don't work with them (or didn't, this is now supposed to work since git 2.26)

oh interesting. i wondered how it kept multiple checked out versions in there but never dug in

yeah, it keeps one git object dir under /.gitlibs/_repos and per-sha work trees under /.gitlibs/libs

I have used a procure-git.sh script inspired by clj cli in ci/build scripts :

#!/bin/sh

if [ -z "$1" ] || [ -z "$2" ]; then
    echo "Usage: $0 <git-repo> <ref>"
    exit 1
fi

repo=$(echo $1 | sed -e 's/.*\///' -e 's/\.git$//')

mkdir -p /tmp/.gitlibs/
if [ ! -d /tmp/.gitlibs/$repo ]; then
    git clone --quiet --mirror $1 /tmp/.gitlibs/$repo
fi

if [ ! -d .gitlibs/$repo/$2 ]; then
    git --git-dir /tmp/.gitlibs/$repo worktree add --force --detach .gitlibs/$repo/$2 $2
fi
echo .gitlibs/$repo/$2

Ehm... Ben, what is this for? How do you use it?

procure-git.sh <sha> , it then echos you with the gitlib dir / workdir of that repo at that ref + you can potentially have that for multiple refs. And it returns, if you already have that worktree. I use that to pull in git dependencies for a build