If I have a workspace directory that looks like this, deft update completely breaks.
14:59:40 ~/dylan/workspaces/lsp
$ ll
total 24
drwxr-xr-x 7 cgay staff 224 May 2 22:14 _build
drwxr-xr-x 12 cgay staff 384 May 2 22:13 _packages
lrwxr-xr-x 1 cgay staff 7 May 3 14:59 deft -> ../deft
drwxr-xr-x@ 30 cgay staff 960 Apr 26 11:08 lsp-dylan
-rw-r--r--@ 1 cgay staff 46 Jun 24 2025 workspace.json
15:04:31 ~/dylan/workspaces/lsp
$ deft --verbose --debug update
Reading package file /Users/cgay/dylan/workspaces/lsp/lsp-dylan/dylan-package.json
Package pacman-catalog@master is already installed.
Package directory: /Users/cgay/dylan/workspaces/lsp/_packages/
%resolve-deps(deps: #(), seen: #())
<= #()
%resolve-deps(deps: #(), seen: #())
<= #()
%resolve-deps(deps: #(), seen: #())
<= #()
Registry /Users/cgay/dylan/workspaces/lsp/registry/ is up-to-date (0 files).
If I rm deft; mv ../deft . everything works fine again.
There are lots of reasons why using a symbolic link like this is a bad idea, the main one being that changes to Deft that are in relation to the LSP workspace should happen in a different branch than general changes to Deft, so cloning deft in the LSP workspace would be the best. For that reason I consider this low priority.
If I have a workspace directory that looks like this,
deft updatecompletely breaks.If I
rm deft; mv ../deft .everything works fine again.There are lots of reasons why using a symbolic link like this is a bad idea, the main one being that changes to Deft that are in relation to the LSP workspace should happen in a different branch than general changes to Deft, so cloning deft in the LSP workspace would be the best. For that reason I consider this low priority.