Parses the text following a '#' and a space all the way up to the next return character. Additional #'s can be added for parsing of other type of headings!

Case insensitive match the whole word betwween \bword\b

Regular expression to check the email syntax validity. Certainly requires improvement, but it's a good basis to work from. Work with Java and JavaScript.

Crude CSV regex to split only by characters surrounded by non-whitespace characters. Ignore that it dosen't highlight all of the other commas in the editor. If you select the g regex flag it will properly show here, but not work in Java. Credit to @merosity (Merosity#0135) on Discord!

Regex to select PlantUML Block in Asciidoc documents

^(((\d{3}1-9]|\d{2}[1-9]\d|\d[1-9]\d{2}|[1-9]\d{3})(\/)(((0[13578]|1[02])(\/)(0[1-9]|[12]\d|3[01]))|((0[469]|11)(\/)(0[1-9]|[12]\d|30))|(02(\/)(0[1-9]|[1]\d|2[0-8]))))|(((\d{2})(0[48]|[2468|13579)|((048]|[2468|3579)00))(\/)02(\/)29))$ Match year/month/day, date format. E.g: 2021/08/25 [match] 2021/09/30 [match] 2018/02/28 [match] 2024/02/29 [match] 2023/02/29 [mismatch]

Regex expression for comparing decimal numbers with the usual comparison operators such as (greater than), >= (greater than or equal to), != (not equal to), == (equal to), ... The regex also allows filtering of data from e.g. a database, whereby the first value is not needed, e.g. [FIELD] < 100

Analyze whether the torrent name is a Movie or TV Episode Inspired from https://regex101.com/library/yP4bY4 There is two versions, see differences at the bottom Groups: Title (of the Movie/of the TV Series) Season (if TV Episode) Episode (if TV Episode) Year (if Movie) Name (only in v1, should match the TV Episode title if present) Release name (PROPER, REPACK, LIMITED, etc..) Resolution (720p, 1080p, etc..) Quality (HDTV, BluRay, WebRip, etc..) Codec (Xvid, x265, x264, etc..) Audio coding (AAC, AC3, DTS, etc...) Team (torrent group/team) Extension (mkv, avi, mp4, etc...) Versions: v1, include the TV Episode title, and have all the groups in a single match, but will misinterpret the "name" and "team" groups if the expected pattern is not respected (see in the test strings/regex rules) v2, does not include "name" group but is more reliable, will ignore unexpected patterns.

A regex for validating decimal numbers in the European number format (in many parts of Europe at least, including Germany). A comma is used as a separator for the decimal number, a dot as a separator for thousand places.

Flagged / disallowed text expression used in cApStAn's build of OmegaT

Custom tags expression used in cApStAn's build of OmegaT

"^([\w_]+)(?:\{(*)\})?\s+([\d\\.e+-]+)(?:\s+(\d+))?$"gm

Validation pattern to validate the minimum_should_mach value in opensearch and elasticsearch queries. For more information on the minimum_should_match field have a look here for opensearch or here for elasticsearch

Addes a non-breaking space after any of the letters included in the [vozuskia] class.

Gets the ID of a YouTube Video from any link to it.

get prefecture from Japanese address

This validates AWS EventBridge scheduling expressions using the rate() and cron() formats. It may not catch all invalid expressions, but it should properly validate all valid expressions, as demonstrated in the unit tests. Please let me know if I missed any valid expressions. Originally attempted this using named capture groups and named back-references to reduce duplication. Unfortunately, named capture support is tricky, so they were all converted to duplicated non-capturing groups instead.

Parses an IANA Media Type value. Doesn't seem to capture repeating parameters, which is a bit of an edge case but valid I think - any suggestions on how to fix would be appreciated.

操作系统文件名称验证，参考了Windows，Linux，Mac

verificare indirizzo IPV6 (regole base)