regex - What do 'lazy' and 'greedy' mean in the context of regular ...

stackoverflow.com/questions/2301285/what-do-lazy-and-greedy-mean-in-the-context-of-regular-expressions
For all people reading the post: greedy or lazy quantifiers by themselves won't match the longest/shortest possible substring. You would have to use either a tempered greedy token, or use non-regex approaches.

Regex Quantifier Tutorial: Greedy, Lazy, Possessive

www.rexegg.com/regex-quantifiers.php
Regex Quantifiers Tutorial. Explains the fine details of quantifiers, including greedy, lazy (reluctant) and possessive.

How Greedy and Lazy Quantifiers Work in JavaScript Regular Expressions

tutorialreference.com/javascript/advanced-topics/regular-expressions/javascript-regular-expressions-greedy-and-lazy-quantifiers
The previous guide on quantifiers introduced the concept of greedy vs. lazy matching. This article goes much deeper. Understanding how the regex engine backtracks is the single most important skill for debugging regular expressions that return unexpected results, match too much, or run painfully slow.

Greedy and lazy quantifiers - The Modern JavaScript Tutorial

javascript.info/regexp-greedy-and-lazy
The regular expression engine understands that it took too many .+ and starts to backtrack. In other words, it shortens the match for the quantifier by one character: Now it assumes that .+ ends one character before the string end and tries to match the rest of the pattern from that position.

Regex Quantifiers — *, +, ?, {n}, and Greedy vs Lazy Matching

xerobit.dev/blog/regex-quantifiers-guide/
Quantifiers specify how many times a pattern element must match. Misusing them is the most common source of regex bugs — especially the difference between greedy and lazy matching.

Greedy vs lazy regex quantifiers explained | toolhq.io

www.toolhq.io/blog/regex-greedy-vs-lazy-quantifiers
Why .* swallows the whole line, how lazy quantifiers differ, when a negated character class beats both, and how backtracking causes catastrophic slowdowns.

Regular Expressions Tutorial => Greedy and Lazy quantifiers

riptutorial.com/regex/topic/429/greedy-and-lazy-quantifiers
A lazy (also called non-greedy or reluctant) quantifier always attempts to repeat the sub-pattern as few times as possible, before exploring longer matches by expansion. Generally, a lazy pattern will match the shortest possible string. To make quantifiers lazy, just append ? to the existing quantifier, e.g. +?, {0,5}?.

Lazy vs Greedy Quantifiers in Regex — RegexPro

regexpro.dev/reference/concept-lazy-vs-greedy
Adding ? makes the quantifier lazy +? and *? switch to lazy (also called non-greedy or reluctant) matching. They match as few characters as possible, expanding only when needed to complete the overall match.

Regex Greedy vs Lazy Quantifiers Explained | Irreva

www.irreva.com/regex-greedy-vs-lazy
Greedy vs lazy quantifiers in regex: why greedy matches too much and how to fix it with ? to make quantifiers lazy.

Quantifiers in Regular Expressions - .NET | Microsoft Learn

learn.microsoft.com/en-us/dotnet/standard/base-types/quantifiers-in-regular-expressions
Appending the ? character to a quantifier makes it lazy. It causes the regular expression engine to match as few occurrences as possible. For a complete description of the difference between greedy and lazy quantifiers, see the section Greedy and Lazy Quantifiers later in this article.