Regular Expressions 101

Spo⁠nsors

Community Library

23

Get path from any text

Created·2023-01-31 14:38
Updated·2023-07-23 20:17
Type·Match
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 ExpressionOpen Workspace

/
^(?<pre>\D*?)(?<num>\d*\.\d+|\d+\.\d*|\d+)(?<sp>\s*?)(?<units>bytes|kb|mb|gb|tb|b|k|m|g|t)$
/
gi

Description
Created·2022-05-05 17:45
Updated·2024-04-19 19:06
Type·Match
Flavor·JavaScript

Purpose

This pattern is used to parse human readable text strings regarding file sizes.

The pattern names four capture groups in the string for the following purposes:

  • pre: any text before the numeric characters begin are captured and filtered out
  • num: matches any real number with or without a decimal point. ex: [1.3, 0.19, .6, 21., 42]
  • sp: captures whitespace between numeric characters and units
  • units: captures alpha text to match with units resolver

The "pre" and "sp" captures can be discarded. The num capture can be changed to numeric with a parseFloat. The units capture can be used to determine any unit conversions required.

Submitted by Vincent Engler
Open Workspace