allow disabling default regexp

[jacob-keller]

Is it possible to disable the default search parameters? I don't really need number searching, and I don't really find the path searching that useful since it gets a lot of false positives. Thus, these hints clutter the display making it harder to locate the things I want to copy.

[Morantron]

In the current version is not possible to disable default patterns, but that's a good point.

It could be fixed by conditionally adding patterns to the PATTERN_LIST array here.

To enable this, a new variable @fingers-enabled-default-patterns could be set to comma separated names of patterns. ex: shas,digits,ips

PR welcome! \o/

[aspiers]

I agree that this would be a useful modification. Also even without disabling default patterns, I think the user ones should take precedence. Currently it seems they are matched after the built-ins.

[quite]

@Morantron sounds like you'd then have to give clear, understandable names to the default patterns? Might be tricky to do it well. We could go for adding just a way to disable the default patterns? Since the user anyway is about to customize their own... Like @fingers-disable-default-patterns with values 0 (default) or 1. I could prepare a PR with that.

[Morantron]

@Morantron sounds like you'd then have to give clear, understandable names to the default patterns? Might be tricky to do it well. We could go for adding just a way to disable the default patterns? Since the user anyway is about to customize their own... Like @fingers-disable-default-patterns with values 0 (default) or 1. I could prepare a PR with that.

You are right 🤔

Regarding the PR, I'm rewriting the whole thing in ruby. Just need to get my ass to document the changes and release it once and for all.

[quite]

Oh, that's somewhat unfortunate for me personally. Bash and gawk is O-K, but I'd not depend on having ruby on my systems for this kind of basic working-environment stuff. I'd have to remain on tmux-fingers in bash. Hohum.

[Morantron]

¯\_(ツ)_/¯

[Morantron]

Fixed in 2.2.0 (seven years later hehehehehe). Check out this new option