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
Make / behave like in ido #321
Comments
You can use this in your config: (define-key counsel-find-file-map "/" 'ivy-alt-done) This is too surprising to be on by default, in my opinion. In addition, you would lose the ability to quickly go to the root directory and to |
Yeah, in case of ido you can press slash twice and you'll get to root directory... |
I've just checked how / works in |
Ok, makes sense, I'll try adapting to what ivy does. :) |
* ivy.el (ivy--magic-file-slash): Extract from `ivy--exhibit'. (ivy--exhibit): Update. Update to the behavior: the slash ("/") will enter a directory even if its name isn't completely typed out if either: 1. It's the only candidate. 2. The candidate index isn't 0, i.e. "C-n" has been typed at least once. 3. The input isn't "/". The above rules still allow to keep the old behavior with "//" moving to root and "/ssh:" opening tramp. This is an experimental feature, please report if it breaks someone's workflow. Re #321.
Please test the new functionality, let me know if anything's weird. |
Works nicely! Except in one case: if I type |
By default, |
Ah right! Thanks a lot, works like a charm. |
So in ido, when you press
/
during find-file, it effectively "opens" the directory: you still can choose between directories, but if you start typing, currently chosen directory is assumed and after that you search inside of it.I wonder if it's possible to make
counsel-find-file
behave somewhat like that? I think I can live with just slash choosing a directory during finding files (but not in other completion contexts). Is there a way I can do that?The text was updated successfully, but these errors were encountered: