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

How to make ivy ignore certain files? #122

Closed
kaushalmodi opened this Issue May 29, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@kaushalmodi
Contributor

kaushalmodi commented May 29, 2015

Is there a way to make ivy not list the #*#, .* and *~ files when using find-file with ivy-mode enabled?

Just like ido, is it possible to not list them by default, but auto-complete them if the user wants to?

Here is an example use case:

  • .gitignore should not be listed when I do M-x find-file
  • But if I type .giti and then hit TAB it should autocomplete it.
@abo-abo

This comment has been minimized.

Show comment
Hide comment
@abo-abo

abo-abo May 29, 2015

Owner

You can do it using :matcher, see the implementation of counsel-git-grep. But then you'd have to call your own custom find-file-1.

Owner

abo-abo commented May 29, 2015

You can do it using :matcher, see the implementation of counsel-git-grep. But then you'd have to call your own custom find-file-1.

@abo-abo abo-abo closed this in efd74b8 May 30, 2015

@abo-abo

This comment has been minimized.

Show comment
Hide comment
@abo-abo

abo-abo May 30, 2015

Owner

Thanks. I'll probably make counsel-find-file-ignore-regexp not hide anything by default in the future, so that it's less surprising.

Owner

abo-abo commented May 30, 2015

Thanks. I'll probably make counsel-find-file-ignore-regexp not hide anything by default in the future, so that it's less surprising.

@kaushalmodi

This comment has been minimized.

Show comment
Hide comment
@kaushalmodi

kaushalmodi May 30, 2015

Contributor

Thanks for implementing this; I hadn't yet got a chance to look into this.

Contributor

kaushalmodi commented May 30, 2015

Thanks for implementing this; I hadn't yet got a chance to look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment