helix-ext - [contrib] fork of the helix editor, with various inactive and rejected patches applied

	Commit message (Collapse)	Author	Age
*	revamped snippet text element parsing	Pascal Kuthe	2023-03-16
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Snippet text elements can contain escape sequences that must be treated properly. Furthermore snippets must always escape certain characters (like `}` or `\`). The function has been updated to account for that. `text` is now also included with `anything` to match the grammar and can also match empty text. To avoid infinite loops the `non-empty` combinator has been added which is automatically used in the `one_or_more` and `zero_or more` combinator where the problemn would occur.
*	Remove now unused the pattern combinator	Urgau	2023-03-08
\|
*	Optimize LSP snippet parsing	Urgau	2023-03-08
\|
*	Add a parser-combinator crate	Michael Davis	2023-03-08
	Parser-combinators are one of the simpler tools for building ad-hoc parsers. They're a good fit because they are... * Small: each parser / parser-combinator is around 10 LOC. * Functional: helix_core strives to be a functional set of utilities usable throughout the rest of the editor. * Flexible: use them to build any sort of ad-hoc parser. In the child commit, we'll parse LSP Snippet syntax using these new parser combinators. Why not use an existing parser-combinator crate? Existing popular parser-combinator crates have histories of making breaking changes (for example nom and combine). > Implementation note: I tried to not introduce a new trait since the > types can be expressed in terms of `impl Fn`s. The trait is necessary > to build `seq` implementations without a proc macro though, and also > allows us to use `&'static str`s very conveniently: see the trait > implementation for `&'static str`.