Apropos of last weekends #emacs hacking. How many times would you ask an #llm to generate a #regex for you before you give up and just use a #rx form?

Adding lookbehinds to rust-lang/regex

https://systemf.epfl.ch/blog/rust-regex-lookbehinds/

Muss ich jetzt wirklich so was hier benutzen?

.*[Ss][Ee][Ll][Ee][Cc][Tt].*[Ff][Rr][Oo][Mm]

We've added an optional "Regex" field to Custom Bangs for more precise control. You can now define exactly how your query is split to create more powerful shortcuts.

Read more about this in our latest changelog: https://kagi.com/changelog#7389

@jwildeboer

My guess is #ReGex:

In regular expressions, the underscore counts as a "word character", whilst dashes, commas, dots, whitespaces etc. count as "non word characters".

This is a hugely important thing: All relevant APIs rely heavily on RegExes.

I'm afraid, your initiative won't succeed for that reason:

All #ActivityPub software would have to be revised and patched to solve a niche annoyance.

My bet: It ain't gonna happen.

@Gargron @evan

This is a good overview of how regex works

“Regex is a pattern-matching language; it’s a way to expressively describe patterns that match strings (e.g., words or sentences). For example, say you’re searching your hard drive for an image called foo, but you cannot remember if it’s a JPEG or a ...continues

See https://gadgeteer.co.za/this-is-a-good-overview-of-how-regex-works/

This is a good overview of how regex works

https://squeet.me/display/962c3e10-7278276a-3c95d8c275d4d002

Attention Scrivener users, and anyone with RegEx search in your editor:

I have three comprehensive RegEx search strings that you can use and optionally make a collection in Scrivener: (1) Negative or positive words, (2) Confused words, and (3) Weasel and Hedge words.

The Google Doc contains full instructions to create collections for fast access, as well as the strings. In the future, I will update this document as I add words.I will take suggestions!

https://docs.google.com/document/d/1-g6jx8teJQE1uXLA-XwZP6cTMe5_-xz2AGLRHffNVlc/edit?usp=sharing

#BoostingIsSharing

Rethinking Regex: Smarter detection for a modern threat landscape

Using regular expressions, or regex, was once a convenient and powerful way for web application firewalls (WAFs) to find malicious code in web requests.

https://www.scworld.com/resource/rethinking-regex-smarter-detection-for-a-modern-threat-landscape

Après quelques recherches j'ai compris qu'il pouvait y avoir un certains défis à réintroduire les #regex sur #mastodon que ce soit par la complexité d'utilisation ou le ralentissement les services avec possible faille #DDOS le risque est le taille.

Personnellement, j'aurais bien aimé avec a profiter des nombreux avantages qui en découle malgré tout. Et j'ai cru comprendre qui que beaucoup de #moderation en aurait apprécié l'efficacité.

1/n

https://framapiaf.org/@JBrickelt963/114523955748256138

My recent obsession with the #OscarMamen travel logs of his journey(s) to & time in #Mongolia #BogdKhanate, I wrangled data from a photo archive database.
For unknown reasons, the database doesn't have a field for "date". All date info is stored alongside content descriptions of the photos and their location in the physical archive in the free-text field "motive description".
To work through 7.500 photos + matching them to log entries, I re-taught myself #regex & @OpenRefine
Can recommend!

I still can't believe that most programming systems we use today are preoccupied with numbers. AFAIK, half of (R5RS?) #Scheme standard is numbers and operations on them. Same for #C, #CommonLisp, #Java—ten different types of numbers and huge libraries for them.

Humans think in images and words. Structured text-oriented languages feel like a much better fit for everyone not corrupted by C. Yet we have little to no popular attempts in that space. Structured Regular Expressions didn't catch up; #ed1 and #awk are considered mere #regex automation tools. Modal and the term rewriting systems have their Merveilles Town, but not much beyond. sh/#bash and the like are quite successful, but aren't considered real programming languages either.

Why.

Do I have #regex experts among my followers: echo "123.4506000" | sed -E 's/(\.[0-9]*[1-9])?0+$//; s/\.$//' is intended to remove trailing 0s when its a number with a decimal point. But when there are no cifers behind the decimal point other than 0s, the whole number shall be stripped of the point and the 0s. What are I am doing wrong? Sharing appreciated.

[FR]
Arrivée ici début 2025, big up aux @admin de Piaille.fr ! #introduction :
Tombée dans la marmite #OpenSource en 2000, je me nourris de commandes #bash. Fichiers texte, #grep et ses jolies #regex, #ansible, #git, #greasemonkey, les tests auto et la supervision sont tes amis.
Cordes frottées, grattées et frappées, sons soufflés, chantés ou beatboxés, sons électro ou scratchés me touchent. Rien de tel qu'une bonne soirée à jammer / à enregistrer pour un beatmaker / à débarquer sur scène pour accompagner quand il manque un instrumentiste / à repiquer des morceaux entiers sur papier à l'ancienne / à improviser avec les enfants
Engagée #AMAP et pro #CNV

Im trying to provide aliases for #regex definitions so that humans would be able to understand things better scanning my coding.

However, an identifier as terse as `/[^\s\t_-\/\.=<>:]+/` becomes hideously long to describe in english descriptors.

Is there a midpoint reference or shorthand that could serve as a compromise?

I may just provide a vague numbered reference as a hack - but this obviously is ineligent and a recipe for bugs (should I label something else with the same nomenclature)

Perl is not my favourite language, but I admit that its #regex syntax did a tonne of good for #programming.

We need a similar boost to the #bit twiddling syntax. I like the sensibility of C and Erlang bit-manipulation syntax.

Also, we geeks need to agree on how we clean up that politically induced mess that is the #timezone.