-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
feat: add buffer-close-others --skip-visible flag #5393
base: master
Are you sure you want to change the base?
Conversation
0dc79b3
to
d9aef1d
Compare
d9aef1d
to
2bb5319
Compare
Hello! I know it's been a while, but I'm still interested in this. I've rebased it and simplified things as much as possible. Please let me know if there's something problematic with this or if I'm missing an obvious alternative. If there just hasn't been time to get to it yet though, no worries! |
I'd still really like to have this... Sorry for the ping @kirawi, but is there anything I can do to move this forward? No worries if there just hasn't been time; admittedly the lack of comments by other users seems to indicate that this might not be something many people have run into, so I understand if it's not a priority. That being said, the changes are quite minimal so I don't think it introduces much extra maintenance burden. |
I think this could fit as a flag (#5828) on |
Ok, I'll keep an eye on #12527 then. |
2bb5319
to
809327b
Compare
Hi @the-mikedavis, I see that #12527 has been merged, so I've rebased this to make use of that. I've used |
This pull request adds the a boolean
--skip-visible
flag to thebuffer-close-others
andbuffer-close-others!
commands, which modifies their behaviour so that instead of closing all buffers except the currently focused one, any other buffers that are visible (i.e. in a split) are also left open.