Thorsten Ball

> Most likely, all configurations are contained within the Zed binary, as I was unable to locate any separate configuration files. Therefore, I am unable to test this myself. Yep,...

Ahh, interesting. Yeah, `stems` seems like something we'd need in the language config then.

With Preview release [0.124.2](https://zed.dev/releases/preview/0.124.2) we now pick up `gopls` in a project worktree, if it is findable in the `PATH` of a shell spawned in that directory. (See here: https://github.com/zed-industries/zed/pull/8188)...

Yeah, you can set config per project in `.zed/settings.json`, but we don't have the ability to set the rootpath per language yet. I'll look into it.

I got it working! The trick is to use Go workspaces. If you look here https://github.com/golang/go/issues/36899 you'll see that what we're discussing here was marked as `Unsupported` by the `gopls`...

I think what we need is to register a custom URL scheme, like here: https://github.com/chrisliuqq/mac-custom-url-scheme-to-script?tab=readme-ov-file#register-the-url-scheme-in-application If you'd like to pair with me on this, feel free to book some time...

cc @maxbrunsfeld @maxdeviant the panic report contains: ``` Thread 2 Crashed:: Dispatch queue: com.apple.root.user-initiated-qos 0 libsystem_kernel.dylib 0x18a2fa0dc __pthread_kill + 8 1 libsystem_pthread.dylib 0x18a331cc0 pthread_kill + 288 2 libsystem_c.dylib 0x18a23da40 abort...

So @nikensss and I just looked at this and we're not sure whether we should do this, or how exactly it should work if we were to do it. No...

> Maybe, instead we should create an internal Zed module with the related code bits implemented? I think that sounds reasonable, since all we want is `cwd` and `name`.

Great! I simplified code a bit and moved the comment around (and mentioned fish). Will merge once CI is green — you did test that this makes it work, right?