Lindrian

regex101 has a few more distinguishing features:

- more flavor support,

- a regex debugger,

- code generator, with support for a lot of languages,

- a complete quick reference with examples,

- an extensive regex library,

- a regex quiz for "golfing" and learning purposes,

Perhaps, most importantly, it runs entirely client side and does not submit any information to the server unless you hit save (which returns a delete link to remove all data). You can even run the website and (most) of its features offline.

Regexr submits all input to the server for processing.

But, I'm biased, since I wrote regex101 :)

Typically not. Sometimes they are tagged as nominal mentions.

Don't agree. LSTM is a very good option for NER. I have personally experimented with simple FFNN and language models to accommodate variable width input and achieved very good results. I will be publishing a paper on this soon.

The system in the article fails at quite simple sentences, such as:

"Rex Tillerson is the secretary of state."

It tags "Rex Tillerson" as ORG instead of PER. If you change "is" to "was" it tags it as PER.

The unit testing feature is located in the menu on the left, under the submenu "TOOLS" (the checkbox icon).

I posted this last night but was told it was incorrect format so I'm giving it another try. Hope this is alright! Please enjoy the site and any feedback is appreciated.

Hello

I'm the creator. PCRE offers a neat feature to limit backtracking, Python does not. I still havent found a decent solution to this issue.

Javascript is run in your own browser so you'll only be screwing yourself there :p

I think this shows quite clearly what is going on and why I get the result I get: http://regex101.com/r/kU3cJ6/#debugger (imgur link: http://imgur.com/H2IkNGy)

If you don't agree with me, could you perhaps suggest an improvement?

I have thought about this, but in cases where it would be useful, it's impossible to generate a sample match string. For example, creating a match string for /(?:a|[bc])efg?/ is super simple, but for something like: /(ab(?1)*)/ it becomes much harder. Not to mention the performance hit you would see for these more complex expressions. (These are just dummy expressions for illustrative purposes, but I'm sure you get my gist.)

Forgot to tell you how to use it. Simply insert an expression and some text and press the little red button right above the input for the regex. That's all you have to do! Enjoy :)

You could always comment the regex. My website provides a full and accurate explanation, step by step, of almost any given regex. Have a look here: http://regex101.com/r/dG4lP3

Not sure if im understanding you correctly but the site does show the content of all capture groups: http://regex101.com/r/nB1bR1

You mean the fact that it doesnt show matches instantly?

You're right.

I managed to mess up some entries of the database, thats why you see some ungodly stuff like 11b email validation. I'll patch it up.

Hmm, I don't want users to see shorter answers and then modifying their own to get the same length or even shorter (since they didnt do the real work). What about something like being able to see the shortest answer, but after that you are no longer allowed to modify your pattern? Feel free to pitch in if you have an idea of a neat way to do it.

I don't think the problem is the click event sending you to the top of the page, its the fact that the textarea is out of sight and its being modified. The browser will then focus it for you, which scrolls you up. Only way I can think of to solve this would be to make sure the textarea is always visible (even if not for the user), which is more work than its worth I'm afraid.

Hmm, the explanation part does part of what you're asking. However, I don't know of any straight forward documentation that I can link to that will explain each and every one of these tokens. I have just read through pcre.txt many times and implemented stuff from there. If you know a source I can use I will look into it.

Thats a great idea! I'll work something out.

Glad you like the design :). Hmm, something like "Regex library" maybe? Unsure of how to word it properly.

I'm not sure I agree it should be default; it's not expected behavior. Either way, there are too many flags to add them all to the quickref, I figured I would just show the most common.

In the about page I mention what version of PCRE is running, and from there you can get to: http://www.pcre.org/pcre.txt

No its not but feel free to send me an email on [email protected] so we can talk privately :)

Do you mean its not explained correctly or its not in the quickref? Its not enabled by default because it changes the behavior of many things, for example what \d and \w match. The user has to decide for himself what flags to use.

Haha, hopefully my website will help you keep regex-related problems to a minimum :).

Adjusted, thank you!

The colorizer does most of the grunt work, it tokenizes the regex and colors it properly. The explainer then basically just loops over those tokens and explain them. It's a bit hacked together as it works right now though; but it seems to do the trick. The explainer does some additional error-checking which the colorizer doesn't have enough resources to do as well. Anything in particular you want to know?