From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: BUG org-babel-goto-named-src-block with indented block
Date: Fri, 07 Mar 2014 08:56:51 +0100 [thread overview]
Message-ID: <87txbae918.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87fvmvug5k.fsf@gmail.com
Hi Eric,
thanks for looking into this!
Eric Schulte <schulte.eric@gmail.com> writes:
> Hi Andreas,
>
> The problem is with your example. You can not put a header line between
> a #+name and it's source block.
>
If that is the case, then the manual should be fixed. As the manual
explicitly allows that: See the last example on here [fn:1].
Regards,
Andreas
Footnotes:
[fn:1]
http://orgmode.org/manual/Code-block-specific-header-arguments.html#Code-block-specific-header-arguments
> Best,
>
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> Hi all,
>>
>> there seems to be a bug, where org-babel-goto-named-src-block does not
>> find an indented source block.
>>
>> Here is an example:
>>
>> --8<---------------cut here---------------start------------->8---
>> * Test org-babel-goto-named-src-block
>>
>> Try org-babel-goto-named-src-block (C-c C-v g) with point on the
>> following line. (This works for me.)
>> #+call: block1(20)
>>
>>
>> Try org-babel-goto-named-src-block (C-c C-v g) with point on the
>> following line. (This does not work for me.)
>> #+call: block2(20)
>>
>>
>> ** The first block *without* indentation
>> #+name: block1
>> #+header: :var end=10
>> #+begin_src R
>> 1:end
>> #+end_src
>>
>>
>> ** The second block *with* indentation
>> #+name: block2
>> #+header: :var end=11
>> #+begin_src R
>> 2:end
>> #+end_src
>> --8<---------------cut here---------------end--------------->8---
>>
>>
>> Regards,
>> Andreas
>>
>>
next prev parent reply other threads:[~2014-03-07 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 9:32 BUG org-babel-goto-named-src-block with indented block Andreas Leha
2014-03-06 21:16 ` Eric Schulte
2014-03-07 7:56 ` Andreas Leha [this message]
2014-03-07 15:28 ` 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=87txbae918.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).