From: Ihor Radchenko <yantar92@posteo.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 60626@debbugs.gnu.org
Subject: bug#60626: 30.0.50; `buffer-live-p' sometimes returns t on killed buffers
Date: Wed, 11 Jan 2023 11:08:04 +0000 [thread overview]
Message-ID: <87ilhdfhwr.fsf@localhost> (raw)
In-Reply-To: <87fsckqa99.fsf@web.de>
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> > Are you sure this is the right interpretation?
>>
>> I think so.
>
> 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.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-01-11 11:08 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 [this message]
2023-01-11 12:50 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilhdfhwr.fsf@localhost \
--to=yantar92@posteo.net \
--cc=60626@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).