Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't open dir/(dir)/file.ext on windows with Telescope find_files #3306

Closed
seccentral opened this issue Sep 26, 2024 · 1 comment
Closed
Labels
bug Something isn't working

Comments

@seccentral
Copy link

Description

On a default lazyvim install, opening a nextjs project with a bunch of route groups that structure files inside dirs within brackets - Round brackets - in the form of ./src/app/(myroutegroup)/layout.tsx fails with error
ENOENT: no such file or directory: [...]\src\app(app)
Opening the same file on linux works just fine, must be a different way it handles paths and escaping.

Neovim version

NVIM v0.10.1
Build type: Release
LuaJIT 2.1.1713484068
Run "nvim -V1 -v" for more info

Operating system and version

Windows 11 23H2

Telescope version / branch / rev

cb3f98d

checkhealth telescope

==============================================================================
telescope: require("telescope.health").check()

Checking for required plugins ~
- OK plenary installed.
- OK nvim-treesitter installed.

Checking external dependencies ~
- OK rg: found ripgrep 14.1.1 (rev 4649aa9700)
- OK fd: found fd 10.2.0

===== Installed extensions ===== ~

Telescope Extension: `fzf` ~
- OK lib working as expected
- OK file_sorter correctly configured
- OK generic_sorter correctly configured

Steps to reproduce

just try opening a file in a path like dir/(dir)/file.txt

Expected behavior

The file should open

Actual behavior

Error: file not found probably because the path is not properly escaped

Minimal config

- not needed -
@seccentral seccentral added the bug Something isn't working label Sep 26, 2024
@jamestrew
Copy link
Contributor

See this issue. #2446
There is a workaround: #2446 (comment)

There is also something of a fix in the works but it relies on some upstream plenary changes.
#3275

I'll close this issue as its a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants