dotnet completions for bash disables tab complete of file names

[mikekistler]

Describe the bug

Without dotnet completions enabled, bash will tab-complete filenames -- a very useful feature. But when dotnet completions are installed, tab-complete of filenames is disabled. This means that users will be forced to choose between tab complete for keywords of the dotnet command and tab complete for filenames.

As a practical example, consider this dotnet command:

dotnet run --project Demo.AppHost/Demo.AppHost.csproj

Without dotnet completions installed, I can tab at the first "D" to get "Demo.", type "A" and get "AppHost/", then "D" to complete the rest of the line. With dotnet completions installed, I can enter "dotnet run --p" and it will complete "project", but I must type every character of "Demo.AppHost/Demo.AppHost.csproj".

To Reproduce

I installed the dotnet bash completions as follows:

dotnet completions script bash > ~/.dotnet_completions
source ~/.dotnet_completions

Then I tried this within an Aspire project and got the reported behavior.

Exceptions (if any)

Further technical details

• Include the output of dotnet --info
• The IDE (VS / VS Code/ VS4Mac) you're running on, and its version

dotnet version: 10.0.100-preview.4.25258.110