-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Problem with grouping special buffers #25
Comments
Thanks, but what do you mean by "properly"? You've provided some changed code, but not described why it was changed, so it's not obvious why a change might be necessary. |
Sorry I wasn't clear. In the Screenshot in the README, the special buffers like Does that make sense now? Oh, and the changes in the code are at the beginning. In particular, in the |
To add to this discussion, as an issue I've noted seems related. For me, the default special buffers like Other special buffers such as Perhaps this behaviour is intentional as you could presume if one opens a In any case, thanks for this and your other packages and for your time. Hope this helps. |
Yes, those buffers inherit their |
ah I see thanks for explaining |
FWIW, I've faced the same issue, and this solved it for me: (setq ibuffer-vc-include-function (lambda (file) (not (file-directory-p file)))) |
Good to know thanks. |
For me some of the special buffers get listed under a VC project. I had to change
ibuffer-vc-root
like this to make it work properly:The text was updated successfully, but these errors were encountered: