[debbugs-tracker] bug#25656: closed (25.1; remember-notes-mode makes every temporary buffer created from it unkillable)

[GNU bug Tracking System]

Your message dated Sat, 25 Feb 2017 13:15:45 +0100
with message-id <address@hidden>
and subject line Re: bug#25656: [PATCH] 25.1; remember-notes-mode makes every 
temporary buffer created from it unkillable
has caused the debbugs.gnu.org bug report #25656,
regarding 25.1; remember-notes-mode makes every temporary buffer created from 
it unkillable
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
25656: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25656
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 25.1; remember-notes-mode makes every temporary buffer created from it unkillable
>
>
>
>
> Date: 
>
> Thu, 9 Feb 2017 00:12:32 +0100
>
>
>
>
> I wrote an Emacs package that takes an Org file, processes it with Org's
> element API and exports to a file.  Later I've noticed that if I use it
> on an Org buffer created with remember-notes-mode, it creates ~500
> temporary buffers that cannot be killed.  Bisection reveals that this is
> the fault of `remember-notes--kill-buffer-query` which is added locally
> to `kill-buffer-query-functions` and returns nil if
> `remember-notes-bury-on-kill` hasn't been customized.
>
> This raises an interesting question, should a temporary buffer as
> created by `with-temp-buffer` let-bind potentially troublesome hooks
> including, but not limited to `kill-buffer-query-functions`?  Another
> example coming to mind is `buffer-list-update-hook`, adding a function
> to it that scans the buffer list makes creating and killing temporary
> buffers an expensive action.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#25656: [PATCH] 25.1; remember-notes-mode makes every temporary buffer created from it unkillable
>
>
>
>
> Date: 
>
> Sat, 25 Feb 2017 13:15:45 +0100
>
>
>
>
> User-agent: 
>
> Mutt/1.7.2 (2016-11-26)
>
>
>
>
> Bug reason found in Org, resubmitting issue on their bug tracker.
>
>
> --- End Message ---