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

Feature suggestion: accept and ignore -E and --extended-regexp flags for grep compatibilty #345

Open
markstos opened this issue Aug 15, 2021 · 3 comments
Labels

Comments

@markstos
Copy link

I have to switch back and forth between ack on my latop and lots of services that only have grep. Compatibility with grep is a valued feature.

So it would be welcome of ack accepted the -E and --extended-regexp flags and ignored them (while possibly issuing a warning that they don't anything). Since ack has regex's enabled by default, essentially the -E flag is "working" by just ignoring it.

Thanks!

@petdance
Copy link
Collaborator

Is this just for your fingers, or are you writing scripts that use -E and you'd like ack -E to work?

If it's just your fingers, then is --extended-regexp actually something that gets used?

@markstos
Copy link
Author

Hi Andy!

It's just for my fingers, and I never type --extended-regexp. My brain thinks "Oh, I want to use the pipe symbol, I better add -E".

@markstos
Copy link
Author

BTW, I tried ag and rg and ran into problems. ack works great!

I ran into a bug with ag where it missed a 100 matches and it wasn't clear why (!!). ggreer/the_silver_searcher#553 (comment)

Maybe the problem with Ripgrep was that compiling with PCRE was optional, so that I couldn't actually rely on Perl regex's to work reliably with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants