From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Multiple results blocks for the same source code
Date: Fri, 23 Sep 2011 15:51:00 -0600 [thread overview]
Message-ID: <871uv7exmj.fsf@gmail.com> (raw)
In-Reply-To: <80aa9vszmh.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 23 Sep 2011 23:44:06 +0200")
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Eric,
>
> Eric Schulte wrote:
>> I could not reproduce the error you describe, and your test case passes
>> for me. I have added your test case to testing/test-ob.el however so it
>> should protect from this error in the future.
>
> I can't reproduce it anymore right now. But the goal was to have a fuse
> against that for the future, yes.
>
>> You could try running the test suite in batch mode (which will not load
>> your configuration) and see if the test still fails for you. If not
>> then the problem is probably due to either something in your config.
>
> When I get back in a "broken" config such as the one described here, I'll do
> it.
>
>> Thanks for the test case! -- Eric
>>
>> ps. the only comments I have on the test itself are
>> 1. The initial placement of the point is described in the
>> documentation string for the `org-test-with-temp-text' function
>
> That's very clear, yes, but for the case where we don't have the string
> "<point>" in the initial text. Is point at the end of the string, then? I
> guess so.
>
Oh, I see I didn't address that in the function documentation. In the
case of no explicit "<point>" marker the point is placed at the
beginning of the inserted text (which also happens to be the very
beginning of the buffer).
>
> But my question was more about...
>
>>> (org-babel-execute-src-block) ;; second code block execution
>>> ;; where is point (supposed to be)?
>
> ... the position of point after `org-babel-execute-src-block'.
>
The point should remain wherever it was before executing the code block.
>
>> 2. In the future if you could share new test cases as patches to the
>> relevant test file (i.e., using git format-patch) that would be
>> ideal
>
> That was my intention, after receiving a "nihil obstat" from you, or some
> suggestions for changes.
>
> Anyway, next time, I'll directly send a properly formatted patch.
>
Wonderful. Thanks again -- Eric
>
> Thanks.
>
> Best regards,
> Seb
--
Eric Schulte
http://cs.unm.edu/~eschulte/
prev parent reply other threads:[~2011-09-23 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 12:11 [babel] Multiple results blocks for the same source code Sebastien Vauban
2011-09-23 15:53 ` Eric Schulte
2011-09-23 21:44 ` Sebastien Vauban
2011-09-23 21:51 ` Eric Schulte [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871uv7exmj.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).