Ignore folders

[jeroenbourgois]

What would you like to see?
The ability to ignore certain folders.

Why?
We use worktrees a lot and have them stored in .worktrees. This makes that when using go-to-definition there are always multiple matches, whereas there should be only the 'current' one. I realize this might not be that easy to solve, but as of now this renders the go-to-definition a bit useless.

Alternatives considered
No, but I am happy to learn if we need to approach it differently because there must be other people also using worktrees.

[JesseHerrick]

Hi @jeroenbourgois, what does your worktree structure look like? Based on your description, I'm guessing that you have a main repo and then worktrees nested underneath it in .worktrees. Is that correct? Personally, I wouldn't recommend doing this, Dexter or not because the nesting confuses various tools.

The simpler approach is to allow your worktrees to each have their own directory (not underneath an existing git repo). For example, if you have your main repo as ~/code/my_project, you'd create a worktree folder called ~/code/my_project-worktrees and then create worktrees in there. That way it's organized without any repo nesting.

If you don't want to change your worktree workflow and you're working principally with worktrees, then I'd just delete the repo root .dexter folder and run dexter init in each of your worktrees (the LSP does this for you automatically if you open up the worktree in a new editor).

[JesseHerrick]

I'm going to close this based on my comment above. As mentioned, the solution here is to use worktrees outside of your main project directory and ensure that the Dexter root is in the right spot.