6 Commits

Author	SHA1	Message	Date
Zoltán Nyikos	b109b1abce	fix(glob): avoid subcapture nesting too deep error (#29520) ... Use Cmt to evaluate Cond and Elem during match to avoid building the nested capture structure later.	2024-07-06 11:40:08 +02:00
Jon Huhn	4bd86120d4	fix(glob): handle overlapping {} condition elements #29236 ... This change fixes an issue where glob patterns like `{a,ab}` would not match `ab` because the first option `a` matches, then the end of the string is expected but `b` is found, and LPeg does not backtrack to try the next option `ab` which would match. The fix here is to also append the rest of the pattern to the generated LPeg pattern for each option. This changes a glob `{a,ab}` from being parsed as ("a" or "ab") "end of string" to ("a" "end of string" or "ab" "end of string") Here, matching against `ab` would try the first option, fail to match, then proceed to the next option, and match. The sacrifice this change makes is dropping support for nested `{}` conditions, which VSCode doesn't seem to support or test AFAICT. Fixes #28931 Co-authored-by: Sergey Slipchenko <faergeek@gmail.com>	2024-06-10 04:23:03 -07:00
altermo	9707363b09	refactor(lua): refactored glob	2024-01-19 11:54:04 +00:00
altermo	5aa14e1231	fix(lua): return after assert returns assert message (#27064)	2024-01-17 13:34:25 -06:00
Mathias Fußenegger	5dc0bdfe98	docs(glob): add glob module (#26853)	2024-01-02 14:32:43 +01:00
Steven Arcangeli	92204b06e7	refactor(lsp): move glob parsing to util (#26519) ... refactor(lsp): move glob parsing to vim.glob Moving the logic for using vim.lpeg to create a match pattern from a glob into `vim.glob`. There are several places in the LSP spec that use globs, and it's very useful to have glob matching as a generally-available utility.	2023-12-22 11:40:01 +01:00