Neovim LSP Auto‑Start: Missing File‑Size Constraint

Goal

Establish a reproducible development environment where language servers launch automatically when a buffer is opened.

Unresolved Constraint

The current auto‑start mechanism in nvim‑lspconfig triggers for any buffer matching a filetype, but the documentation does not specify limits such as file size, complexity, or user‑defined predicates. This omission can lead to unnecessary resource consumption when opening large files or preview windows.

Key Questions

• Should the auto‑start be unconditional for all matching filetypes, or should it be gated by a user‑defined predicate such as file size?
• If predicates are allowed, what is the stable configuration format for expressing them across plugins?
• How can the system expose the server’s capabilities to decide whether it is appropriate to launch for a given buffer?