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

Flag for "don't ignore anything" #275

Closed
max-sixty opened this issue Apr 6, 2022 · 3 comments · Fixed by #695
Closed

Flag for "don't ignore anything" #275

max-sixty opened this issue Apr 6, 2022 · 3 comments · Fixed by #695
Labels
new feature Requests or requires a new feature

Comments

@max-sixty
Copy link

Is your feature request related to a problem? Please describe.

I often want to see what files a process changes, and I run something like this and then run the process:

 watchexec --no-vcs-ignore --no-default-ignore --print-events -- echo 1

But I realize there are actually 4 separate ignore flags that I should be passing to see every file change:

        --no-default-ignore    Skip auto-ignoring of commonly ignored globs
        --no-global-ignore     Skip auto-loading of global or environment-wide ignore files
        --no-project-ignore    Skip auto-loading of project ignore files (.gitignore, .ignore, etc)
        --no-vcs-ignore        Skip auto-loading of VCS (Git, etc) ignore files

Describe the solution you'd like
What do you think about having --no-ignore (or a different name) to not have any ignores?

Describe alternatives you've considered

fd & rg both use -u as unrestricted, so passing -uu is unrestricted in hidden files and ignores. I'm not sure there's a hierarchy here such that we can progressively add on us, though.

@passcod
Copy link
Member

passcod commented Apr 6, 2022

The -u -uu thing is interesting but as you say, probably not applicable here. There's one added complexity for Watchexec in that --no-ignore was the previously-used name for --no-project-ignore, so it could be a bit confusing to have it "come back" as a different option! But doable, after 2.0.

Good idea! I'll add it to the pile :)

Update: tentatively slated for 2.1, such that --no-ignore will break completely on 2.0, prompting anyone relying on it to change.

@passcod passcod added the new feature Requests or requires a new feature label Apr 7, 2022
@passcod passcod added this to the Ignore handling issues milestone Aug 3, 2023
@passcod
Copy link
Member

passcod commented Aug 30, 2023

As of 1.23.0 this is reduced to 2 flags: the existing --no-default-ignore, and the new --no-discover-ignore. I'm still planning to have --no-ignore as described above, though.

@passcod
Copy link
Member

passcod commented Nov 27, 2023

As of next version, there's --ignore-nothing. 2.1 will still have --no-ignore for naming consistency, which will have --ignore-nothing as alias, but at least this is now done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature Requests or requires a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants