Sharkey supports Regular Expressions for your hard and soft word mutes. Mastodon should too! If not raise holy hell with them.

The syntax for a case-insensitive #RegEx (#RegularExpression) for blocking "international airport" or "physical therapy" would be:

/.*international ?airport*./i
/.*physical ?therapy*./i

This would match:
- international airport
- International Airport
- InternationalAirport

And so on. Also, I'm purposefully not using any common triggers so as not to trigger any one.

Once you go regex in your word mutes you'll never want to go back to plain words ever again.

RE: https://social.growyourown.services/users/FediTips/statuses/114604240538234292

How do I use regular expressions to mute specific terms without muting them if they're just part of a word?
So like, in a stupid example:
I want to block "lol" but not "testloltest"
#regularexpressions #regularexpression #sharkey #misskey #wordmute

My PhD student was still feeling uncomfortable with #regex, so I searched and found these awesome regex games that can help you improve your regex-fu and help you have some fun during your daily commute:

https://regexcrossword.com

https://www.the-regex-game.com/?level=integer

and this imho is more geared towards beginners:

https://regexone.com

Things I Learned Today
#TILT #bash #linux
Still working on #regularExpression in bash.

re='^~\s~\s~'
if [[ "${lineN}" =~ ${re} ]] ; then bla bla bla...

The extra variable declaration is needed; found on web
"While not always necessary, it is advisable to store the regex in a variable first, because Bash has trouble with regex literals containing \."

Things I Learned Today
#TILT #bash #linux

It took me while to figure this out and now I remember that I fell in this hole before.

When using #regularExpression like:

if [[ ! ${suffix} =~ .*voScript.txt$ ]] ; then echo "something" ;fi

do NOT quote the regular expression. It is not a string.

Hackaday Links: August 11, 2024 - “Please say it wasn’t a regex, please say it wasn’t a regex; aww, crap, it was a r... - https://hackaday.com/2024/08/11/hackaday-links-august-11-2024/ #regularexpression #hackadaycolumns #hackadaylinks #wiringharness #crowdstrike #bassinette #lithiumion #rootcause #bricking #wildcard #paywall #doggo #pylon #regex #tower #fire #grid #iot

I see a lot of unnecessarily specific regexs (typically excessive captures & pointless `.*$`) being used. Logic says they'll be slower so I spent about 90 seconds testing an example on 3 in-browser JS benchmark apps.
Comparing:
`/^(Hello), this is a string (.*)$/` to
`/^Hello, this is a string /`
the latter is 1.5-5x faster on all 3 apps.
#RegEx #RegExp #RegularExpression

Galvanize Your Grip On Grep With This Great Grep Guide - These days, you can’t throw a USB stick without hitting something that’s running L... - https://hackaday.com/2024/03/26/galvanize-your-grip-on-grep-with-this-great-grep-guide/ #softwaredevelopment #regularexpression #tutorial #linux #regex #news #grep #unix

Emacs Regex https://unixbhaskar.wordpress.com/2024/02/21/emacs-regex/ #TechnicalEmacsEditorOpensourceRegexTools

I just published “Hugo Regular Expressions (featuring ignoreFiles)” at
https://www.ii.com/hugo-regular-expressions-ignorefiles/
#InfiniteInk #GoHugo #Hugo #ignoreFiles #RE2 #RegEx #RegExp #RegularExpression #RegularExpressions #ReplaceRE #Tech #Byℵ #ByNM

It is a known fact that the magic of a #RegularExpression degrades with each word of comment you explain it with. Wizardry is achieved when your regex has to be broken up into multiple lines of, say, #Python, uses nested parentheses, line beginning or ending operators ^ and $, and gets assigned to an inscrutable variable name.

These are secrets jealously guarded by The Old Man #Programming Guild.

/s

#BrianKernighan - Where #GREP Came From - #Computerphile

"Commonly used grep was written overnight, but why and how did it get its name?"

https://www.youtube.com/watch?v=NTfOnGZUZDk&ab_channel=Computerphile

Slides from the talk I gave today about #neovim #nvim #regularExpression #regex plugin `nvim-regexplainer`:

https://bennypowers.dev/decks/nvim-regexplainer

#EmacsTip: It is always better to use #Rx instead of raw #RegularExpression, because they are error-prone, especially the escapes. But if you need to use raw #RegularExpression, install #Relint, a #RegularExpression linter for #EmacsLisp. Just run relint-current-buffer in your buffer, it will find most of your #Regex bugs.

https://github.com/mattiase/relint