doomemacs / doomemacs/core

I can't open a new file because it hits matches to other files

Open
#7,394 3 comments 0 reactions 0 assignees View on GitHub
is:bug needs-triage
Dominant language
Emacs Lisp
Stars
22.7k
Forks
3.1k
Avg merge
10h 46m
Merged PRs (30d)
4

Description

### I confirm that...

- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.

- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.

- [X] The issue can be reproduced on the **latest** available commit of Doom.

- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*

### Expected behavior

When I do `SPC .` or `SPC f f` it should open a new file if the search doesn't match one.

### Current behavior

I am not able to open a new file `dataset.py` because it always finds a fuzzy match to `data_setup.py`. I am initiating file search with `SPC f f` and `SPC .`, doesn't work with either.

I tried unhighlighting the match using - `C-S-k` and `C-M-S-j` - see https://github.com/doomemacs/doomemacs/issues/2554 but neither works. I am using projectile via tramp. It looks like `C-M-S-j` is creating a new file on local with the full ssh path instead of creating on remote. Maybe there is a simpler way that I am missing.

### Steps to reproduce

easily reproduced on tramp/projectile in doom

### System Information

GNU Emacs v28.2 nil Doom core v3.0.0-pre grafted, HEAD -> master, origin/master, origin/HEAD e966249 2023-01-01 21:55:13 -0500 Doom modules v22.10.0-pre grafted, HEAD -> master, origin/master, origin/HEAD e966249 2023-01-01 21:55:13 -0500

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.