From: Bastien <bzg@altern.org>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: test failure
Date: Sat, 15 Dec 2012 09:18:58 +0100 [thread overview]
Message-ID: <8738z7iv7x.fsf@bzg.ath.cx> (raw)
In-Reply-To: <6097.1355553446@alphaville> (Nick Dokos's message of "Sat, 15 Dec 2012 01:37:26 -0500")
Hi Nick,
Nick Dokos <nicholas.dokos@hp.com> writes:
> ``make test'' fails on just-updated org:
>
> Org-mode version 7.9.2 (release_7.9.2-725-ge55681 @ /home/nick/elisp/org-mode/lisp/)
>
> with the following backtrace:
>
> ,----
> | Test test-org-src/blank-line-block backtrace:
Fixed, thanks.
> I thought Michael Brand's problem described in
>
> http://thread.gmane.org/gmane.emacs.orgmode/63523
>
> might have something to do with it, but wrapping a progn around the
> forms of the test did not make any difference.
>
> When I simulate the test by hand, I don't get the error, so this seems
> to be another of those errors that only surface when the test suite is
> run in batch mode.
Indeed. Actually, the test passed okay when trying to edit from line
2 (#+begin_src) so I changed that, since we really want to test whether
those source blocks can be edited at all.
> BTW, why in the above is the following a prog1, rather than a progn?
>
> (prog1 (goto-line 3) (org-edit-special) (insert "blah") (org-edit-sr
No reason, this is an error.
(prog1 ,@body (kill-buffer)) in org-test-with-temp-text-in-file had two
problems:
(1) (prog1 ,@body ...) is unpredictible
(2) (kill-buffer) within (with-temp-buffer ...) does not make sense.
I fixed this.
Thanks,
--
Bastien
next prev parent reply other threads:[~2012-12-15 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 6:37 test failure Nick Dokos
2012-12-15 8:18 ` Bastien [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-22 21:32 Test failure Nick Dokos
2014-07-22 21:50 ` Rasmus
2014-07-22 22:02 ` Nick Dokos
2014-07-23 8:10 ` Nicolas Goaziou
2018-02-14 19:19 Nick Dokos
2018-02-15 14:06 ` Nicolas Goaziou
2018-02-15 16:47 ` Nick Dokos
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=8738z7iv7x.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/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.