-
Notifications
You must be signed in to change notification settings - Fork 62
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 Helpful buffers behave better #33
Comments
Thanks for reporting! Your first issue is a bug with elisp-refs. Would you mind opening an issue there? The second issue has been fixed in #35 :) |
I'll be more than happy to file a bug on If that is the expected behavior, how are you trying to not have the persistent buffer when calling |
OK, I may have misunderstood you. Suppose you look up a function
Option 1 would be a bug, whereas 2 is intended behaviour (but all behaviour is open for discussion if it doesn't fit your workflow). |
What happens is 1 |
@Wilfred this is actually one of the few things that's preventing me moving to |
OK, this should now be fixed. Let me know if not. |
Unfortunately, it's not. If you open emacs and call
I just updated emacs and helpful just to be sure, and the behavior is still the same. |
Sure, I understand creating multiple helpful buffers may not be to everyone's taste :). Would you mind creating a separate issue? |
Sure, just ask as a question. Some project have an adamant opinion about features. Just wanted to get the feel :) |
Are you sure you'd upgraded? I've added a test too, to confirm this bug is fixed. |
I have essentially two problems with Helpful:
Every time I check a definition using it, Helpful create some persistent buffers (at least 2), one for the searched function source file and one for the Helpful buffer itself.
I think Helpful should use
with-temp-buffer
instead offind-file
to visit the references (I found this article referencing this trade-off: http://ergoemacs.org/emacs/elisp_find-file_vs_with-temp-buffer.html), this way it wouldn't create a persistent buffer for the source file, and it would be faster.I can't configure Helpful to play nice with Shackle.
This point probably spills over the first one (and that is why I didn't open two issues). Helpful is using
switch-to-buffer
to show its content. Unfortunately, this function does not use thedisplay-buffer-alist
and is harder to manage the window/buffers it creates. Also, if Helpful would use a function likedisplay-buffer
instead, it would create a persistent buffer for itself.The text was updated successfully, but these errors were encountered: