From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: michael_heerdegen@web.de, 60626-done@debbugs.gnu.org
Subject: bug#60626: 30.0.50; `buffer-live-p' sometimes returns t on killed buffers
Date: Wed, 11 Jan 2023 14:50:40 +0200 [thread overview]
Message-ID: <83fschmdzz.fsf@gnu.org> (raw)
In-Reply-To: <87ilhdfhwr.fsf@localhost> (message from Ihor Radchenko on Wed, 11 Jan 2023 11:08:04 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, 60626@debbugs.gnu.org
> Date: Wed, 11 Jan 2023 11:08:04 +0000
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Couldn't it be that the buffer had been live when the form had been
> > evaluated, but killed when the form had been printed (later)? The
> > information you posted does not necessarily imply that `buffer-live-p'
> > ever returned t when called with a killed buffer.
>
> This is likely true.
>
> The test looks like
>
> (unwind-protect
> (org-test-with-temp-text
> (format "#+begin_src octave :results file graphics :file %s
> sombrero;
> #+end_src"
> file)
> (org-babel-execute-src-block)
> (should (search-forward (format "[[file:%s]]" file) nil nil))
> (should (file-readable-p file))
> (should-not (buffer-live-p (get-buffer "*Org-Babel Error Output*"))))
> ;; clean-up
> (delete-file file)
> (when (get-buffer "*Org-Babel Error Output*")
> (kill-buffer "*Org-Babel Error Output*")))
>
> So, unwind fallback forms are likely executed.
>
> Thanks for the pointer!
>
> I think this bug report can then be closed.
Thanks, closing.
prev parent reply other threads:[~2023-01-11 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 12:44 bug#60626: 30.0.50; `buffer-live-p' sometimes returns t on killed buffers Ihor Radchenko
2023-01-07 13:42 ` Eli Zaretskii
2023-01-07 15:01 ` Ihor Radchenko
2023-01-09 10:21 ` Michael Heerdegen
2023-01-11 11:08 ` Ihor Radchenko
2023-01-11 12:50 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fschmdzz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60626-done@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.