The Wayback Machine - https://web.archive.org/web/20200429045210/https://github.com/8051Enthusiast/regex2fat/issues/1
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

`regex2fat` is nine characters long #1

Open
anthonypants opened this issue Apr 15, 2020 · 7 comments
Open

`regex2fat` is nine characters long #1

anthonypants opened this issue Apr 15, 2020 · 7 comments

Comments

@anthonypants
Copy link

@anthonypants anthonypants commented Apr 15, 2020

Please pretend I attached a pull request which replaces all instances of regex2fat with REGEX2~1. Thank you.

@stuaxo
Copy link

@stuaxo stuaxo commented Apr 15, 2020

How about regex2.fat ?

@gwern
Copy link

@gwern gwern commented Apr 15, 2020

There's an additional documentation bug:

A: Haha OS-driven regex engine go brrrrr

'brrrrr' is incorrect as it doesn't cover many uses of regex2fat such as making it go 'brr' or 'brrrrrr'. It should be generalized to

A: Haha OS-driven regex engine go br+

@RReverser
Copy link

@RReverser RReverser commented Apr 15, 2020

@gwern Excuse me, but it's (Ha)+.

@resynth1943
Copy link

@resynth1943 resynth1943 commented Apr 16, 2020

Someone port this to Linux. :trollface:

@kiding
Copy link

@kiding kiding commented Apr 16, 2020

REGEX2~1 will cause confusion with the inevitable exFAT fork, regex2exfat. Not good.

@mebeim
Copy link

@mebeim mebeim commented Apr 16, 2020

@kiding what confusion? That would obviously be called REGEX2~2...

@fauxparse
Copy link

@fauxparse fauxparse commented Apr 16, 2020

@gwern Excuse me, but it's (Ha)+.

I hate myself for this, but H(ah)*a.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.