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

Please enhance long description #71

Open
sten0 opened this issue Feb 4, 2020 · 0 comments
Open

Please enhance long description #71

sten0 opened this issue Feb 4, 2020 · 0 comments
Assignees

Comments

@sten0
Copy link
Contributor

sten0 commented Feb 4, 2020

Continuing from #65

  1. How does wgrep compare to the built-in replace-regexp and query-replace? eg: What is a 'grep buffer"?
  2. Why would users want to use wgrep over the above methods?
  3. Why would users want to use wgrep over helm-ag?

From what I can tell it seems to be like replace-regexp, except that it operates on all open buffers in an Emacs instance. Also (again, only from reading the description), it sounds like the "grep buffer" can be generated using a variety of backends. So I'm guessing is something that a) generates a pattern matching space using one of the backends b) that this then becomes an editable buffer c) finally there's an output stage that applies all changes to patterns in the "grep buffer" to all active buffers.

My feeling is that wgrep enhances efficiency in an interactive way :-) Please let me know if the above short paragraph is accurate so I can get started on a PR, unless you'd rather handle it yourself.

Thanks,
Nicholas

@mhayashi1120 mhayashi1120 self-assigned this Feb 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants