emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Limit on length of babel block #+name: value?
Date: Thu, 16 May 2013 09:02:28 +0200	[thread overview]
Message-ID: <m24ne3v24t.fsf@vpn-client437.uio.no> (raw)
In-Reply-To: <CA+M2ft-kUgCeLqDT_R84P+4JdMeZSKMOu-jkp+h-=mBGBr0xeA@mail.gmail.com>


Hi,

I cannot reproduce this on 8.0.2, at least not with the info
provided. E.g., the following works fine:

#+name: improvement-treatment
#+begin_src R :results graphics :file test.png
  x <- 1:10
  y <- x^2
  plot(x, y)  
#+end_src

#+RESULTS: improvement-treatment
[[file:test.png]]

So does any variation with an arbitrarily long string as NAME.

Yours,
Christian

John Hendy writes:

> I was just completely baffled for about 5-10 straight minutes as to
> why my block was not producing a  results section with my generated
> graphics file from an R block.
>
> I kept double checking my header options one by one despite having
> simply copied/pasted/modified it from a previous working block. Turns
> out it appears that #+name has a character limit!
>
> This (on Org-mode version 8.0.2 (release_8.0.2-65-g1e32d7)), doesn't work:
>
> #+name: improvement-treatment
>
> It appears the name can be 20 characters long (the above is 21).
>
> Is this by design or something I accidentally uncovered? Forgive me if
> it's come up before or is documented. I did a couple searches but
> didn't see it.
>
>
> Thanks,
> John

  reply	other threads:[~2013-05-16  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  4:41 Limit on length of babel block #+name: value? John Hendy
2013-05-16  7:02 ` Christian Moe [this message]
2013-05-16 12:08 ` Eric Schulte
2013-05-17 21:00   ` John Hendy

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=m24ne3v24t.fsf@vpn-client437.uio.no \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.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).