doomemacs / doomemacs/core

+vertico/project-search doesn't work with tramp

Open
#6,224 7 comments 8 reactions 0 assignees View on GitHub
:completion vertico is:bug re:remote
Dominant language
Emacs Lisp
Stars
22.7k
Forks
3.1k
Avg merge
10h 46m
Merged PRs (30d)
4

Description

### What did you expect to happen?

Using `+default/search-project` (and by extension `+vertico/project-search`in my case) over tramp should act as if I was working on a local project and return a results list when there are matching lines.

### What actually happened?

Something seems to happen as the "prefix" in front of the search terms goes from nothing to `;` then `!`. Despite this, results list is always empty even if there are matching lines in the project.

### Describe your attempts to resolve the issue

I've searched through existing issues and found this one which seems pretty similar: https://github.com/hlissner/doom-emacs/issues/1087

I tried to apply the suggested fix (`(advice-remove #'projectile-locate-dominating-file #'doom*projectile-locate-dominating-file)`) but it looks like the issue was a bit old and that Doom changed the way its inhibit this functionality when trying to use over Tramp. `project-root` looks good but `(executable-find "rg")` points to my local `rg` binary.

### Steps to reproduce

1. Open Emacs
2. Go to a remote SSH project using Tramp
3. Try to use `+default/search-project`
4. Answers list is always empty (with an exclamation mark in front of the search terms) even if the same `rg` search works by logging into the remote server through SSH and manually typing the command

### System Information

https://pastebin.com/LCDga5Dh

Contributor guide

Open the contributing guide

Research direction

Start with +default/search-project and +vertico/project-search, then inspect the Tramp/project-root handling and the projectile-locate-dominating-file advice mentioned in the report. Reproduce the four-step SSH project search and compare it with the working remote rg command; done means matching remote lines appear in the results list without the failing prefix behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
emacs, emacs-lisp
Domain
search, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.