-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Find in Files doesn't search in .cs
files out of the box in Mono build
#95496
Comments
Is it text in the |
I found #52789 which seemed to suggest If I create a brand new project with one Control and one attached GDScript script, I cannot find the text in that script after I create a |
This is a mixed GDScript/C# project, so not sure why .cs isn’t showing up as an option. However, I am using Godot to search my .gd files, which is what is failing. |
That seems to be intentional, directories with a |
Fair enough, I’ll have to see why I wanted to exclude files from res:// (probably to keep ReadMe.txt from cluttering the Godot editor file list), and if there’s a different way to do it. |
To be clear, If you put it in |
In fact, everything worked in 4.2 with a top-level Not sure if I should close the issue though, it does seem odd that none of the |
.cs
files out of the box in Mono build
I repurposed the issue to keep track of that, which should be fixed when #95502 is merged. |
Tested versions
Reproducible in 4.3 RC3
Not reproducible in 4.2
System information
Godot v4.3.rc3.mono - macOS 12.7.6 - GLES3 (Compatibility) - Apple M1 Pro - Apple M1 Pro (8 Threads)
Issue description
After I updated to 4.3 RC3, Find in Files no longer returns any results.
Steps to reproduce
Using not-menu-bar, Search > Find in Files (or shift+command+F).
Enter text you can see
Click Find…
Search results are empty and show 0 matches in 0 files.
Minimal reproduction project (MRP)
My sincere apologies, this did work with a new project. It repeatedly fails with my large project (unless I go back to 4.2). So I can’t provide an MRP. I do want to make you aware of the bug, however.
The text was updated successfully, but these errors were encountered: