From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Charles C. Berry" <cberry@tajo.ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel ':session ' bug?
Date: Mon, 22 Nov 2010 14:47:20 -0700 [thread overview]
Message-ID: <87r5eddo9j.fsf@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1011221323260.18205@tajo.ucsd.edu> (Charles C. Berry's message of "Mon, 22 Nov 2010 13:27:54 -0800")
Hi,
I get the following when calling (org-babel-get-src-block-info) on the
following code block
#+BEGIN_SRC R :session :results output
xyz
#+END_SRC
("R" "xyz
" ((:colname-names) (:rowname-names) (:result-params "output" "replace")
(:result-type . output) (:comments . "") (:shebang . "") (:cache . "no")
(:noweb . "no") (:tangle . "no") (:exports . "code") (:results . "output
replace") (:session) ...) "" nil 0)
note that I'm getting "(:session)" for the session header argument, which
is correct. Could you send me a copy of the offending code block?
Thanks -- Eric
"Charles C. Berry" <cberry@tajo.ucsd.edu> writes:
> On Mon, 22 Nov 2010, Eric Schulte wrote:
>
>> Hi Charles,
>>
>> I've just pushed up a change which should fix this issue.
>>
>
> Thanks.
>
> ':session' has the right number of colons, but is followed by '\ \ ',
> and no session was started.
>
> i.e.,
>
> M-x eval-expression RET (org-babel-get-src-block-info) RET
>
> gives:
>
> ("R" "xyz
> " ((:colname-names) (:rowname-names) (:result-params "output"
> "replace") (:result-type . output) (:comments . "") (:shebang . "")
> (:cache . "no") (:noweb . "no") (:tangle . "no") (:exports . "code")
> (:results . "output replace") (:session\ \ ) ...) "" nil 0)
>
>
> Chuck
>
>
>> Thanks for the report -- Eric
>>
>> "Charles C. Berry" <cberry@tajo.ucsd.edu> writes:
>>
>>> Correction in line below. CCB
>>>
>>> On Sat, 20 Nov 2010, Charles C. Berry wrote:
>>>
>>>> I think :session without passing a string used to start a session, but
>>>> now it does not. I think this is a bug. Details:
>>>>
>>>> Just did git pull and now with this:
>>>>
>>>> ,----
>>>> | #+BEGIN_SRC R :session :results output xyz
>>>> | #+END_SRC
>>>> | | #+results:
>>>> | | #+BEGIN_SRC R :session *R* :results output xyz
>>>> | #+END_SRC
>>>> `----
>>>>
>>>
>>> Oops! That should have been
>>>
>>> ,----
>>> | #+BEGIN_SRC R :session :results output | xyz
>>> | #+END_SRC
>>> |
>>> | #+results:
>>> |
>>> | #+BEGIN_SRC R :session *R* :results output | xyz
>>> | #+END_SRC
>>> `----
>>>>
>>>
>>>
>>>
>>>> If I put point after 'xyz' in the first block and do
>>>>
>>>> M-x eval-expression RET (org-babel-get-src-block-info) RET
>>>>
>>>> I get
>>>>
>>>> ("R" "xyz
>>>> " ((:colname-names) (:rowname-names) (:result-params "output"
>>>> "replace") (:result-type . output) (:comments . "") (:shebang . "")
>>>> (:cache . "no") (:noweb . "no") (:tangle . "no") (:exports . "code")
>>>> (:results . "output replace") (::session\ \ ) ...) "" nil 0)
>>>>
>>>> Note '(::session\ \ ).
>>>>
>>>> Whilst putting point in the second block leads to
>>>>
>>>> ("R" "xyz
>>>> " ((:colname-names) (:rowname-names) (:result-params "output"
>>>> "replace") (:result-type . output) (:comments . "") (:shebang . "")
>>>> (:cache . "no") (:noweb . "no") (:tangle . "no") (:exports . "code")
>>>> (:results . "output replace") (:session . "*R*") ...) "" nil 0)
>>>>
>>>>
>>>> Chuck
>>>>
>>>>
>>>> Charles C. Berry Dept of
>>>> Family/Preventive Medicine
>>>> cberry@tajo.ucsd.edu UC San Diego
>>>> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Emacs-orgmode mailing list
>>>> Please use `Reply All' to send replies to the list.
>>>> Emacs-orgmode@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>
>>>>
>>>
>>> Charles C. Berry Dept of Family/Preventive Medicine
>>> cberry@tajo.ucsd.edu UC San Diego
>>> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>>>
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
> Charles C. Berry Dept of Family/Preventive Medicine
> cberry@tajo.ucsd.edu UC San Diego
> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
next prev parent reply other threads:[~2010-11-22 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 0:51 Babel ':session ' bug? Charles C. Berry
2010-11-21 2:57 ` Charles C. Berry
2010-11-21 4:01 ` Nick Dokos
2010-11-21 20:09 ` Charles C. Berry
2010-11-22 13:44 ` Eric Schulte
2010-11-22 21:27 ` Charles C. Berry
2010-11-22 21:47 ` Eric Schulte [this message]
2010-11-23 0:27 ` Charles C. Berry
2010-11-23 16:40 ` Eric Schulte
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=87r5eddo9j.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=cberry@tajo.ucsd.edu \
--cc=emacs-orgmode@gnu.org \
/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).