Regular Expressions 101

Community Patterns

22

Get path from any text

Created·2023-01-31 14:38
Updated·2023-07-23 20:17
Flavor·PCRE2 (PHP)
Recommended·
Get path (windows style) from any type of text (error message, e-mail corps ...), quoted or not. THIS IS THE SINGLE LINE VERSION ! If you want understand how it work or edit it, go https://regex101.com/r/7o2fyy Relative path are not supported The goal is to catch what "Look like" a path. See the limitations UNC path and prefix path like //./], [//?/] or [//./UNC/] are allowed some url path like [file:///C:/] or [file://] are allowed Catch path quoted with ["] and [']. But these quotes are include with the catch Quoted path is not concerned by limitations Limitations : (only unquoted path) [dot] and [space] is allowed, but not in a row [dot+space] or [space+dot at end of file name isn't catched INSIDE A NAME FILE (or last directory if it is a path to a directory) : [comma] is not supported (it stop the catch) after a first [dot], any [space] stop the catch after a [space], catch is stoped if next character is not a [letter], [digit] or [-] so, double [space] stop the catch Compatibility compatible PCRE, PCRE2 AutoHotkey : don't forget to escape "%" in "`%" /!\ Powershell and .Net /!\\ : this regex need some modification to be interpreted by powershell. You have to replace each (?&CapturGroupName) by \k. Use this powershell code to do this replacement : ` $powershellRegex = @' [Put here the regex to replace (?&CapturGroupName) with \k] '@ -replace '\(\?&(\w+)\)', '\k' ` This example code must return : [Put here the regex to replace \k with \k]
Submitted by nitrateag

Community Library Entry

0

Regular Expression
Created·2018-12-19 16:59
Flavor·PCRE (Legacy)

/
^ # Start of version string \s* # Ignore leading whitespace (?:v\.?)? # Optional "v" or "v." before the version (?<major>\d+) \. (?<minor>\d+) \. (?<patch>\d+) # MAJOR.MINOR.PATCH (?:- # Pre-release versions start with '-' (?<pre> # Capture the pre-release identifier(s) (?: # The PR rules are annoyingly tight [0-9A-Za-z-] # No leading `0`, but a `0` on its own is fine | # More than one character... [1-9A-Za-z-][0-9A-Za-z-]* # ...means no leading zero ) # That's the FIRST pre-release identifier (?: # Multiple are allowed... \. # ...dot-separated... (?: # ...with the same rules as above [0-9A-Za-z-] | [1-9A-Za-z-][0-9A-Za-z-]* ) )* # Of course, you can also have just the one ) # End name-cap group `pre` )? # End non-cap group encompassing the leading `-` and the identifiers (?: # Built metadata is SIMILAR, but with two differences: \+ # Difference one: starts with `+` (?<meta> [0-9A-Za-z-]+ # Difference two: leading `0` is allowed, so the match rule is simpler (?:\.[0-9A-Za-z-]+)* # Same dot-delim repetition ) # End name-cap group `meta` )? # End non-cap group encompassing leading `+` and identifiers \s* # Ignore trailing whitespace $ # End version string
/
gmix
Open regex in editor

Description

Implements PCRE named-capture (with comments) for the Semantic Versioning 2.0.0 standard - processing is left an exercise for the reader ;)

Submitted by anonymous