-
Notifications
You must be signed in to change notification settings - Fork 12
Leaves open buffers behind #4
Comments
That seems reasonable. I will implement that soon. |
Awesome |
I've pushed some change that implements it to this branch. Although I'm doubtful about merging that to the master. Let me list some pros and cons of the change. Pros:
Cons:
As you stated for you the issue is managing the buffers. Maybe we can do something else about it? Name the buffer with |
Hmmm... I have the same request (/problem with lots of opened buffers) that @eethann has. If we could add the open buffers to a list and kill them on entering a buffer that would work for me or just supplying a manual "kill-peeped-buffers" command would probably solve this for me. |
@mijoharas I've added |
That sounds perfect. Thanks for implementing this. I'll give it a test but I'll likely be away from my computer for a while. I'll post once I've had a chance to look at this, but in the meantime, thanks. |
I'm also excited to check this out. I also wonder if there might be some sort of popwin integration possibility here... |
Is there any way to bind |
@priyadarshan I'm very glad you like it. (add-hook 'kill-emacs-hook #'peep-dired-kill-buffers-without-window) |
Thanks to That hook makes sense, but I would still be left with hundreds of buffers, popping up every now and then, while I navigate. Based on your advice, I was wondering if a pre-command hook would be possible, so that it would clean up any buffer right before any action? Something like this (very naive, and not working) code?
Thank you again for |
Please try the new version and set the correct variable to t to have this feature. (setq peep-dired-cleanup-eagerly t) Let me know how it works. |
[Sorry, posted with wrong account] Thank you, the new features are wonderful.
Right now I am testing on OS X: I launch Emacs, maximize frame, launch Dired. I can see that now Then, I quit Emacs, and add the following to This time, launching Dired and with |
In Sublime's preview, until you explicitly open a file, it is temporary, so the buffer is closed as soon as you move to the next preview. I think something like that would be good here. When I checked out 20 or 30 files with peep-dired I wound up with 30 or so buffers to manage. Can buffers opened just via peep (and not edited), close when the user goes to the next peep target?
The text was updated successfully, but these errors were encountered: