222

I'm attempting something which I feel should be fairly obvious to me but it's not. I'm trying to match a string which does NOT contain a specific sequence of characters. I've tried using [^ab], [^(ab)], etc. to match strings containing no 'a's or 'b's, or only 'a's or only 'b's or 'ba' but not match on 'ab'. The examples I gave won't match 'ab' it's true but they also won't match 'a' alone and I need them to. Is there some simple way to do this?

kmorris511
  • 13,542
  • 6
  • 26
  • 29
  • @finnw maybe he was refering to it into the context of http://stackoverflow.com/q/36754105/3186555? –  Apr 21 '16 at 01:24

9 Answers9

365

Using a character class such as [^ab] will match a single character that is not within the set of characters. (With the ^ being the negating part).

To match a string which does not contain the multi-character sequence ab, you want to use a negative lookahead:

^(?:(?!ab).)+$


And the above expression disected in regex comment mode is:

(?x)    # enable regex comment mode
^       # match start of line/string
(?:     # begin non-capturing group
  (?!   # begin negative lookahead
    ab  # literal text sequence ab
  )     # end negative lookahead
  .     # any single character
)       # end non-capturing group
+       # repeat previous match one or more times
$       # match end of line/string
Peter Boughton
  • 102,341
  • 30
  • 116
  • 172
207

Use negative lookahead:

^(?!.*ab).*$

UPDATE: In the comments below, I stated that this approach is slower than the one given in Peter's answer. I've run some tests since then, and found that it's really slightly faster. However, the reason to prefer this technique over the other is not speed, but simplicity.

The other technique, described here as a tempered greedy token, is suitable for more complex problems, like matching delimited text where the delimiters consist of multiple characters (like HTML, as Luke commented below). For the problem described in the question, it's overkill.

For anyone who's interested, I tested with a large chunk of Lorem Ipsum text, counting the number of lines that don't contain the word "quo". These are the regexes I used:

(?m)^(?!.*\bquo\b).+$

(?m)^(?:(?!\bquo\b).)+$

Whether I search for matches in the whole text, or break it up into lines and match them individually, the anchored lookahead consistently outperforms the floating one.

Community
  • 1
  • 1
Alan Moore
  • 68,531
  • 11
  • 88
  • 149
  • 14
    I believe this is more efficient: (?:(?!ab).)* – Blixt Jun 10 '09 at 18:12
  • 1
    Also wants to use start/end markers to enforce the check on the whole string. – Peter Boughton Jun 10 '09 at 18:15
  • 8
    @Blixit: yes, it is. But it's also harder to read, especially for regex newbies. The one I posted will be efficient enough for most applications. – Alan Moore Jun 10 '09 at 18:24
  • @Peter: I was fixing that as you posted the comment. Anchors aren't necessary in all cases (eg, when using Java's matches() method), but they don't hurt anything either. – Alan Moore Jun 10 '09 at 18:27
  • 28
    Don't write code aimed at newbies! If code is hard to read, leave comments/documentation so they can learn, instead of using lesser code that keeps them ignorant. – Peter Boughton Jun 10 '09 at 18:29
  • 32
    If I had thought there would be a noticeable difference between the two approaches, I wouldn't have hesitated to recommend the faster one. On the other hand, regexes are so opaque (if not cryptic), I think it's worthwhile to break the knowledge into smaller, more manageable chunks whenever possible. – Alan Moore Jun 10 '09 at 18:56
  • 1
    In my case the second one worked, and the first one didn't. I was trying to match certain ` .. ` elements that contained `windows` somewhere between the start and end tags and not match the TD elements that didn't. I used `).)+` to find the whole TD element where `).*` wouldn't work. Final regex was `).)+windows.*?` . For a good example of "breaking the knowledge into smaller chunks" see below where the explanation of the regex characters used is included in the answer. – Luke Mar 25 '13 at 00:48
  • @Luke: That is a very different problem. You're searching for a substring that starts with `AAA` and ends with `BBB`, that does not contain any other instances of `AAA` or `BBB`, but does contain `CCC` (where `AAA`, `BBB` and `CCC` are arbitrary multi-character sequences). *This* question is about matching a whole string that does not contain `AAA`. Peter's approach works here too, but this approach is just as valid, and a little more intuitive. – Alan Moore Mar 25 '13 at 15:23
  • If you break my problem down, before worrying about the `windows` part, i first needed to find one complete `...` tag, which involved, as you say, finding the middle section "that does not contain any instances of `aaa` or `bbb`" (this part pretty closely matches the question). I was just adding my experience to try to help anyone else who arrives at this page. – Luke Mar 25 '13 at 22:00
  • You just saved my life. I have been banging my head against a wall for an hour trying to match simple out-of-place Javascript inline comments (` // `) except I wanted to ignore matches where the comment was at the start of the line; I _only_ wanted to move the comment up to its own line. Thanks to you I got it complete in short order. – Pierce Apr 19 '16 at 16:51
  • if you are planning to not have any "ab" s at all, `(?:(?:(?!.*ab).*).)*` is going to be best –  Apr 20 '16 at 08:57
63

Yes its called negative lookahead. It goes like this - (?!regex here). So abc(?!def) will match abc not followed by def. So it'll match abce, abc, abck, etc.

Similarly there is positive lookahead - (?=regex here). So abc(?=def) will match abc followed by def.

There are also negative and positive lookbehind - (?<!regex here) and (?<=regex here) respectively

One point to note is that the negative lookahead is zero-width. That is, it does not count as having taken any space.

So it may look like a(?=b)c will match "abc" but it won't. It will match 'a', then the positive lookahead with 'b' but it won't move forward into the string. Then it will try to match the 'c' with 'b' which won't work. Similarly ^a(?=b)b$ will match 'ab' and not 'abb' because the lookarounds are zero-width (in most regex implementations).

More information on this page

Abhinav Gupta
  • 4,300
  • 1
  • 20
  • 18
  • 2
    Referencing the 'lookbehind' operators as well was useful, not all online regex parsers/documentation will include it, even if it is valid and works. – Leith Dec 18 '17 at 23:57
6

abc(?!def) will match abc not followed by def. So it'll match abce, abc, abck, etc. what if I want neither def nor xyz will it be abc(?!(def)(xyz)) ???

I had the same question and found a solution:

abc(?:(?!def))(?:(?!xyz))

These non-counting groups are combined by "AND", so it this should do the trick. Hope it helps.

Krabat
  • 133
  • 1
  • 5
  • Where is that quote from? Only part of it comes from [this Answer](https://stackoverflow.com/a/977316/12695027). Apart from that, you've not answered the Question, but seems to have answered something that you haven't linked to. I think `abc(?:(?!def)(?!xyz))` would do. They're in the con-capturing group already. No need to put another one inside it. They're also not "combined by "AND"". They're checked one at a time, just like `ab` is first checked for `a`, then for `b`, but lookaheads just don't move the cursor along. – Scratte Feb 04 '21 at 12:12
5

Using a regex as you described is the simple way (as far as I am aware). If you want a range you could use [^a-f].

Copas
  • 5,750
  • 5
  • 27
  • 43
4

Simplest way is to pull the negation out of the regular expression entirely:

if (!userName.matches("^([Ss]ys)?admin$")) { ... }
Amit Joki
  • 53,955
  • 7
  • 67
  • 89
user71268
  • 779
  • 1
  • 5
  • 6
  • While this is useful if you are consuming *just* that expression, as part of a larger expression the negative lookahead method described by Peter allows both positive and negative conditions in a single string. – Godeke Jun 10 '09 at 18:26
  • Absolutely true. But the question was to "match a string which does NOT contain a specific sequence of characters". I think for that purpose negative lookahead is overkill. – user71268 Jun 10 '09 at 18:36
  • 2
    Can't do this if you're using a text editor. – Jamel Toms Jun 13 '13 at 19:01
  • Not useful if you're using regex outside of a programming language, like Apache or Nginx config.... – mwieczorek Mar 07 '20 at 16:14
3

Just search for "ab" in the string then negate the result:

!/ab/.test("bamboo"); // true
!/ab/.test("baobab"); // false

It seems easier and should be faster too.

Diego Perini
  • 7,197
  • 1
  • 16
  • 9
3

The regex [^ab] will match for example 'ab ab ab ab' but not 'ab', because it will match on the string ' a' or 'b '.

What language/scenario do you have? Can you subtract results from the original set, and just match ab?

If you are using GNU grep, and are parsing input, use the '-v' flag to invert your results, returning all non-matches. Other regex tools also have a 'return nonmatch' function, too.

If I understand correctly, you want everything except for those items which contain 'ab' anywhere.

Wiktor Stribiżew
  • 484,719
  • 26
  • 302
  • 397
maxwellb
  • 11,744
  • 2
  • 21
  • 33
  • "The regex [^ab] will match for example 'ab ab ab ab' but not 'ab', because it will match on the string ' a' or 'b '.". This seems to be incorrect. `[^ab]` is a character class that matches everything except a's and b's. Obviously it will match the spaces. – Scratte Feb 04 '21 at 12:21
3

In this case I might just simply avoid regular expressions altogether and go with something like:

if (StringToTest.IndexOf("ab") < 0)
  //do stuff

This is likely also going to be much faster (a quick test vs regexes above showed this method to take about 25% of the time of the regex method). In general, if I know the exact string I'm looking for, I've found regexes are overkill. Since you know you don't want "ab", it's a simple matter to test if the string contains that string, without using regex.

patjbs
  • 4,024
  • 3
  • 21
  • 18
  • This is a good point! If the sequence is a simple string then a regex is over-complicating things; a contains/indexOf check is the more sensible option. – Peter Boughton Jun 10 '09 at 21:05