Extend "..." support to more settings

[porada]

What are you proposing?

Support "..." in more list settings, letting users add their own entries without replacing the inherited ones.

After my initial research, file_scan_inclusions and hidden_files seem the best next candidates.

Why does this matter?

Having used "..." in language server settings, I was surprised that file_scan_exclusions didn’t support it, especially given its default value. Adding one pattern shouldn’t require copying the entire default list and maintaining that copy as Zed’s defaults evolve.

Are there any examples or context?

That led to #62769 for file_scan_exclusions, followed by #64222 for read_only_files. For these settings, ["...", "my-pattern"] extends the inherited list, while omitting "..." still replaces it.

Possible approach

I’d be happy to implement these follow-ups in separate PRs if this direction is welcome, starting with the straightforward cases rather than applying the convention to every list.

The file pattern settings can reuse the existing SplicingVec implementation. I’m also open to generalizing that shared implementation later if other settings demonstrate a need.

@SomeoneToIgnore — since you reviewed both PRs, I’d appreciate your input on this.

Additional candidates worth considering later on:

• edit_predictions.disabled_globs
• edit_predictions_disabled_in
• terminal.path_hyperlink_regexes

[SomeoneToIgnore]

Sure, why not?

[porada]

Using this comment for progress tracking.

Current status

Setting	PR	Merged	Stable Release
edit_predictions.disabled_globs
edit_predictions_disabled_in
file_scan_exclusions	#62769	✅	1.17.2
file_scan_inclusions	#64440	✅
hidden_files	#64484	✅
read_only_files	#64222	✅
terminal.path_hyperlink_regexes

Meta PRs

• Document hidden_files setting #64403
• Align "..." documentation for file pattern settings #64452
• file_scan_exclusions: Fix files.watcherExclude import from VS Code #64492