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

Documentation Not Clear #149

Open
justinhandley opened this issue May 30, 2020 · 1 comment
Open

Documentation Not Clear #149

justinhandley opened this issue May 30, 2020 · 1 comment

Comments

@justinhandley
Copy link

Hi There - before I run this, I feel a bit nervous - what is the scope of running this? Is it in the directory you are in? Is it recursive? I need to replace a word potentially used in many places, but only in one folder and it's subdirectories - is that achievable?

Also, is it possible to do a 'file name only' replace, or will it always do words inside files as well as their names?

@beeman
Copy link
Owner

beeman commented May 30, 2020

Hi, thanks for the issue! I agree the documentation is poor, very open to PR's :).

As a general tip, don't run any automated tool on a branch that's not clean, meaning if you have uncommitted changes. That way it's trivial to a) spot what changes are made and b) to revert them.

Also, there is a --dry flag that will show you what changes it will make.

It's currently only recursive and will always change content (not file name only option).

For quickly changing filenames for now you're probably better off by using Finder in macOS:

image

This brings up a popup for doing the renaming:

image

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