Thread panic due to "incorrect regex expression"

[JeffCarpenter]

It's pretty short, so I'll leave the trace here:

% RUST_BACKTRACE=1 fselect "select path from . where path regexp \(NOT '^./code'\) and name regexp '\.conf$'

thread 'main' panicked at 'Incorrect regex expression', src/searcher.rs:1246:45
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: __libc_start_main
  17: <unknown>

[jhspetersson]

Thank you for the issue!

Unfortunately, expression negation (NOT before regexps or anything else) is not currently supported.
With the release version it is possible to rewrite the command to this one (note that globs work with = and !=):

fselect "path from . where path rx '^\./[^c][^o][^d][^e]' and name = *.conf"

...what is really terrible for somewhat lengthy prefixes.

So I updated the master with !=~ and notlike operators to negate the regexp operand.
Please try this one:

fselect "path from . where path !=~ '^\./code' and name = *.conf"

I suppose NOT negation to be implemented in some future.

[JeffCarpenter]

Thanks for the solution. This is going to be a great tool for getting a handle on all the config files in my home directory!